Prepare the workflow
Configure sources, parameters, checks and destinations. Mark the steps the operator should see in the wizard, then review those interactions in a simulation.
Illustrative use case
Start the action you need with one button
Add a button to a familiar business app. Users choose parameters or a file, start the prepared workflow and see the result. They do not need to open the workflow editor.
IBM Planning Analytics WorkspaceUBC AnalyticsCorporate portalExcel
HOW THE WORKFLOW RUNS
IBM Planning Analytics WorkspaceUBC AnalyticsCorporate portalExcel
01Prepare the workflow
02Configure the button
03Embed the generated address
04Walk through the task
THE CHALLENGE
What slows the work down
A simple operation requires opening another tool, finding the workflow and remembering each step. Users do not need the full designer, and written instructions do not show current status. They need a clear entry point to a prepared action.
Portal owners, Planning Analytics Workspace analysts and UBC Analytics users.A PRACTICAL EXAMPLE
Illustrative scenario: a finance user presses “Refresh reporting period” in a Planning Analytics Workspace book. The wizard asks for a month and current workbook, performs configured checks and continues processing. The button displays the run state and the configured result feedback.
HOW THE WORKFLOW RUNS
From the first step to the right action.
Configure the button
Set its label, permitted origins and authorised operators. Choose colours, typography and a border that fit the working page while keeping the action easy to recognise.
Embed the generated address
Add the link as a webpage object in Workspace or a suitable portal component. Test authentication and wizard opening in the browser your operators use.
Walk through the task
Enter parameters, select the required file and continue execution. Check ready, running, completed and error behaviour against the actual configured workflow.
VALUE FOR THE TEAM
Make the work repeatable.
- Operators perform a defined task in a familiar context without needing to edit the integration workflow.
- The workflow owner maintains one process even when several authorised people use its embedded button.
- A guided sequence explains the required steps and collects information at the moment the process starts.
Keep control of the result.
- Restrict permitted origins and operator rights; opening the working book alone must not trigger a write.
- For a different domain, verify embedding policies and any permission needed for the wizard popup.
- Test completion, cancellation and failure; refreshing the book’s tables requires a separately defined mechanism.
THE WORKFLOW OUTCOME
Users gain a clear button for repeated operations, while the integration team controls process logic, access and execution history.
Capabilities behind this workflowFROM IDEA TO WORKING FLOW
Bring your challenge. See a way forward.
Sources, rules and outcomes — let’s build the conversation around your workflow.