Request for Workflow Design: End-User Report Finalization & Stakeholder Notification with Version Co

PavelSaraev

Hi everyone,

I'm looking to design a workflow and would appreciate your input or guidance on how to set this up effectively in Anaplan.

So, the goal is:

Once end users complete their data input, they should be able to trigger a process that:

1. Notifies stakeholders via email with a link to a report.
2. The report includes:
   • A data table (for base version)
   • A comparison chart (base version vs other versions)
   • A base version (e.g., v5)
   • Three comparison versions for chart (e.g., v1, v2, v3)
3. Stakeholders should be able to:
   • View the report via the email link
   • Switch the comparison versions (e.g., replace v1 with v4)
4. The original link should remain valid, showing the report with default preset versions (as they were at the time of sending).

Thanks in advance!

allison_slaught

Hi PavelSaraev, Currently notification tasks do not include links to pages, but task emails include a link to a page. When planning my workflows, I design my linked pages so the context is a page selector, and when users use the email link or workflow task to navigate to the page, the page selector syncs to the context for the task.

Anaplan's page will display the model's current structure and data so if you want to have data not change from when the task was sent, you may need to use modeling techniques like snapshotting so the data shown in the page is based off snapshot data that users cannot edit and it will not update when the model structure changes.

There are a number of variables that would influence how I'd design the page including whether the engine is classic or polaris, existing structure and conventions of the model that users are used like versions approach ( including whether using native version vs custom versions as a list, parallel versions and use of snapshots), number of users, data volume (number of versions and other dimensions), frequency and nature of hierarchy changes, etc. What you mention about wanting the user to be able to change the default preset versions and reverting to the default if the link is clicked isn't currently natively possible. One of the techniques I'd consider to approximate this behavior is user filters, but my exact recommendation would vary depending on your model. Happy modeling!