SAP Personas 3 - locking of objects in transports
Hello Personas group. We are using the transport utility for Personas 3 which allows us to centrally manage the development of Personas objects.
We have a Dev. environment that is not fully configured as our default client using TMS is not customized. That means that we develop personas screens/scripts in another client, then copy (zip file) the content over to the default client in order to transport it through the landscape. We are now in UAT and noticed that we not only lock objects in all target systems (which is what we want), but also lock all further editing in the other dev. client as well. Is there a way to mark or reset the editing lock on personas objects in specific systems, so we can maintain the objects? Is this a DB based table entry or a lock reading transports as Personas editor starts up?