Contents
Table of Contents
Create a Task
Choose a Client/Client Contact
Choose a Workflow
Choosing one of the workflows and clickingAdd Taskwill give you a preview of the firstformon the first status (if one is present):
Create a Case
You can add multiples of workflows at this point, just choose from the dropdown and click Add Task. These will all be related tasks that have the same internal reference (e.g. 20-12345)and will be collected under the summary page for you to see. When creating a Task, you will be also creating a Case (from which SwiftCase derives its name!) in which the created Task can be one of multiple tasks that constitute a Case. Once created you will be presented with the following page:
ClickView Taskto see the page related to the Task you have created (or the last Task of the multiple Tasks you have created in a Case).
To see the overview of all Tasks that are part of a Case just click theGo to Summarybutton on any task page.
The example below shows a Case that has a meeting and an expense claim task associated with it.
So any search for that reference on the dashboard will return the tasks associated with the Case:
You can also add new Tasks to the Case from the Summary page using theQuick Actionspanel:
This will present you with the default option of the currentClientandClient Contact, but these can be changed if necessary. Please note that although they are in the sameCase, none of the tasks created through the summary page will be aChild Taskof another. To be a Child Task, this needs to be created from within another task (essentially through clicking a widget defined on the workflow).
Create a Child Task
Child Tasksare tasks that form part of aParent Task. They can be created separately, but they are usually a sub task that needs to be completed to then move on in the Parent Task. You can configure child tasks by creating the child workflow first, and then adding the child workflow as aChild Task Widgetin the parent workflow (link toTask Widgets section).
Child Tasks will share the same reference as the parent, and when created will pull through the answers to questions from the parent taskifthe questions are also present in the child workflow.
When building the child workflow, you can opt to have the child task have separate answers in the database (so these can be altered to be specific to the task) or you can opt to have the child task share the answers with the parent task. This would mean that changing answers to the questions shared between the parent and child wouldupdate both(regardless of which task you change the answer on). For instance: if you share the Client Address question on both workflows you would only have to update the address on one of the tasks for it to update both. By default SwiftCase will treat both tasks as separate database entities.
Ready to automate your workflows?
SwiftCase helps operations teams streamline their processes with powerful workflow automation, case management, and AI-powered communication tools.