Forum Discussion
Ioana Thank you for responding.
1. Yes, I did check Security, and it set correctly.
2. Unlocking the Parent first still does not give the user access to the "Execute Batch" button. It is still greyed out for them. I even tested for one month.
- T_Kress2 months agoContributor III
If there were no security changes between versions then it should not be security related but here are the 3 security roles that impact the batch execution:
As you can see, in addition to these security roles a person would also need Access, Execute and Certify to the particular workflow(s) in order to perform the batch execute.
I still think if the button is greyed out, more than likely it has something to do with an ancestor or descendant that is still locked, preventing the batch process from being able to run. You cannot execute certain steps like Import, Validate, Load or Process if children or ancestors workflows are locked.
I think more than likely that is the root cause.
Related Content
- 2 years ago
- 11 months ago