Installation

This component is to be installed in Development environments only. It reads module history and publishes data to a scoring service; running it against Production or QA is not the intended use and is not supported.

1. Install the component from the Forge into the Development environment you want to benchmark. 

2. The SyncImpactOnPublish timer runs automatically and starts the initial analysis of your factory's history. This first run can take longer than regular runs, depending on how much history the platform retains.

3. Once the first run completes, open the Dashboard. Heatmaps, trends and metrics are populated from day one, up to a year back, subject to what the platform still retains.

From that point on, the SyncImpactDailySync timer processes incremental changes on its regular schedule. New publishes are scored within the next cycle.

Where it runs

Impact Benchmark can be installed on any OutSystems O11 Development environment, whether on a Personal Environment or under an enterprise subscription. Peer comparisons keep Personal Environments separate from factories running under enterprise subscriptions, so you are always compared against factories of similar nature.

Accessing the Dashboard

The Dashboard uses Service Center as its identity provider. Anyone with Service Center access on that environment can log into the Dashboard with the same credentials. No user provisioning is required.

Connectivity requirements

Impact Benchmark relies on a scoring service for percentile comparisons, pattern analysis, dead code breakdown, and trend data. The Development environment must be able to reach benchmark.afonsometello.com on port 443.

If the environment is behind a corporate proxy, configure it in Service Center under Administration, Configuration, Proxy, and allowlist benchmark.afonsometello.com.

When the service is not reachable, the Dashboard shows an Offline badge in the header and a yellow banner above the content with guidance on how to connect. The parts of the Dashboard that do not require the service continue to work.

Troubleshooting

The Dashboard shows no data after installation. The SyncImpactOnPublish timer runs the initial analysis when the module is published. If the Dashboard is still empty, verify that the module was published successfully. In Service Center, locate the SyncImpactOnPublish timer and confirm it has a recent Last Run with Status OK. For factories with deep history, the first run can take several minutes.

Dashboard shows "Offline" or "service not reachable". The Development environment is not reaching the scoring service. Check that benchmark.afonsometello.com is reachable on port 443. If the environment is behind a corporate proxy, configure it in Service Center under Administration, Configuration, Proxy, and allowlist the domain. Also verify that the SyncImpactDailySync timer shows Status OK with a recent Last Run. If it never ran, trigger it manually.

Percentile comparisons are missing. Percentiles require the scoring service to have enough peer data for the current window. If the factory has just come online, peer percentiles may appear after the next service refresh cycle.

Historical data is shallow. The depth of the initial analysis depends on what OutSystems still retains in the version history. Factories with aggressive cleanup policies will have shorter baselines. This is expected and does not affect the quality of ongoing measurement.

Support

For questions, feedback or issues, contact Afonso Metello.