Rules Sequencing for Launch Mobile Property

[ptmurphy]

In Web Launch properties, it's obvious how to sequence rules per this blog post: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-data/rule-component-seque...

But in Mobile Launch Properties, when creating a rule, the Advanced Options just says, "Rule component sequencing disabled" with instructions to enable it in the Property Settings.

But when looking in the Property Settings, no such feature is available to enable.

Is it possible to sequence rules in Mobile Properties? If not, in what order do rules run? 

[gkalyan]

@ptmurphy Are you looking into ordering the rules themselves or ordering actions inside the rule? As this property does the latter. Conditions and actions are evaluated within each rule.

If this property is disabled, when an event is triggered at runtime, the rule’s conditions are immediately evaluated. Multiple conditions are evaluated in parallel.

[ptmurphy]

I am looking to order the rules themselves. Or at least understand how Launch (Tags) decides to order these rules. 

For example, if two rules have the same conditions but different actions, which one is executed first (or last)?

[gkalyan]

@ptmurphy Check this Adobe link which will help you understand the rule ordering and settings

https://experienceleague.adobe.com/en/docs/experience-platform/tags/ui/rules#rule-ordering

Exceprt from the above link - "Event settings will differ based on the event type. Some events don’t have any settings that need to be configured."

[ptmurphy]

Thanks but this documentation seems to apply to Launch rules for Web Properties. This doesn't answer how Mobile Properties sequence their rules.

[gkalyan]

@ptmurphy 

I'm going through multiple documentations for Mobile rules and everywhere it is the same. Rules will be executed based on the conditions met but there is no scenario provided where if conditions are the same with different actions which rule will work?

Check this to understand more on the above.

https://developer.adobe.com/client-sdks/home/base/mobile-core/rules-engine

Having said that, I would like to see how you want to play this? If conditions are the same, why do you want to create 2 different rules? Why can't you can add all the actions in the same rule.

[ptmurphy]

Rules can have different conditions and still both qualify. For example:

Rule 1: Condition - data element "stateName" is set: Action - set some XDM field to the value of stateName

Rule 1: Condition - data element "stateName" is "Home": Action - modify the same XDM field to a static value of "HomePage"

Both rules would fire, but which one would actually set the XDM field value when stateName = "Home"?

[ptmurphy]

Two rules can have different conditions can both qualify to be run but have competing actions. But there are scenarios where only one or the other runs. This is not uncommon at all.

[Rite18]

@ptmurphy 

@ptmurphy  there are three parts to it 

• Event: The SDK listens for predefined events and each event is evaluated against the rules configured in Launch.
• Rule : rules in Adobe can be assigned a priority level to determine the execution order when the same event triggers multiple rules.
• Action: If an event trigger and rule executed [considering the condition defined ]  which in turn triggers action/ action order is applied here/ meaning more than one action can occur considering the in order they defined, 1st goes and last goes last

So in your case to control the rule , options could be use a priority or a condition which comes after priority in order of execution but condition is optional is not required 

[ptmurphy]

Thanks for your response but there is no priority level on rules in a Mobile Property, hence my question.

It is clear that it is possible to order the actions inside of a rule, but order of execution on the rules themselves is not clear.

[Rite18]

@ptmurphy  sure what mean is in your case consider how  an event, rule[with condition] and action flow works and definer per your use case need.

if rule is not an option , use condition at rule level to control the flow of action, but remember actions are  occurred considering the in order they defined, 1st goes and last goes last

[ptmurphy]

But this doesn't answer what order the rules are executed. Has no one actually read my initial question?

This is for a Mobile Property in Tags(Launch)

There is no ability to prioritize rules like there is in a web property

The ability to order the rules is useful and needed, that's why the functionality exists in web properties

How do I do the same in a mobile property?

[kautuk_sahni]

@ptmurphy Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!