ISA

Information Steward Accelerator (ISA) Overview

ISA extracts data that failed Information Steward (IS) rules, then distributes the data to groups of users. These user groups, called Project Distributions, can receive the data as an Excel file (.xlsx) attached to an email or can view a summary of the rule’s data.

A user is added to a Project Distribution through:

  • Assignment to a security role containing the Project Distribution
  • Assignment of a Security Definition Key Value of the Project Distribution to the user.

Refer to Set Security for more information.

Project Distributions, along with users, have rules. These rules have associated Quality Dimensions by which rules are grouped. Filters can be applied at the user or project distribution level to filter the data sets sent to specific user groups.

Once rules are processed in IS, ISA sends workflow emails to users who are configured to receive them. These emails notify the user of failed records. The email can contain an attachment in .xlsx format with all of the failed records, or can contain a summary table with failed record counts for each rule. The email also contains a link to the associated IS scorecard and back to the Stewardship Tier workflow.

A dashboard is also available in the ISA to visualize the project distribution and user level statistics not available in the IS scorecards. Refer to View the ISA Dashboard for more information.

Workflow Frequency

The ISA depends on data that fails IS rules, written to a local database to generate Excel files with reports of failed data. The ISA distributes reports through workflow emails. The frequency that rules are run and the frequency that failed data is updated in the database is set in IS.

Service pages in the ISA can be updated to increase the number of times a day that the ISA checks for updated data sent from IS to the local database. Updating this frequency in the ISA does not control how frequently rules are run in IS.

Setup and Configuration for ISA

Before working with ISA, configure settings and create objects in IS and Central Management Console (CMC).

NOTE: All of these steps must be performed for the ISA to work.

Refer to CMC documentation for information about working in the Central Management Console.

Use CMC to:

Use Information Steward to:

  • Create tables for connections
  • Import tables
  • Create views

NOTE: If the name of the view that is bound to the rule contains a period, columns will not download after the rule runs. Remove periods from view names in IS.

Use the System Administration component of the Stewardship Tier to:

  1. Add Users
  2. Create an ISA Security Role
  3. Assign a Key Value of Target -dgRepository_IS to the Security Role
  4. Add WebApp groups to the security role
  5. Add Users to the Security Role
  6. Set the Connection information for the ISSAP data source

Use the Common component of the Stewardship Tier to:

  1. Add an SAP Data Services Definition

Use the Collect component of the Stewardship Tier to:

  1. Set Data Services ID for the dgRepository_IS target.

    In Collect, select Targets > Vertical view for dgRepository_IS > Edit > select an option in the Data Services ID list box.

  2. Set Data Services Connections
  3. Build and Refresh tables
  4. Refresh Tables if Projects, Rules, or Rule Bindings are Updated

Use the ISA to:

  1. Activate Users in a Project Distribution