tc_workflow_postprocess

Executes a specific action on a specific task in the workflow process from which the related background process was initiated. For example, you can use this utility to evoke the complete action on the Review task in the workflow process from which a background tessellation process was initiated. This utility then prompts the workflow task to either execute an action (defined with the -action argument) or submit a decision (defined with the -signoff argument). This can be useful when the conditions to execute the action are not met until the background process completes. In these cases, the user has typically moved on to other tasks or ended the session. Use the -member_group and -member_role arguments to define the group/role used for the background process. This is useful at sites where users have multiple groups/roles and the user has changed to a group/role that is different from his default login group/role while initiating the background process. These arguments allow the tc_workflow_postprocess utility to assume the same group/role the user was using at the time the workflow process was initiated. It is expected that the same group/role is required to execute any action in that workflow process on behalf of the user. Syntax tc_workflow_postprocess [-u=user-id {-p=password | -pf=password-file} -g=group-name] -status_xfer_type=transfer-type [itemid=item-id | -key=[keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN]] -revid=rev-id -dsname=dataset-name -dataset_tag=dataset-tag -task_tag=tag [-member_group=group] [-member_role=role] [-action=action-name] [-trigger_comment=comment] [-signoff=decision] [-signoff_comment=comment] [-h] Arguments -u Specifies the user ID. This is a user with Teamcenter administration privileges. -p Specifies the user's password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. For more information about managing password files, see Manage password files. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. If the utility is called using the EPM-invoke-system-action or EPM-invoke-system-rule handlers, use -u=- and -p=- arguments with the utility so it inherits the session authentication. -status_xfer_type Indicates the type of status transfer to perform. An argument value of cae_mesh transfers the release status to an associated CAEMesh dataset. Any other value, or not supplying the argument, transfers the release status to an associated DirectModel dataset. This argument and value are valid only if the -dataset_tag argument is specified; otherwise, this argument is ignored. -itemid Identifies the item under which to locate the CAEMesh dataset. The utility transfers the release status to the CAEMesh dataset at the location indicated by this argument, the -revid, and the -dsname arguments. This argument and value must be supplied only if the argument/value -status_xfer_type=cae_mesh is specified; otherwise, it is ignored. -key Specifies the key of the item under which to locate the CAEMesh dataset. The utility transfers the release status to the CAEMesh dataset at the location indicated by this argument, the -revid, and the -dsname arguments. This argument and value must be supplied only if the argument/value -status_xfer_type=cae_mesh is specified; otherwise, it is ignored. Use the following format: Copy [keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] To find the key of an object, use the get_key_string utility. For more information, see Introduction to multifield keys in BMIDE for Data Model Design. -revid Identifies the item revision under which to locate the CAEMesh dataset. The utility transfers the release status to the CAEMesh dataset at the location indicated by this argument, the -itemid, and the -dsname arguments. This argument and value must be supplied only if the argument/value -status_xfer_type=cae_mesh is specified; otherwise, it is ignored. -dsname Identifies the name of the CAEMesh dataset to which to transfer the release status. The utility transfers the release status to the CAEMesh dataset at the location indicated by this argument, the -itemid and the -revid arguments. This argument and value must be supplied only if the argument/value -status_xfer_type=cae_mesh is specified; otherwise, it is ignored. -dataset_tag Specifies the tag of the dataset to which the release status is transferred. The release status of the primary object (target object of the workflow process) is applied to the specified dataset. -task_tag Provides a text representation of the tag of the workflow task. The value can be extracted from the XML file provided by either the EPM-invoke-system-action or EPM-invoke-system-rule handler. -member_group Assumes the defined group name before executing an action on the workflow process. Use when users have multiple groups/roles and the user is expected to change to a group different from their default login group while initiating the background process. This argument allows the utility to assume the same group the user was using at the time the workflow process was initiated. It is expected that the same group is required to execute any action in that workflow process on behalf of the user. -member_role Assumes the defined role name before executing an action on the workflow process. Use when users have multiple groups/roles and the user is expected to change to a role different from their default login role while initiating the background process. This argument allows the utility to assume the same role the user was using at the time the workflow process was initiated. It is expected that the same role is required to execute any action in that workflow process on behalf of the user. -action Defines which action to trigger in the workflow task specified with the -task_tag=tag argument. Valid actions are: assign, start, complete, skip, suspend, resume, undo, abort, and demote. These action values are not case sensitive. -trigger_comment Provides the comment when triggering the action specified in the -action=action-name argument. -signoff Specifies the utility will perform a signoff with the specified decision. Valid signoff values are: approve, reject, nodecision. These signoff values are not case sensitive. -signoff_comment Provides the comment for the signoff specified with the -signoff=decision argument. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions None. Examples The following example checks the group/role defined by the -member_group and -member_role arguments (Body/Designer) against the group/role the user is currently logged on with. If they do not match, the group/role of the background processes group/role is changed to Body/Designer. The complete action is then invoked for the task specified by the -task_tag argument and the comment Tessellation completed successfully is displayed. Copy $TC_ROOT/bin/tc_workflow_postprocess -member_group=Body -member_role=Designer -task_tag=AZwszeaegnHvqDAAAAAAAAAAAAA -action=Complete -trigger_comment="Tessellation completed successfully" The following example checks the group/role defined by the -member_group and -member_role arguments (Body/Designer) against the group/role the user is currently logged on with. If they do not match, the group/role of the background processes group/role is changed to Body/Designer. The signoff decision No Decision is then made for the task specified by the -task_tag argument. Copy $TC_ROOT/bin/tc_workflow_postprocess -member_group=Body -member_role=Designer -task_tag=AZwszeaegnHvqDAAAAAAAAAAAAA -signoff=NoDecision -signoff_comment="Tessellation failed - disk full" The following example illustrates the use of the -dataset_tag argument to apply the release status of a rendering parent object to the related child object. Copy $TC_ROOT/bin/tc_workflow_postprocess -dataset_tag=AXwszeagnHvqDAAAAAAAAAAAAA The following example transfers the release status from a UGMASTER dataset to its corresponding CAEMesh dataset: Copy $TC_ROOT/bin/tc_workflow_postprocess -dataset_tag=QZPBK4_6x4$kbDAAAAAAAAAAAAA -status_xfer_type=cae_mesh -itemid=000266 -revid=A -dsname=000266/A Related Topics Workflow Designer on Rich Client