Your Paxata Administrator must enable this feature in your application. |
---|
...
- You must have permissions to all of the datasets and all of the Projects in the Flow before creating a Flow, otherwise it will never successfully run.
Note: if a user has permissions to an AnswerSet, but not the Project from which that AnswerSet was produced, the user can still create a Flow up to the point at which the user ceases to have the "read" permission. This flexibility in Flow creation enables users to independently manage the operationalization of Flows for the portions they have permissions to access. - You must also have permissions to all of the datasets and all of the Projects in the Flow in order to manage it from the Monitoring Interface. Your Paxata System Administrator provides these permissions.
- Anything produced downstream from your target Project is not included in your defined Flow. For example, returning to the illustration above, if there were a Project that consumed your "Sales Variance Report" AnswerSet, then that Project would never be included in the Flow—the target Project is always the end point for a Flow.
...
The Configuration Interface has three tabs where you configure the settings for your Flow. The Configuration Interface is presented when you first create a Flow and also opened when you choose to "edit" any of the saved Flows displayed in the Monitoring Interface. Three configuration tabs are used to configure your Flow. The three tabs are described below. Note that buttons for "Graph", "Actions" and "Discard Changes" and "Save" are always present in the Configuration Interface and provide common actions you can take for all Flows.
...
- Update the Name and Description of a Flow that you've created.
- Specify the triggers to run your Flow. The triggers are time and frequency based. You can also use the custom option to provide a cron expression for the trigger.
- Provide email addresses for run status. Separate each address you add with a comma.
Note: as soon as a Flow is created, a Project ID Flow will also display on the General tab. This ID is used to identify the Flow for REST API calls and also for any required troubleshooting of the Flow.
Inputs tab Anchor inputs inputs
...
2. Snapshots page lists all of the Snapshots for a Flow. Every time a Flow is executed, which is called a "run" of the Flow, a Snapshot is created to capture the configuration settings used to create the output for the run. The runs will continue with this Snapshot until any configuration changes are made to the Flow—for example changes to the schedule, notifications, inputs, output settings, etc. Then a new Snapshot is created for the Flow and the new Snapshot captures all of the executed runs with the modified configuration settings.
Snapshots provide clear audit-ability of the exact state of a Project Flow for each run.
Important: a new Snapshot is not created if datasets are configured to use the latest version from the Library. See the Inputs section for dataset configuration options.
...
Generate a visual graph for Flow Anchor generate generate
The Graph button generates an APF graph in a new browser window that displays the datasets and how they flow into the individual Projects used to generate a Flow's final output AnswerSet.
Hovering over any dataset or Project in the Flow also displays the corresponding downstream lineage (in pink) and upstream dependencies (in blue).
For example, when hovering over the dataset for March 2016 Transactions:
When hovering over an intermediate Project in the Flow—in this example Customer Loyalty-Women Members—the upstream dependencies display through the blue lines while the downstream lineage displays through the pink lines.
Notice in both examples that if datasets and Projects do not participate in the portion of the Flow that you've selected, then they are grayed out in the graph.
...