Hi Hazem, I would imagine that if it is possible to do as a transition action, an API call should exist for it to be done with an addin, why do you wish to run it as a task rather than as a transition action?
i'm asking about the task for 2 reasons :
1- if i want to export the xml now and i don't want to pass through the workflow.
for example, i created the transition action during the approval state and the assembly is released now and the xml file is generated also, what about if i want to create another xml file without passing through the workflow as the assembly is released already ?
2- the xml file wasn't generated as output file from the transition action.
Hey Hazem Taha
One option is to use automatic state transition at the workflow to return the files to the originating state after running "Create XML" -change state.
With SW PDM 2017 there is a new feature to overwrite latest version when checking in files, this option can also be enabled for workflow transitions of your choice to work behind the scenes.
This way your file versions & references stay unchanged and you can execute tasks & other stuff tied to state changes.
These state changes are still recorded in the file history, but there is an indication that the latest version was overwritten in the process.
many thanks for your cooperation