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
why did 1Stream design their workflow to start from / associated with a cube?
Acceptance Criteria: Definition of fixed, expected behaviour
I created this enhancement request with 1Stream - do you agree with me ? Do you have any suggestions to improve 1Stream...
What tasks do you want those Workflows to manage?
Normally speaking, Workflows govern the collection, validation and reporting of data entered into the Cube, hence it's logical they are built with association to the Cube and Scenario Types within.
We all know how workflow works, that's why it is illogical to "built with association to the Cube and Scenario Types ".
A workflow can update and run reports from ANY cubes and scenarios. So why not let us build workflows using a Workflow explorer/ tree of any custom design?