Expand my Community achievements bar.

SOLVED

Commit changes to OOTB technical workflow as non-admin user

Avatar

Level 2

Hi,

 

We are creating a custom user group in Adobe Campaign, which is not able to do any changes to OOTB technical workflows (start/stop/restart)

mattiaslunden_0-1740406978825.png

The user group has the below named rights, and have read/write rights to folder 'Administration/Production/technical workflows' (including subfolders)

mattiaslunden_1-1740407049308.png

 

We have tried adding all named rights (except), adding delete right on the folder level, but no luck. Also have tried copy a OOTB worfklow under custom name and can be executed without issues. Seems to be hardcoded on internalName level or similar. 

 

Any ideas??

 

Kind regards

Mattias

 

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 2

I solved it myself. There's writeAccess sysfilter on the workflow schema which controls this. Extended workflow schema and altered the sysfilter.

View solution in original post

4 Replies

Avatar

Level 2

Edit: We have tried adding all named rights (except **admin**), adding delete right on the folder level, but no luck. Also have tried copy a OOTB worfklow under custom name and can be executed without issues. Seems to be hardcoded on internalName level or similar. 

Avatar

Level 3

@mattiaslunden 

I’ve implemented your requirement in my sandbox without granting admin rights or access to the admin operator group for my test user. I logged in as this user and was able to successfully start several OOTB workflows, such as Campaign Jobs, Campaign Tracking, and Jobs on Deliveries within campaigns, without any issues.

Could you please apply the same rights and operator group to your user and run a test?



SushantTrimukheD_0-1740410727371.png


Workflow logs :

SushantTrimukheD_1-1740410781945.png

 

Thanks.

Avatar

Level 2

Yes, I have tried that, but same issue still.
Im thinking maybe the admin named right is under one of your custom operator groups.

mattiaslunden_0-1740412326073.png

 

Avatar

Correct answer by
Level 2

I solved it myself. There's writeAccess sysfilter on the workflow schema which controls this. Extended workflow schema and altered the sysfilter.