Using a Form to make input for Data Source Flow
Comments
-
Hi there,
Im using a flow run part to select a date, and my goal is to use the date created by the flow run part as an input for the Data Source flow which kicks off the SQL for the report.
What is the best way to do this?
-
Hello there,
There is a way to do this that involves using the "Get Page Variable" step within your data source flow. Your configuration should look something like this:
[img]att2[/img]Basically, this is just taking the variable "DateFilter" string from the URL and passing it into the flow.
Ive attached an example project thats already configured for you to experiment with.
Hope this helps!
-
Thank you! This was very helpful.
However, there is one piece of this which I could not figure out, and Im sure its very simple.
On the form where you pick the date, there is an Outcome Scenario called "Leave" (which, I assume, means leave or tab out of the selected form). How can I create that as an outcome on my form? -
Glad it helped.
Normally we would use a button to specify an outcome. However, since we are using this form on a dashboard to automatically update the report date range, having to press a button after picking a date would be kind of clunky.
To avoid using a button we use something called a form outcome rule that allows us to create an outcome path that the form follows if a rule evaluates as true when triggered.
In the form designer, there is a section under "Form Rules" in the properties tab called "Outcome Rules".
Here is some further reading from our documentation site: [url=https://documentation.decisions.com/docs/form-outcome-rules]https://documentation.decisions.com/docs/form-outcome-rules[/url]
Howdy, Stranger!
Categories
- 4.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 490 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions