Defining Recipes

Creating a Recipe

To define a recipe:

1. Click the Recipes icon in the application menu.

2. Click New Recipe.

3. For Recipe Name, enter a descriptive name to display in the Recipes Dashboard.

4. For Recipe Short Name, enter a short name to be used within the names of the generated tables used by this recipe.

5. For Recipe Group, optionally select the name of a recipe group.

   You can move this recipe later to another group or remove it from the group.

6. Click Submit.

The system then displays a page where you can add activities to the recipe.

Adding a Staging Activity

To add a staging activity to a recipe:

1. Display the recipe:

   1. Click the Recipes icon in the application menu.

   2. If the recipe is in a group, expand that group.

   3. Click the recipe name.

      The recipe is then displayed on the right side of the page.

2. Click Add Staging Activity.

3. For Name, enter a descriptive name to display within the recipe.

4. For Short Name, enter a short name to be used within the names of the generated tables used by this recipe.

   If you are going to use only one data source in this recipe, you could use a generic short name like Load, but if you are going to use multiple data sources, it may be helpful for the short names to indicate the data source.

5. For Data Source, select a data source.

6. Click Submit.

   The system then displays a page where you can edit the details of how to use this data source. This page lists all the schemas that belong to this data source, and each schema represents a data asset such as a table, an specific API call, or a specific format of file. You can load data from any number of these items, within this staging activity.

7. For each schema of interest, click the schema name in the left. The right side of the page then displays information about the schema, including (if applicable) information about the last time data was loaded from the associated data source.

8. Then specify how to use this data source. First, optionally select the following check boxes:

   • Stage on Target Table—Enables you to copy data to the table name of your choice. The table is generated for you. If you select this, you are prompted for a full table name.

   • Use SQLQuickload—Enables the recipe to perform a bulk load for this step. If you select this, also specify the following options:

     • Action On Dropped Records—Specifies the action to take when the bulk load encounters more than the specified number of dropped records. The Use SQLQuickload option drops a record if that record cannot be inserted, which can occur if the record is invalid in some way (such as not having a required field or having a value in an incorrect format). For Action On Dropped Records, select one of the following, to specify how the system should behave if the maximum number of dropped records is reached:

       • Abort—The recipe is automatically aborted, without any workflow intervention.

       • WorkflowStrict—The recipe is stopped and a workflow task is generated. The workflow task provides the options Abort and Retry.

       • Workflow—The recipe is stopped and a workflow task is generated. The workflow task provides the options Abort, Retry, and Ignore and Proceed.

       • Proceed—The recipe continues.

     • Max Dropped Records—Specifies the maximum number of dropped records before the specified action is triggered.

9. Choose the fields to load. To do so, either click the check box at the top of the column of check boxes or click the check box for each field of interest.

10. When you are temporarily done with this activity, click Save Draft. Or if you are done defining the activity, click Publish Activity.

    When you save the draft for the first time, the Staging Table field is updated to show the name of the staging table. The table is not generated until you publish the activity. If you want to add additional activities that use the staging table, it is necessary to publish the staging activity.

11. Click the Recipe link in the upper left to return to the recipe.

Adding a Transformation Activity

To add a transformation activity to a recipe:

1. Display the recipe.

2. Click Add Transformation Activity.

3. For Name, enter a descriptive name to display within the recipe.

4. For Target Source, select a schema; the list includes all schemas used in published staging activities within the same recipe.

   The system then displays the fields in the associated staging table, with options to specify transformations for any of the fields.

5. For each field where you want to apply a transformation, select the field name.

   The system then displays options on the right side of the page. Make edits described below and then click Apply.

   • Function Type—See Transformation Functions.

   • Overwrite—Select this if you want the new value to replace the old value. In this case, the system will not generate a new field in the staging table.

     Otherwise, leave Overwrite cleared and specify a new field name (see below).

   • Transformation Name—Specify a short name for this field transformation.

   • Result Field Name—Specify a name for the new field that will store this transformed value. In this case, the system will automatically add a field to the staging table; the actual name of the new field is %T_newname where newname is the name you specified.

   • Result Field Type—Select the type for the new result field.

   • Other options—See Transformation Functions.

6. When you are done editing this activity, click Save Draft. Or click Publish Activity so that the recipe will use it.

7. Click the Recipe link in the upper left to return to the recipe.

Transformation Functions

This section provides reference information on the transformation functions.

Adding a Validation Activity

A validation activity essentially defines a validation report; the report will flag any rows that failed the validation rules that you specify. For each validation rule, you specify whether to halt the recipe or to simply issue a warning. In the case of any validation error, the system generates a workflow task for the assigned role (specified when the recipe is scheduled).

To add a validation activity to a recipe:

1. Display the recipe.

2. Click Add Validation Activity.

3. For Name, enter a descriptive name to display within the recipe.

4. For Target Source, select the applicable data asset by choosing the schema that describes the asset. The list includes all schemas used in published staging activities within the same recipe.

   The system then displays the fields in the staging table, with options to specify validation rules for any of the fields. Note that any field can have at most one validation rule, within a given validation activity.

5. For each field where you want to apply a validation rule, select the field name.

   The system then displays options on the right side of the page. Make edits described below and then click Apply.

   • Function Type—See Validation Function Details.

   • Validation Name—Specify a short name for this field transformation.

   • Result Field Name—Specify a name for the report field that will store either 1 (if the field value passes the validation rule) or 0 (if it does not). It is useful for the name to indicate the field being examined, for example CheckItemCount.

   • Validation Failure—Specify how the system should respond when it encounters a field value that fails this specific rule. A Fatal failure halts the recipe. A Warning failure logs a warning. Both kinds of failures are visible in the Workflow Inbox.

   • Other options—See Validation Function Details.

6. When you are done editing this activity, click Save Draft. Or click Publish Activity so that the recipe will use it.

7. Click the Recipe link in the upper left to return to the recipe.

Validation Functions

This section provides reference information on the validation functions.

Adding a Reconciliation Activity

A reconciliation activity uses comparison data, which can be either data that you have loaded (and if needed transformed and validated) within the same recipe or data from another data source.

To add a reconciliation activity to a recipe:

1. Display the recipe.

2. Click Add Reconciliation Activity.

3. For Reconciliation Activity Name, enter a descriptive name to display within the recipe.

4. In the Primary Source section, specify the table that you ultimately want to promote and use downstream. To do so:

   1. For Data Source, select the location of the table that you want to use. Typically this is Staging Tables, because the most common use case is to reconcile data you have loaded within a recipe.

   2. For Tables, select the table.

5. In the Secondary Source section, specify the comparison table. To do so:

   1. For Data Source, select the location of the table that you want to use.

   2. For Tables, select the table.

6. Click Create Activity.

7. On the Key Map Definition tab, optionally click the Report Missing Records from Primary Source (Full Outer Join) check box. If you select this check box, the comparison will report whenever there are records in the primary source that are not found in the secondary source.

   Below this check box, the page initially displays a list of the fields in the primary source, with no information about how these are to be matched to fields in the secondary source.

8. The next step is to specify how to match a row in the primary source to a row in the secondary source. Typically, each source has a primary key (consisting of one or more fields), and the primary keys can be matched to each other; that is a record that has a specific primary key in the one source will be matched to the record that has the same primary key in the second source.

   If the sources both have a primary key, the easiest approach is to click Auto Match Primary Keys. When you do so, the Key Map area shows the primary key fields from the primary source on the left, with the primary key fields from the secondary (comparison) source on the right.

9. Now add fields to the comparison, as follows:

   1. Click a field name under Primary Source—this adds the field to the left column in Key Map area.

   2. Look for the field under Secondary Source that should be used for comparison for this field. Click that field name. The system adds this field to the right column in Key Map area.

      Or click Try to Match Selected Column. In this case, the system looks for an appropriately named field in the secondary source.

   To remove an item in the Key Map area, click its X button.

10. When you are done adding fields, click Create. The system then creates the key map for this reconciliation activity. If needed, you can return later and make edits.

11. Click Reconciliation.

    Now the page displays a table listing the fields from the two sources. Here you specify rules used to compare the values.

12. Briefly review the table for familiarity. The Primary Field column lists the fields from the primary source, and the Secondary Field column list the fields from the secondary source. This information is the same as in the key map. In addition, note that Data Type indicates the data types of the fields from the primary source (which is helpful in choosing a comparison function).

13. If many or most of the fields have the same name in the two tables, click Quick Match All to quickly create a set of reconciliation rules that you can then review and edit. With this option, the system automatically creates a rule for each pair of fields that have the same name (including case). Each automatically generated rule includes a unique rule name, a comparison function, a generated field name (to hold the comparison result), and (for numeric comparisons), an initial setting for Tolerance.

    Some fields may not yet have rules (which is OK).

14. Make edits (as needed) for each rule:

    1. In Function Type, choose a comparison function.

    2. For Rule Name, click the Edit icon and then type a unique rule name.

    3. For Result Field, click the Edit icon and then type a unique field name. The reconciliation activity will write a 1 or a 0 to this field, to indicate whether reconciliation was successful.

    4. For Tolerance (required for numeric comparison), click the Edit icon and then type the numeric tolerance.

       If the tolerance ends with a percent sign (%), then the system treats it as a percentage.

    5. If failing this reconciliation check should be a fatal error (halting the recipe), select the Fatal check box.

15. When you are done editing this activity, click Save Draft. Or click Publish Activity so that the recipe will use it.

16. Click the Recipe link in the upper left to return to the recipe.

Viewing the Staging Table Details

Before you can add a promotion activity, it is helpful to review the structure of the staging table or tables used by the recipe. In particular, make a note of the field names that you need to use. To see the definition of a staging table:

1. Display the recipe.

2. At the bottom of the page, see the list in Indices and Staging Table Details.

   This section shows one row for each data source used in the recipe.

3. Click the row for a given data source. The page then lists the generated staging tables associated with this data source.

4. Click a table name in this list. The right side of the page then provides information about the indices on the table, along with details about the fields in this table.

5. Optionally add indices as needed. To add an index, click New Index and then specify an index name and select one or more properties to be indexed.

Adding a Promotion Activity

A promotion activity copies data from the staging table to a final table or final tables, which can be within InterSystems TotalView For Asset Management or which can be in an external database. The activity consists of one or more promotion items, each of which uses custom SQL to delete, insert, or update records of an existing table.

Because the staging table name is generated, it is necessary to refer to the staging table name in an indirect way. Similarly, it is necessary to refer indirectly to the current run of the recipe. Accordingly, the product provides options that insert special tokens that you can use within your SQL; these tokens are automatically replaced when the recipe is run.

To add a promotion activity to a recipe:

1. Display the recipe.

2. Click Add Promotion Activity.

3. For Name, enter a descriptive name to display within the recipe.

4. For Run Order, select or type an integer, which controls the order in which the promotion activities are run, with respect to other promotion activities in the same recipe.

5. For Promotion Type, select one of the following:

   • Internal — Select this to load data into a table within this database (that is, the database native to InterSystems TotalView For Asset Management).

   • External — Select this to load data into a table in another database.

     If you select External, choose a database for Target Database.

6. Click Submit.

7. Click New Item.

8. Specify the following values:

   • Run Order—Specify the order in which this item should be executed, relative to other items in the same promotion activity. Select an integer.

   • Description—Enter an optional description of this item, as an aid to yourself and others reviewing this recipe later.

   • SQL Expression—Enter an SQL UPDATE, INSERT, or DELETE statement that affects the final table.

   The right side of the page provides samples to assist you in writing the query. When you are getting started, it is a good idea to review these and find a example that matches your scenario, to use as a starting place.

   Below SQL Expression, the page provides options that you can use to insert helpful tokens into the query. To insert a reference to a staging table:

   1. Place the cursor within SQL Expression at the position where you need the staging table reference.

   2. For Placeholders, select Staging Activity.

   3. For Staging Activities, select the short name of the staging activity to which the desired staging table belongs. (For example, mystage.)

   4. For Data Source Items, select the data schema to which the desired staging table belongs. (For example, samplecsv.)

   5. Click Add to SQL.

      This inserts the following string into your query:

      {mystage}.samplecsv
      

      

      This is a generic reference to the staging table for the samplecsv, generated and populated by the mystage staging activity within this recipe. When the recipe is run, this token is replaced with the actual name of this staging table.

   Similarly, when selecting records from the staging table (to insert or update the final table), you typically select only the records from the current run of the recipe. To modify your query to do this:

   1. If there is no WHERE clause yet, move the cursor to the end of SQL Expression and type WHERE followed by a space.

   2. For Placeholders, select BatchID.

   3. Click Add to SQL.

      This inserts the following string into your query:

      %BatchId={%BatchId}
      

      

      Note that %BatchId is the name of the field that stores the recipe run ID, and the token {%BatchId} is converted automatically into the ID of the current recipe run.

   You can also type these syntaxes directly into the query.

9. Click Save Activity Item.

10. If necessary, add other items to this promotion activity.

11. When you are done editing this activity, click Save Draft. Or click Publish Activity so that the recipe will use it.

12. Click the Recipe link in the upper left to return to the recipe.

Adding a Custom Activity

A recipe can include custom activities. For example, it may be necessary to have a custom activity that retrieves the data from a data source (for example, to place files within the file system). In such cases, two items are needed:

• Custom code in the form of a business host added within the interoperability engine that system uses internally. The business host must be a business operation or a business process that accepts as input a message of type SDS.DataLoader.CustomActivityRequest. Details are currently beyond the scope of the documentation.

• Configuration of the recipe to use that code at the applicable phase. To configure a recipe to use custom code:

  1. Display the recipe.

  2. Click Add Custom Activity. This displays a dialog box where you specify the details.

  3. For Name, enter the name of this activity.

  4. For Target Business Host, enter the configuration name of the business host.

  5. For When to Run, select Before Staging, Before Transformation, Before Validation, Before Reconciliation, Before Promotion, or After Promotion.

  6. For Enabled, select this check box if the activity should be enabled.

  7. Click Submit.

Step Mode

You can run a recipe in step mode, a mode that lets you use a subset of data—perhaps a very small subset—so that you can test the recipe quickly from end to end. In this mode, you specify the number of rows of data to load into the staging tables (and then to use in the subsequent processing).

To configure a recipe for step mode:

1. Display the recipe.

2. Click the Step Mode toggle.

3. In the box next to Step Mode, select or type the number of records to use.

A recipe remains in step mode until you change the Step Mode toggle back to off.

See Also

• Introduction to Recipes and Staging Tables

• Editing and Managing Recipes

• Managing Recipe Groups

• Scheduling and Running Tasks

• Viewing Run History (includes information on viewing dropped records, validation reports, and reconciliation reports)