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.

 

[ayushpandey]

This works, but it renders an "Update" button as well, let's say I don't want to render the button, is there any way to handle this ? 

[ccrow11]

You could use the built in features for record or flow conditions or require write access to the table via ACL and select the write access option under advanced to require the user have write access to be able to see the button. Otherwise it is stated in the document it is required to have the update function to be able to edit fields.

[Yoshita]

where can we add the action assignment?

[ccrow11]

Under playbook experience > playbook experiences, open the playbook you created, and select the action mappings related list. You will need to select the custom activity and the update_record action assignment.

[ccrow11]

You have to update the sys_data_flow record. I would check the subflow or action of the task on your PAD flow and make sure it sets there. Additionally you might also need to add the mark complete button the same way you added update, make sure the defining the task in your PAD flow moves with the same stages you are setting. If it does not have some form of close in the flow you will run into issues.