Q&A from the live session: Mastering Case Management in Quick Automate: Orchestration and Parallel Processing

Questions and answers generated from Webex chat and transcript
Q: Hi Do we have a workshop link for this please?

A: These automations presented by Kushal will be available as 1 click samples - most likely in April. A workshop will follow likely in May, but this videos will be released on our YouTube channel and Quick Community Channel for future reference by end of this week.


Q: Is there a way to have case processing always running so that cases are processed as they are created?

A: You can create a trigger to run the case processing automation at a regular interval. Each time it is run, it will pull all of the cases of the defined ‘case type’ that are in the READY status.


Q: Can you confirm… A [case] is comprised of multiple [tasks], that are just for (that case). So, tasks can’t traverse multiple cases?

A: A task refers to a ‘human in the loop’ task. If a task is created in a case processing scope, it will return the data provided by the human for that case only.


Q: Can a trigger be [new object created] in [object store]?

A: As of today, the only trigger that’s available is a time based trigger, and that’s the way that I would recommend designing it if you were to design it today. We are working on event-based triggers, so you’ll have API as well as event based triggers through quick events. But right now with the current scenario which you have time based is what you have. So you schedule at a certain time and do it, but we would have event based triggers pretty soon, and that would be connected to case management as well.