Template (ISA External Request Scenario) H

Description

Displays the rule name (e.g., NoRegion).

Displays the name of the ISA rule the scenario applies to (e.g., Customers – Region) listed on the Report Data Viewer page in ISA.

Displays the format used for the request description for a request created from this external request scenario. The DESCRIPTION field on the Request page defaults to Request from ISA - #Date# where the Date is the date a user clicked the Create Compose Request button on the Report Data Viewer page in the ISA.

NOTE: A value preceded and followed by # is a dynamic substitution value for replacement at run time  A user can add these variables to the description.

• #ISAProjectID# - ISAProjectID (ISA Project ID)
• #ISARuleBindingID# - ISARuleBindingID (ISA Rule Binding ID)
• #ISARuleID# - ISARuleID (ISA Rule ID)
• #RuleID# - ExternalRequestAlias (Rule ID)
• #RuleBindingID# - Scenario (Rule Binding ID)
• #RequestConnectionID# - RequestConnectionID (RequestConnectionID)

Click to open the Template (External Request Scenarios Connections) page to set a connection to a target system for each process template.

Description

Definition

Displays the name of the project that contains the IS rule that, when run, generates a report. The data on this report can be used as the basis for a request.

Displays the unique identifier for the ISA view on which the report is based.

Displays the ISA Rule Binding Description once the scenario has been saved.

Displays the rule name (e.g., NoRegion).

Displays the name of the ISA rule the scenario applies to (e.g., Customers – Region) listed on the Report Data Viewer page in ISA.

Click to open the Template (External Request Scenarios Connections) page to set a connection to a target system for each process template

Advanced

Displays the name of the data source where the staging table will be created and stored. The default dspCompose_Data data source is the recommended selection.

Displays the name of the table that will be used to import Information Steward report data.

The name is automatically generated by dspCompose™ in the format st [Template Name] [Scenario]_ISAStaging.

NOTE: Data is moved from the ISA report to this staging table where custom rules can then be run against the data before the data is moved to the Data Entry table of a request.

Click to create the staging table in the data source identified in the Staging Data Source ID field with the name in the Staging Table Name field.

NOTE: If the template has not been generated, this icon is disabled.

Click to open the Template (External Request Scenario Column) page to map columns from the staging table to columns in the template.

NOTE: If the template has not been generated, this icon is disabled.

NOTE: The count on this icon represents the number of columns that have been mapped from the Information Steward report to the staging table.

Click to open the Template (Event Rule) page to add, edit and delete rules. Refer to Create Custom Rules for Information Steward-initiated Requests for more information.

NOTE: The count on this icon represents the number of rules that have been added to the external request scenario. These rules run on data in the staging table before it is moved to the data entry table.

Click to clear the staging area, allowing the staging table to be rebuilt if the ISA report must be rerun after the scenario was saved.