When a component is XML checked into a package where it already exists any changes to the user options (&USROPnn) for that component in that package are lost.
When one user checks out an element in Composer, that element is locked and cannot be edited by any other user. If that user has left the company or is out of the office and won't be back for some time, you may need to break that user's lock to regain control of the element.
If you create any Rest Data Source in ANY Process app and deploy and then do a Get from AE ALL process apps will now fail when importing to Composer. They all contain this Rest Data Source (including the global) and will fail with error "Root element is missing".
Perhaps highly structured files, binary files, are candidates for this. In some situations, customers have mentioned the desire to "lock" a configuration file or certain properties files or xml files for tomcat, web servers and application servers to keep most users that work in the stream from changing these.
******************************* Bottom of data ******************************** As can be seen above, the PARMS.SERVICE.LOCK and UNLOCK XML Services are not affected by this issue and can be used as a short term solution to the problem.
Scratch a Component - CMPONENT SERVICE SCRATCH 231 Lock or Unlock a Component - CMPONENT SERVICE LOCK/ UNLOCK 232 Component Staging Version Management 234 5
