API Calling and Multiple Flows

Unknown

API Calling and Multiple Flows

Unknown

[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]1. Is there a way I can model what output the API call to a flow returns? I tried JSON format of an existing entity but it doesnt return anything. [/font][/color]
[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]2. Is there a way to create a session that will reference multiple flows? For instance I need Flow1 to return an output that I will process with my mobile app and send more data to Flow2. Will Flow2 know anything about data submitted in Flow1? [/font][/color]
[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]3. Is there a way to create a session with decisions.com API based on an arbitrary field, lets say a customer that is not a user in decisions.com ?[/font][/color]

Unknown

[font=Roboto, Arial, Helvetica, sans-serif]1. If your flow has Input Data (usually defined at the start step) then your API call will require those inputs as JSON or XML. (This is assuming youre using REST otherwise you can just use the SOAP WSDL for the flow.) The Inputs and the Outputs are described with examples if you hit the "Integration Details" button at the top of your SteerageFlow1 diagram as shown here: [/font]
[font=Roboto, Arial, Helvetica, sans-serif]
[/font]
[font=Roboto, Arial, Helvetica, sans-serif]2. Yes. You can definitely link flows together. You can do this so that Flow 1 doesnt send any data back to the caller until Flow 2 has completed or you can hand the results of Flow 1 off to BOTH the calling API and to kick off Flow 2 to run in the background. This is done using "Linked Flow" or "Run Linked Flow Async" in Flow 1, to call Flow 2. [/font]
[font=Roboto, Arial, Helvetica, sans-serif]
[/font]
[font=Roboto, Arial, Helvetica, sans-serif]3. [/font][font=Roboto, Arial, Helvetica, sans-serif]I think that there are possibly a couple ways to do this, but it seems youre looking for a way to "authorize" or "identify" someone by some non-user-login method and have that users permissions and rights enforced in Decisions when your application is calling Decisions. If thats correct - yes, you can do this. There are a couple ways, but the easiest way to get started with an application to application identity is to use what we call Named Sessions (or your SSO provider). [/font]
[font=Roboto, Arial, Helvetica, sans-serif]
[/font]
[font=Roboto, Arial, Helvetica, sans-serif]Named sessions are explained here: [/font][url=https://documentation.decisions.com/create-named-session/]https://documentation.decisions.com/create-named-session/[/url][font=Roboto, Arial, Helvetica, sans-serif] There are also webservices you can call in Decisions to validation or create a user specific session.[/font]