MAUT-12558 - Token replacement for DWC in Email is not working for Custom Object/Items Field filters

[fedys]

Q	A
Bug fix? (use the a.b branch)	❌
New feature/enhancement? (use the a.x branch)	✅
Deprecations?	❌
BC breaks? (use the c.x branch)	❌
Automated tests included?	✅
Related user documentation PR URL
Related developer documentation PR URL
Issue(s) addressed	https://acquia.atlassian.net/browse/MAUT-12558

Description:

Token replacement for DWC in Email is not working for Custom Object/Items Field filters. (Scope Landing Page/ Email Body/ Subject Line)

Steps to test this PR:

1. Create a DWC with a filter for Custom Object/Item field like ‘Custom Object Name’ equals 'CO1' .
2. Place it in an email body and/or a subject.
3. Send the email to a contact which is linked to ‘Custom Object/Item' named 'CO1’.
4. Check the email preview and the received email.
5. The DWC token should be replaced with the content for the contact appropriately.
6. Place the token in a landing page.
7. Check the landing page's preview and live version.
8. The DWC token should be replaced with the content for the contact appropriately.

[dadarya0]

Thanks @fedys

[dadarya0]

@avikarshasaha you can start your review.

[avikarshasaha]

Tested on beta. Thanks @Fedy.

Everyone is aware of the custom object limitation. This will only parse contact, company, and custom objects; other filters, such as the versity filter, will fail.