and more in a single search tool across platforms. Read the announcement here. |
05/04/2022 05:43 AM
We're trying to understand if there is a way to convert an ARS workflow that is in XML format back to the GUI interface format. Does anyone know if this is possible?
05/04/2022 05:54 AM
Hello,
Once the Workflow is converted to XML, it cannot be converted back to the GUI format.
05/04/2022 10:13 AM
if you want to edit workflow in XML version use transport - Export & re import it, it will not remove your Wiring (GUI)
05/05/2022 12:13 AM
Hi Rushikesh,
When doing that, if you are adding a different node/modules, wouldn't you need to add the same to the JSON Data element of the WF file in the export? or have used it just to add more reminder blocks?
Also with respect to error handling, in case of syntax issues, Workflow does not allow you to save unless the syntax is correct.
But in case of importing improper transport packages, you would need to look at the error from logs as the UI would complete the import but not load the workflow.
05/05/2022 06:32 AM
Hi Sahaj,
Additional Reminder does not create block, that can be added in XML will work.
I do agree JSON also needs to be updated for GUI Representation. but at the end XML is used for processing
you can use transport if
if you are adding new block (approval/if-else) you should add from GUI
05/05/2022 06:46 AM
Thanks Rushikesh for providing these inputs and solutions.
To go back to the original post, once a workflow is made XML and saved as such, it cannot be reverted back to GUI.
Editing transport packages to manage can be a solution scenarios where the WF has not already been created but the management of the package metadata has to be maintained separately by the administrator/integrator and is not covered under the product's functionality.
05/05/2022 06:45 PM
Thanks for the confirmation. I didn't think there was a way to convert it back. Appreciate the quick response!