Define case participants to identify the people, businesses, and organizations that receive case correspondence. Participants are also known as work parties.
|Primary role||Lead System Architect|
Work parties (plural) is a single record that defines the different kinds of participants in a case, or an item of work. You define (or modify the default) one Work parties record for each type of work that you define in your application. You do not di this directly in the record; instead, you use the Settings > Participants navigation within the Case Type view of your case.
Work parties are usually set up as required by the System Architect who is implementing the functionality required in any given user story.
Configuring your work parties
- View the parties associated with each of your cases by using the Settings > Participants link on each case type.
- To add a new party, use + Add participant.
- Give the party a role name, such as Customer, or Next of kin
- Choose the type of participant. This list allows you to select any one of the defined Data-Party- classes, which by default is:
- To run a data transform when a party of this type is added to a case, select the data transform to use. This is useful for setting up default property values on the party.
- If there can be more than one of a given party associated with a case, tick Allow multiple participants for this role.
- To create an empty/default party of the give type as soon as the case begins, tick Create participant automatically when the case starts.
- By ticking At least a single participant is required for the case, you can make it mandatory that a case as at least one of this type of party.
Define parties that represent the types of individual that participate in cases in your application. The default list is Customer, Owner, and Interested, where Customer is the target of the case, Owner is the case worker, and Interested is a list of other parties interested in the case. It is good practice to use specifics instead of the generic Interested list.