Standard workflows

The TRIRIGA® integration object is delivered with several IBM® TRIRIGA workflows.

The following workflows are triggered from the integration object record or its supporting records.
triIntegration - Execute

This asynchronous workflow is triggered when the user selects the Execute action. This workflow is the primary workflow that supports the integration between IBM TRIRIGA and external systems. This workflow controls the record status that is displayed on the form. The Trigger Integration task is a Custom task that calls Integration:com.tririga.custom.integration.Integration and is the primary entry point for all integration object records. The information about the processes to run during the integration is defined in the integration object record and is passed to the Custom task through the record ID.

The standard workflow contains the following workflow tasks:
  • Start task
  • Modify Records task that is named Mark Status as Processing
  • Custom task that is named Trigger Integration
  • Switch task
    • If the Switch condition is true, run the following tasks:
      • Trigger Action task
      • Modify Records task that is named Mark Status as Ready
    • If the Switch condition is false, run the following tasks:
      • Modify Records task that is named Mark Status as Failed
  • End task
triIntegration - Generate SQL for Table
This synchronous workflow is triggered from the Database section action of an integration object record to generate the SQL for use with your staging tables.
triIntegration - Generate Test Data
This synchronous workflow is triggered from the Database section action of an integration object record to generate randomized test data in your staging tables. This test data can be used for functional testing or load testing.
triIntegration - HideShow Data Sections
This synchronous workflow is triggered from the initial loading of a new integration object record, and from various form elements such as a field-action OnChange workflow. This workflow shows and hides the form elements as needed to suit the integration that you are defining.
triIntegration - PreLoad
This synchronous workflow is called when a new integration object record is opened. In turn, this workflow calls the triIntegration – ResetMetaData and triIntegration – HideShow Data Sections workflows.
triIntegration - Reset MetaData
This synchronous workflow resets the form elements that are cleared. This workflow is called from the triIntegration – PreLoad workflow.
triIntegration – Resubmit
This asynchronous workflow is triggered when you resubmit a failed record from the instance failure (triIntegrationInstanceFailure) record.
triIntegration - Test DB Connection
This synchronous workflow is triggered from the Database section action of an integration object record to call select count(1) from [table_name] on the defined database. This call validates that the integration definition can communicate and run SQL commands on that database.
triIntegration - Test File Access
This synchronous workflow is triggered from the File section action of an integration object record to validate the create, retrieve, update, and delete permissions to the specified file location.
triDataSource - Reset Metadata
This asynchronous workflow resets the data source (triDataSource) record.
triDataSource - Test DB Connection
This synchronous workflow is triggered from the data source (triDataSource) record to call select count(1) from [table_name] on the defined database. This call validates that the data source definition can communicate and run SQL commands on that database.