Claim your change request to project scope - HxGN SDx - Update 64 - Administration & Configuration

Administration and Configuration of HxGN SDx
Language
English
Product
HxGN SDx
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
10

This functionality was modified in an update. For more information, see Claim your change request to project scope (modified in an update).

Why should I claim the change request to project scope?

Claim to project scope to implement the requirements of change request at the project level.

What happens when I assign a project to the change request?

When a project is assigned, the workflow will claim the tags and revise the documents to the assigned project automatically.

If the changes are not necessarily to be implemented at project scope, you can opt out of assigning the project and continue at the plant scope.

Process step class

This process step class can be used to claim the change request to project scope. The arguments define what the workflow does when a workflow step is initiated to claim the change request to project scope.

Process class name: Claim to project

Syntax: ClaimAndReviseRelatedDocuments,Arg1,Arg2,Arg3,Arg4,Arg5,Arg6,Arg7,Arg8

Example:

ClaimAndReviseRelatedDocuments,,SDAContractTransferDocVersion,True,,,,,False

Where:

Arg1: Relates the change request to a project. (Optional)

Arg2: Relates the change request to a document version. (Optional)

Arg3: Transfers the workflow to the project scope. (Optional)

Arg4: Relationship definition between the workflow item and the claimed objects (; separated). (Optional)

Arg5: Claims the document before the revision. Ignores if already claimed. (Optional)

Arg6: Ignores the system exclusive claim. (Optional)

Arg7: Lists the properties and values, colon separated, that need to be updated on the higher configuration workflow item. (Optional)

Arg8: Specifies whether to increment the minor (True) or major (False) revision. The default is to increment the major revision. (Optional)

The following examples show each type of the ClaimAndReviseRelatedDocuments process step:

<SPFStepDef>

    <IObject UID="STP_SOPSClaimToProject" Name="Claim to project" Description="Claim change request to project" ContainerID="SOPS.ProjComsSecurity" />

    <ISPFAdminItem />

    <ISPFStepDef />

</SPFStepDef>

<Rel>

    <IObject UID="STP_SOPSClaimToProject.WSC_SOPSClaimToProject" ContainerID="SOPS.ProjComsSecurity" />

    <IRel UID1="STP_SOPSClaimToProject" DefUID="SPFStepDefStepClass" UID2="WSC_SOPSClaimToProject" />

</Rel>

<SPFStepDefClass>

    <IObject UID="WSC_SOPSClaimToProject" Name="Claim to project" Description="Claim change request to project" ContainerID="SOPS.ProjComsSecurity" />

    <ISPFAdminItem />

    <ISPFStepDefClass SPFProcessClassName="ClaimAndReviseRelatedDocuments,SDAChangeRequestProject,SDAChangeRequestDocVersions,True,,,,,False" />

</SPFStepDefClass>

<Rel>

    <IObject UID="WSC_SOPSClaimToProject.WST_P" ContainerID="SOPS.ProjComsSecurity" />

    <IRel UID1="WSC_SOPSClaimToProject" DefUID="SPFStepClassStepType" UID2="WST_P" />

</Rel>

<SPFStepDefType>

    <IObject UID="WST_P" Name="P" Description="Process" ContainerID="Core.Workflow_Admin" />

    <ISPFStepDefType />

    <ISPFAdminItem />

</SPFStepDefType>