Conditional notification event
complete
R
Rick van den Dijssel
With this feature, we support the ability to determine which notification and even, if you want to send a notification. You can determine if you want to send a notification based on if a mapped attribute (with used in notification option enabled) has a value or if it's a certain value (based on equal or contains) in a similar interface as the business rules.
Because this feature needs which attributes are used for notification this is linked to the Powershell Target system mapping feature. Because Powershell Target system mapping is a breaking change we will mark this feature as Beta until we have a full feature set. This means that you shouldn't use this currently for the production system but to test and give you a glimpse into what is coming.
Curious about this feature! Request your support department to enable this Beta feature
Photo Viewer
View photos in a modal
G
Grady Koopman
marked this post as
complete
R
Rick van den Dijssel
Merged in a post:
Notification create event target powershell system
K
KaHo Man
Unlike the built-in target systems (ActiveDirectory and AzureAD), the create event mail notification is always sent. This is propably because the create event is always executed in a target powershell system. In the built-in systems there is propably a correlation executed first and from there on a create or an update event triggered. In the built-in systems only when an actual create is done, a notification is sent. When an update takes place because of the correlation, then no notification is sent. This functionality is also needed for target powershell systems.
R
Rick van den Dijssel
Merged in a post:
Send different notification based on attribute
Ramon Schouten
We would like to be able to send a (different) notification based on the available person data.
Example:
When provisioning an internal employee we want the notification with account details to go to the manager.
When provisioning an external employee we want the notification to go to the servicedesk
R
Rick van den Dijssel
marked this post as
planned
Planned March release
R
Rick van den Dijssel
Merged in a post:
Suppress Notifications for PowerShell Targets
J
J. Anderson
Please provide a flag passable in the Result return object that will allow suppressing the Notification Event for that event (Create, Update, Disable, etc).
Use Case: During Google Create event, successfully correlate to an existing account. Thus, no Create notification is needed.
The built in AD Target already does this for Correlated accounts.
K
KaHo Man
Totally agree, similar to this feature request: https://helloid.canny.io/provisioning/p/notification-create-event-target-powershell-system
R
René de Jong
If we could sent notification on entering and leaving a rule, that would solve this i think.
Or have the option to select a rule as extra codition for a notification.
E
Ernst
Heel graag!
E
Erika Eling-Farr
Graag!!
S
Steve MIller
You can add a custom field in the source data with a complex mapping, and output the desired email address depending on the employee's type (or another value). Then that custom field can be used in the notification's TO field.
E
Erika Eling-Farr
Steve MIller: that would mean that you have to describe all the possible outcomes...mmm
Is there a max to the code in a costum field?
S
Steve MIller
Erika Eling-Farr: Not all possible outcomes. Map those that need special treatment, and then fall back to a default for everyone else.
I'm sure there's a theoretical maximum length to the code for a custom field, but I doubt anyone is likely to reach it.
Load More
→