Hello all, I am trying to deploy a workflow in my company, but I don’t want the exact operation (workflow) to be shown. It is the result of Capture-Workflow/Workflow-writer. I think there is a way you can turn the captured workflow into a shareable node. can anyone point me in a direction? thank you in advance…
Hi,
You can turn your workflow into a component and share it, then others can drag it into their workflows and use it. Or you deploy the workflow as workflow service, then others can use it with the Call Workflow Service node. With the first approach, people need the extensions you use in the component installed in their AP and they can see what you did in the component. With workflow services, the workflow is hidden, because it runs on Business Hub in an execution context that you control.
Kind regards
Alexander
3 Likes
Hello Alexander:
Thank you so much for the answer; yes, it is an elegant solution; if you put the captured workflow in the Private Space, with grant access, others can call the workflow but won’t be able to look inside. Thank you again for the timely response.
1 Like
Hi,
As a side note: it may make sense to also share a component for calling your workflow service. That way your colleagues do not need to know anything about the deployment. They use the component and that then calls the service in the background. It makes using the service a bit easier.
Kind regards
Alexander
Uerr, do you mean to warp the Call-Workflow node inside the component? Won’t that be just the same? thank for the clarification
Hi,
Yes, it will be almost the same, but the user does not need to configure the Caller node and does not need to know where exactly the service is deployed. Otherwise you will have to document somewhere how to call the service and users will need some extra effort for configuration.
Kind regards
Alexander
Got it, thank you so much for the insights…
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.