Overview

This article will detail how to setup Input Flow. Input flow allows users to automate the execution of Planning templates in Solver Cloud and Private Host (v5.2.4.408##+). This can be useful to organizations who may do driver based budgeting and want to be able to apply these drivers across a budget model. 

This article makes the following assumptions

1. You are familiar with and have created your Input templates
2. You are familiar with drivers (and other types of data) and being able to reference this in other workbooks and sheets. 

This article is broken down into a couple of sections:

1. Pre-configuration Information
2. Configure an Input Flow
3. Execute an Input Flow
4. Troubleshooting Input Flow Errors

Before proceeding, here are some things to know 

Pre-Configuration Information

General

1. Input flow is included with your purchase of the Planning module within Solver Cloud and Private Host. 
2. Input flow is not available in the BI360 4x application, however similar concepts can be implemented using Solver Consulting services. Please reach out to Solver Support to inquire more about this. 

Implementation Need to Knows

1. A configured Input Flow is "yours" and cannot be viewed/edited by other administrators. 
   • You can use the transfer ownership feature to "take over" someone else's Input Flow. 
2. Input flow has a max iteration (explained below) of 25. 
   • To use iterations, the parameter must have Allow Multi-Selection enabled. 
3. Templates using the same parameter (such as "department") that will need to have different values, should be named uniquely on the template. Should you have two Parameters called "Choose Department", it will be difficult to know which Parameter belongs to which template. 
4. Input templates should be tested and validated before being added to an input flow. Should you make a change to the template, it must be removed from the Input Flow before you can publish those changes to your input template
   • We recommend that if you had to make a change, do not delete your Input Flow, you will lose your configuration. Just simply remove the template that needs to be published and replace it with a temporary ("dummy") template. 
5. Input flow requires at least 2 published templates to be added.
6. Input flow does not support scheduling or email notifications. 
7. Input flow can only store back to one integration, you cannot add Input Templates belonging to different integrations. 

Configuration

Input Flow simply requires Input templates that have been built out, tested and confirmed working in a manual process. Your testing should include storing each form in the order that will be defined in the Input Flow. 

Create Your Input Flow

To create an Input Flow

1. Navigate to the Input Flow menu 
2. A listing of your Input Flows will appear. Click New to begin
3. In the setup that appears, provide the following
   • The name of the input flow, this will appear on the Input Flow main menu
   • The integration. This is the integration for the reports being ran. In most cases, this will just be the Data Warehouse
     • The company will auto-populate to the tenant name for Data Warehouse 
     • For ERPs, choose the company. 
4. Once you select the integration, the templates list will become active. This dropdown shows only the templates that have been published. Select the templates to be part of this Input Flow. 
   • All parameters found in the templates will appear in the Parameters section
   • If your template has default parameters they will appear in the parameters section
   • Please provide parameter values where applicable to all parameters. 
5. At this point, your screen should looks something like this, with you selected templates appearing as Cards in the bottom grid
   
6. Next, define your order of operations. In this example you can see that I want "Input Flow - Driver Setup" to go first, followed by "Input Flow - Storage by Dept" to follow. 
   
7. Input Flow - Driver Setup references the "Choose Department" parameter while Input Flow - Storage by Dept references the "Choose Budget Department". While they both reference the same Department dimension, in this input flow they act differently.
   • On the Drivers form I want all departments to come into the sheet
   • On the storage by department form, I want the form to be ran for each department individually. 
8. As configured, the Storage by Dept template would run for the single department "100:500" and error out because this is not a department in my setup. To achieve the effect of running this report for departments 100, 200, 300, 400, 500, I must setup the "Choose Budget Department" parameter with Iterate enabled. To do so, simply click the lookup for this parameter and choose the Iterate option. 
   
   • The iterate option is only available if the parameter option for "Allow Multi-selection" is turned off in the Input Template. 

Once all parameters are defined, scroll to the top and click Save. This completes the configuration of an Input Flow. 

Executing an Input Flow

There are two ways to execute an Input Flow

1. Ran manually from the input flow menu
   • This option may be popular in cases where no templates need to be ran manually. You may choose this option if budget data or drivers are imported and then calculations and new budget numbers are driven off this imported data. 
2. Kick off the input flow after you click Save data from the first template in your input flow. 
   • This option will kick off an Input flow once you click Save data from the first form in an Input Flow. 
     • Users will see text on this input template, indicating it is part of an Input Flow
     • Users do not need to stay on this template after saving it, for the Input Flow to execute and complete

Manual Executions of Input Flow

An Input Flow by default is setup to be ran manually. You can verify this be whether or not you see the "Enable" option. If you see this option, the Input Flow is setup for manual Execution

To execute this Input flow, simply click Run.

Additionally, you have the following options

Executing an Input Flow Via a Template

If you have Enabled the Input Flow, this means that it will be executed once the user clicks Save Data.

1. Once Enabled, navigating to the template via the Input templates menu, users will see an indicator that this template belongs to an Input Flow and additional data storage will happen. 
   
2. After the users types in the budget numbers and hit saves, the Input Flow is executed in the back ground and the user can exit the menu. 

Troubleshooting Input Flow Errors

"Storing Failed. SQL Error 8672"

SQL Error 8672 indicates no unique combinations of data found during storage. This will occur when the data coming into the report is not unique, OR the storage settings are not detailed enough to identify uniqueness. 

Resolution

Check for uniqueness in the data coming in problematic parameters where this error is thrown, and also ensure that the storage settings are correct.

NOTE: Ignore logic does not work and the budget template should be considered as set to force store.