Use shared fields in notifications
Important
With this method, data is guaranteed to be up to date, but dependencies are created. Enforcement may take longer, and it's possible to accidentally create race conditions with circular dependencies. We recommend using this method only when the shared fields are absolutely required in your notification. The alternative is to Use shared fields in notifications (dependency-free). For more information on dependencies, see Dependency order.
To use shared fields in Notifications of a dependent (guaranteed) system:
Share a field from another target system, then make this system (that the notification is for) dependent on the shared system. See Make a system dependent.
For this example, we've shared the sAMAccountName field from our AD system, and made our PowerShell v2 system dependent on AD:
Add a new notification, or edit an existing notification.
For this example, we've added an Account Create email notification for our PowerShell v2 system:
On the Message tab, click the Variables button to open the variable hint box.
Locate and click the shared field to copy its merge code to your clipboard. Paste it into your message body. These merge codes use the syntax
{{Person.Accounts.<SharedSystemIdentifier>.<SharedFieldName>}}.For this example, we've copied & pasted the
{{Person.Accounts.MicrosoftActiveDirectory.SamAccountName || ""}}merge code.
Save your changes.
The shared field(s) will be calculated when the notification is triggered during enforcement.
The shared system will be resolved first. The current system (the dependent system) waits until that is finished, to ensure the shared fields are available.
For example:
