object locking in Charm

[former_member244060]

In testing Charm functionality, I am finding that objects are not being locked and 2 developers can make customizing changes in a table at the same time and one transport can overwrite the others changes with no notification!

This seems very dangerous.

Is there any way to lock these objects?

Thank you!

[Former Member · Accepted solution]

Hi,

goto SPRO: ...change mgmt -> charm -> extended configuration -> charm -> configure and activate cross-system object lock

do the 2 steps and enable konflict analysis for: "cross-project, client-specific" or whatever you need.

hope this helps!?

[Former Member]

This has nothing to do with ChaRM. Customizing objects (beside some cross-client objects) do not get locked in transport requests. This is default by design.

[Former Member]

Hi Randy,

I am not aware of any functionality to help you here. You use the same development processes you used before to avoid this.

You could use the Solution Managers Business Process Structure and the Development tab to maintain a status for all of your objects. You would have to instruct the developers to go to Solution Manager, assign the object to themselves, set the objects status to "In development" (or whatever custom status you come up with), double click the object to open it up and make changes, and when done set the status back to "complete" and remove their name. This also provides an audit trail.

Hope this helps.

regards,

Jason