When creating an event monitoring rule it is possible to use the following variables to use in an notification message:

• {link}
• {modulelink}
• {rulename}
• {description}
• {eventname}

There should be a variable for {activity} (Name of the Activity) and {course} (Name of the Course) in order for notifications messages to be unique and easily distinguishable.

Current disadvantages:

• a site-admin can create an event monitoring rule (rule name: "New Database Entry") and use all variables inside the notification message template.
• users can subscribe to this rule for their own databases but won't be able to see from which database the notification came from

Current workaround:

• a Site-Admin can create an event monitoring rule (rule name: "New Entry in Database XY")
• now users can subsrcibe to this rule for database XY
• disadvantages: admins have to create 50 different rules for 50 different databases. Users see all those rules and have to select the correct one. Furthermore users are not able to create their own event monitoring rules with an unique rule name for activities they created.

Feature request:

• implement {activity} and {course} as variables for the notification message templates.
• a site-admin now only has to create one event monitoring rule let's say for event "New Database Entry" containing all variables.
• Users now only see one rule for the event "new databse entry" and can subscribe to it for all their databases.

Example template:

The rule {rulename}, monitoring the event {eventname}, has just been fulfilled.
The event occured in the activity {activity} within the course {course}.
Click the following link to go to the database: {link}

----------------------------------------
The rule Database-Subscription, monitoring the event New Database Entry, has just been fulfilled.
The event occured in the activity Registration-Form within the course Spanish.
Click the following link to go to the database: https://example.com/