This document was generated from CDN thread
Created by: Stephan Steiner on 23-09-2013 11:01:52 AM
Hi
In provisioning, I usually go the getObject, modify that object, addObject route. That means I cannot use returnTags in getObject because I never know what might have been configured in my template object. Since we now have the filter for return tags to filter out stuff we don't need, it would be useful to have the ability to copy an existing object (just like you can do using the ccmadmin web interface).. so for instance, the operation copyPhone would take the deviceName of the phone to be copied plus the device name of the copy. Then you could do a getPhone for the newly created phone using returnTags to get only the tags that are interesting for modification, apply those modification and send back the object. So instead of sending a hundred properties back and forth, you've effectively limited yourself to the 10 or so that are really needed.
Alternatively, a copy syntax could be imagined that would take the unique identifier of the object to be copied, plus the properties you'd like to modify, but that would probably be more expensive to implement on Cisco's end (but reducing the number of AXL operation that have to be sent).
What do you think?
