cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Need help navigating or using the PTC Community? Contact the community team. X

ACL works when you open an xml normally, but not in Resolved Document View

william_maclean
4-Participant

ACL works when you open an xml normally, but not in Resolved Document View

Hello,

I am posting this problem for one of our developers.

 

In an .acl file, we are using the functions ‘oid_modify_attrs’ and ‘oid_delete_attr’.

 

When running the .acl on an .xml file opened directly from within Epic (File > Open [filename] or opening the xml from a ditamap file, the atttibute function calls work as expected. When working from within Resolved Document View, the functions fail.

 

What needs to be done differently in order for these functions to work in Resolved Document View?

 

Thank you,

Will

 

2 REPLIES 2

Hi Will--

 

When you say "Resolved Document", do you mean Resolved Document for Editing? If so, you may need to lock the inclusions in order to change content in them.

 

The Resolved Document for Editing is built by basically making a wrapper document analogous to the ditamap, but using xinclude to bring the topics inline. However, you have to lock an inclusion before you can edit it. In the Editor, this happens automatically, but with a script you probably need to do it explicitly.

 

Try this: before the calls to oid_modify_attr() or oid_delete_attr(), call oid_entity_lock(oid), where oid is the element whose attributes you want to modify or delete.

 

--Clay

Hi Clay,

Sounds like a good itdea - I've forwarded this to the developer.

Thanks very much for your response,

Will

Announcements

Top Tags