Form View in PLAYBOOK appearing as read-only and NOT moving to the next ACTIVITY/STAGE

[architmishra]

I am setting up a playbook which makes a new record in a table and then provides required/needed fields access to users in order to move forward to different states as configured. 
While its creating a new record, the form view thereafter comes as read-only and provides no scope for editing it through the playbook.

Also, once the user uses the UI action to move to the next state, even though the state changes to the next one, the playbook remains stuck and does not move to the next activity/stage.

 

[Bimschleger]

What activity were you using to create the new record? I assume that you used 'Create Record' ? Playbook respects platform-level access rules. If the end user does not have write access to the underlying table, they won't be able to have write access in the form...

As far as advancing to the next step, all Activties initiate an underlying subflow or flow action. The Activity will complete when the underlying subflow / action is complete. Perhaps dig into sys_pd_context, find your process and stuck activity. Then click in to view what is going on with the subflow for the stuck activity (docs for reference).

[martypa]

I have the same problem as described above. I have created my own case type and use the Product Support Case Playbook. All fields are also read only in the playbook view. What could be the reason for this?

[ccrow11]

If you are using the UI Layout for record, you need to include the Playbook action assignment "Update" otherwise the fields on your playbook cards will be read only. Additionally if you have not used the access analyzer to view your intended users access levels I would check there as well.

[sebastianl]

That was it thank you.