Hi , I just created a work flow, and inside it , I would like to call a Projection like this:
As you can see, I need pass the “Objkey” to VirtualSet inside the URL,
while, in work flow there is no way to pass parameter to a VirtualSet
I passed Objkey , but it failed to call.
Best answer by Achala
“ConfigurationSpecVirtual_Complete()” is a bound action. you cannot specify the entity type parameter for bound action in Workflow. that is why it does not ask input parameter when you select a bound action in Workflow designer.
To use bound action in Workflow, First read the exact record which you want to call this bound action and then call bound action without any parameter.
Below is the property panel of the Read Activity
Below is the property panel of the CALL Activity
Hope this will usefully for your issue. Please try this out
“ConfigurationSpecVirtual_Complete()” is a bound action. you cannot specify the entity type parameter for bound action in Workflow. that is why it does not ask input parameter when you select a bound action in Workflow designer.
To use bound action in Workflow, First read the exact record which you want to call this bound action and then call bound action without any parameter.
Below is the property panel of the Read Activity
Below is the property panel of the CALL Activity
Hope this will usefully for your issue. Please try this out
Hi
I followed your instructions but is not working. Can you please advise?
IFS Cloud Web version: 23.1.1
Hi
I followed your instructions but is not working. Can you please advise?
IFS Cloud Web version: 23.1.1
What I mean, is that the Workflow is working fine, no errors, and generating the Response correctly from the Call function, but when checking into the system I don’t see the generated record.
Thank you
You are in the troubleshooting mode (debug mode), this mode is used to inspect the Workflow execution path for the given input parameters and data do not persist in this mode. That is way you don’t see the data changes.
Regards,
Achala
You are in the troubleshooting mode (debug mode), this mode is used to inspect the Workflow execution path for the given input parameters and data do not persist in this mode. That is way you don’t see the data changes.
Regards,
Achala
You’re right! I did a real test and it worked!
So for creation/updates if we have the response it means it will work.
Thank you very much!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
