Hi Anil–
Thank you for taking the time to answer my questions! I’m a beginner, so appreciate the detailed explanations!
So let me see if I understand:
Process 1:
- User launches
- User fills out form and submits
- Task is added to Action Center.
- TaskID is added to queue
- end process
Process 2:
- Triggered upon addition of TaskID record to queue?
- Job checks task ID to see if completed
- If no – pause and wait.
- If yes – fetch task details
- Send email to OP with results
- Remove task from queue
- end process
Do I have this right? So this leads to me to a question about #5 in Process 2. Is there a way to add not only the TaskID to the Queue, but also the name or “release key” of the job that I want to run on completion of the task? In other words, is there a way to set this up so the queue-checking job will not only get all the task details on completion, but then run a named job to handle it?
If so, that would be a flexible way to handle different sorts of actions. Is this possible?
Or maybe I’m over engineering this? Is there a way to attach code (or to run a job) to a submit button in Action Center form? If so, maybe I just need to figure out how to do that.