Is there a reason you need this to happen in a transition action?
If not, you could you do the reverse and set it to some value for all other configurations by using the 'Default overwrites' box in the card editor and then tell it to exclude the flat patterns in the 'Excluded configurations' box. This box accepts wildcards and should do the right thing when you add new configurations.
Search for 'excluded configurations' in the EPDM Card Editor help for more details.
Of course there is a reason ;-)
The default setting on the datacard is 'Unchecked'. So for normal files everything works fine. But..
We also have epdm templates to create certain types of new parts. And in some of these templates the checkbox is set to '1' and it is not possible for template variables to specify the configuration (not that I know of). So for these cases, I want to reset it back to '0' for the @ configuration and the flat-pattern configurations.
I'm sure you could do this using the API. It also looks like you may be able to do this using Dispatch, but I mostly use the API.
At this point it seems not possible to create a transition action for multiple configurations in the workflow. So I tried dispatch...
I'm creating a dispatch script now and I run in to the same problem again. Dispatch command 'Set card variable' doesn't allow wildcards in the configuration name either. And besides that, file variable %CurrentConfig% doesn't work either.
Is what I'm trying to do so unusual or is the EPDM functionality so limited on this subject?
Set Card Variables.jpg 110.4 KB
I think you'd have to write some code to step through the configurations and see if the name contains CurrentConfig.
Did you try asking your VAR? Your VAR may be able to help you out on an API add-in.
Unless really necessary, we don't want another add-in. Add-ins are slowing down the system too much already.
I called my VAR and they attached us to the following SPR:
SPR #: 571124
Product: Enterprise PDM
Fixed in: none none
Area: Enterprise PDM
Sub-Area: EntPDM Dispatch
Customer Impact: High
Summary: Dispatch set card variable action does not update datacard for the file variable 'CurrentConfig'
I also created an ER for the ability to select multiple configurations and use wildcards in a transition action (don't have an spr number yet).
Thanks for your help anyway,