When designing a workflow, actions can be included (using the same tools) and be taken on the data showing up in reports. These actions are attached to the data concept – not the data view – meaning wherever the data shows up, the action is available. These actions are also secured so only the authorized user can trigger the action. For instance, if I have a chart that shows tickets that are late over time, I can drill into the data under the chart to see the actual tickets and might take action to re-assign that ticket.
The rule engine can be used to summarize data and provide information on areas of the processing that needs attention. This can be as simple as setting up some thresholds for different metrics or as the rule engine digging into the data to suggest reasons that the data is not exactly what is expected. These values can be added as ‘Tiles’ to dashboards or proactively communicated to users and/or managers.
Business Models are flows that only contain the key business events that are triggered by workflow execution or other events in the system. Unlike actual flow execution that might have a high noise to signal ratio from a business perspective, Business Models show the key indicators for overall business management. At runtime, these business models can be used to view where one flow is in its execution or a summary of a number of flows.