Skip to main content
Documentation
Documentation
Adaptive Planning
Last Updated: 2026-05-15
Complete Advanced Workflow Tasks

Complete Advanced Workflow Tasks

  • Your administrator shares the hub with you.
  • Access to the destination on the task.
  • The task destination still exists.
  • Access to the relevant levels in access rules and level ownership, if needed.
  • The relevant levels still exist and are available.
  • Your administrator adds you to the relevant associations, user groups, and related assets.
  • Security:
As an individual assigned to a workflow task, you can access the relevant task specific dashboards, sheets and reports directly from the My Tasks area. This task might be 1 task in a sequence of tasks that your administrator created. Your task might involve:
  • Submitting your work for approval, and resubmitting after making changes if the approver sends the task back to you.
  • Submitting your work, and resubmitting after making changes if someone in the hierarchy level above you sends the task back to you.
  • Approving a submitter’s data submission.
  • A to-do action that you need to mark as complete.
For more guidance, refer to the instructions your administrator included on your task.
If enabled, You can access your tasks from the
My Task
 section of the hub or through notifications. Depending on how your administrator sets up your notifications, you might receive the notifications through methods like:
  • Adaptive Planning notifications.
  • Emails.
  • Slack.
  • Workday notifications.
All notes that you include as you work are visible to all other users. Be careful of putting restricted or sensitive information in notes.
  1. Select
    Hubs
     from the main menu.
  2. Select
    My Tasks
    .
  3. Complete the action on the task assigned to you.
    Don’t change the version that’s already selected on the workflow filter.
  4. Depending on the task type, select the appropriate action.
    • Complete
       for to-do tasks.
    • Submit
      ,
      Submit All
      , or
      Send Back
       for hierarchy submit tasks.
    • Submit
       or
      Submit All
       for submit tasks.
    • Approve
      ,
      Approve All
      , or
      Send Back
       for approve tasks.
    You can only select
    Approve All
     after all submit assignees complete their actions on all their levels you are responsible to approve. When you select
    Approval All
    , you approve all the levels that you’re responsible for approving.
When you submit and approve levels on submit approve task groups or submit levels on hierarchy submit tasks, we automatically make the data read-only or available to edit for certain roles for the level, version, and any scoping specified in the definition:
Role
Action
Read-Only Behavior
Submitter
The participating level on the task is in
In Progress
 status and this submitter is working on their task
We allow this submitter to edit this data and any user with edit access to the same data.
Submitter
Submits the level
We make the data read-only for the submitter.
Users who aren’t part of the workflow
N/A
We make the data read-only after the submitter submits.
Approver
Submitter on a higher hierarchy level
The level on the task is in
Not Ready
 status and they’re waiting for their submitter to submit
As an approver or a submitter on a higher hierarchy level, this user can still edit data for that participating level.
Approver
Submitter on a higher hierarchy level
Pending Approval
 means that the submitter has submitted and the level is ready for the approver to approve
In Progress
 means that the lower hierarchy level submitter has submitted and the higher hierarchy level submitter to submit
As an approver or a submitter on a higher hierarchy level, this user can still edit data for that participating level.
Approver
Submitter on a higher hierarchy level
Approves the level
Submits the level
We make the data read-only for the approver after approval.
We make the data read-only for this submitter after submission.
Approver
Submitter on a higher hierarchy level
Sends the level back to the submitter
Sends the level back to the lower hierarchy level submitter
We allow the submitter to edit the data again. This approver still has access to edit the data as long as they have access in your access rules. When the submitter submits, we make the data read-only again for that submitter.
We allow the lower hierarchy level submitter to edit the data again. This higher hierarchy level submitter still has access to edit the data as long as they have access in your access rules. When the higher hierarchy level submitter submits, we make the data read-only again.
Administrators with access to the
Manage Workflows
 permission
N/A
We don’t make the data read-only to administrators as part of the workflows process. As long as you have access to the data in your access rules, you can continue to change the data.
Users with access to the
Import Capabilities
 permission
N/A
We make the data read-only to these users if the workflow locks data.
Users with access to the
Import To All Locations
 permission
N/A
We don’t make the data read-only to these users as part of the workflows process.
We also:
  • Remove the
    Complete
    ,
    Submit
    ,
    Submit All
    ,
    Approve
    ,
    Approve All
    , and
    Send Back
     buttons from tasks when workflow action is complete.
  • Move the workflow to the next task, if any exist. Example: You complete a to-do task fully, then we trigger the next to-do or submit task.
A submit and approve task group must be complete in its entirety before we trigger the next task. Up to 5 approve tasks can exist in a submit and approve task group. Example: If the submit and approve task group contains 1 submit task and 4 approve tasks, assignees must complete all 4 approve tasks before we trigger the next task.