Overview
Built-in notifications are system messages triggered by certain system events and delivered to recipient as notifications. Notifications are delivered to Console even if the ‘Collaboration Centre’ token is disabled for your tenant.
This article uses the default terminology. Your tenant may be using alternate words for the terms we are using in the article. See Terminology for details.
Note: Although the article mentions zoom integration, the zoom integration was deprecated as of 31st March 2024.
Who gets notifications?
Any userType may receive built-in notifications, depending on the event which triggers a message and notification properties/rules.
Notifications are available from:
- Collaboration Centre, Classic (displayed as private message within a particular chat, all titled as ‘System Message’).
- Notifications side panel in Consoles; this is the only place where Learner can get Notifications in case ‘Collaboration Centre’ token is disabled on their programme.
- Messages in Consoles (within opened chat if ‘Show notifications’ toggler is On).
Notifications side panel in Consoles
Notifications displayed in side panel in Consoles are grouped as follows:
- ‘New’: all unread Notifications
- ‘Today’: all notifications delivered during same calendar day, not within latest 24 hours.
- ‘This week’: all notifications delivered in time period later than 7 days ago and earlier than today (example: if today is 24/07/2023, then considered time period is from 17/07/2023 00:00:00 till 23/07/2023 23:59:59)
- ‘Earlier’: all notifications delivered earlier than 7 days ago.
Notification card properties (Messages, Consoles)
When viewed from Messages (Consoles), notification card is displayed differently from personal messages and consists of the following parts:
- Notification Title
- Notification Main text (may contain links to other parts of the application)
- Additional details (optional element, may be hidden)
- Action button
List of built-in notifications
The list of built-in notifications has been indexed by two different methods - by message title in Console, and type of notification. You can use the table / list below the table to look at the various notification, and then use the hyperlinks to look at the details of the notification.
Built-in notifications - by Message title
The following table lists all the notifications that are sent by Aptem to different users.
- Column 1 shows the Message title in Aptem Console - this appears as a general subject when the templated notification is sent to the recipient. In some cases, a variable is used in the subject line. In the table, such variables are mentioned in angle brackets, and is greyed out. For example: <AssetName> or <Assessment Overall comment>.
- Column 2 shows the users in Aptem that this notification is sent on behalf of.
- Column 3 shows the users in Aptem that this notification is sent to.
- Column 4 shows the Product Area that the notification is related to.
In the table below, click on the subject line to view details of the system notification.
Message title (Console) | Sent on behalf of | Recipient | Product Area |
System Message |
Learner |
Administrator (Learner’s case owner) | Old Courses |
Evidence Accepted |
Learner |
Admin, component owner | Learning Plan |
Evidence Approved |
Admin (Assessor) |
Learner | Learning Plan |
Evidence Approved |
Admin (Trainee Assessor) |
Learner | Learning Plan |
Evidence Referred |
Admin (Assessor) |
Learner | Learning Plan |
Evidence Referred |
Admin (Trainee Assessor) |
Learner | Learning Plan |
System Message |
Admin |
Learner | Old Courses |
System Message |
Administrator |
Learner and/or Administrator (Learner’s case owner) | Trackers |
Congratulations! |
Admin (The one who enrolls learner onto programme) |
Learner | Programme enrollment |
System Message |
Admin (Assessor, the one who commented on evidence assessment) |
Admin (Trainee Assessor, the one whose assessment was commented on by Assessor administrator) | Learning Plan |
New Task | Admin (who triggered task creation for Learner or another Administrator) | Admin or Learner (task assignee) | Tasks |
Updated Task | Administrator (who updates a task of Learner or another Administrator) | Administrator or Learner (task assignee) | Tasks |
Overdue Task/Tasks | Administrator (Learner’s case owner) | Learner | Tasks |
Task Reminder | Administrator (Learner’s case owner) | Learner | Tasks |
Completed Task | Administrator (who completes a task of Learner or another Administrator) | Administrator or Learner (task assignee) | Tasks |
Placement/Workshop | Administrator | Learner | Placements/Workshops |
Placement/Workshop Agreement | Administrator | Learner | Placements/Workshops |
Thank You for Your Recent Application | Administrator | Learner | Placements/Workshops |
Placement/Workshop Application Completed | Learner | Administrator (Learner’s case owner) | Placement/Workshop Wizard |
New Tracker Assigned to You | Administrator (creator/editor or a tracker) | Administrator (Tracker Assignee) | Trackers |
Tracker Updated | Administrator (editing the tracker) | Administrator (Tracker Assignee and/or Tracker Creator) | Trackers |
Tracker Rejected | Administrator (rejecting the tracker) | Administrator (Tracker Assignee and/or Tracker Creator), Learner (Tracker Creator) | Trackers |
New Job Suggestion | Administrator | Learner/Jobseeker | Job Finder |
Respond To Suggested Job | Learner/Jobseeker | Administrator (job suggestion creator) | Job Finder |
Signature Required | Learner (if sent to Administrator/Employer/Referrer); Administrator/Employer/Referrer (if sent to Learner) | Administrator (Learner’s case owner)/Employer (Learner’s Manager)/Referrer (all Learner’s Referrer Organisation referrers)/Learner | Reviews |
File Sent | Learner, Administrator, Referrer | Learner, Administrator, Employer, Referrer | Messages |
PDF Created |
Administrator |
Learner | Placements/Workshops |
Overdue Component | Learner | Administrator (Learner’s case owner) | Learning Plan |
Overdue Components | Learner | Administrator (Learner’s case owner) | Learning Plan |
Trainee Tutor Has Marked Evidence | Administrator (Trainee Assessor) | Administrator (Assessor, the author of latest ‘Tutor Feedback Received’/’Comment’ evidence feedback) | Learning Plan |
Evidence Feedback Approved | Administrator (Assessor, the one who validates Trainee Assessor’s evidence assessment) | Administrator (Trainee Assessor, the author of evidence assessment) | Learning Plan |
Evidence Feedback | Administrator (Assessor, the one who validates Trainee Assessor’s evidence assessment) | Administrator (Trainee Assessor, the author of evidence assessment) | Learning Plan |
System Message | Learner (if sent to Administrator/Employer/Referrer); Administrator/Employer/Referrer (if sent to Learner) | Administrator (Learner’s case owner)/Employer (Learner’s Manager)/Referrer (all Learner’s Referrer Organisation referrers)/Learner | Compliance documents |
Tracker Accepted | Administrator | Administrator (Learner’s case owner) or Learner | Trackers |
Tracker Rejected | Administrator Recipient |
Administrator (Learner’s case owner) or Learner | Trackers |
New Tracker Created | Administrator or Learner (as a Tracker creator) | Administrator (Learner’s case owner) | Trackers |
QA ‘Accepted’ Feedback | Administrator (Internal Verifier, the one who validates evidence assessment) | Administrator (Trainee Assessor/Assessor, the author of evidence assessment) | Learning Plan |
QA Feedback Actioned | Administrator (Internal Verifier, the one who validates evidence assessment) | Administrator (Trainee Assessor/Assessor, the author of evidence assessment) | Learning Plan |
Change Of Contact Details Accepted | Administrator (the one who approves the tracker) | Learner | Trackers |
Change Of Contact Details Rejected | Administrator (the one who rejects the tracker) | Learner | Trackers |
Start Contributing To Your Review | Administrator (Learner’s case owner) | Learner | Review |
Review Ready For Contribution | Learner | Employer (Learner’s Manager) | Review |
Complete Your Assessment | Administrator (the one who resets Learner’s results) | Learner | Aptem Assess |
Built-in notifications - by event
Click on the notification view details of the system notification.
- Notify case owner when Learner finishes a verifiable old courses asset.
- Notify component owner if Learner adds a new evidence to their Learning Plan.
- Notify Learner if Assessor accepts Learning Plan evidence.
- Notify Learner when Assessor confirms Trainee Assessor’s evidence approval.
- Notify Learner if Assessor rejects Learning Plan evidence.
- Notify Learner if Assessor confirms evidence referral made by Trainee Assessor.
- Notify Learner when Administrator completes ‘old course’ asset assessment.
- Notify/Send message to Learner and/or Learner’s case owner from the ‘Return to learning’ tracker form.
- Notify Learner when they are enrolled to an Onboarding or Delivery programme.
- Notify Administrator when another Administrator leaves a comment on their Learning Plan assessment.
- Notify Learner/Administrator when a new task is created for them.
- Notify Learner/Administrator when an existing task is being updated.
- Notify Learner on their overdue tasks, on a nightly basis.
- Notify Learner on their upcoming task(s), on a nightly basis.
- Notify Learner/Administrator when an existing task has been marked as completed.
- Notify Learner when Administrator enrols them on a Placement/Workshop.
- Notify Learner when Administrator uploads Placement/Workshop Agreements documents or marks them as Skipped.
- Notify Learner when Administrator rejects Placement/Workshop enrolment.
- Notify Learner’s case owner when Learner has finished the ‘Application’ step of Placement/Workshop wizard.
- Notify Administrator when they are assigned to a tracker.
- Notify Tracker Creator and/or Tracker Assignee in case there are changes applied to a Tracker.
- Notify Tracker Creator and/or Tracker Assignee if Tracker is marked as Rejected.
- Notify Jobseeker when a new job is suggested by the Administrator.
- Notify Administrator about Jobseeker’s response to suggested job.
- Notify required Signatory about Review document requiring their signature.
- Notify Aptem User on a new file received via Messages/Collaboration Centre.
- Notify Learner when Administrator attaches a ‘Standard parental agreement’ to their Placement enrolment.
- Notify Learner’s case owner about a single overdue Learning Plan component.
- Notify Learner’s case owner about multiple overdue Learning Plan components.
- Notify Assessor when Trainee Assessor responds to ‘Tutor Feedback Received’/ ‘Comment’ evidence assessment.
- Notify Trainee Assessor when their evidence assessment is confirmed by Assessor.
- Notify Trainee Assessor when their evidence assessment is referred by Assessor.
- Notify required Signatory about Compliance document requiring their signature.
- Notify Learner’s case owner and/or Learner about Process automation Tracker being processed (closed).
- Notify Learner’s case owner and/or Learner about Process automation Tracker being rejected.
- Notify Learner’s case owner when a new ‘Change of Name’ or ‘Change of Address’ tracker is created.
- Notify evidence assessment author when their assessment is confirmed by IQA (Internal Verifier).
- Notify evidence assessment author when their assessment is rejected by IQA (Internal Verifier).
- Notify Learner when their ‘Change of Contact Details’ request has been approved by Tutor.
- Notify Learner when their ‘Change of Contact Details’ request has been rejected by Tutor.
- Notify Learner when a Review instance is ready for their contribution.
- Notify Employer when their Learner’s Review instance is ready for their contribution.
- Notify Learner when their Aptem Assess Cognitive Assessment results are reset by Tutor.
Details of built-in notifications
In this section, you will find the following details for each notification:
- Product area
- Sender
- Recipient
- Event that triggers the notification
- Message Template (Classic)
- Message Template (Console)
Notify case owner when Learner finishes a verifiable old courses asset
Product area: Old Courses
Sender: Learner
Recipient: Administrator (Learner’s case owner)
Event: Triggered when Learner finishes either old course asset Verifiable by Tutor or asset which raw URL contains ‘SkillAssessment’ (Questionnaires), as part of old course (from old course player, Classic).
List of Questionnaires with ‘SkillAssessment’ in their raw URL:
- CV Knowledge Questionnaire
- Power Words Knowledge Questionnaire
- Employment & Achievements Knowledge Questionnaire
- Skills Knowledge Questionnaire
- Hobbies, Interests & Additional Information Knowledge Questionnaire
- Reference Knowledge Questionnaire
- Preparing for your interview knowledge questionnaire
- Interview questions knowledge questionnaire
- Teamwork knowledge questionnaire
- Job application knowledge questionnaire
- Constructing a letter knowledge questionnaire
- Check your understanding
- Understanding customers knowledge
- Numeracy Test
- Literacy Test
- Understanding motivation knowledge questionnaire
Message Template (Classic):
Title: "System Message"
Text: "Dear administrator
User <Sender Fullname> has completed course exercise."
Note: <Sender Fullname> is a link leading to corresponding asset in old course player (if Learner clicks) or to “Course assessment” page filtered by Sender fullname and Status=”Pending” (if Administrator clicks), opened in a new browser tab.
Example:
System Message
Dear administrator
User Edmund Croyle has completed course exercise.
Message Template (Console):
Title: "System Message"
Text: "Dear administrator
User <Sender Fullname> has completed course exercise."
Note: <Sender Fullname> is a link leading to Dashboard (if Learner clicks) or to Caseload Dashboard (if Tutor clicks), opened in the same browser tab.
Action button: None
Example:
System Message
Dear administrator
User Edmund Croyle has completed course exercise.
Notify component owner if Learner added a new Learning Plan evidence
Product area: Learning Plan
Sender: Learner
Recipient: Admin, component owner
Event: Triggered once a Learner adds a new evidence to the Learning Plan component. Also applies when an auto-generated evidence is being added on behalf of Learner’s name (for instance, Digital Learning component evidence).
NOTE: doesn't apply if Admin or Employer adds an evidence on behalf of Learner.
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> added evidence related to: <Component Type> - <'Component'> <Component Name>"
Note: The Link to 'Component Name' leads to the learner's learning plan, and opens in a new browser tab with relevant component details expanded.
Example:
System Message
Edmund Croyle added evidence related to: Scheduled online event – Component Course introduction catch-up
Message Template (Console):
Title: "Evidence Added"
Main text if Recipient views: "<Sender Fullname> added evidence related to: <Component Type> - <Component Name>"
Main text if Sender views: "You added evidence related to: <Component Type> - <Component Name>"
Action button: "View Evidence"
'Component Name' link and "View Evidence" action button lead to Learner's Learning Plan opened in the same tab with Mark Evidence page expanded (for Admin) or Component details side panel (for Learner).
Example:
Evidence Added
Edmund Croyle added evidence related to: Scheduled online event – Course introduction catch-up
Notify Learner if Assessor accepted Learning Plan evidence
Product area: Learning Plan
Sender: Admin (Assessor)
Recipient: Learner
Event: Triggered when Assessor admin accepts Learning Plan evidence
NOTE: applies even if Learner is not an evidence owner
NOTE2: applies even when Assessor is an owner of evidence themselves (if Assessor added an evidence and accepted it)
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> approved evidence for the <Component Type> - <'Component'> <Component Name>
<Sender's assessment comment>"
Link is attached to 'Component Name' leading to Learner's Learning Plan opened in a new browser tab with relevant component details expanded.
Example:
System Message
Matthew Barker approved evidence for the Mentoring - Component Mentoring July 2023
Everything looks fine, thank you
Message Template (Console):
Title: "Evidence Approved"
Text if Sender views: "You approved evidence related to: <Component Type> - <Component Name>. The feedback is as follows:"
Text if Recipient views: "<Sender Fullname> approved evidence related to: <Component Type> - <Component Name>. The feedback is as follows:"
Additional details: “<Sender's assessment comments>”
Action button: "View Evidence"
For the Administrator, the 'Component Name' link and "View Evidence" action button lead to the learner's learning plan, which opens in the same tab with Mark Evidence page expanded.
For the Learner, the 'Component Name' link and the "View Evidence" action button lead to a download of the Assessment report PDF file in a new browser tab.
Example:
Evidence Approved
Matthew Barker approved evidence for the Mentoring - Mentoring July 2023.
The feedback is as follows:
Everything looks fine, thank you”
Notify Learner when Assessor confirms Trainee Assessor’s evidence approval
Product area: Learning Plan
Sender: Admin (Trainee Assessor)
Recipient: Learner
Event: Triggered when Assessor confirms Trainee Assessor's ‘Accepted’ evidence assessment results (i.e. when evidence status is ‘Trainee Accepted’ and Assessor selects “Accept Trainee Tutor Marking” option from Mark Evidence form in Console)
NOTE: applies even if Learner is not an evidence owner
NOTE2: Notification text will contain Trainee Assessor's assessment comment
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> approved evidence for the <Component Type> - <'Component'> <Component Name>
<Sender's assessment comment>"
The link to 'Component Name' leads to the learner's learning plan, and opens in a new browser tab with relevant component details expanded.
Example:
System Message
Cameron Metcalfe approved evidence for the Mentoring - Component Mentoring July 2023
I can confirm the task may be marked as completed, everything is good
Message Template (Console):
Title: "Evidence Approved"
Main text if Sender views: "You approved evidence related to: <Component Type> - <Component Name>. The feedback is as follows:”
Main text if Recipient views: "<Sender Fullname> approved evidence related to: <Component Type> - <Component Name>. The feedback is as follows:”
Additional details: “<Sender's assessment comments>”
Action button: "View Evidence"
For the Administrator, the 'Component Name' link and "View Evidence" action button lead to the learner's learning plan, which opens in the same tab with Mark Evidence page expanded.
For the Learner, the 'Component Name' link and the "View Evidence" action button lead to a download of the Assessment report PDF file in a new browser tab.
Example:
Evidence Approved
Cameron Metcalfe approved evidence related to: Mentoring - Mentoring July 2023.
The feedback is as follows:
I can confirm the task may be marked as completed, everything is good”
Notify Learner if Assessor rejected Learning Plan evidence
Product area: Learning Plan
Sender: Admin (Assessor)
Recipient: Learner
Event: Triggered when Assessor admin refers Learning Plan evidence
NOTE: applies even if Learner is not an evidence owner
NOTE2: applies even when Assessor is an owner of evidence themselves (if Assessor added an evidence and referred it)
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> referred evidence for the <Component Type> - <'Component'> <Component Name>
<Sender's assessment comment>"
Link is attached to 'Component Name' leading to Learner's Learning Plan opened in a new browser tab with relevant component details expanded.
Example:
System Message
Matthew Barker referred evidence for the Mentoring - Component Mentoring July 2023
Please could you provide more details.
Message Template (Console):
Title: "Evidence Referred"
Text: "Evidence has been referred in relation to: <Component Type> - <Component Name>. Please review the following feedback:
Additional details: “<Sender's assessment comments>"
Action button: "View Evidence"
For the Administrator, the 'Component Name' link and "View Evidence" action button lead to the learner's learning plan, which opens in the same tab with Mark Evidence page expanded.
For the Learner, the 'Component Name' link and the "View Evidence" action button lead to a download of the Assessment report PDF file in a new browser tab.
Example:
Evidence Referred
Evidence has been referred in relation to: Mentoring - Mentoring July 2023.
Please review the following feedback:
Please could you provide more details
Notify Learner if Assessor confirms evidence referral made by Trainee Assessor
Product area: Learning Plan
Sender: Admin (Trainee Assessor)
Recipient: Learner
Event: Triggered when Assessor confirms Trainee Assessor’s ‘referral’ result on Learning Plan evidence assessment (i.e. when evidence status is ‘Trainee Referred’ and Assessor selects “Agree with Trainee Tutor Referral Decision” option from Mark Evidence form in Console)
NOTE: applies even if Learner is not an evidence owner
NOTE2: Notification text will contain Trainee Assessor's assessment comment
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> referred evidence for the <Component Type> - <'Component'> <Component Name>
<Sender's assessment comment>"
Link is attached to 'Component Name' leading to Learner's Learning Plan opened in a new browser tab with relevant component details expanded.
Example:
System Message
Cameron Metcalfe referred evidence for the Mentoring - Component Mentoring July 2023
Please could you provide more details
Message Template (Console):
Title: "Evidence Referred"
Text: "Evidence has been referred in relation to: <Component Type> - <Component Name>. Please review the following feedback:”
Additional details: “<Sender's assessment comments>"
Action button: "View Evidence"
For the Administrator, the 'Component Name' link and "View Evidence" action button lead to the learner's learning plan, which opens in the same tab with Mark Evidence page expanded.
For the Learner, the 'Component Name' link and the "View Evidence" action button lead to a download of the Assessment report PDF file in a new browser tab.
Example:
Evidence Referred
Evidence has been referred in relation to: Mentoring - Mentoring July 2023.
Please review the following feedback:
Please could you provide more details
Notify Learner when Administrator completes ‘old course’ asset assessment
Product area: Old Courses
Sender: Admin
Recipient: Learner
Event: Triggered when Administrator completes an assessment on ‘old course’ asset finished by Learner from Classic Course Player. Assessment should be performed from “Outstanding approvals” page (“Course assessment” tile).
‘Approved’ asset has ‘Overall’ criteria set to ‘Yes’;
‘Rejected’ asset has ‘Overall’ criteria set to ‘No’.
Message Template (Classic):
Title: "System Message"
Text if asset Rejected: "You have not passed <AssetName> with the following comments:
<Assessment Overall comment>"
Text if asset Approved: "Well done. You have passed <AssetName> with the following comments:
<Assessment Overall comment>"
‘<AssetName>’ is a link leading to Classic Course Player page with corresponding asset selected (if Learner clicks) and “Course assessment” page filtered by Learner fullname (if Administrator clicks), opened in a new browser tab.
Examples:
System Message
You have not passed Manchester United - A case study with the following comments:
"Hi Edmund, please could you re-take the asset one more time and pay more attention to the details.
Regards
Theodore Reese"
System Message
Well done. You have passed Are you a team player? with the following comments:
"Great job! Exactly what was expected!".
Message Template (Console):
Title: "System Message"
Text if asset Rejected: "You have not passed <AssetName> with the following comments:
<Assessment Overall comment>"
Text if asset Approved: "Well done. You have passed <AssetName> with the following comments:
<Assessment Overall comment>"
Action button: None
‘<AssetName>’ is a link leading Dashboard (if Learner clicks) and Caseload Dashboard (if Administrator clicks), opened in the same browser tab.
Example:
System Message
You have not passed Manchester United - A case study with the following comments:
"Hi Edmund, please could you re-take the asset one more time and pay more attention to the details.
Regards
Theodore Reese"."
Example:
System Message
Well done. You have passed Are you a team player? with the following comments:
"Great job! Exactly what was expected!".
Notify / Send message to Learner and/or Learner’s case owner from the ‘Return to learning’ tracker form
Product area: Trackers
Sender: Administrator
Recipient: Learner and/or Administrator (Learner’s case owner)
Event: Triggered when Administrator creates/edits ‘Return to learning’ process automation tracker.
Message to Learner’s case owner (Administrator) will be sent if ‘Message to Primary Tutor' /’New message to Primary Tutor' is populated on create/edit tracker form and form is submitted;
Message to Learner will be sent if ‘Message to Learner’ is populated on edit tracker form and form is submitted – the field becomes available on edit tracker form only in case tracker status is selected as Rejected or Process.
Message Template (Classic):
Title: "System Message"
Text if sent to Administrator: "<Message to Primary Tutor>"
Text if sent to Learner: "<Message to Learner>"
Example:
System Message
Please could you take a look at the case and let me know if Learner is ready to get enrolled onto the programme back."
Message Template (Console):
Title: "System Message"
Text if sent to Administrator: "<Message to Primary Tutor>"
Text if sent to Learner: "<Message to Learner>"
Action button: None
Example:
System Message
Please could you take a look at the case and let me know if Learner is ready to get enrolled onto the programme back."
Notify Learner when they are assigned to Onboarding or Delivery programme
Product area: Programme enrollment
Sender: Admin (The one who enrolls learner onto programme)
Recipient: Learner
Event: Triggered when Administrator enrols Learner onto Onboarding or Delivery programme (via any possible way, even via Users bulk upload option)
Message Template (Classic):
Title: "System Message"
Text: "You’ve been enrolled on <Programme name>"
Link is attached to 'Programme Name' leading to Learner's Learning Plan opened in the same browser tab.
Example:
"System Message
You've been enrolled on D1 - Compliance docs "
Message Template (Console):
Title: "Congratulations!"
Main text if Recipient views: "You’ve been enrolled on <Programme name>"
Main text if Sender views: "<Recipient Fullname> has been enrolled on <Programme name>"
Action button: "View Learning Plan"
The 'Programme name’ link and "View Learning Plan" action button lead to Learner's Learning Plan opened in the same tab.
Example:
Congratulations!
You've been enrolled on D1 - Compliance docs”
Notify Administrator when another Administrator left a comment on their LP assessment
Product area: Learning Plan
Sender: Admin (Assessor, the one who commented evidence assessment)
Recipient: Admin (Trainee Assessor, the one who’s assessment was commented by Assessor administrator)
Event: Triggered when there is an assessment left by one Administrator on Learning Plan evidence and another Administrator comments it (navigates to Learner’s Learning Plan Overview page (Classic), launches ‘Evidence Assessment’ modal form, selects an Assessment left by other Administrator from “Assessment History” pane, provides their own feedback and selects ‘Comment’ option on submitting the form)
Message Template (Classic):
Title: "System Message"
Text: "Assessment feedback received
<raw link to evidence assessment>"
Link is leading to Learner's Learning Plan opened in the new browser tab with commented evidence assessment form launched automatically.
Example:
System Message
Assessment feedback received
/MWS.LearningProgrammes/LearningProgramme/OverviewMessageLink?userId=8&evidenceId=1013&componentId=2&openAssessment=True
Message Template (Console):
Title: "System Message”
Main text: "Assessment feedback received
<raw link to evidence assessment>"
Action button: none
Example:
System Message
Assessment feedback received
/MWS.LearningProgrammes/LearningProgramme/OverviewMessageLink?userId=8&evidenceId=1013&componentId=2&openAssessment=True
Notify Learner/Administrator when a new task is created for them
Product area: Tasks
Sender: Admin (who triggered task creation for Learner or another Administrator)
Recipient: Admin or Learner (task assignee)
Event: Triggered when Administrator creates a task for Learner or another Administrator:
- Manually
- Via creating personal Learning Plan component of task-based types (Assignment, Meeting, Online training – external, End-point assessment, Mentoring, Shadowing)
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> created a Task: <type of task>"
<Type of task> is a link that leads to the corresponding task, launched in a new browser tab once clicked.
Example:
System Message
Theodore Reese created a(n) task: Feedback"
Message Template (Console):
Title: "New Task”
Main text if Recipient views: "<Sender Fullname> created a Task: <type of task>”
Main text if Sender views: "You created a Task: <type of task>"
Action button: “View Task”
The '<Type of task>’ link and “View Task” action button lead to the corresponding Edit Task form being launched in the same browser tab.
Example:
New Task
Theodore Reese created a task: Feedback
Notify Learner/Administrator when an existing task is being updated
Product area: Tasks
Sender: Administrator (who updates a task of Learner or another Administrator)
Recipient: Administrator or Learner (task assignee)
Event: Triggered when Administrator amends a task for Learner or another Administrator:
- Manually
- Via updating task-related fields in existing personal Learning Plan component of task-based types (Assignment, Meeting, Online training – external, End-point assessment, Mentoring, Shadowing)
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> updated a Task: <type of task>"
<Type of task> is a link leading to a corresponding task being launched in a new browser tab once clicked.
Example:
System Message
Theodore Reese updated a(n) task: Feedback
Message Template (Console):
Title: "Updated Task”
Main text if Recipient views: "<Sender Fullname> updated a Task: <type of task>”
Main text if Sender views: "You updated a ‘Task’: <type of task>"
Action button: “View Task”
The ‘<Type of task>’ link and “View Task” action button lead to corresponding Edit Task form being launched in the same browser tab.
Example:
Updated Task
Theodore Reese updated a task: Feedback
Notify Learner on overdue tasks, nightly
Product area: Tasks
Sender: Administrator (Learner’s case owner)
Recipient: Learner
Event: If ‘Send overdue task reminders’ option is enabled in account programme (Collaboration Centre token);
Triggered nightly, and sent to Learners who have logged in to the platform during the past 3 months and have overdue tasks (incomplete with Due Date < current date, not cancelled).
Message Template (Classic):
Title: "System Message"
Text: “You have <number of overdue tasks> overdue 'Task/Tasks'>"
“<Number of overdue tasks> overdue Task/Tasks” is a link leading to Tasks page; it opens in a new browser tab once clicked.
Example:
System Message
You have 13 overdue Tasks
Message Template (Console):
Title: "Overdue Task/Tasks”
Main text if Recipient views: "You have <number of overdue tasks> overdue Task/Tasks”
Main text if Sender views: "<Recipient Fullname> has <number of overdue tasks> overdue 'Task/Tasks'>”
Action button: “View Task/Tasks”
The “<Number of overdue tasks> overdue Task/Tasks” link and “View Task/Tasks” lead to the Tasks page, opened in the same browser tab with Overdue side panel expanded.
Example:
Overdue Tasks
You have 13 Overdue Tasks
Notify Learner on upcoming task(s), nightly
Product area: Tasks
Sender: Administrator (Learner’s case owner)
Recipient: Learner
Event: Triggered nightly, and sent over to Learners who have Task(s) configured to send a reminder in X days before “Due Date” from Task details form – if Task ‘Due Date’ – X days = current date;
X must be greater than 0;
Task must not be Cancelled or Completed; Notification is being sent on behalf of Learner’s case owner.
Message Template (Classic):
Title: "System Message"
Text: “You have an upcoming Task: <Task type>"
“<Task type>” is a link leading to Tasks page opened in a new browser tab once clicked.
Example:
System Message
You have an upcoming Task: Marking
Message Template (Console):
Title: "Task Reminder”
Main text if Recipient views: "You have an upcoming Task: <task type>”
Main text if Sender views: "<Recipient Fullname> an upcoming Task: <task type>”
Action button: “View Task”
The “<Task type>” link and “View Task" lead to the corresponding Edit Task form opened in the same browser tab.
Example:
Task Reminder
You have an upcoming Task: Marking
Notify Learner/Administrator when an existing task is being marked as completed
Product area: Tasks
Sender: Administrator (who completes a task of Learner or another Administrator)
Recipient: Administrator or Learner (task assignee)
Event: Triggered when Administrator marks a task as Completed for Learner or another Administrator:
- Manually
- Via using ‘Complete’ option on task-based Learning Plan components (Assignment, Meeting, Online training – external, End-point assessment, Mentoring, Shadowing)
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> completed a Task: <type of task>"
<Type of task> is a link leading to a corresponding task being launched in a new browser tab once clicked.
Example:
System Message
Theodore Reese updated a(n) task: Feedback"
Message Template (Console):
Title: "Completed Task”
Main text: "This Task has been completed: <type of task>”
Action button: “View Task”
‘<Type of task>’ link and “View Task” action button lead to corresponding Edit Task form being launched in the same browser tab.
Example:
Completed Task
This task has been completed: Feedback
Notify Learner when Administrator enrols them on a Placement/Workshop
Product area: Placements/Workshops
Sender: Administrator
Recipient: Learner
Event: available only if ‘Send workshop notification’ option is enabled in account programme (Collaboration Centre token);
Triggered when Administrator enrols Learner on Placement/Workshop with EndDate > today.
Trigger for re-sending enrolment notification: when Administrator enables ‘Use Zoom’ option on Placement profile AND Learner is already enrolled AND enrolment EndDate > today.
Message Template (Classic):
Title: "System Message"
Text: “Your ‘placement/workshop’> with <Placement/Workshop organisation name> has been arranged.
[if more than 1 day]
Start date: <Placement/Workshop enrolment start date>
End date: <Placement/Workshop enrolment end date>
[if only 1 day]
Date: <Placement/Workshop enrolment start date>
Time: <Placement/Workshop enrolment working hours – separated by comma if two sessions>
<Placement/Workshop organisation name>
[if ‘Use Zoom’ is activated in Placement/Workshop profile]
Join Zoom
[otherwise]
<Placement/Workshop address, including postal code>
Please sign into your Aptem account for more details by clicking /MWS.Organizer/ToDoTask/Calendar.”
‘Join Zoom’ is a link leading to Zoom meeting URL being opened in a new browser tab;
‘/MWS.Organizer/ToDoTask/Calendar’ is a link leading to Tasks page opened in a new browser tab.
Example:
System Message
Your placement/workshop with Reynolds-Bayer has been arranged.
Start date: 04-09-2023
End date: 06-09-2023
Time: 9:00-12:00, 13:00-17:00
Reynolds-Bayer
Join Zoom
Please sign into your Aptem account for more details by clicking ...."
Message Template (Console):
Title: "Placement/Workshop”
Main text if Recipient views: "Your ‘Placement/Workshop’ with <Placement/Workshop organisation name> has been arranged.
Start: <Placement/Workshop enrolment start date> End: <Placement/Workshop enrolment end date> Time: <Placement/Workshop enrolment working hours – separated by comma, if two sessions>”
Main text if Sender views: "<Recipient Fullname>’s ‘Placement/Workshop’> with <Placement/Workshop organisation name> has been arranged.
Start: <Placement/Workshop enrolment start date> End: <Placement/Workshop enrolment end date> Time: <Placement/Workshop enrolment working hours – separated by comma, if two sessions>”
Action button: “View Details”
The “View Details” action button leads to the learner’s Tasks page, opened in the same browser tab with the ‘Overdue’ side pane expanded.
Example:
Placement/Workshop
Your placement/workshop with Reynolds-Bayer has been arranged.
Start: 04 Sep 2023 End: 06 Sep 2023 Time: 9:00-12:00, 13:00-17:00
Notify Learner when Administrator uploads Placement/Workshop Agreements documents or marks them as Skipped
Product area: Placements/Workshops
Sender: Administrator
Recipient: Learner
Event: available only if ‘Send workshop notification’ option is enabled in account programme (Collaboration Centre token);
Triggered when Administrator uploads all required Agreements documents into Placement/Workshop Agreements or marks them as ‘Skipped’;
‘Agreements’ form is only available in Classic (Placement/Workshop profile or User profile) from ‘Agreements’ option displayed for placement/workshop enrolment.
Is not re-sent to Learner if placement/workshop enrolment has ever got all agreements already uploaded/skipped and these are being re-uploaded/skipped again now.
Message Template (Classic):
Title: "System Message"
Text: “You have been allocated a ‘placement/workshop’> opportunity at <Placement/Workshop organisation name>
At <Placement/Workshop address, excluding postal code>
On <Placement/Workshop enrolment start date> to <Placement/Workshop enrolment end date>
Please view and complete the required paperwork for your placement/workshop here.”
‘Here’ is a link leading to Learner’s Placement/Workshop Wizard opened in a new browser tab.
Example:
System Message
You have been allocated a placement/workshop opportunity at Britches of Georgetown
At 13 Lairg Road, NEWBARN, United Kingdom
On 11/09/2023 to 18/09/2023
Please view and complete the required paperwork for your placement/workshop here.
Message Template (Console):
Title: "Placement/Workshop Agreement”
Main text if Recipient views: "You have been allocated a Placement/Workshop at <Placement/Workshop organisation name>.
Please view and complete the required paperwork for your Placement/Workshop here.
Start: <Placement/Workshop enrolment start date> End: <Placement/Workshop enrolment end date>
Location: <Placement/Workshop address, excluding postal code>”
Main text if Sender views: "<Recipient Fullname> has been allocated a Placement/Workshop at <Placement/Workshop organisation name>.
Start: <Placement/Workshop enrolment start date> End: <Placement/Workshop enrolment end date>
Location: <Placement/Workshop address, excluding postal code>”
Action button: “View Agreement”
The ‘Here’ link and “View Agreement” action button lead to Learner’s Placement/Workshop Wizard page opened in Classic in a new browser tab.
Example:
Placement/Workshop Agreement
You have been allocated a placement/Workshop opportunity at Study IT.
Please view and complete the required paperwork for your placement/Workshop here.
Start: 11 Sep 2023
End: 18 Sep 2023
Location: 68 Baldock Street, NEWTOWN, United Kingdom
Notify Learner when Administrator rejects Placement/Workshop enrolment
Product area: Placements/Workshops
Sender: Administrator
Recipient: Learner
Event: available only if ‘Send workshop notification’ option is enabled in account programme (Collaboration Centre token);
Triggered when Administrator rejects Shortlisted/Applied placement/workshop enrolment.
Message Template (Classic):
Title: "System Message"
Text: “Unfortunately, your application has been rejected, this is due to '<reject reason>'.”
Example:
System Message
Unfortunately, your application has been rejected, this is due to 'Unfortunately, we ran out of placements available.'
Message Template (Console):
Title: "Thank You for Your Recent Application”
Main text if Recipient views: "Unfortunately, your application has been rejected, this is due to:”
Main text if Sender views: "<Recipient Fullname>’s application has been rejected, this is due to:”
Additional details: “<reject reason>”
Action button: None
Example:
Thank You for Your Recent Application
Unfortunately, your application has been rejected, this is due to:
Unfortunately, we ran out of placements available."
Notify Learner’s case owner when Learner has finished ‘Application’ step of Placement/Workshop Wizard
Product area: Placements/Workshop Wizard
Sender: Learner
Recipient: Administrator (Learner’s case owner)
Event: available only if ‘Send workshop notification’ option is enabled in account programme (Collaboration Centre token);
Triggered when Learner finishes ‘Application’ step of Placement/Workshop Wizard.
Message Template (Classic):
Title: "System Message"
Text: “<Sender Fullname> has completed the initial Placement/Workshop application.”
Example:
System Message
Steven Hawkinson has completed the initial placement/workshop application.
Message Template (Console):
Title: "Placement/Workshop Application Completed”
Main text if Sender views: "You’ve completed the initial Placement/Workshop application.”
Main text if Recipient views: "<Sender Fullname> has completed the initial Placement/Workshop application.”
Action button: None
Example:
Placement/Workshop Application Completed
Steven Hawkinson has completed the initial placement/Workshop application.
Notify Administrator when they are assigned to a tracker
Product area: Trackers
Sender: Administrator (creator/editor or a tracker)
Recipient: Administrator (Tracker Assignee)
Event: Triggered when a Tracker is being created or edited, and Assignee is not empty and not equal to the logged in Administrator.
Message Template (Classic):
Title: "System Message"
Text: “The Tracker for <Learner Fullname> has been assigned to you.”
‘Tracker’ is a link leading to corresponding Edit Tracker page opened in a new browser tab.
Example:
System Message
The Tracker for Sandra Wilkinson has been assigned to you.
Message Template (Console):
Title if Recipient views: "New Tracker Assigned to You”
Title if Sender views: "New Tracker Assigned to <Recipient Fullname>”
Main text if Recipient views: "The <Tracker type> Tracker for <Learner Fullname> has been assigned to you.”
Main text if Sender views: The <Tracker type> Tracker for <Learner Fullname> has been assigned to <Recipient Fullname>.”
Action button: “View Tracker”
The “View Tracker” action button leads to the corresponding Edit Tracker form opened in the same browser tab.
Example:
New Tracker Assigned To You
The job Tracker for Sandra Wilkinson has been assigned to you.
Notify Tracker Creator and/or Tracker Assignee in case there are changes applied to a Tracker
Product area: Trackers
Sender: Administrator (editing the tracker)
Recipient: Administrator (Tracker Assignee and/or Tracker Creator)
Event: Triggered when an Administrator make any changes to an already existing Tracker, and sent over to:
- Tracker Creator if logged in Administrator is not the Tracker Creator;
- Tracker Assignee if logged in Administrator is not the Tracker Assignee.
Message Template (Classic):
Title: "System Message"
Text: “The Tracker for <Learner Fullname> has been update.”
‘Tracker’ is a link leading to the corresponding Edit Tracker page opened in a new browser tab.
Example:
System Message
The Tracker for Sandra Wilkinson has been updated.
Message Template (Console):
Title: "Tracker Updated”
Main text: "The <Tracker type> Tracker for <Learner Fullname> has been updated.”
Action button: “View Tracker”
“View Tracker” action button leads to corresponding Edit Tracker form opened at the same browser tab.
Example:
Tracker Updated
The self-employment Tracker for Sandra Wilkinson has been updated.
Notify Tracker Creator and/or Tracker Assignee in Tracker is marked as Rejected
Product area: Trackers
Sender: Administrator (rejecting the tracker)
Recipient: Administrator (Tracker Assignee and/or Tracker Creator), Learner (Tracker Creator)
Event: Triggered when an Administrator updates Tracker to ‘Rejected’ status, and sent over to:
- Tracker Creator if logged in Administrator is not the Tracker Creator;
- Tracker Assignee if logged in Administrator is not the Tracker Assignee.
Message Template (Classic):
Title: "System Message"
Text: “The Tracker for <Learner Fullname> has been rejected.”
‘Tracker’ is a link leading to corresponding Edit Tracker page opened in a new browser tab.
Example:
System Message
The Tracker for John Creasman has been rejected.
Message Template (Console):
Title: "Tracker Rejected”
Main text if Administrator views: "<Learner Fullname>’s recent <Tracker type> request has been rejected.”
Main text if Learner views: “Your recent <Tracker type> has been rejected. If you have any questions regarding this request, please contact <Sender Fullname>.”
Action button if Administrator views: “View Tracker”
Action button if Learner views: None
“View Tracker” action button leads to corresponding Edit Tracker form opened at the same browser tab.
Example:
Tracker Rejected
John Creasman's recent address change request has been rejected.
Notify Jobseeker upon new job suggestion created by Administrator
Product area: Job Finder
Sender: Administrator
Recipient: Learner/Jobseeker
Event: Triggered when an Administrator suggests a job to Jobseeker from Job Finder page.
Message Template (Classic):
Title: "System Message"
Text: “<Administrator Fullname> suggested a job opportunity: <JobTitle>”
‘<JobTitle>’ is a link leading to Jobseeker’s Suggested jobs page (Job Finder) opened in a new browser tab.
Example:
System Message
Theodore Reese suggested a job opportunity: Commercial Account Executive
Message Template (Console):
Title: "New Job Suggestion”
Main text if Sender views: “You suggested a job opportunity: <JobTitle>”
Main text if Recipient views: “<Sender Fullname> suggested a job opportunity: <JobTitle>”
Action button: “View Job”
The “<JobTitle>” link and the “View Job” action button lead to the corresponding Job item opened in the same browser tab.
Example:
New Job Suggestion
Theodore Reese suggested a job opportunity: Commercial Account Executive
Notify Administrator on Jobseeker’s response to suggested job
Product area: Job Finder
Sender: Learner/Jobseeker
Recipient: Administrator (job suggestion creator)
Event: Triggered when Jobseeker responses to a job suggested by Administrator earlier from Job Finder page.
NOTE: functionality is currently available from Classic only.
Message Template (Classic):
Title: "System Message"
Text: “<Sender Fullname> has responded to the suggested job opportunity – (<JobResponseStatus> - <JobseekerResponseMessage>): <JobTitle>”
‘<JobTitle>’ is a link leading to Jobseeker’s Suggested jobs page (Job Finder) opened in a new browser tab.
Example:
System Message
Margaret Costello has responded to the suggested job opportunity - (Not suitable - Office location is too far away from my home location, I'm afraid. Thanks.): Commercial Account Executive"
Message Template (Console):
Title: "Respond To Suggested Job”
Main text if Recipient views: “<Sender Fullname> has responded to the suggested job opportunity: <JobTitle>”
Main text if Sender views: “You have responded to the suggested job opportunity: <JobTitle>”
Additional details: “<JobResponseStatus>- <JobseekerResponseMessage>”
Action button: “View Job”
“<JobTitle>” link and “View Job” action button lead to corresponding Job item opened at the same browser tab.
Example:
Respond to Suggested Job
You have responded to the suggested job opportunity: Commercial Account Executive
Not suitable- Office location is too far away from my home location, I'm afraid. Thanks.
Notify required Signatory on Review document pending signing
Product area: Reviews
Sender: Learner (if sent to Administrator/Employer/Referrer); Administrator/Employer/Referrer (if sent to Learner)
Recipient: Administrator (Learner’s case owner)/Employer (Learner’s Manager)/Referrer (all Learner’s Referrer Organisation referrers)/Learner
Event: Triggered when a Review PDF document is generated AND there are signatures pending from Signatories configured for Review type (“Signatures” options).
If document is generated and Learner signature is pending, notification is sent on behalf of document creator (Administrator/Employer/Referrer); if other userTypes signatures are pending, notification is sent on behalf of Learner the review/document belongs to.
Example: review type is configured as “Signatures”=Advisor, Employer, Participant, Referrer; scenarios:
1. Administrator is generating Review PDF document (no signatures are put into the document yet); As a result, notifications will be sent to:
- Employer, Learner’s Manager (on behalf of Learner’s name); if Manager is not provided, notification will not be sent over to Employer(s)
- Referrer, all Learner’s Referrer Organisation referrers (on behalf of Learner’s name); if Referrer Organisation is not provided, notification will not be sent over to Referrer(s)
- Administrator, Learner’s case owner – even if Learner’s case owner generated the document themselves (on behalf of Learner’s name);
- Learner (on behalf of Administrator’s name – the one who generated the document in fact)
2. Learner is signing the document (while other signatures are still pending); As a result, notifications will be sent to:
- Employer, Learner’s Manager (on behalf of Learner’s name); if Manager is not provided, notification will not be sent over to Employer(s).
- Referrer, all Learner’s Referrer Organisation referrers (on behalf of Learner’s name); if Referrer Organisation is not provided, notification will not be sent over to Referrer(s).
- Administrator, Learner’s case owner (on behalf of Learner’s name).
Check if should say: "will receive this notif. also when some other signatory signs it, but their sig is still pending.
Message Template (Classic):
Title: "System Message"
Text: “Your signature is required for the Review: <Review - <ProgrammeName> - <ReviewTypeName> <ReviewCreatedDate>>”
‘<Review - <ProgrammeName> - <ReviewTypeName> <ReviewCreatedDate>>’ is a link leading to Review Signatures page (filter applied: User name = Learner Fullname, Document name = <Review - <ProgrammeName> - <ReviewTypeName> <ReviewCreatedDate>>) opened in same browser tab.
Example:
System Message
Your signature is required for the Review: Review - D1 - Rev 3 29/08/2023
Message Template (Console):
Title: "Signature Required”
Main text if Recipient views: “Your signature is required for the Review: <Review - <ProgrammeName> - <ReviewTypeName> <ReviewCreatedDate>>”
Main text if Sender views: “<Recipient Fullname>’s signature is required for the Review: <Review - <ProgrammeName> - <ReviewTypeName> <ReviewCreatedDate>>”
Action button: “Sign”
“<Review - <ProgrammeName> - <ReviewTypeName> <ReviewCreatedDate>>” link and “Sign” action button lead to Signatures page (filter applied: Tab=Signature Required, Type=’Review’, Learner Name = Learner’s Fullname) opened at the same browser tab (if Administrator/Employer clicks), and to Documents page (Signatures Required tab) opened at the same browser tab (if Learner clicks).
Example:
Signature Required
Your signature is required for the Review: Review - D1 - Rev 3 29/08/2023
Notify Aptem User on a new file received via Messages/Collaboration Centre
Note that this will not appear in the Notifications side pane, but will appear in the Messages.
Product area: Messages
Sender: Learner, Administrator, Referrer
Recipient: Learner, Administrator, Employer, Referrer
Event: Sent over to the Recipient once Sender attaches an uploaded file to private message in Messages/Collaboration Centre and confirms sending it.
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> sent a file: <file description>"
<File description> is a link leading to a corresponding file being launched in a new browser tab once clicked.
Example:
System Message
Edmund Croyle sent a file: Additional details on qualification
Message Template (Console):
Title if Sender views: “File Sent”
Title if Recipient views: "File Received”
Main text if Sender views: "You sent a file: <file description>”
Main text if Recipient views: "<Sender Fullname> sent a file: <file description>”
Action button: “View File”
The‘<File description>’ link and “View File” action button lead to the corresponding file being launched in a new browser tab once clicked.
Example:
File Received
Edmund Croyle sent a file: Additional details on qualification
Example:
File Sent
You sent a file: Additional details on qualification
Notify Learner when Administrator attaches Standard parental agreement to Placement enrollment
Product area: Placements/Workshops
Sender: Administrator
Recipient: Learner
Event: Sent over Learner when Administrator attaches ‘Standard parental agreement’ file to Placement enrolment AND selects ‘Message’ option on ‘Agreements’ popup up form.
Message Template (Classic):
Title: "System Message"
Text: "<Sender Fullname> uploaded a file: Standard parental agreement"
‘Standard Parental Agreement’ is showing as a link but in fact it has no anchor.
Example:
System Message
Theodore Reese uploaded a file: Standard parental agreement
Message Template (Console):
Title: “PDF Created”
Main text if Sender views: "You uploaded a file: Standard parental agreement >”
Main text if Recipient views: "<Sender Fullname> uploaded a file: Standard parental agreement”
Action button: “View File”
‘Standard parental agreement’ and “View File” action button do not navigate to any other pages.
Example:
PDF Created
Theodore Reese uploaded a file: Standard parental agreement"
Notify Learner’s case owner on a single overdue Learning Plan component
Product area: Learning Plan
Sender: Learner
Recipient: Administrator (Learner’s case owner)
Event: Triggered nightly and sent over to Learner’s case owner if Learner has 1 overdue Learning plan component.
Learners taken into consideration:
- Of Subscription status = “Full User”
- And Programme Status is other than “Withdrawn”
Components taken into consideration:
- Of Learner’s current programme episode
- “Require evidence” = true
- “Complete by” date = current date
- Component Status is other than “Completed”
Message Template (Classic):
Title: "System Message"
Text: “<Learner Fullname> has an Overdue Component”
‘Overdue Component’ is a link leading to Learner’s Learning Plan with corresponding component expanded, opened in same browser tab.
Example:
System Message
John Creasman has an Overdue Component
Message Template (Console):
Title: "Overdue Component”
Main text if Recipient views: “<Learner Fullname> has an Overdue Component in relation to: <ComponentName>”
Main text if Sender views: “You have an Overdue Component in relation to: <ComponentName>”
Action button: “View Component”
The “<ComponentName>” link and “View Component” action button lead to the learner’s corresponding learning Plan component details opened in the same browser tab.
Example:
Overdue Component
John Creasman has an Overdue Component in relation to: ICT assessment"
Notify Learner’s case owner on several overdue Learning Plan components
Product area: Learning Plan
Sender: Learner
Recipient: Administrator (Learner’s case owner)
Event: Triggered nightly and sent over to Learner’s case owner if Learner has more than 1 overdue Learning plan component.
Learners taken into consideration:
- Of Subscription status = “Full User”
- And Programme Status is other than “Withdrawn”
Components taken into consideration:
- Of Learner’s current programme episode
- “Require evidence” = true
- “Complete by” date = current date
- Component Status is other than “Completed”
Message Template (Classic):
Title: "System Message"
Text: “<Sender Fullname> has<NumberOfOverdueComponents> Overdue Components”
The "<NumberOfOverdueComponents> Overdue Components" link leads to the learner’s learning plan opened in the same browser tab.
Example:
System Message
John Creasman has 2 Overdue Components
Message Template (Console):
Title: "Overdue Components”
Main text if Recipient views: “<Sender Fullname> has <NumberOfOverdueComponents> Overdue Components”
Main text if Sender views: “You have <NumberOfOverdueComponents> Overdue Components”
Action button: “View Components”
“<NumberOfOverdueComponents> Overdue Components” link and “View Components” action button lead to Learner’s Learning Plan opened at the same browser tab.
Example:
Overdue Components
John Creasman has 2 Overdue Components
Notify Assessor when Trainee Assessor responses on ‘Tutor Feedback Received’/’Comment’ evidence assessment
Product area: Learning Plan
Sender: Administrator (Trainee Assessor)
Recipient: Administrator (Assessor, the author of latest ‘Tutor Feedback Received’/’Comment’ evidence feedback)
Event: Triggered on evidence assessment status becoming ‘Trainee Accepted’ or ‘Trainee Referred’ AND evidence having nested assessment hierarchy.
Scenarios:
- ‘Tutor Feedback Received’ assessment:
- There is an evidence in ‘Requires marking’ status
- Trainee Assessor marks evidence as ‘Trainee Accepted’
- Assessor marks evidence as ‘Tutor Feedback Received’ (meaning, Assessor disagrees with Trainee Assessor’s assessment)
- Trainee Assessor marks evidence again (either as ‘Trainee Accepted’ or ‘Trainee Referred’). Results: Assessor will receive a notification authored by Trainee Assessor.
- ‘Comment’ assessment:
- There is as evidence in ‘Requires marking’ status
- Trainee Assessor marks evidence as ‘Trainee Accepted’
- From Classic UI, Assessor selects Trainee Assessor’s assessment and chooses ‘Comment’ option for submitting their own assessment
- Trainee Assessor provides their assessment on the top of Assessor’s comment (so that current status of evidence is either ‘Trainee Accepted’ or ‘Trainee Referred’). Results: Assessor will receive a notification authored by Trainee Assessor.
If there was a sequence of ‘Tutor Feedback Received’/‘Comment’ assessments registered for the same evidence, the most recent one is taken into account (so, Recipient – as assessment author - will be defined based on it).
Message Template (Classic):
Title: "System Message"
Text: “Trainee Tutor has marked evidence related to: <component type> - Component <component name> Please review marking to provide feedback to the trainee Tutor”
‘<Component name>’ and ‘review marking’ are links leading to corresponding evidence assessment modal form opened in new browser tab.
Example:
System Message
Trainee tutor Cameron Metcalfe has marked evidence related to: assignment (task) - component Research Assignment
Please review marking to provide feedback to the trainee tutor.
Message Template (Console):
Title if Recipient views: "Trainee Tutor Has Marked Evidence”
Title if Sender views: “Evidence Marking Submitted”
Main text if Recipient views: “Trainee Tutor <TraineeAssessor fullname> has marked evidence related to: <component type> - <component name>
Please review marking to provide feedback to the Trainee Tutor.”
Main text if Sender views: “You provided feedback for the following: <component type> - <component name>”
Action button if Recipient views: “Review Marking”
Action button if Sender views: “View Evidence”
“Review marking”, “<component name>” links and action buttons lead to corresponding Mark Evidence form (with related evidence pre-selected) opened at the same browser tab.
Example:
Trainee Tutor Has Marked Evidence
Trainee tutor Cameron Metcalfe has marked evidence related to: Assignment (task) - Research Assignment
Please review marking to provide feedback to the Trainee tutor.
Example:
Evidence Marking Submitted
You provided feedback for the following: Assignment (task) – Research Assignment”
Notify Trainee Assessor when their evidence assessment is confirmed by Assessor
Product area: Learning Plan
Sender: Administrator (Assessor, the one who validates Trainee Assessor’s evidence assessment)
Recipient: Administrator (Trainee Assessor, the author of evidence assessment)
Event: Triggered when Assessor validates ‘Trainee Accepted’/’Trainee Referred’ evidence assessment – and Trainee Assessor’s assessment is confirmed/agreed (so that evidence status is ‘Accepted’/’Referred’ now).
Message Template (Classic):
Title: "System Message"
Text: “You have received approval feedback from <Sender Fullname> related to: <componentType> - Component <componentName>”
‘<Component name>’ is a link leading to corresponding evidence assessment modal form opened in new browser tab.
Example:
System Message
You have received approval feedback from Matthew Barker related to: assignment (task) - component Research Assignment"
Message Template (Console):
Title if Recipient views: "Evidence Feedback Approved”
Title if Sender views: “Marking Approved”
Main text if Recipient views: “You have received approval feedback from <Sender Fullname> related to: <componentType> - <componentName>”
Main text if Sender views: “You approved marking by <Recipient Fullname> for the following: <componentType> - <componentName>”
Action button if Recipient views: “View Feedback”
Action button if Sender views: “View Evidence”
“<ComponentName>” links and action buttons lead to the corresponding Mark Evidence form (with related evidence pre-selected) opened at the same browser tab.
Example:
Evidence Feedback Approved
You have received approval feedback from Matthew Barker related to: Assignment (task) – Research Assignment"
Example:
Marking Approved
You approved marking by Cameron Metcalfe for the following: Assignment (task) – Research Assignment
Notify Trainee Assessor when their evidence assessment is referred by Assessor
Product area: Learning Plan
Sender: Administrator (Assessor, the one who validates Trainee Assessor’s evidence assessment)
Recipient: Administrator (Trainee Assessor, the author of evidence assessment)
Event: Triggered when Assessor validates ‘Trainee Accepted’/’Trainee Referred’ evidence assessment – and Trainee Assessor’s assessment is referred/disagreed (so that evidence status is ‘Tutor Feedback Received’ now).
Message Template (Classic):
Title: "System Message"
Text: “You have received feedback that requires action from <Sender Fullname> related to: <componentType> - Component <componentName>
Please view feedback to see the actions required.”
‘<Component name>’ and ‘view feedback’ are links leading to corresponding evidence assessment modal form opened in new browser tab.
Example:
System Message
You have received feedback that requires action from Matthew Barker related to: assignment (task) - component Research Assignment
Please view feedback to see the actions required.
Message Template (Console):
Title if Recipient views: "Evidence Feedback”
Title if Sender views: “Marking Referred”
Main text if Recipient views: “You received feedback that requires action from <Sender Fullname> related to: <componentType> - <componentName>
Please view feedback to see the actions required.”
Main text if Sender views: “You referred marking by <Recipient Fullname> for the following: <componentType> - <componentName>”
Action button: “View Feedback”
“<ComponentName>”, “view feedback” links and action buttons lead to corresponding Mark Evidence form (with related evidence pre-selected) opened at the same browser tab.
Example:
Evidence Feedback
You received feedback that requires action from Matthew Barker related to: Assignment (task) – Research Assignment
Please view feedback to see the actions required.
Example:
Marking Referred
You referred marking by Cameron Metcalfe for the following: Assignment (task) – Research Assignment”
Notify required Signatory on Compliance document pending signing
Product area: Compliance documents
Sender: Learner (if sent to Administrator/Employer/Referrer); Administrator/Employer/Referrer (if sent to Learner)
Recipient: Administrator (Learner’s case owner)/Employer (Learner’s Manager)/Referrer (all Learner’s Referrer Organisation referrers)/Learner
Event: Triggered every time Compliance PDF document is being generated/re-generated (manually or automatically by system) AND there are signatures pending from Signatores configured for selected Compliance template (hardcoded property, cannot be amended from UI).
Notification is not being sent to the same userType which is generating PDF (for instance, if Administrator is generating a document without providing their signature, notification will not be sent to Administrator userType).
If document is generated and Learner signature is pending, notification is being sent on behalf of document creator (Administrator/Employer/Referrer); if other userTypes signatures are pending, notification is being sent on behalf of Learner the compliance document belongs to.
Example: compliance template has the following signatories: Advisor, Employer, Participant, Referrer;
scenarios:
1. Administrator is generating compliance PDF document (no signatures are put into the document yet);
As a result, notifications will be sent to:
- Employer, Learner’s Manager (on behalf of Learner’s name); if Manager is not provided, notification will not be sent over to Employer(s)
- Referrer, all Learner’s Referrer Organisation referrers (on behalf of Learner’s name); if Referrer Organisation is not provided, notification will not be sent over to Referrer(s)
- Learner (on behalf of Administrator’s name – the one who generated the document in fact)
2. Learner is signing the compliance document (while other signatures are still pending);
As a result, notifications will be sent to:
- Employer, Learner’s Manager (on behalf of Learner’s name); if Manager is not provided, notification will not be sent over to Employer(s)
- Referrer, all Learner’s Referrer Organisation referrers (on behalf of Learner’s name); if Referrer Organisation is not provided, notification will not be sent over to Referrer(s)
- Administrator, Learner’s case owner (on behalf of Learner’s name)
Message Template (Classic):
Title: "System Message"
Text: “Your signature is required for the <ComplianceTemplateName>: <ComplianceGroupName>”
<ComplianceGroupName>’ is a link leading to User Profile -> Compliance documents section expanded (if Administrator/Employer/Referrer clicks) OR to Documents page (if Learner clicks), opened in same browser tab.
Example:
System Message
Your signature is required for the ESFA - Training Plan v1: ESFA Training Plan
Message Template (Console):
Title: "Signature Required”
Main text if Recipient views: “Your signature is required for the <ComplianceTemplateName>: <ComplianceGroupName>”
Main text if Sender views: “<Recipient Fullname>’s signature is required the <ComplianceTemplateName>: <ComplianceGroupName>”
Action button: “Sign”
The "<ComplianceGroupName>” link and “Sign” action button lead to Signatures page (filter applied: Tab=Signature Required, Type=’Compliance’, Learner Name = Learner’s Fullname) opened at the same browser tab (if Administrator/Employer clicks), and to Documents page (Signatures Required tab) opened at the same browser tab (if Learner clicks).
Example:
Signature Required
Your signature is required for the ESFA - Training Plan v1: ESFA Training Plan
Notify Learner’s case owner and/or Learner on Process automation Tracker being processed (closed)
Product area: Trackers
Sender: Administrator
Recipient: Administrator (Learner’s case owner) or Learner
Event: Triggered when a Tracker of below types is processed (closed) by Administrator and may contain additional text (if ‘Message to Primary Tutor’/’Message to Learner’ details are filled out on Edit Tracker form):
- Break in Learning (always sent over to Administrator; sent over to Learner only in case ‘Message to Learner’ is populated in Tracker form upon its processing)
- Withdrawal from Learning (always sent over to Administrator; sent over to Learner only in case ‘Message to Learner’ is populated in Tracker form upon its processing)
- Change of Working Conditions (can only be sent over to Administrator)
- Change of Programme (always sent over to both Administrator and Learner; additional text for message to Learner is always ‘Please await further instructions’, hardcoded)
- Change of Employer (can only be sent over to Administrator)
- Additional Learning Support (can only be sent over to Administrator)
Additional text is ONLY displayed in Collaboration Centre, Classic.
Message Template (Classic):
Title: "System Message"
Text for Administrator: “The <trackerType> request for <Learner Fullname> has been processed. Contact <Sender Fullname> for further information. <Additional text>”
Where <Additional text>: “Additional information: <MessageToTutor from Tracker>”
Text for Learner: “Your recent <trackerType> request has been processed. <Additional text>”
Where <Additional text>: “Additional information: <MessageToLearner from Tracker>”
Example:
System Message
The additional learning support request for Edmund Croyle has been processed.
Contact Theodore Reese for further information.
Additional information: Please could you coordinate further actions
Message Template (Console):
Title: "Tracker Accepted”
Main text for Administrator: “<Learner Fullname>’s recent <trackerType> request has been approved. Please allow up to 24 hours for this change to reflect.”
Main text for Learner: “Your recent <trackerType> request has been approved. Please allow up to 24 hours for this change to reflect. If you have questions regarding this request, please contact <Sender Fullname>”
Action button if view by Administrator: “View Tracker”
Action button if view by Learner: None
The Action button leads to the corresponding Edit Tracker form opened in the same browser tab.
Example:
Tracker Accepted
Edmund Croyle's recent additional learning support request has been approved.
Please allow up to 24 hours for this change to reflect.
Example:
Tracker Accepted
Your recent break in learning request has been approved.
Please allow up to 24 hours for this change to reflect.
If you have any questions regarding this request, please contact Theodore Reese.
Notify Learner’s case owner and/or Learner on Process automation Tracker being rejected
Product area: Trackers
Sender: Administrator
Recipient: Administrator (Learner’s case owner) or Learner
Event: Triggered when a Tracker of below types is rejected by Administrator and may contain additional text (if ‘Message to Primary Tutor’/’Message to Learner’ details are filled out on Edit Tracker form):
- Break in Learning (always sent over to Administrator; sent over to Learner only in case ‘Message to Learner’ is populated in Tracker form upon its processing)
- Withdrawal from Learning (always sent over to Administrator; sent over to Learner only in case ‘Message to Learner’ is populated in Tracker form upon its processing)
- Change of Working Conditions (can only be sent over to Administrator)
- Change of Programme (always sent over to both Administrator and Learner; additional text for message to Learner is always ‘Please await further instructions’, hardcoded)
- Change of Employer (can only be sent over to Administrator)
Additional text is displayed in both Classic and Console.
Message Template (Classic):
Title: "System Message"
Text for Administrator: “The <trackerType> request for <Learner Fullname> has been rejected. Contact <Sender Fullname> for further information. <Additional text>”
Where <Additional text>: “Additional information: <MessageToTutor from Tracker>”
Text for Learner: “Your recent <trackerType> request has been rejected. <Additional text>”
Where <Additional text>: “Additional information: <MessageToLearner from Tracker>”
Example:
System Message
The break in learning request for John Creasman has been rejected.
Contact Theodore Reese for further information.
Additional information: Please could you coordinate further actions.
Message Template (Console):
Title: "Tracker Rejected”
Main text for Administrator: “<Learner Fullname>’s recent <trackerType> request has been rejected.”
Main text for Learner: “Your recent <trackerType> request has been rejected. If you have questions regarding this request, please contact <Sender Fullname>”
Additional text for Administrator: “Additional information: <MessageToTutor from Tracker>”
Additional text for Learner: “Additional information: <MessageToLearner from Tracker>”
Action button if view by Administrator: “View Tracker”
Action button if view by Learner: None
Action button leads to corresponding Edit Tracker form opened at the same browser tab.
Examples:
Tracker Rejected
John Creasman's recent break in learning request has been rejected.
Additional information: Please could you validate requests dates and re-apply
Tracker Rejected
Your recent break in learning request has been rejected.
If you have any questions regarding this request, please contact Theodore Reese.
Additional information: Please could you contact your primary tutor to adjust requested dates.
Notify Learner’s case owner when a new ‘Change of Name’ or ‘Change of Address’ tracker created
Product area: Trackers
Sender: Administrator or Learner (as a Tracker creator)
Recipient: Administrator (Learner’s case owner)
Event: Triggered when a new Tracker of ‘Change of Name’ or ‘Change of Address' types is created:
- If Learner requests ‘Change of Name’ or ‘Change of Address’ updates from Account Settings
- If non-case owner Administrator requests ‘Change of Name’ updates from Edit Learner page
Message Template (Classic):
Title: "System Message"
Text: “A <trackerType> Tracker for <Learner Fullname> has been created.”
‘Tracker’ is a link leading to the corresponding Edit Tracker form opened in a new browser tab.
Example:
System Message
A change of name Tracker for Edmund Croyle has been created.
Message Template (Console):
Title: "New Tracker Created”
Main text: “A <trackerType> Tracker for <Learner Fullname> has been created.”
Action button if view by Administrator: “View Tracker”
Action button if view by Learner: None
Action button leads to corresponding Edit Tracker form opened at the same browser tab.
Example:
New Tracker Created
A change of name Tracker for Edmund Croyle has been created.
Notify evidence assessment author when their assessment is confirmed by IQA (Internal Verifier)
Product area: Learning Plan
Sender: Administrator (Internal Verifier, the one who validates evidence assessment)
Recipient: Administrator (Trainee Assessor/Assessor, the author of evidence assessment)
Event: Triggered when Internal Verifier confirms on evidence status provided by Assessor/Trainee Assessor if status is either ‘Accepted’ or ‘Referred’, so that evidence status becomes ‘QA Verified’.
If Assessor provides their own assessment, Assessor is treated as assessment author;
If Trainee Assessor provides assessment and then Assessor confirms/agrees with it, Trainee Assessor is treated as assessment author.
Message Template (Classic):
Title: "System Message"
Text: “You have received ‘Acceptance’ feedback for <componentName> from <Sender Fullname>.”
‘<ComponentName>’ is a link leading to corresponding evidence assessment modal form opened in new browser tab.
Example:
"System Message
You have received 'Acceptance' feedback for Research Assignment from Henry Davis."
Message Template (Console):
Title: "QA ‘Accepted’ Feedback”
Main text if Recipient views: “You have received ’Acceptance’ feedback for <componentName> from <Sender Fullname>.”
Main text if Sender views: “<Recipient Fullname> has received ’Acceptance’ feedback for <componentName> from you.”
Additional details: <Sender comments> (taken from “Your QA Feedback to the Tutor” from Quality Assure page)
Action button: “View Feedback”
“<ComponentName>” link and action button lead to corresponding Mark Evidence form (with related evidence pre-selected) opened at the same browser tab.
Example:
QA 'Accepted' Feedback
You have received 'Acceptance' feedback for Research Assignment from Henry Davis.
Hi, assessment is approved, thanks.
Notify evidence assessment author when their assessment is rejected by IQA (Internal Verifier)
Product area: Learning Plan
Sender: Administrator (Internal Verifier, the one who validates evidence assessment)
Recipient: Administrator (Trainee Assessor/Assessor, the author of evidence assessment)
Event: Triggered when Internal Verifier refers/disagrees with evidence status provided by Assessor/Trainee Assessor if status is either ‘Accepted’ or ‘Referred’, so that evidence status becomes ‘QA Feedback Received’.
If Assessor provides their own assessment, Assessor is treated as assessment author;
If Trainee Assessor provides assessment and then Assessor confirms/agrees with it, Trainee Assessor is treated as assessment author.
Message Template (Classic):
Title: "System Message"
Text: “You have received ‘Referral’ feedback for <componentName> from <Sender Fullname>.”
'<ComponentName>’ is a link leading to the corresponding evidence assessment modal form opened in a new browser tab.
Example:
System Message
You have received 'Referral' feedback for Research Assignment from Henry Davis.
Message Template (Console):
Title: "QA Feedback Actioned”
Main text: “<Sender Fullname> has responded to feedback for <Learner Fullname>’s <componentName> and is now available for quality assurance.”
Additional details: <Sender comments> (taken from “Your QA Feedback to the Tutor” from Quality Assure page)
Action button: “View Feedback”
“<ComponentName>” link and action button lead to corresponding Mark Evidence form (with related evidence pre-selected) opened at the same browser tab.
Example:
QA Feedback Actioned
Henry Davis has responded to feedback for Edmund Croyle’s Research Assignment and is now available for quality assurance.
Hi, please could you re-assess the evidence – the criteria don’t seem to be met.
Notify Learner when their ‘Change of Contact Details’ request has been approved by Tutor
Product area: Trackers
Sender: Administrator (the one who approves the tracker)
Recipient: Learner
Event: Triggered when Administrator approves (i.e. selects ‘Approved’ option for Tracker status) Learner’s request to change their own contact details via ‘Change of Contact Details’ process automation tracker.
Message Template (Classic):
Title: "System Message"
Text: “Your recent contact details change request has been approved. Please allow up to 24 hours for the change to reflect within your profile.
If you have any questions regarding this request, please contact <Sender Fullname>”.
Example:
System Message
Your recent contact details change request has been approved.
Please allow up to 24 hours for the change to reflect within your profile.
If you have any questions regarding this request, please contact Cameron Metcalfe.
Message Template (Console):
Title: "Change Of Contact Details Accepted”
Main text: “Your recent contact details change request has been approved. Please allow up to 24 hours for this change to reflect on your profile.
If you have any questions regarding this change request, please contact <Sender Fullname>.”
Action button if Sender views: “View Tracker”
The Action button leads to the corresponding Edit Tracker form opened at the same browser tab.
Action button if Recipient views: None
Example:
Change of Contact Details Accepted
Your recent contact details change request has been approved.
Please allow up to 24 hours for this change to reflect on your profile.
If you have any questions regarding this change request, please contact Cameron Metcalfe.
Notify Learner when their ‘Change of Contact Details’ request has been rejected by Tutor
Product area: Trackers
Sender: Administrator (the one who rejects the tracker)
Recipient: Learner
Event: Triggered when Administrator rejects (i.e. selects ‘Rejected’ option for Tracker status) Learner’s request to change their own contact details via ‘Change of Contact Details’ process automation tracker.
Message Template (Classic):
Title: "System Message"
Text: “Your recent contact details change request has been rejected.
If you have any questions regarding this request, please contact <Sender Fullname>.”
Example:
System Message
Your recent contact details change request has been rejected.
If you have any questions regarding this request, please contact Cameron Metcalfe.
Message Template (Console):
Title: "Change Of Contact Details Rejected”
Main text: “Your recent contact details change request has been approved.
If you have any questions regarding this change request, please contact <Sender Fullname>.”
Action button if Sender views: “View Tracker”
The Action button leads to corresponding Edit Tracker form opened at the same browser tab.
Action button if Recipient views: None
Example:
Change of Contact Details Rejected
Your recent contact details change request has been rejected.
If you have any questions regarding this request, please contact Cameron Metcalfe.
Notify Learner when Review instance is ready for their contribution
Product area: Review
Sender: Administrator (Learner’s case owner)
Recipient: Learner
Event: Triggered nightly. Notification will be sent over to Learner if:
- Learner’s subscription status is ‘Full User’
- AND Learner has a review instance which ‘Planned/Scheduled Date’ = currentDate + ‘Allow editing prior to reviews?’ (Review type configuration, Programme builder level) NOTE: only Date is considered, Time is not taken into account (so even if Review is scheduled at 12:00 while the job is executed manually at 15:00, Learner will get the notification)
- AND associated Review type has ‘Participant’ option checked for ‘Visible To’ setting (Programme builder level)
- AND associated Review type has ‘Participant’ option is checked for ‘Notify when available for editing’ setting (Programme builder level)
- AND Learner’s Review instance status is not ‘Completed’
Message Template (Classic):
Title: "System Message"
Text if ‘Allow editing prior to reviews?’=0: “The upcoming review is now available for your contribution: <reviewInstance Title>
Review Date: <reviewInstance Planned/Scheduled Date> Time: <reviewInstance Planned/Scheduled Time>”
Text if ‘Allow editing prior to reviews?’>0: “You upcoming review <reviewInstance Title> is <‘Allow editing prior to reviews?’ value> days away. You can start contributing to the review and complete any pre-work that is required. Review Date: <reviewInstance Planned/Scheduled Date> Time: <reviewInstance Planned/Scheduled Time>”
NOTE: if <reviewInstance Planned/Scheduled Time> is not set for a review or equals to ‘All day’, ‘All day’ will be showing in the notification. Otherwise, the format is ‘<reviewInstance Planned/Scheduled Start Date>’ – ‘<reviewInstance Planned/Scheduled End Date>’.
Example:
System Message
Your upcoming review Weekly Review (Sept 2023) is two days away.
You can start contributing to the review and complete any pre-work that is required.
Review Date: 09/09/2023 Time: All day"
Message Template (Console):
Title: "Start Contributing To Your Review”
Main text if ‘Allow editing prior to reviews?’=0: “The upcoming review is now available for your contribution: <reviewInstance Title>
Review Date: <reviewInstance Planned/Scheduled Date>
Time: <reviewInstance Planned/Scheduled Time>”
Main text if ‘Allow editing prior to reviews?’>0: “Your upcoming review <reviewInstance Title> is <reviewInstance Title> days away. You can start contributing to the review and complete any pre-work that is required.
Review Date: <reviewInstance Title>
Time: <reviewInstance Planned/Scheduled Time>”
Action button: “Go to Reviews”
NOTE: If <reviewInstance Planned/Scheduled Time> is not set for a review, or equals to ‘All day’, ‘All day’ will be showed in the notification. Otherwise, the format is ‘<reviewInstance Planned/Scheduled Start Date>’ – ‘<reviewInstance Planned/Scheduled End Date>’.
The '<ReviewInstance Title>' link and action button lead to the Reviews page (‘Planned’ tab pre-selected) opened at the same browser tab.
Example:
Start Contributing to Your Review
The upcoming review is now available for your contribution: Weekly Review (Sept 2023)
Review Date: 07 Sep 2023
Time: 18:00 - 19:00
Example:
Start Contributing to Your Review
Your upcoming review Weekly Review (Sept 2023) is two days away.
You can start contributing to the review and complete any pre-work that is required.
Review Date: 09 Sep 2023
Time: All day
Notify Employer when their Learner’s Review instance is ready for contribution
Product area: Review
Sender: Learner
Recipient: Employer (Learner’s Manager)
Event: Triggered nightly. Notification will be sent over to Employer if:
- Learner’s subscription status is ‘Full User’
- AND Learner has a review instance which ‘Planned/Scheduled Date’ = currentDate + ‘Allow editing prior to reviews?’ (Review type configuration, Programme builder level) NOTE: only Date is considered, Time is not taken into account (so even if Review is scheduled at 12:00 while the job is executed manually at 15:00, Learner will get the notification)
- AND Learner has Employer set as their Manager in Edit Learner details
- AND associated Review type has ‘Employer’ option checked for ‘Visible To’ setting (Programme builder level)
- AND associated Review type has ‘Employer’ option is checked for ‘Notify when available for editing’ setting (Programme builder level)
- AND Learner’s Review instance status is not ‘Completed’
Message Template (Classic):
Title: "System Message"
Text: “<Sender Fullname>’s upcoming review is now available for your contribution. <reviewInstance Title>
Review Date: <reviewInstance Planned/Scheduled Date> Time: <reviewInstance Planned/Scheduled Time>”
NOTE: if <reviewInstance Planned/Scheduled Time> is not set for a review or equals to ‘All day’, ‘All day’ will be showing in the notification. Otherwise, the format is ‘<reviewInstance Planned/Scheduled Start Date>’ – ‘<reviewInstance Planned/Scheduled End Date>’.
Example:
System Message
Edmund Croyle's upcoming review is now available for your contribution.
Weekly Review (Sept 2023)
Review Date: 07/09/2023 Time: 18:00 - 19:00
Message Template (Console):
Title: "Review Ready For Contribution”
Main text: “<Sender Fullname>’s upcoming review is now available for your contribution. <reviewInstance Title>
Review Date: <reviewInstance Planned/Scheduled Date>
Time: <reviewInstance Planned/Scheduled Time>”
Action button: “Go to Reviews”
NOTE: If <reviewInstance Planned/Scheduled Time> is not set for a review, or equals to ‘All day’, ‘All day’ will be showed in the notification. Otherwise, the format is ‘<reviewInstance Planned/Scheduled Start Date>’ – ‘<reviewInstance Planned/Scheduled End Date>’.
The ‘<ReviewInstance Title>’ link and action button lead to Reviews page (‘Planned’ tab pre-selected) opened at the same browser tab.
Example:
Review Ready For Contribution
Edmund Croyle's upcoming review is now available for your contribution.
Weekly Review (Sept 2023)
Review Date: 07 Sep 2023
Time: 18:00 - 19:00
Notify Learner when their Aptem Assess Cognitive Assessment results are reset by Tutor
Product area: Aptem Assess
Sender: Administrator (the one who resets Learner’s results)
Recipient: Learner
Event: Triggered when Tutor resets the latest Aptem Assess Cognitive Assessment results gained by Learner (option is only available from Tutor Console, Learning Support page).
Message Template (Classic):
Title: "System Message"
Text: “Cognitive assessment for <Recipient Fullname> has been reset”
Example:
System Message
Cognitive assessment for Ryan Gibbons has been reset.
Message Template (Console):
Title if Recipient views: "Complete Your Assessment”
Title if Sender views: "Cognitive Assessment Reset”
Main text if Recipient views: “Please click below to be taken to your Assessment:
Go to Assessment”
Main text if Sender views: “Cognitive assessment for <Recipient Fullname> has been reset”
Action button: None
The ‘Go to Assessment’ link navigates Learner to ‘Aptem Assessment’ onboarding wizard step opened at the same browser tab; if Tutor clicks on the notification, they are being redirected to corresponding Learner’s Onboarding page opened at the same browser tab.
Example (if Recipient views):
Complete your Assessment
Please click below to be taken to your Assessment:
Go to Assessment
Example (if Sender views):
Cognitive Assessment Reset
Cognitive assessment for Ryan Gibbons has been reset.