To enable ordering and stop processing options for "Inbound Email" trigger type within a flow

[SUBHAM_SHAW_SN]

Scenario : You have created a flow where the trigger type is "Inbound Email" but you don't know how can you  control the order of processing ? As in most of the scenarios , we need to provide order of execution for Inbound Actions. Then you are at the right place.

Problem : We all know that we are into flow era of ServiceNow where we try to accomplish most of our tasks by using flow designer. Then why not to leverage inbound email trigger of a flow instead of conventional inbound actions. Having said that, there is no OOB ordering & stop processing options available which we generally use to set the precedence of executing an inbound action & to stop processing other matching inbound actions (by saying matching inbound action , I mean to say that inbound actions with matching condition)when the desired one is executed.

Solution : To achieve this , you can create a system property named "glide.hub.flow.inbound_email_trigger.show_advanced" as shown in the following image :

Once done, you could see the desired options available in your flow as shown in the below image :

Thanks & Regards,

Subham Kumar Shaw

Senior ServiceNow Consultant

[Rohit Sarkar1]

Wonderful post!

[Paul Curwen]

Nice find! Appreciate the effort.

[Rob Greeley]

Really helpful.  

I'm wondering why this system property is not set OOTB...

[shaikleyakath]

Thank Subham, I have spent hours and hours to solve the problem. Thank you for the post.

[Avinash_M]

Hi @SUBHAM_SHAW_SN ,
I have used this property and enabled in my enterprise instance, but its not working as expected.

My Requirement is - "The existing inbound actions ideally don't need modified.  We need to create a flow which checks if a watermark exists in any inbound email.  If the watermark does not exist, then the email processing should be halted in the flow.  If the watermark does exist, then the flow should allow the email processing to continue to be processed by all flows/inbound actions."

So, I have tried this, but its not working. could you pls check.

Regards,
Avinash

[vishokmohan]

In few cases even when the system property glide.hub.flow.inbound_email_trigger.show_advanced is activated, flows created before enabling this property fail to display the advanced inbound email trigger fields Order and Stop processing .

Problem Details

Administrators activated the system property glide.hub.flow.inbound_email_trigger.show_advanced to expose additional configuration options for inbound email triggers. Despite the property being set to true, flows that existed prior to this change do not show the Order and Stop processing fields in their inbound email trigger configuration.

Reproduction Steps

1. Navigate to Flow Designer

2. Open an existing flow with an Inbound Email trigger

3. Expand the Inbound Email trigger section

4. Verify that the Order and Stop processing fields are not displayed

Root Cause

The system property glide.hub.flow.inbound_email_trigger.show_advanced only takes effect when a trigger is initially created. Flows constructed before the property was enabled retain their original configuration schema and do not automatically inherit the advanced field visibility.

Solution

The inbound email trigger must be reelected to force Flow Designer to apply the current property settings and render the advanced fields.

Resolution Steps

1. Open the affected flow in Flow Designer

2. Expand the Inbound Email trigger configuration

3. Click the Trigger dropdown menu and reselect Inbound Email from the list

4. Verify that the Order and Stop processing fields now appear

5. Click Done to confirm the trigger configuration

6. Save and reactivate the flow

Reference Article: Advanced inbound email trigger fields not visible after enabling system property