Hi Greg,
I believe you are talking about the Monitor Event operator. You can certainly use that to "keep track" of your detached processes, but keep in mind that you will need to also include a corresponding Send Event in the detached approval process. Those two operators work in conjunction. The Monitor Event will sit and listen for an event to be sent from a Send Event operator. If the event details match (these are those parameters you were looking at), then the process that is monitoring the event will continue. For some further explanation of those parameters, you can check out the PAM reference guide under Process Control. Below though are some important ones to what you might need:
Event Name- this is a name you define and is used to match the send event with the Monitor Event. On the Monitor event operator, this can be a regular expression so as to be able to match several different event names. This is also the only parameter that is required.
Event Parameters - This is on for the Send Event operator only. This is used to send data between processes. In your case, you could pass through the outcome of the approval (approved/rejected). You could also send the userid of the user who completed the task. When the listener receives the event, this information is stored in the payload parameter and can be accessed and parsed as needed.
Expire After (sec) - This is on for the Send Event operator only. This sets a time to live for the event to wait until a listener consumes it. The reason its important for you is if you don't set a value, the event only lives for an instant and if your Monitor Event operator is not listening for it at that time, it goes away and the event is missed. You can set this value to be long enough so that the event will still be active after your parent process has processed a previous event.
This might seem a little confusing so I have attached some sample processes that show how this can be done. The Monitor Event process spawns three detached processes then waits for the "Approval Event" to be sent. The detached processes have a user interaction task. When that task is completed, the process sends an "Approval Event" with a payload of the response from the form and the userid of the user who completes the task. The event will live for 60 seconds. The parent process then parses that payload into an array called ApprovalResponses, then waits for the next event. After all three events are received, the parent process completes.
These are for PAM 4.2 by the way. The concepts still apply to previous PAM version but these examples might not import properly.