I need some help getting a quick task to show up as a related action inside a re

For an entity backed record, you will have to create a new process model with the task you want and add the process model as a related action to the record type. You can then call this process as a sub process in your current model.

forum.appian.com/.../Record_Design.html

You can configure the related action in related action section of record type designer for your record . You just need to mention your process model there(for your quick task) and pass the particular parameter for your process model in the context expression. Check this for more.

forum.appian.com/.../Records_Tutorial.html

Ok, so when I make it into a subprocess and and expose it there I can get to the related action but it never leaves the subprocess. Any ideas on what could be causing this?

The related action will launch the process model independently. I only mentioned the sub process example in case you wanted to launch a certain process with your task via a sub process call as well as a related action.

The main process model is already active and I need the related action (sub-process at the moment) to pass information back to the main process model. To Elaborate on what Im trying to do: The main process creates an assessment and sends it off to certain departments to be completed. What I want the related action to do is to allow an administrator to go in and pick out a section to override and complete, they would then be sent to the user input task for that section and fill out that departments assessment on demand. The issue I am having right now is that the quicktask(in the sub-process) is showing up but the sub-process (in the main model) will not terminate and pass the information to the required node. Any Ideas on what could be stopping that sub-process not terminate?

Try adding a terminate process trigger to your end event

forum.appian.com/.../End_Event.html

Hi bonniet, As said in some of the earlier post, that the related action in the entity backed record needs to be a standalone process model. As you mentioned, you need to pass the result of a related action to your master process model for further workflow execution, what you can do is - you can create one standalone process which will be configured as the related action, taking some unique values to identify for which master process instance this related action is run, and once the action is completed, you can set the value of the result in the necessary process variable of your master process model using a custom smart service available on forum named - Set External Activity (it takes the process instance id, process variable name and the value that needs to be set in that process variable of the given process instance id). And once the value is set in your master process, you can accordingly drive your next workflows. Hope it helps.

You could also make use of the send and receive message events by placing a receive message event in the main process and a send message event in the related action process and correlating on an ID of some sort - usually the identifier used in the record list view.