Documentum XML Adapter fails to note attribute changes from ACL code

Answered by: Lou Argyres Last Updated: 2007-12-12

=Question=

I'm seeing a behavior with Editor 5.2 Documentum XML Adapter and I'm not sure if it's by design, and if so, whether it should be by design.

When attributes of a chunk element are modified by ACL code, the Adapter does not recognize it, i.e., dctm:obj_status does not change from 'Unchanged' (or 'Default') to 'Changed'. (The ACL code is fired by a Save callback, but it also happens when called by hand.) The same changes made with the Modify Attributes dialog by hand *do* get recognized.

I'm now managing dctm:obj_status thru the ACL, but I can foresee circumstances where a user somehow backs out of something and the dctm:obj_status will be wrong.

=Lou Argyres has the solution=

The problem was that the ACL changes were coming from a save callback. Adding the "PREPEND" parameter to my save callback put it ahead of the undocumented Documentum XML Adapter save callbacks and the ACL attribute changes were recognized in the dctm:obj_status="Changed".

(Editors Note: John Dreystadt (PTC) confirms that "this behavior is not by design".)