I challenged 1Stream's consultants and they say they will research this.
I would like to mention that your statement is correctly, but it just proves that WF is NOT dependant on cubes and dimensionality. Its components, such as dashboards and transformation rules are, but WF is not dependant on any cubes.
Again, your statement is correct:
the Data Sources and Transformation Rules need to know what Cube Dimension are being used and identify the Dimension Members to validate against from 1 specific Cube. "
But I disagree with your other statements:
"There will always be an association with Workflow to a Cube. "
So Workflow and Cube are closely aligned.
An example of a worflow explorer:
Division1
|__ Finance Dept
|__ WF 1 that may update and report from different cubes such as Budget and Planning
|_ WF2 that may update and report from different cubes
|__ Accounting Dept
|_ WF3 that may update and report from different consolidation cubes
|__ WF4 that may update and report from different cubes such as Budget and Planning
Another way to look at it - I believe that Workflow should be people centric, not cube centric - which is the existing design.
In a large company like Walmart, they have people needing different workflows, so WF explorer may go to deeper levels:
Company1:
Division1
|__ Finance Dept1
Company2:
Division1
|__ Finance Dept1
etc.
