This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Transport of IT Shop approval workflows and policies

We have an IT Shop approval workflow that is about 26 steps long which references many custom Business Roles for approvals.   Is there a way to transport IT Shop workflows using the Data Transporter tool?  Having to re-create the workflow when moving to another environment would be tiresome.

Parents
  • Obviously the workflow contains steps with a relation to Orgs (business roles) - for example „OR“ (Members of a certain role) or “OM” (Manager of a specific role).

    The screenshot shows that the related Orgs have been exported too.

    But these orgs are linked to an OrgRoot (Role class) which is not contained in the Transport.

    And this OrgRoot ("Job roles") doesn’t exist in the target database.
    Or: The OrgRoot exists there but with a different UID.

     

    We have defined in the default which dependend objects will be exported automatically.

    Not all dependencies are affected, it would be too much.

     And the OrgRoot of an Org is NOT marked to be exported automatically, that's why it was not added to the Transport.

     

    Solution:

    Transport the OrgRoot with an extra Transport before.
    Or if the OrgRoot already exists with a different UID: Change the UID. The same objects must have the same UID in every OneIM database.
    For that purpose I can provide a SQL script.

    Following you can import the decision workflow.

Reply
  • Obviously the workflow contains steps with a relation to Orgs (business roles) - for example „OR“ (Members of a certain role) or “OM” (Manager of a specific role).

    The screenshot shows that the related Orgs have been exported too.

    But these orgs are linked to an OrgRoot (Role class) which is not contained in the Transport.

    And this OrgRoot ("Job roles") doesn’t exist in the target database.
    Or: The OrgRoot exists there but with a different UID.

     

    We have defined in the default which dependend objects will be exported automatically.

    Not all dependencies are affected, it would be too much.

     And the OrgRoot of an Org is NOT marked to be exported automatically, that's why it was not added to the Transport.

     

    Solution:

    Transport the OrgRoot with an extra Transport before.
    Or if the OrgRoot already exists with a different UID: Change the UID. The same objects must have the same UID in every OneIM database.
    For that purpose I can provide a SQL script.

    Following you can import the decision workflow.

Children
No Data