Working collaboratively on decision services
Several collaborators can work on the same decision services. To make your changes available to others, you must share them.
When you make a change, it is automatically saved to your personal copy and visible to you only. Your decision automation must be connected to a remote repository to share your work with collaborators.

Sharing your work
Before you share changes, you must be up to date with the changes shared on the remote repository. Then, you might need to resolve conflicts. You can share when there is no more conflict. You can also revert to the state of your decision artifacts before you made changes, or you can restore your decision artifacts to a previous state that was shared with your collaborators.
| Task | What to do | Where to find information |
|---|---|---|
|
Create decision artifacts |
Model and create decision artifacts. |
|
|
Revert changes |
Revert the changes that you made before you publish them. |
|
|
Load changes |
Check whether your collaborators made changes in the same decision automation. You see an icon
with a blue dot If there is any conflict between the changes that you made and your collaborator shared, you must resolve it first. Then, you load the changes that are shared by your collaborators. |
|
|
Run decisions |
If you retrieved changes from a collaborator, check the behavior of your updated decision model. Changes that do not conflict from a file perspective might conflict from a semantic one. You can run test data to validate this behavior before sharing. |
|
|
Share changes |
Share your changes. Your changes are now available to your collaborators. If there is any conflict between the changes that you made and your collaborator shared, you must resolve it first. Then, you share your changes. |
|
|
Restore changes |
Restore your artifact to a previous state that was shared by you or your collaborators. |