Set Optionset value transition validation

There are scenarios we want the option set field value has to transition in an order, for instance, if Low, Medium and High are the available labels of an option set field, and we want to restrict transitions so that from low, can transition only to medium, and from high only to medium. We would need some client side scripting for best UI experience to achieve this. 

We do have this OOB for Status reason, but not for option set fields.

We will need to have functions onLoad, onChange (OnRatingLevelChange) of the option set field and onSave , as named in the script.

On Load, we save the value in a variable which will be used for accessing the Pre - Change value.

Below is an example where in the valid transitions are stored in an object - ratingMapping for        Low<->Medium->High transition and accordingly the changes to the option set field are validated. 

// if HS namespace is not defiende create it.

if (typeof (myNamespace) == "undefined") { myNamespace = {}; }

myNamespace.optionValidation =

{   

    previousRatingLevel: null,

    OnLoad: function (executionContext) {

        var formContext = executionContext.getFormContext();

        this.SetOnLoadRatingLevel(formContext);

    },

    OnSave: function (executionContext) {

        var formContext = executionContext.getFormContext();

        if (this.ValidateRatingLevel(formContext)) {

            this.SetOnLoadRatingLevel(formContext);

        }

    },

    SetOnLoadRatingLevel: function (formContext) {

        previousRatingLevel = formContext.getAttribute("abc_ratinglevel").getValue();

    },

    OnRatingLevelChange: function (executionContext) {

        var formContext = executionContext.getFormContext();

        this.ValidateRatingLevel(formContext);

    },

    ValidateRatingLevel: function (formContext) {

        if (!!previousRatingLevel) {

            var validated = false;

            var lowStatus = 717710000;

            var mediumStatus = 717710001;

            var highStatus = 717710002;

            var ratingMapping = { 717710002: [highStatus, mediumStatus], 717710000: [lowStatus, mediumStatus], 717710001: [mediumStatus, lowStatus, highStatus] };

            var ratingLevelAttribute = formContext.getAttribute("abc_ratinglevel");

            var ratingLevelControl = formContext.getControl("abc_ratinglevel");

            var currentRatingLevel = ratingLevelAttribute.getValue();

            var ratingLevelErrorMessage = 'Please make Valid transition Low-> Medium, Medium -> Low / High, High -> Medium';

            var invalidRatingLevelTransitionMessageId = 'invalidRatingLevelTransitionMessageId';

            var timeout = 5000;

            if (!!ratingMapping[previousRatingLevel] && ratingMapping[previousRatingLevel].indexOf(currentRatingLevel) > -1) {

                validated = true;

                ratingLevelControl.clearNotification(invalidRatingLevelTransitionMessageId);

            }

            else {

                ratingLevelControl.setNotification(ratingLevelErrorMessage, invalidRatingLevelTransitionMessageId);

                setTimeout(function () {

                    ratingLevelControl.clearNotification(invalidRatingLevelTransitionMessageId);

                }, timeout);

                ratingLevelAttribute.setValue(previousRatingLevel);

                validated = false;

            }

            return validated;

        }

    }

}

Create Email in Power automate using Email address string / for unresolved recipients

WE come across scenarios where the Email recipients are not the CRM Users/ Contacts/ Queues which can get resolved when chosen in the Activity Party field as To. In such cases, we can use the addressused property of the activity Party to intake the email address string directly. 

In the below example, I am going to use a CRM user having a valid address as a sender and direct Email address for the 'To' field.

Steps:

1)Set the, "Allow messages with unresolved email recipients to be sent" option to Yes in System Settings. 

2)Set the sender variable with the record type and Guid(Optional, This can also be input directly in the step 4, or the Email address can also be set directly instead of record type-guid)

Store in a variable using compose step - this I did environment specific by storing in a custom config entity. and below is what I have for the dev environment.

systemusers/336e28c4-bdc4-ea11-a812-000d3a79607c

3)In the Create Email Action,  at the right top corner of Activity Party section, click on "Switch to detail inputs for an array item".

4)Input the string as below: 

[

  {

    "participationtypemask": 1,

    "partyid@odata.bind": @{variables('EmailSender')}

  },

  {

    "participationtypemask": 2,

    "addressused": "testemail@fabrikam.com"

  }

]

In the above expression,
   "participationtypemask": 1 corresponds to Sender, 

   "participationtypemask": 2 corresponds to recipient.

@{variables('EmailSender')}--> should resolve to the Email sender variable. Sender can also use "addressused" in place of "partyid@odata.bind" in case want to use Email address string instead of the user with guid.

Below is a snapshot

And We are ready! Save and Test the flow!!