How two people can update case from app studio

How we can allow two people to work on the same case , pydefault, from the app studio? they are saying that once it goes to a branch, other person is not able to work on it?

that is correct, if person 1 is working on the case in branch 1 and person 2 in branch 2, working on the case would create conflicts, it is not an ideal approach to dividing up work in a development team.

App Studio’s “save” will save far more than pyDefault, so you need to be careful having two people working on the case. It would also create a lot of “stale information” messages and likely “cross-pollination” of branches.

  • IF you want this kind of fine tuned development I would be looking to utilise dev studio.
  • IF you want to use App Studio, I would be looking at dividing up work in the team between case types, not overlapping on the same case type (app studio changes are just too wholesale for this approach to work)

Thank you and you summarized well, In this case, only one person 1 can edit/update on a given case until the branch is merged and then person 2 can start working on the same case? Is there any way where both can work and changes will be saved in their own branches or Pega is not giving this option as conflict will be too much to manage from the App studio? thank you

Hi @SharadK17674862
Branches provide isolated development, so if a developer creates and works in a branch, others cannot access those changes unless they switch to the same shared branch or the branch is merged. For multiple developers working on the same feature, a common branch should be used. If the requirement is about multiple users working on the same case, it should be handled through case design approaches such as parallel processing or appropriate locking strategies.

You can also use the Workspaces feature, it was new to '24 to allow more isolated development than branching.

Is that work in app studio as well? so Idea is to let them work in same branch ?

Yes, branching works in App Studio as well since it’s part of Pega’s ruleset model.If multiple developers work on the same feature, they should use the same shared branch to collaborate.