factory-probe-business-applications
Service icon

Factory Probe - Business Applications

Stable version 1.0.0 (Compatible with OutSystems 11)
Uploaded
 on 7 Nov (22 hours ago)
 by 
0.0
 (0 ratings)
factory-probe-business-applications

Factory Probe - Business Applications

Documentation
1.0.0

Overview


The Factory Business Applications Probe is designed to automatically discover and maintain the relationship between Applications and their corresponding Business Applications within your OutSystems Factory.

It does this through a Timer that executes a SQL synchronization routine on a regular basis, ensuring that two governance tables are always up to date:

  • BUSINESSAPPLICATION — list of Business Applications

  • BUSINESSAPPLICATION_APPLICATION — mapping between Applications and Business Applications


Timer Configuration


By default, the Timer runs once per day to keep the data synchronized.

This schedule can be easily adjusted in Service Center:

  1. Go to the FactoryProbe_BusinessApps_Col module.

  2. Open the Timers tab.

  3. Locate the timer.

  4. Update the Schedule as needed (e.g., hourly, weekly).

When triggered, the Timer executes the SQL MERGE queries that:

  • Extract Business Application names from Application descriptions;

  • Insert, update, or delete entries in the tables accordingly.


Application Tagging


For the probe to detect and associate Applications correctly, each application must include a Business Application tag in its Description field, following this exact format:

@BusinessApp(Name=YourBusinessAppName)

Example:

⚠️ Make sure there are no typos or extra spaces — the tag is parsed exactly as written.

Only active applications (Is_Active = 1) are considered.


Data Model


The component works with two main tables:

Table

Description

FCT_BUSINESSAPPLICATION

Contains the list of Business Applications detected in the factory.

FCT_BUSINESSAPPLICATION_APPLICATION

Maps each Application to its corresponding Business Application.


These tables can be used for:

  • Governance dashboards;

  • Reporting on Application portfolios;

  • Tracking AO consumption per Business Application;

  • Impact and dependency analysis.


Typical Use Cases


  • Visualize how many Applications belong to each Business Application.

  • Measure total AOs or ownership per Business Application.

  • Support governance or audit reports.

  • Provide insights for portfolio management and refactoring decisions.