<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hello Jason,<br></div><div><br></div><div>I'm sorry, this mail slipped out of my view. <br></div><div><br></div><div>As for your question about ordering of notifications: generally yes, notifications are sent after changes were made. There are two kinds of notifications that might be of interest here:<br></div><div>- "focal object" (model-level) notifications<br></div><div>- resource object (provisioning-level) notifications<br></div><div><br></div><div>The former are related to changes in focal objects - users, roles, and orgs. They are invoked by model, among model hooks, in the FINAL stage - i.e. after all the changes were made.<br></div><div>The latter are related to changes in resource objects. They are invoked by the provisioning module. Again, they are invoked after operation attempt has been carried out - either successfully, unsuccessfully, or unsuccessfully with the hope of eventual sucess. You can differentiate between these states by looking at operationStatus field: it is either SUCCESS, FAILURE, or IN_PROGRESS, respectively.<br></div><div><br></div><div>Back to your code. Requestee is the focal object that the operation deals with (typically, the user). Your expression returns the current administrative status of this user. </div><div><br></div><div>If it's used within the context of a focal object notification, it displays the new status of the object (an exception is the DELETE operation, where it would show the original status). </div><div><br></div><div>But if it's used within the context of a resource object notification, it displays the status of the user object just after the resource object (account) operation was carried out. So it is *not* the final state. Imagine e.g. that there would be a "disable account" operation, followed by inbound mapping of newly changed value of account's administrativeStatus to user's administrativeStatus. In this case, the notification would show the original vlaue of the user's administrativeStatus. (But, this example is perhaps too artificial to be present in real life.)<br></div><div><br></div><div>Hope this helps (at least a bit...)<br></div><div>Pavol<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Jason Everling" <jeverling@bshp.edu><br><b>To: </b>"midPoint General Discussion" <midpoint@lists.evolveum.com><br><b>Sent: </b>Tuesday, November 10, 2015 8:17:46 PM<br><b>Subject: </b>[midPoint] New notification, need to verify my code<br><div><br></div><div dir="ltr">I tested the below code and it seems to work but I just wanted to verify I am using it correctly. Also, notification are the last item to process correct, after all changes have been made to the account?<div><br></div><div>Snippet from body expression code:</div><div><br></div><div>"Status: " + requestee?.getActivation()?.getAdministrativeStatus() + " \n" +<br><div><br></div>Thanks!</div><div>JASON<br clear="all"><div><br></div></div></div><br> <span style="font-size: small;" data-mce-style="font-size: small;" size="2"><span style="font-size: small;" data-mce-style="font-size: small;" size="2"><br></span></span><div><br></div><span style="font-size: small;" data-mce-style="font-size: small;" size="2">CONFIDENTIALITY NOTICE:<br>This e-mail together with any attachments is proprietary and confidential; intended for only the recipient(s) named above and may contain information that is privileged. You should not retain, copy or use this e-mail or any attachments for any purpose, or disclose all or any part of the contents to any person. Any views or opinions expressed in this e-mail are those of the author and do not represent those of the Baptist School of Health Professions. If you have received this e-mail in error, or are not the named recipient(s), you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited by the sender and to do so might constitute a violation of the Electronic Communications Privacy Act, 18 U.S.C. section 2510-2521. Please immediately notify the sender and delete this e-mail and any attachments from your computer. </span><br><div><br></div>_______________________________________________<br>midPoint mailing list<br>midPoint@lists.evolveum.com<br>http://lists.evolveum.com/mailman/listinfo/midpoint<br></div><div><br></div></div></body></html>