Workflow / Rule Run History

Unknown

Workflow / Rule Run History

Unknown

Hello,

I was wondering if there was a way to trace the execution of a flow or rule after it has been run outside of the flow or rule debugger. When debugging a flow we have a nice trace of the flow that shows what paths were executed, what were the inputs and outputs for each step, etc. Is there any way to get the same sort of data after a flow has executed, say from being kicked off via a scheduled job? Also, is there a way to output this data in a flow or some sort of way for use to be able to capture and consume that data from an external API? Or, if need be an API available within decisions we can call from another API to get this type of data.

Thanks

Unknown

[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]Hi,[/font][/color]
[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]
[/font][/color]
[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]Decisions does not allow you to retrieve debugger information in a flow as it may become a potential security issue depending on the data that is passed through the flow. Alternatively, you need to collect the necessary flow data manually. You may use a customer Flow Structure to house this information and send it to your external API by using REST call.[/font][/color]

[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]Please check below documentation about how to creating flow structure and how to setting up an external REST API call. If you have additional questions please let me know.[/font][/color]
[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif] [/font][/color]
[url=https://documentation.decisions.com/docs/creating-simple-flow-structure]Creating A Simple Flow Structure[/url]
[url=https://documentation.decisions.com/docs/external-applications-calling-flows-rest]External Applications Calling Flows (REST)[/url]
[url=https://documentation.decisions.com/docs/rest-handling-services]Calling a flow as a REST Service[/url]