How does the playbook buttons' (action assignment) client conditions "Can complete = true" and "Can skip = true" work?

[User492770]

Hello,

Im trying to show Mark complete and Skip action assignments in playbook for itil users (both are Client actions). I found workaround to make them visible, however that introduces another problem. When itil user clicks the Complete Activity or Skip button, the system will popup message "This activity does not support the complete state" or "This activity does not support the skipped state". This is not a problem for admin. For a side note, in the subflows that run playbook activities we use "Run as = User who initiates session" and "Run with role(s) = major_incident_manager, itil".

I can't find any detailed documentation for the Playbook's (Process automation) action assignment's section "Client conditions". In oob Mark complete and Skip action assignments there is condition "Can complete = true" or "Can skip = true" respectively. When using these, the button's will not show to non-admins. If I use custom button where this condition is erased (and leave only Activity state = In Progress), the buttons will appear to non-admin users. However then the skip button doesn't work, and will show error message as described above.

I have checked the sys_flow_data ACL, and that should not be the case.

I feel ServiceNow lacks detailed documentation in regards to playbooks, so often HI-tickets are created. Maybe someone could help me here though.

Many thanks!

[Mike Adams1]

We have the same question. It would be nice if someone provided a solution. I think it is telling that there has not been a solution in 3 years.