Configuring for State Blocking

State blocking enables you to set up a route that blocks promotion. To set this up, you must configure a trigger on states in the policy that governs the type, whose promotion you need to block based on route approvals.

Complete this procedure for each state in the policy that you want to be blocked from promotion based on a route. For more details on routes and triggers, see the Collaboration and Approvals Administration Guide.

  1. Modify the policy that governs the object type you want to block, and add the promote trigger to each state.

    modify policy NAME state STATE add Trigger Promote check emxTriggerManager input NAME ;

    Where,
    • Policy NAME: Name of the policy you want to modify.
    • State: Named state is changed according to the state modification clauses entered.
    • Input NAME: Name of the eService Trigger Program Parameters object that represents the promote trigger program you want to run. It must have a unique name. If a name already exists, do not change it.

    For example:

    modify policy "Document Release" state RELEASED add Trigger Promote check emxTriggerManager input PolicyDocumentReleaseStateFROZENPromoteCheck;

    For details, see Installation and Setup | Customize | 3DEXPERIENCE Platform: 3DSpace | Legacy Tools | MQL Command Reference | Policy Command | Modify Policy .

  2. Find a value of eService Sequence Number field from above trigger program parameter if it exists and make a note of it.

    print businessobject BO_NAME select attribute[<ATTRIBUTE NAME >]BO_NAME includes TYPE,NAME,REVISION

    Where,
    • TYPE: eService trigger program parameters.
    • NAME: The input name you assigned for the promote trigger in Step One.
    • REVISION: Enter text that makes the Type/Name/Revision combination unique.
    • ATTRIBUTE NAME: eServiceSequenceNumber.

    For example:

    print bus "eService Trigger Program Parameters" PolicyDocumentReleaseStateFROZENPromoteCheck CheckIfConnectedChangeActionIsCompleted select attribute[eService Sequence Number];

  3. Create a new eService trigger program parameters business object:

    add businessobject BO_NAME policy POLICY_NAME vault VAULT_NAME BO_NAME includes TYPE NAME REVISION

    Where,
    • TYPE: eService trigger program parameters.
    • NAME: The input name you assigned for the promote trigger in Step One.
    • REVISION: Enter text that makes the Type/Name/Revision combination unique and indicates the purpose of the trigger. For example, CheckRoutesForPreliminaryState.
    • POLICY _NAME: eService trigger program policy.
    • VAULT_NAME: eService Administration.

    For example:

    add bus "eService Trigger Program Parameters" PolicyDocumentReleaseStateFROZENPromoteCheck

    CheckIfConnectedChangeActionIsCompleted policy "eService Trigger Program Policy" vault "eService Administration" ;

  4. Add attributes for the new object, such as:

    mod businessobject BO_NAME "eService Sequence Number" Sequence Number "eService ProgramName" Program Name "eService Method Name" Method Name ;

    BO_NAME includes TYPE NAME REVISION

    Where,
    • Program Name: JPO programor tcl. eg., eServiceCheckRoutes_if.tcl.
    • Method Name: Name of method from jpo.
    • Sequence Number: Add 1 to the last sequence number from above step 2.

    For example:

    mod bus "eService Trigger Program Parameters" PolicyDocumentReleaseStateFROZENPromoteCheck

    CheckIfConnectedChangeActionIsCompleted "eService Sequence Number" 1 "eService Program Name" eServiceCheckRoutes_if.tcl;

  5. Promote the object to the Active state.

    Promote businessobject BO_NAME;

    BO_NAME includes TYPE NAME REVISION

    For example:

    promote bus "eService Trigger Program Parameters" PolicyDocumentReleaseStateFROZENPromoteCheck CheckIfConnectedChangeActionIsCompleted;