Capture Conditional Content in Typology Rule

[SkylerQu2]

Hi,

Is it possible to capture personalization/conditional content in a typology rule?

Take the following typology rule code which executes "at the end of analysis" for the alertAssignee delivery template.

• logInfo(delivery.content.text.source)

This will return the following, which is the content of the alertAssignee delivery template.

• "<%= dataSource.message %>"

However, when an alert is sent out, this <%= dataSource.message %> can become many different things. How can we capture this in the typology rule?

[ccg1706 · Accepted solution]

Hi @SkylerQu2, 

If I understand correctly, rather than a typology rule to extract the alert message, I will recommend using a content block or personalization block to generate the message, and then include it in the delivery template. This ensures, the message will be rendered correctly during delivery preparation.

You will be able to reference the result in a typology rule if you need more validations.

Find attached the following documentation about content blocks and personalization blocks:

Personalizing emails with content blocks 

Personalization blocks | Adobe Campaign

Hope it helps!

Best, 

Celia

[SkylerQu2]

@ccg1706  thank you - this is very helpful. Is there a value we can check in the delivery to determine who the recipient is? For the notifySupervisor template, for example, could we check which operator group is designated as the workflow supervisor and therefore will receive the notification?

[ccg1706]

Hi @SkylerQu2,

You're welcome! 

If you are using the notifySupervisor templare or an Alert activity, the notification will normally be sent to an operator or operator groups, not a regular recipient profile. You can check who it is via the delivery or typology rule if needed.

And if you want to know who is assigned as the workflow supervisor, you can get that info and pass it along the workflow as a variable. Thta way, you can use it in your delivery or even use it on your typology rule for extra validation. 

Hope it helps!

Best, 

Celia

[SkylerQu2]

Hi Celia,

Got it, thank you.

I asked because the ideal solution here would be a content block in every alert delivery that only "wakes up" if it detects the operator group is set to technical workflow supervisors, for example, so we would only get API calls to Teams if the workflows were in this subset. This would make an easier implementation as we wouldn't have to go in and individually modify each workflow we want to trigger this content block.

If there is any solution that might accomplish this (maybe we can view the execution folder of the workflow?) using out-of-the-box delivery attributes that can be accessed by the content block, let me know! If not, this solution will work with a little bit of implementation time.

Thanks,

Skyler