Hello Pega folks,

We have multiple developers work on Pega customer decision hub to work on creating/updating Action rules through NBA Designer in CDH app studio.  Below is an example to better explain use case:

For below use case. We created two separate applications CDHApp1, CDHApp2 and access groups CDHApp1:Admins and CDHApp2:Admins which is built on main CDH application. Below use case is not working when both developers works on same NBA designer through separate application.

1) Developer-1 is working on Customer Service/Billing Issue group hierarchy to create new action "TransferToAgent" under Billing Group. He updated Design time access group CDHApp1:Admins pointed to CDH-Artifacts: 01-05-30 and also limited CDHApp1 application to 01-05-30. He checked in Action rule and associated rules saved in 01-05-30. 

2) Developer-2 is now working on Customer Service/Billing Issue group hierarchy to create new action "TransferToBillingAgent" under same Billing group. He updated Design time access group CDHApp2:CdhAdmins pointed to CDH-Artifacts: 01-05-31 and also limited CDHApp2 application to 01-05-31. He checked in Action rule and associated rules saved in 01-05-31. 

Now issue is happening when Developer-2 tries to checkIN rule, associated rules are saving into 01-05-30 version and it messes up Engagement policy conditions created by Developer-1.

We tried above approach by using only CDH application with more than 1 CDH-Artifacts version but some OOTB decision data and proposition filters rules saves into different RSV.

We also tried using different application, different access group and opening only 1 CDH-Artifacts RSV, update changes and lock RSV. Example: Dev-1 works on 01-05-01 version Action rule, he checked in rule with engagement policies and locked 01-05-01 version. Dev-2 now sees no RSV checked out, he creates 01-05-02 version, create action and checked in rule. Now Dev-1 forgot to update some engagement policy condition on 01-05-01 and he tried to unlock 01-05-01 version and updated engagement policy condition and locked 01-05-01 version. After this, when Dev-1 tried to open Action rule then he do not see newly updated engagement policy condition because dev-2 worked on 01-05-02 and proposition filter shows previously configured conditions but not latest.

With above, this creates dependency structure for other dev team member and can't able to work on NBA Designer at same time. Do you know any possible solution to above where multiple dev member can work similtaneously without affecting Engagement policy or any other conflicting changes ?