Submission Details & Activity
Every Scenario in a Workflow step has a submission behind it, and each submission has a page of its own. It shows where the submission stands, lets you promote or demote it, and keeps the full history: who moved it, when the Scenario was re-shared, which step imported it, and every comment anyone left.
Opening a submission
- Open the project and click the Workflows icon in the navigation bar on the left. Everyone with read access to the project has it.
- Click the Workflow you want. Its submissions page opens.
- The table has one row per Workflow step and one column per Scenario. Each cell is a single submission, showing its name, its status and, if you have the rights, buttons to promote or demote it on the spot.
- Click the submission name. The status tag beside it is not a link.
The page that opens has Details at the top and Activity underneath it.
A Workflow still in ‘Draft’ has no submissions yet. Clicking it opens its step configuration instead. Submissions are created when the Workflow is started.
Contributors have a shortcut. In both the ‘Import Previous Steps’ and ‘Share Workflow Steps’ dialogues in the Scenario Manager, the step in the first column is a link to that step’s submission, so you can read the history behind a set of numbers without leaving your work.
The Details section
Details holds the submission’s current status, the description of the Workflow step it belongs to, and a link to the workspace it was made from.
The description is set on the step rather than the submission, so every submission of that step shows the same text, and it reads ‘No description’ if the step was created without one. If you have no access to the workspace, that field says so instead of linking, but the rest of the page still loads, so you can follow a step that is not yours.
Promoting, demoting and updating
Three buttons sit in the page header, each greyed out when it does not apply to you or to the submission’s current status.
- Promote moves the submission on to the next status. It is unavailable once the submission is at the final status.
- Demote moves it back one status. It is unavailable at the first status, and only project admins can demote out of ‘Done’.
- Update Submission Data re-shares the contributor’s Scenario as it stands now, on top of what was shared before. Creating & Managing Workflows (For Admins) covers when to use it and when it fails.
Each of the three opens a confirmation naming the target status, with an optional comment. What you type there is attached to the entry the action creates under Activity, which makes it the right place to record why you sent a submission back.
A finished Workflow is read-only. Once a Workflow has been completed or stopped, all three buttons and the comment box are disabled. The history stays visible, but nothing more can be added to it.
Activity
Activity lists everything that has happened to the submission, newest first. Each line names the person, what they did and when.
| You see | What happened |
|---|---|
| promoted to ‘Preview’ | Someone moved the submission on to that status. |
| demoted to ‘Open’ | Someone moved it back to that status. |
| updated from ‘Scenario v1’ to ‘Scenario v2’ | The Scenario was re-shared. The two names are the versions before and after; a first share shows only the new one. |
| imported ‘Scenario’ into Step ‘Consolidation’ | Someone pulled this submission’s Scenario into their own step. |
| imported ‘Scenario’ from Step ‘EU Base Assumptions’ | This submission imported a Scenario from that step. |
| a name with text below it | A comment. |
One import appears on both sides. When somebody imports your step, the import is recorded on your submission as well as on theirs, under their name. An import you did not make showing up under your own submission is normal: it means a later step has picked up your numbers.
Commenting on a submission
Click ‘Add a comment’ at the top of Activity, type, and click ‘Comment’. The comment appears at the top of the list straight away and cannot be edited or deleted afterwards.
You can comment while the Workflow is running if you are a project admin or are assigned to one of the step’s states. Everyone else sees the box greyed out.
Each comment e-mails everyone holding a permission on one of that step’s states, apart from you. Mail goes out on a ten-minute cycle rather than immediately, and it is skipped for anyone who has ticked ‘Disable e-mail notifications’ on their user profile. If nobody on your Workflow ever receives these, e-mail is probably not switched on for your Valsight installation; ask your administrator.
The same rules cover the notifications for data updates and status changes, described under Email notifications in Creating & Managing Workflows (For Admins).