Momentum FAQs

What are Momentum Constants?

Momentum constants are reusable definitions that help you assign roles, track data, and control workflow behaviour inside a Momentum.

They ensure consistency when assigning forms, sending emails, or configuring transitions between workflow nodes.

Why are Constants Important?

Assigning Users: Define who completes which part of the workflow (e.g., applicant, manager).
Reporting: Enable reporting on form responses and workflow outcomes.
Transitions: Power conditional workflows by linking constants to user actions or data.
File Handling: Attach uploaded files from forms to automated emails.

Common Examples of Constants

Application Owner – the user who starts the application.
Manager/Supervisor – the user who reviews or approves a submission.
Form Response – pulls data from a form field (e.g., Approved/Denied).
File Upload Constant – tracks uploaded files to include them in workflow emails.

What are Momentum Transitions?

Momentum Transitions are the pathways that connect Nodes within a Momentum workflow. They determine how an application moves from one step to the next, either automatically or based on conditions.

They allow workflows to branch, pause, or continue depending on user actions, timing, or enrolment data.

What are the Transition Types?

Base Transition – the default pathway that simply connects one Node to the next.
Equals Transition – moves the application forward based on a specific response in a form (e.g., Approved/Denied).
Contains Transition – checks if a text response includes certain values (e.g., “X, Y, or Z”).
Time Transition – delays progression by a set number of days/weeks/months.
Cron Transition – progresses on a scheduled recurrence (e.g., quarterly reviews).
IsEmpty Transition – checks if a user exists in Acorn before moving forward.
User in Cohort Transition – only progresses if the user belongs to a specific cohort.
Is Course Completed Transition – checks if a course has been completed before advancing.
Is Course Enrolled Transition – checks enrolments before determining the next step.

What are commonly used Momentum Workflows?

The most common Momentum workflows support training approvals, study support, and compliance processes.

Examples include:

Professional Development Applications (PDAs): Learners apply for external training, with manager review and approval.
Study Assistance Requests: Staff request financial or time support for formal study, routed through manager and HR approval.
External Training Submissions: Learners record training done outside the LMS and attach evidence for validation.
Withdrawal Requests: Learners request to withdraw from a course or program, requiring supervisor approval.
CPD/Compliance Submissions: Staff upload compliance or CPD evidence for verification and reporting.

Can I restrict a Momentum to a cohort?

Yes — Momentums can be restricted so only specific cohorts have access. When creating or editing a Momentum, you can use the Cohort restriction settings. This ensures only users who belong to the selected cohort(s) can view or participate in that workflow. It’s commonly used for workflows like PDAs, study assistance requests, or compliance submissions that apply to a particular group.

Can you hide a Momentum?

You can’t strictly “hide” a Momentum, but you can control its visibility through Momentum Restrictions.

In the Momentum Restriction area, you can:

Deactivate – makes the Momentum invisible to learners (only admins can see it).
Lock – prevents new applications while keeping existing ones stored.
Close – stops new applications but allows current ones to finish.

These options are often used when you want to make edits or test a workflow before making it live.

To adjust visibility, go to the Momentum Builder, open Momentum Restrictions, and select the appropriate setting. Switch it back when you’re ready to launch to learners.

Can you move Momentum applications?

Yes — applications within a Momentum can be moved between Nodes. You can manually shift applications to a different Node if needed, which is useful for correcting errors or progressing learners through a workflow. The only exception is when an application has already reached a Terminal Node. Once it’s closed out in the terminal stage, it can’t be moved by admins. In those cases, Acorn Support will need to action the request for you.