The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Automation of workflow using connector BR
We are loading data using SQL connector business rule and it works fine manually. Now looking for a way to load it automatically using a extender business rule and then calling from DM step. All d...
If I understand this correspondence, you want to automate the data load of a Workflow that is bringing in data through a Data Connector. If that is the case, yes, you can automate this process.
1. Create an Extensibility Rules Business Rule. You will probably want to create the logic under Unknown and ExecuteDataMgmtBusinessRuleStep. This is so the logic executes manually and during the execution of a Data Managment Step. For example:
Select Case args.FunctionType
Case Is = ExtenderFunctionType.Unknown, ExtenderFunctionType.ExecuteDataMgmtBusinessRuleStepThe BR would use a trigger file with the naming convention for Workflow Name, Scenario, and Time to identify where to load data to. Set the processing switches ( Import, Transform, Load Cube, Process, Confirm etc ) to perform as part of the data loading process. Then execute the batch
2. Create a Data Management Sequence and an Execute Business Rule Data Management Step and assign the Extensibility Business Rule to the Data Management Step. There is an example of this setup in the Golfstream Reference app. It is under Data Management called Batch File Loading
3. To automate, setup a New Task in Task Scheduler. This is under Application > Tools > Task Scheduler. This is where you can automate how often you want this process to execute.
I believe Task Schedule was a new feature starting in 6.4 or 6.5 so you will need to be on, at the minimum, one of those versions. If not, you can use PowerShell to execute the automation.
Hope this answer addresses your question and points you in the right direction.
TonyToniTone
OneStream Employee
OneStream EmployeeIf I understand this correspondence, you want to automate the data load of a Workflow that is bringing in data through a Data Connector. If that is the case, yes, you can automate this process.
1. Create an Extensibility Rules Business Rule. You will probably want to create the logic under Unknown and ExecuteDataMgmtBusinessRuleStep. This is so the logic executes manually and during the execution of a Data Managment Step. For example:
Select Case args.FunctionType
Case Is = ExtenderFunctionType.Unknown, ExtenderFunctionType.ExecuteDataMgmtBusinessRuleStep
The BR would use a trigger file with the naming convention for Workflow Name, Scenario, and Time to identify where to load data to. Set the processing switches ( Import, Transform, Load Cube, Process, Confirm etc ) to perform as part of the data loading process. Then execute the batch
2. Create a Data Management Sequence and an Execute Business Rule Data Management Step and assign the Extensibility Business Rule to the Data Management Step. There is an example of this setup in the Golfstream Reference app. It is under Data Management called Batch File Loading
3. To automate, setup a New Task in Task Scheduler. This is under Application > Tools > Task Scheduler. This is where you can automate how often you want this process to execute.
I believe Task Schedule was a new feature starting in 6.4 or 6.5 so you will need to be on, at the minimum, one of those versions. If not, you can use PowerShell to execute the automation.
Hope this answer addresses your question and points you in the right direction.
Hello!
Our import automation is set up as mentioned above but it does reference a parameter ("LoadMonth") which is manually maintained by the admins. So while it does work as a semi-"lights out" automation, it still does require a monthly update to change the period that's automatically loading.
Hi Nicole,
You could try using a literal parameter with an Dashboard XFBR string to dynamically retrieve the parameter value based on some criteria.
With kind regards,
Tim Vierhout
Hi Tim,
I could, but there's no criteria right now that's consistent with the timing of the load month changes. Thanks though.
JoakimKNicole, often we see the use of the Global POV in these use cases. If its in use for the normal reporting, it can also be leveraged for the parameter for automation scripts.
