Thanks David,I have tinkered with the target mappings and the composite blacklist fields there but feel it's probably cleaner to use a typology.I've ended up opting for a new typology which is just the normal default typology plus a global blacklist exclusion. This will ensure that the globally blacklisted records can never be sent out. If a marketeer needs to send a service message out they can untick the Exclude Recipients who no longer wish to be contacted box. This means that the SMS and glo...

I appreciate the help.As mentioned I already have a typology solution prepared which is similar to your one above, however it seems to me there should be a better way to make this work without me having to untick the 'Exclude Recipients who no longer wish to be contacted' box as this is removing one of the safeguards preventing globally blacklisted data from being sent out by marketeers.

Thanks for that.I've opted to build this in at a typology level rather than at a workflow level but it seems counter intuitive that I can disable only both global and channel level blacklists by default instead of being able to disable only the channel level blacklist whilst still applying the global level blacklist.

This is the correct answer.Once you've added the additional required fields onto your extended delivery log schema you can then add these into the target mapping as additional storage fields.Target Mappings > Your mapping (most likely mapRecipient) > Mapping tab > storage tab > map your fields in the 'additional data' section.