Description

Click to open the Target Object Import page, to begin the process of importing a System Type, database table or Excel file as the basis for a Target design.

NOTE: When accessing the Target Object Import page from the Target Import icon, the Object selected on the Targets page is not carried over to the Target Object Import page. The Object where the Target design is to be imported must be selected on the Target Object Import page.

Click to load all fields found in the System Type for Target System Table Name into DSPTM.

NOTE: The Import Fields icon on the Targets page works the same as the Execute Import icon on the System Type Import page. The user has the option to import one Target at a time on the Targets page or import one or more Targets on the System Type Import page.

Click to sync the selected Target to Map if the STATUS field displays "Pending Design Changes.” If updates have been made in Target Design to Targets, Sources, Target fields, or lookup tables after they have been loaded into Map, this process syncs those updates with the data in Map.

Refer to Sync Map and Target Design for more information.

Displays the Object to which the Target is assigned. Objects can have multiple Targets assigned. Objects are added in Console and assigned to a Wave-Process Area to create a context.

A Target design is imported into the Object selected on the Target Object Import page.

 A user can also select an Object when adding the Target manually.

Click to open the Target Design Pending Changes page to view the change to the Target that must be synced with Map.

If the field is blank, the Target is in sync in Map and Target Design.

Displays the display order of the Target on the Targets page.

When a Wave-Process Area uses the Object, the Object priority cascades down to Target Design. Once the Target that belongs to the Object is synced with Map, the priority is also available in Map and displays on the Objects page. The Priority field in Transform is not updated. To change the order the Object is processed, the Priority field can be updated manually in Transform on the Targets page (Process Area Launch > Targets).

Displays the Target name, which is the table name with tt appended to the front.

Displays a brief description of the Target table.

Displays the status of the Target design.

Values are:

• In Design – A Target is in this Design Status when it has been added and while the Target is being configured. All functionality that can be performed on a Target is available and the Sync to Map icon is enabled.
• Design Finished – When a Target is in this status, the design is locked down, and no changes are allowed. A Target can only move to this status if it is in sync with Map. The Sync to Map icon is enabled. Auto Generation in Data Services and in SQL is allowed.
• Completed When a Target is in this status, the design is locked down, and no changes are allowed. A Target can only move to this status if it is in sync with Map. Auto-generation in Data Services and in SQL is not allowed. The Sync to Map icon is disabled.
• Inactive A Target in Inactive status will not be pushed to Map for mapping and is not available in Transform. When a Target in this status is selected, the Sync to Map icon is disabled.

Refer to Set a Target's Design Status  for more information.

This field is not currently used, but will be activated in a future release.

Displays how data in the Target table moves through the migration process.

• Natural - The Target follows the standard migration process. The Target fields and Source must be entered or imported into Target Design and synced to Map. Map must have Source tables selected and fields mapped. SQL AutoGen creates the Target table, Source table, and rules Objects.
• Utility – The Target is not mapped in Map and SQL AutoGen does not create any Objects. A user must still enter the Target into Target Design and the Target’s fields and Sources. The Target tables, Source Tables and rule Objects must be created manually.

NOTE: If the client’s installation is upgraded from a version that did not use Waves and Process Areas, all Targets are set to Utility

NOTE: A visibility can be set so that Utility fields can be mapped. Refer to Set Field Visibility for Mapping for more information.

NOTE: By default, the visibility of a Utility field is set to NONE, with the exception of zLegacy keys. zLegacy key fields will default to Source visibility.  Refer to Allow Mapping of Utility Columns for more information.

Displays the name of the table in the Target system, which is the name in the NAME field without the tt appended to the front.

Displays the System Type that was imported to create the Target design, or the System Type that was selected for the Target.

Refer to System Types  for more information.

Click to open the Target Sources page to add a Source to the Target.

Refer to Assign a Source to a Target  for more information.

Click to open the Target Fields page to add a field to the Target or activate or deactivate fields for mapping.

Refer to Add Fields to a Target for more information.

Click to open the Rules: Basic Rules page to view all basic rules assigned to active fields in the Target.  Basic rules are logic conditions to apply to the data in the associated field.

NOTE: If the field is a zLegacy field, this icon is disabled.

Refer to Add a Basic Rule  for more information.

Click to open the Targetspage in Map to view all field mappings for the selected Target.

Click to open the Target Contacts page to add Developers to the Target. Developers approve mappings submitted for this Source on the Mapping Approval page (Quick Panel > Mapping Approval).

Refer to Add Developers and Business Contacts to a Target or Source  and  Approve or Reject Field Mappings for more information.

Click to open the Target Contacts page to assign Business Contacts to the selected Target. Business Contacts are used for reporting purposes and automatically receive public reports for the Target–Source in Transform.

Refer to Add Developers and Business Contacts to a Target or Source for more information.

Click to open a dashboard that displays a summary of estimated records and completed records in Construct for the Target.

Refer to View the Dashboard in Construct  for more information.

Click to open the Target Dependencies page to set a parent dependency for the selected Target table.

Refer to Set Target Dependencies for more information.

Description

Basic

Displays the Object to which the Target is assigned. Objects can have multiple Targets assigned. Objects are added in Console and assigned to a Wave-Process Area to create a context.

A Target design is imported into the Object selected on the Target Object Import page (Design > Target Import).  

A user can also select an Object when adding the Target manually.

Displays the display order of the Target on the Targets page.

When a Wave-Process Area uses the Object, the Object priority cascades down to Target Design. Once the Target that belongs to the Object is synced with Map, the priority is also available in Map and displays on the Objects page (Process Area Launch > Objects). The Priority field in Transform is not updated. To change the order the Object is processed, the Priority field can be updated manually in Transform on the Targets page (Process Area Launch > Targets).

Displays the Target name, which is the table name with tt appended to the front.

Displays a brief description of the Target table.

Displays how fields in the Target are used.

Values are:

• Natural – The fields exist in the Target system. The system adds a “z” to the front of the field name used in the Source table.
• Utility – The fields do not exist in the Target system, but can be used to register rules and reports to in Transform. Fields of this type should be captured in Target Design. A utility field is added to the Target table to be used by the AutoGen process. Utility fields will be appended to BOTH the Target and Source table as is. No “z” field will be appended.

NOTE: A visibility can be set so that Utility fields can be mapped. Refer to Set Visibility for Mapping of Target and Source Fields  for more information.

NOTE: By default, the visibility of a Utility field is set to NONE, with the exception of zLegacy keys. zLegacy key fields will default to Source visibility. Refer to Set Visibility for Appended Utility Columns for more information.

Displays the name of the table in the Target system, which is the name in the NAME field without the tt appended to the front.

Displays the System Type that was imported to create the Target design, or the System Type that was selected for the Target.

Refer to Import a Target Design from a System Type and System Types  for more information.

Details

Displays a user-entered comment about the Target.

This field is for documentation purposes only.

Displays instructions about how to use the Target in mapping or other functions.

This field is for documentation purposes only.

Click Upload a file to upload documentation related to the Target field. If documentation has been uploaded, the Download a File icon is active, and the file can be downloaded. The Download a File icon is disabled if no documentation has been uploaded for the Target.

Dependencies

Click to open the Target Dependency (Parents) page to view a list of Target tables that have a parent dependency with the selected Target (i.e., the selected Target is a child of the Targets that display on this page).

The number on the icon represents the number of Targets that have a parent dependency with the selected Target.

Refer to Set Target Dependencies for more information.

Click to open the Target Dependency (Children) page to view a list of Target tables that have a child dependency with the selected Target (i.e., the selected Target is a parent of the Targets that display on this page).

The number on the icon represents the number of Targets that have a child dependency with the selected Target.

Refer to Set Target Dependencies for more information.

Field Formats

Displays the format to use for date fields when writing validation rules in Data Services AutoGen.

The Date Format works in conjunction with the Field Format field on the Target Fields page's Vertical View, where the type of format for data fields is stored.

For example, the Date Format for a Target is set in this field at YYYYDDMM.

A  user selects Date in the Field Format list box on the Target Fields Vertical View for the field Received By Date.

The data in the Received By Date field passes through the migration process with a data type of NVARCHAR. When validation rules are written for this field in Date Services AutoGen, the format of the data in the Received By Date field is formatted as YYYYDDMM so that it can be loaded into the Target with no errors.

Refer to Set the Date, Time, and Decimal Formats for more information.

Displays the format to use for time fields when writing validation rules in Data Services AutoGen.

The Time Format works in conjunction with the Field Format field on the Target Fields page's Vertical View, where the type of format for data fields is stored.

For example, the Time Format for a Target is set in this field as HH:MM:SS.

A  user selects Time in the Field Format list box on the Target Fields Vertical View for the field Received By Time.

The data in the Received By Time field passes through the migration process with a data type of NVARCHAR. When validation rules are written for this field in Date Services AutoGen, the format of the Received By Time field is set as HH:MM:SS so that it can be loaded into the Target with no errors.

Refer to Set the Field Formats for Date, Time, and Decimal For Use in Data Services AutoGen for more information.

Displays the separator format (either "," or ".") to use for decimal fields when writing validation rules in Data Services AutoGen.

The Decimal Format works in conjunction with the Field Format on the Target Fields page's Vertical View, where the type of format for data fields is stored.  

Refer to Set the Field Formats for Date, Time, and Decimal For Use in Data Services AutoGen for more information.

Advanced

Click to open the Target Table Join page to view or enter information about joins in Target tables for the selected Target. This information is for documentation purposes only.