Send Workflow data to Data Fabric
Overview
The Send Workflow data to Data Fabric capability enables automatic transfer of workflow data (including finished workflow instances, workflow steps, and their relationships) from ION Workflow to Data Fabric. Centralizing this data supports robust analysis, long-term storage, and integration with other enterprise systems.
Why and where should it be used?
Use this capability when you require historical workflow analysis, compliance support, or consolidated reporting across platforms. Centralizing workflow data in Data Fabric streamlines business analytics and operational oversight.
When is it appropriate?
Activate this capability to:
- Archive workflow instance data for auditing or compliance.
- Analyze business processes over time by using Data Fabric tools.
- Integrate workflow data with live data or other datasets for comprehensive insights.
Who should use it?
System administrators, business analysts, and IT professionals who manage data and reporting for ION and Data Fabric should configure and use this capability.
How is it implemented?
Configure the workflow to send its data to Data Fabric during workflow setup. You can schedule the transfer or trigger it when the workflow completes.
This setting operates independently from the live data switch, which allows targeted archiving and analysis.
See ION data archiving.
This data is sent to Data Fabric:
- Finished workflow instances (statuses: Completed, Canceled, Failed)
- Workflow steps (as defined in the workflow definition)
- Workflow step relationships
Workflow instance events data
This table shows the properties associated with workflow instance events:
| Property | Description |
|---|---|
| ID | An integer that uniquely identifies the workflow instance. |
| Status | The final status of the workflow. Values: Completed, Canceled, Failed. |
| Name | The workflow name. |
| MajorVersion | An integer that represents the workflow major version. |
| MinorVersion | An integer that represents the workflow minor version. |
| InstanceName | The name of the instance. |
| Reason | The reason for the result. |
| Start | A UTC date-time string that indicates when the workflow started. |
| End | A UTC date-time string that indicates when the workflow ended. |
Workflow step events data
This table shows the properties associated with workflow step events:
| Property | Description |
|---|---|
| ID | An integer that uniquely identifies the step event. |
| WorkflowId | An integer that identifies the workflow to which this step belongs. |
| Name | The step name. |
| Type | The step type. Examples: Assignment, ConditionalApproval, Start, End, Scripting. |
| ExecutionCounter | An integer that tracks how many times this step has executed. |
| Status | The status of the last execution of the step. Values: Skipped, Initial, Completed, Canceled, Failed. |
| Start | A UTC date-time string that indicates when the last execution of the step began. |
| End | A UTC date-time string that indicates when the last execution of the step ended. |
Workflow step relation events data
This table shows the properties associated with workflow step relation events:
| Property | Description |
|---|---|
| ID | An integer that uniquely identifies the relation event. |
| WorkflowId | An integer that identifies the workflow to which this relation applies. |
| Next | An integer that identifies the next step in the workflow sequence. |
| Annotation | An optional annotation for the relation. Values: True, False, LoopBack. |