2014-01-30 04:20 AM
I've created a couple of workflows using some custom functions. One of the functions refuses to be exported together with a workflow.
Have to create a separate export for that particular function.
WFA version 184.108.40.206.32.
Any ideas to why this happens?
Thanks in advance,
Solved! SEE THE SOLUTION
2014-01-30 05:02 AM
I am using Firefox v.26 on a Mac.
The Workflows and Functions are on it's way to you via email.
I was under the impression that all custom functions would be exported with all workflows even the workflows did not depend on them?
2014-01-30 08:26 PM
In 2.0.1, whenever a workflow was exported, all the custom functions were exported. However, in 2.1, this behavior was changed to export only those functions that are referred from within the workflow.
Hence, now whenever a workflow is exported, only the used functions are exported.
Example: A function will get exported if it is used in defining a value for an attribute within the workflow.
2014-01-30 10:29 PM
That sounds like a better solution but then there is still an issue in the WFA version I'm running since one of my workflow uses 2 functions and when exported only one of them was included.
I noticed this when I decided to start from scratch with my WFA install. I exported my 3 workflows, reinstalled WFA, imported the workflows and 2 functions were missing. I rewrote them because they were pretty simple and I had done a backup before reinstall but still...
2014-01-31 03:15 AM
I circled backed the workflow that you sent me, to the Engg team and this has been attributed to a known issue of bug # 740209.
Pls keep an eye on the same, and open a customer case and add it to the bug, if this has any customer associated.
BTW this is happens in case the custom function (only) is referenced from the return parameter, And this does NOT happen for canned functions even if referenced in the return parameter.
The current suggested workaround are the following, which you have already done.
1. Export the function separately from workflow. Import both of them.
2. Write the function again manually or copy/paste.
Message was edited by: Adaikkappan Arumugam
2014-02-01 11:31 PM
I've also seen this bug before, and resolved it by using export-all instead. We also use a subversion repository to track changes and store dar contents which gives diff/version/revert capabilities.
Let me know if I should raise a customer case to ensure it gets a better resolution priority.
2014-02-02 08:51 PM
Pls add open a case for the same and add it to this bug. BTW could you explain a little bit more on the export-all ?
Hope you are aware of how to open a case against WFA, if not here is the procedure for the same.
Valid controller serial number to open case.
ASUP from WFA (manual generation) and the WFA System ID.
2014-02-02 09:24 PM
By export-all I mean, I use the "Administration -> Export All" option, and make sure the WFA instance I'm working with, only has the components I want in it where possible.
Since a .dar file is just a .zip file full of .xml documents, it's pretty easy to combine or remove things you don't want, or track them with a source control system.