Issues with Approving Email for Campaign

This is an interesting one.

In our email pages, we use Images/Assets and CFs that are owned/authored by different teams. The actual authors of the emails do not own these assets or CFs and therefore Email Authors do not have "replicate" permissions to these assets.

But interestingly - when we run the Approve for Adobe Campaign workflow, we notice that when Email Authors run and approve the Newsletter, they end up publishing these Assets too.

I did additional digging and noticed that Approve for Adobe Campaign workflow runs with "workflow-process-service" service user, which has admin-like permissions.

This might create unintended assets/CF to be used on the Email Page and published via workflow.

In an ideal scenario, we would like Adobe's OOTB services to prevent Approve + Publish of the Email Page if Email uses Assets/CF that are not published. Once the appropriate teams Publish the Assets/CF, Email Author should be able to Approve + Publish the email for Campaign.

Please let me know if we should get on a call to explain this issue.

Start by reproducing the Approve for Adobe Campaign workflow with an Email Page that references unpublished Assets or CFs, then inspect how the workflow-process-service user handles those dependencies. Done means approval and publishing are prevented when referenced Assets or CFs are unpublished, while the workflow succeeds after they are published.

Written by the indexing model from the issue text.