Use this template to define a process to group steps. Each step must be in only one process. The process is related to subject areas, and each partner application must have at least one subject area that any processes resides in. The template defines the relationship between the subject area and the partner application's security group as well as between the process and the subject area.
This template is required if the partner application is defining steps to the Data Warehouse Center.
If you create a new process object, the value that you provide for the *ProcessName token must be unique to all processes defined in the warehouse control database.
Table 20 provides information about each token in the
template.
| This template contains only relationship parameters. | ||
| Token | Description | Allowed values |
|---|---|---|
| Entity parameters | ||
| *ProcessName | The unique name of the process. | A text string, up to 80 bytes in length. |
| *ProcessDescription | The description that is associated with the process. | A text string, up to 254 bytes in length. |
| *ProcessNotes | The long description that is associated with the process. | A text string, up to 32,700 bytes in length. |
| *ProcessContact | The name of a person or group to contact for questions or concerns about this step. | A text string. |
| *ProcessType | The processing options if there was no source data. | One of the following values:
|
| Relationship parameters | ||
| *SubjectArea | The name of a subject area that is to contain this process and thesteps being created or being added to this process. | A text string, up to 80 bytes in length. |
| *SecurityGroup | The security group that is to contain all the objects that you are
importing.
This token is required, and you must specify the default security group. | ISV_DEFAULTSECURITYGROUP for the default security group. |
| *CurrentCheckPointID | An index, starting with 0, that increases each time it is substituted in
a token.
This token is required. | A numeric value. |
Table 21 provides example values for each token to illustrate the
kind of metadata that you might provide for each token.
Table 21. Example values for Process.tag tokens
| Token | Example value |
|---|---|
| *ProcessName | Marketing process |
| *ProcessDescription | A collection of steps that is used by the marketing organization |
| *ProcessNotes | Steps that create the star schema that is used by the marketing organization |
| *ProcessContact | Marketing |
| *ProcessType | ISV_ProcessType_2 |
| *SubjectArea | Group of processes generated for this partner application |
| *SecurityGroup | ISV_DEFAULTSECURITYGROUP |
| *CurrentCheckPointID | 9 |