Model Run and Run History
Overview
In this article, you can find information on how to manage the state model run schedule and how to access and interpret run history in Apporetum. The model run controls when and how often the published state model executes against your identity data, while run history provides a complete audit trail of all past executions.
Model Run
Run Status
The model run has two statuses that control whether the state model executes automatically.
Active — the state model runs automatically according to the configured schedule.
Paused — automatic execution is suspended. The model will not run until the status is returned to Active.
To change the status, select Pause to set the run to Inactive, or select Enable to set it to Active.
Scheduling the Model Run
- Select Schedule next to the run status.
- Select a schedule from the Presets options.
- Select Save.
The schedule determines how frequently Apporetum executes the state model against your identity data. Scheduling the model run removes the need to manually trigger executions and ensures your identity landscape remains up to date.
Latest Successful Run
The Latest Successful Run panel sits next to Model Run and displays the date and time of the most recent successful execution. Each state is shown with a count of the accounts currently in that state.
Apporetum uses arrow indicators to show movement between runs.
| Indicator | Meaning |
|---|---|
| Green arrow | The number of accounts in this state has increased since the previous run. |
| Red arrow | The number of accounts in this state has decreased since the previous run. |
Select View Details to navigate to the full Model Execution Results for that run.
Viewing Execution Results
When you open a model execution result, Apporetum presents four tabs.
Overview — shows the account count for each state with increase and decrease indicators.
Audit — shows all actions performed during the model run, providing a complete record of what changed and why.
States — shows detail for each state in the run. Selecting Actions from a state shows the transitions moving accounts to and from that state, including self-connected transitions.
Transitions — lists all transitions, showing which state each transition moves accounts from and to. Select the arrow on the right-hand side of a transition to view its configured Triggers and Actions. The enabled or disabled status of each transition is shown in the upper right corner of the detail view.
Run History
Run history provides your organisation with a documented record of all state model executions, supporting audit and compliance requirements by demonstrating that identity governance processes are operating according to policy.
Accessing Run History
There are two ways to access run history in Apporetum.
Via the navigation menu — select Identity, then Life Cycle Management, then Run History.
Via the state model — select Identity, then Life Cycle Management, then State Model, then select View Runs.
Model Run History View
The run history view provides three features for reviewing past executions.
Latest Run — displays the most recent execution at the top of the page. Select View Result to open the full execution result detail.
Run history calendar — displays a calendar view with indicators on dates where the state model has run. Select a date to view a list of all runs that occurred on that day.
Run history list — displays the list of runs for the selected date. Select a run from the list to open the full Model Execution Results for that execution.
Viewing a Run Result
To view the detail of any past run result, select View More from the latest run panel or select View Results from the run history list.
Apporetum opens the Model Execution Results view, which provides the same Overview, Audit, States, and Transitions tabs described in the Viewing Execution Results section above.
Use the Audit tab when investigating an unexpected account state change. It provides a chronological record of every action performed during the run, including which accounts were affected and what triggered each action.