Workflow versions from child domains are not published with the application to repository or update sets when publishing a parent domain. When performing these operations form a child domain, workflows from current and parent domains are included. This results in an incomplete application depending on the domain from which the operation was executed and makes it impossible to back up the entire operation that has workflows and other files (such as business rules) in different domains.

To commit/register to source control:

1. Create a custom application and select it as the application.

2. Create two workflows on the global domain, one published and one unpublished.

   For more information, see the documentation topic Getting started with workflows.

3. Create two workflows on a child domain of global (for example, "TOP"), one published one unpublished.

4. Set the session to the global domain and link the application to source control.

   For more information, see the documentation topic Link an application to source control.

   Note the messages in the localhost log indicating that the published workflow from the child domain was skipped as if it were unpublished.

5. Make a change to the published workflow on the child domain.

6. Set the session to the global domain and commit changes to the repository.

   For more information, see the documentation topic Publish an application to the repository.

   Note the messages in the localhost log indicating that the published workflow from the child domain was skipped as if it were unpublished.

7. Delete the related sys_repo_config record and repeat the previous steps, but this time, register/commit having selected the child domain in the domain picker.

   Note that only unpublished workflows are skipped. Both published workflows from parent and child are fine.

To publish to an update set:

1. Create a custom application and select it as the application.

2. Create two workflows on the global domain, one published and one unpublished.

3. Create two workflows on a child domain of global (for example, "TOP"), one published one unpublished.

4. Set the session to the global domain and click Publish to Update Set.

   Note that the update set contains only both workflows on the global domain.

5. Set the session to the TOP domain and click Publish to Update Set.

   Note that the update set contains all four workflows from both domains

Develop all new workflows in the global domain and move any existing scoped workflows also to the global domain.