Process Automation Designer - Don't Understand How to use Collect User Data Activity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-11-2022 03:52 PM
I have been playing with Playbooks and Process Automation Designer to demonstrate its capabilities, and for the most part, I'm satisfied with what is possible. However, there is one major issue. I have been trying to use the Collect User Data activity, and I cannot for the life of me figure out how it works. No matter which selection I use for the "User form for data collection" field, the Collect User Data activity within any test or actual playbook will always display no input variables, and the only option on the playbook will be to skip the activity.
The official documentation is no help - it is very bare-bones for this specific activity and covers nothing about how to display anything or actually collect inputs.
I would appreciate any explanation on how "Collect User Data" for Process Automation Designer works, with a specific example/screen shot of it working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-12-2024 04:14 PM
It looks like your submit button is missing. Please try updating to the latest version of the Playbook Experience, Playbook Experience Components and Process Automation Designer store apps. You may need to repair the Playbook Experience Core plugin as well.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2024 02:06 PM
I followed these steps and the Data Definition is still not showing up on the form in the Playbook on the Activity Definition step. It works when using the OOTB Collect User Data activity but not on a custom Data activity.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2024 09:10 AM
If this is a custom activity, you need to add a Data Definition input to your custom sub-flow. It should be of type "reference" and it should reference the Data Definition (sys_flow_data_definition) table. You can map this input to the Create Flow Data action within your sub-flow.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2024 08:33 AM
I did that and it still did not show up in the Workspace. There may be an issue with views when using custom activities. The inputs are mapped correctly into the subflow and the sys_flow_data record is even being generated. Just not appearing in the workspace. I tried to create custom views as well as use Default to no avail.. Idk. At this point I am moving on and will revisit later if I need to. Thank you for your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2024 04:10 PM
If you send a screenshot of your activity definition, I can tell you what's misconfigured. The variables are all defined in a field called vars. So you should add either specify vars in the field list or create a view that only includes this field. You also need to ensure you have a submit button, e.g. a declarative action that requires form fields and has a server script to update the record and mark it as complete. You can use our Collect User Data activity as a guide.