We follow a design principal to get details from driver cubes via rules, but our final Financial Statements cube at the end of the chain is updated via TI (for performance purposes). We designed this for Cognos Insight, which worked well because users have to commit data to base via a commit button. This button can have a process attached to it that we use to push to the Financial Statements.

The commit button is not necessary in Workspace, so I have layered a conditionally formatted cell beneath a see-through button. When data is entered into the driver cubes, the conditional formatting turns red as a hint to the user that they need to press the button.

I think a better solution for us would be to have the ability to run a process, for the 'Defer on Leaf Data Change' option on the grid refresh button of an exploration widget. This could be passed the synchronisation context and users would not need to press any button at all. When the green data turned blue, it would just run a process in the background. Is there an appetite for this type of functionality?