Defining a Data Package - EnterWorks - EnterWorks Process Exchange (EPX) - Precisely EnterWorks - 10.5

EnterWorks Classic Administration Guide

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks > EnterWorks
Precisely EnterWorks
Precisely EnterWorks > EnterWorks Process Exchange (EPX)
Version
10.5
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Classic Administration Guide
Topic type
Administration
Configuration
First publish date
2007

The following steps are used to set up a data package to control the promotion of related records. This functionality is only available to System Administrators.

  1. Open the Feature bar, open Content, open Scheduled Activities, and open the Package Promotions repository.

  1. Click the Create a New Record (+) icon. The detail editor for the Package Promotions repository will appear:

  1. On the Summary tab, edit the configuration attributes.

    1. Package Name: Enter the name of the package to which this record.

NOTE: All package level records for the same package must have the exact same Package Name value.

  1. Repository Name: Enter the name of the repository to which this level applies. Each repository can only be listed once for a package.

  2. Package Level: The top-level repository is level 0. The repositories that link to the top level must be defined as level 1. Repositories that link to the Level 1 repositories must be defined as level 2 and so on. Levels must be consecutive (for example, if there is a level 3, there must be a level 2, 1, and 0).

  3. Status:

  4. ID:

  1. On the Details tab, edit the configuration attributes:

    1. If this is not the top level, in the Parent Link Relationship Name field, enter the name of the link relationship that connects this repository to its parent. For example, if Level 0 is Product and Level 1 is Item, and the link relationship “Product to Item Staging” defines the relationship between Product and Item, set the field to “Product to Item Staging” (without the quotes).

    2. If records in this repository should only be promoted if the entire package containing them gets promoted, set Package Dependent to “Yes”, otherwise set it to “No”.

    3. In the Promotion Configuration Name field, enter the name of the promotion configuration for this repository. This name should be copied from the sharedConfig.properties file.

    4. If warning validation errors are to be ignored, set the Promote Warnings attribute to Yes.

    5. If attributes other than (or in addition to) the primary key attribute(s) should be used to identify a repository record in the Package Promotion reports, enter the names of the attributes in the Display Attributes field (one per line).

    6. If values from the Package Promotion work item should be used to update attributes in this repository, add the names of the work item properties and the repository attributes to the Promotion Attributes table. Whenever a package promotion is initiated, the values from the work item will be set in each package record from this repository before the promotion processing (validation and promotion) begins.

    7. If a package record from this repository should be flagged with an error when the package promotion fails, set the Update Package Errors attribute to Yes.

    8. Package Promotion Parent:

  2. On either the Summary or the Details tab, click Save.

Repeat the above steps to define all levels for a package.