customised ModeledAttributesDelegate is not being run on 'Add to Workspace' in v10.0 - why ?
We managed to get our customised copy of the ModeledAttributesDelegate working as expected in v9.1 M062 but now it only works some of the time in v10.0 M040, using the U-WGM for SolidWorks v2012. and the same behaviour appears to be happening with the embedded WGM in Wildfire4.
It clearly runs when executing "Save to Workspace", and with the Preference set for "Upload upon native save" = Yes, this action clearly ends with an Upload (and then a download), so we have confidence that it is compiled and has been made available as a service by the relevant addition to site.xconf (followed by xconfmanager -p, and restart of Windchill inc. clearing cache folders).
But it does not run upon "Add to Workspace" as it should, so when a file is checked in and deleted from a Workspace, then selected in Commonspace and Added to the Workspace once again, the values of the Attributes are not being updated from the server.
Further tests show that the delegate does run and produce the expected results in the SolidWorks file upon check-out, so it looks much more likely that it is a matter of triggering the delegate to run rather than there being an error in the delegate itself.
There are no clues in the Method Server log for the corresponding times.
Can anyone advise us on how to check and investigate this problem, and what settings control if or when the service is executed ?
We believe that something has changed between v9.1 and v10.0 that effects the ModeledAttributesDelegate, but what ?
We are very grateful for the answer we just got from PTC Technical Support.
It turns out that the Method we are using to retrieve the file modification status (ie. the +sign from the WGM) and show it in an Attribute, from :
is not officially supported and so its behavior can change at anytime without notice - and indeed this is what changed from v9.1 to v10.0.
PTC recommend that we file an enhancement request to get a supported API that retrieve the modification status of an object in the Workspace, so this can be passed to an Attribute/Parameter, in much the same way that the following can be used to get the "NEW" flag (and although this Method isn't shown in the v10.0 M040 JavaDoc either, it is mentioned in many copies of the Customizers Guides and in TAN 150617) :