- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi,
There are a couple options here, in order from simplest to most complex:
- Apply a filtering typology rule to delivery template for deliveries made for that campaign. This can be further secured by hiding typology selection from business users. Downside is it moves the filtering all the way to delivery send which a lot of marketers don't like (harder to see true count, makes workflow approval worse).
- Generate recipient lists with the criteria applied ahead of the workflow, as part of ETL. Can't really secure, have to delete old lists, can get confusing.
- Alter the workflow template to add js in workflow Properties' Script tab: JS parses the workflow's xml on workflow start, looking for query activities that are missing required filters and halting workflow if present. Best to do this in a library and have a single call to it, e.g. validateXXXCampaignWorkflow(). Can hide Script tab from business users if desired. <- what I would do
- Alter the xtk:workflow form to apply a <leave/> check on query activity to prevent tampering with workflow template's predefined filter. Requires arcane coding that can ruin system if not done right, breaks on upgrades.
Thanks,
-Jon
Views
Replies
0 Likes
Total Likes