Skip to main content

So I am running into a weird problem that has ugly software logic written all over it.

I am trying to send email to learners enrolled in an ILT and using shortcodes so I can reuse the email as a template. Specifically it is to go out when a recording of an ILT event is available. 

What I am finding is that while shortcodes are the same platform wide  their application is specific to the where the email is sent from. 

For example I have a session called Study Hall 2025 that contains an event called Welcome to the new year. 

In any general  ILT notification when I use “ session_Name] ‘_event_name]’ Recording Now Available” and I get “Study Hall 2025 ‘Welcome to the new year’ Recording now Available 

But when I send an email at the course level it replaces those with the first name tag so I get “David ‘David’ Recording Now Available”

When I send an email from the session it reads “Study Hall 2025 ‘ ’ Recording Now Available” truncating the event name entirely.

So while the shortcodes are universally the same, they are not valid in all applications.

It seems like only the shortcodes listed as examples for the specific email you are sending are considered valid for that email. 

Is this a bug? An intended feature? is there a workaround?

Starting here for groupthink before I send to support. 

thanks in advance

As I understand it, only the short codes you see when you configure the notification template are those that work with that template. That said, there are a couple of exception (don't recall off hand which ones) but it’s not something you can count on. I certainly agree that all shortcakes should be available across all notifications, certificates, manual email, newsletter, etc.


As I understand it, each notification preset/template contains a set selection of shortcodes that can be used within that template; if the template does not have a shortcode listed in this selection, it cannot be used in that notification. The shortcodes are not global across all notifications. Sometimes you have access to ten+ shortcodes, other times as little as two - it all depends on the template selected and cannot be changed.

This help desk article contains all of the templates and their associated codes without having to open a test notification in the LMS to see firsthand: Notification events and conditions – Docebo Help & Support.

If you share the exact notification templates being selected in your case, we may be able to assist further.


This makes sense to me.

  • When you send the message using short codes from the EVENT screen, Docebo knows exactly which event you are referring to.
  • When you send the message from the SESSION screen, because a session can have multiple events, Docebo doesn’t recognize the event short code because it doesn’t look down to the next level, and even if it did, there is the possibility of multiple events and it wouldn’t know which one to choose. (i.e., it’s not ‘truncating’ the event name - it’s leaving it out entirely).

In other words, Docebo can only use information at the level you’re on or above; it can’t look down a level because it hasn’t gotten there yet.

 

Recommendation: Either always send from the Event screen or rename your session to include the event name and eliminate the event short code. This should add consistency.


It’s been a while since I’ve tested this so I can’t speak to the functionality if you can get away with using shortcodes outside of the ‘available’ options for certain notification types, but I wanted to share the full list of shortcodes if you aren’t already aware https://help.docebo.com/hc/en-us/articles/4429113070226-Notification-events-and-conditions

I feel like there have been times where what is displayed in docebo when configuring the notification itself isn’t the full list of available shortcodes, so this list may be helpful.


Thanks everyone!

The interesting part here is that you can’t send an email from an event. BUT you can send a notification  about an ILT where an event is starting and include the event name and time. so there is clearly some level of backend computation to know that sessions have events and how to reverence them. 

 

My workaround will be to send it from the event with a manual entry of the event name. 

 

Not ideal, but hardly a problematic workaround.


I’m confused. You’ve said that you can’t send an email from an event, but your workaround is to send it from the event… can you be more specific, please?  
Do you mean you can’t send an ad-hoc email from an event in course management, but you will plan to use the automated notification associated with the ILT course (and if so, what trigger will you use?).

Thank you!


Sorry workaround is to send from the session and manually enter the event name so my template looks like this

“session_name] ‘Welcome to the new year’ recording now available.”

 


Reply