Genesys Cloud - Main

Hi all,

Hope someone could advise me. I was under the impression that I could build a common module flow which contained a "decision" action cell where I could write an expression or use the email builder function to block emails (i.e particular domains or specific addresses) - I would then call on this flow at the beginning of every one of our email flows which should disconnect unwanted emails, therefor creating a single place to add domains and such in the future if needed as opposed to entering into a decision in every flow we have.

I have had a look at this though and there doesn't seem to be the ability to use the email builder within the "Decision" cell in the common module flow? I have ensured that the Inbound Email Flow is selected for the compatible flow type.

Does anyone know if this is possible, or could someone please suggest how I achieve the same outcome at all?

Thanks in advance!Post

#Implementation
#PlatformAdministration
#Unsure/Other

------------------------------
Dale Wylie
Aggregate Industries UK Ltd
------------------------------

Hi Dale, 

I created a common module by selecting the inbound email and processing email flows and the decision cell appeared normally.

One test you can do is copy the decision cell from another flow and paste it into the common module. If it doesn't work, it's because an incompatible flow type has been selected.

------------------------------
Wagner Filho
Algar Tecnologia
------------------------------

Hi Wagner,

Thanks for the quick response! - I really can't get my head around it...

I created a common module flow and selected inbound email. I do not see any option for processing email flows? - The decision cell is there but I have no email builder and I am unable to use any email related expressions. I am even trying to use a data table instead where I can enter the blocked email addresses but when trying to write an expression in the input "tostring(email.message.from)" it wont accept the email expression.

------------------------------
Dale Wylie
Aggregate Industries UK Ltd
------------------------------

Original Message:
Sent: 02-29-2024 10:58
From: Wagner Filho
Subject: Blocking email domains using "Common Module Flow"

Hi Dale, 

I created a common module by selecting the inbound email and processing email flows and the decision cell appeared normally.

One test you can do is copy the decision cell from another flow and paste it into the common module. If it doesn't work, it's because an incompatible flow type has been selected.

------------------------------
Wagner Filho
Algar Tecnologia
------------------------------

Hi Dale,

You'll just have to create a new variable in the common module and enable the input property while creating it.

And from your email flow, when you call your Common module, you'll get the option to assign a value to the variable you just created. From here you can assign the value as Email.Message.From and the common module can be able to access the same.

------------------------------
Sriram L
------------------------------

Original Message:
Sent: 03-01-2024 05:07
From: Dale Wylie
Subject: Blocking email domains using "Common Module Flow"

Hi Wagner,

Thanks for the quick response! - I really can't get my head around it...

I created a common module flow and selected inbound email. I do not see any option for processing email flows? - The decision cell is there but I have no email builder and I am unable to use any email related expressions. I am even trying to use a data table instead where I can enter the blocked email addresses but when trying to write an expression in the input "tostring(email.message.from)" it wont accept the email expression.

------------------------------
Dale Wylie
Aggregate Industries UK Ltd
------------------------------


Original Message:
Sent: 02-29-2024 10:58
From: Wagner Filho
Subject: Blocking email domains using "Common Module Flow"

Hi Dale, 

I created a common module by selecting the inbound email and processing email flows and the decision cell appeared normally.

One test you can do is copy the decision cell from another flow and paste it into the common module. If it doesn't work, it's because an incompatible flow type has been selected.

------------------------------
Wagner Filho
Algar Tecnologia

Hi Dale, 

You can do this validation and blocking directly in the incoming mail flow.

Add a Decision block to the beginning of the flow, then click on email builder in the expression type box.

Under email, select the "Check Email Sender Domain" type and add the domains you want to block.

In the "YES" output path, add a disconnect block.

I checked and this is not available in the Common Module.

Please let me know if you have any questions. Good luck!

------------------------------
Wagner Filho
Algar Tecnologia
------------------------------

Original Message:
Sent: 03-01-2024 07:16
From: Sriram L
Subject: Blocking email domains using "Common Module Flow"

Hi Dale,

You'll just have to create a new variable in the common module and enable the input property while creating it.

And from your email flow, when you call your Common module, you'll get the option to assign a value to the variable you just created. From here you can assign the value as Email.Message.From and the common module can be able to access the same.

------------------------------
Sriram L
------------------------------


Original Message:
Sent: 03-01-2024 05:07
From: Dale Wylie
Subject: Blocking email domains using "Common Module Flow"

Hi Wagner,

Thanks for the quick response! - I really can't get my head around it...

I created a common module flow and selected inbound email. I do not see any option for processing email flows? - The decision cell is there but I have no email builder and I am unable to use any email related expressions. I am even trying to use a data table instead where I can enter the blocked email addresses but when trying to write an expression in the input "tostring(email.message.from)" it wont accept the email expression.

------------------------------
Dale Wylie
Aggregate Industries UK Ltd


Original Message:
Sent: 02-29-2024 10:58
From: Wagner Filho
Subject: Blocking email domains using "Common Module Flow"

Hi Dale, 

I created a common module by selecting the inbound email and processing email flows and the decision cell appeared normally.

One test you can do is copy the decision cell from another flow and paste it into the common module. If it doesn't work, it's because an incompatible flow type has been selected.

------------------------------
Wagner Filho
Algar Tecnologia

You are right, the Common module doesn't have the same email builder, which is odd. What you can do instead is pass the value being checked an input to the common module. 

Eg:

If in the email builder you wanted something like:

Click the expression tab and we can see that is the same as:

If(IsSet(EmailAddressDomainPart(Email.Message.from)), Contains(EmailAddressDomainPart(Email.Message.from), "@BadDomain.com"), false)

So you can always create a string variable like EmailAddressDomainPart(Email.Message.from)

Then in the common module have an input string setup like so: (highly recommend you set a default value for edge cases)

Then just do a standard decision action with, Contains(Task.FromAddress, "@BadDomain") for example and away you go, or use a datatable lookup etc.

In the inbound flow when you call the the common module you will have that input

Let me know if you need any further guidance with it.

------------------------------
Anton Vroon
------------------------------