There are two ways to create a new team. If you want to create a team whose characteristics are not similar to any previously created team, then press the “New Team” button.

If you would like to create a team that is similar to an existing team and only want to change a few points, then please select the “Original Team” in the table. The detailed view of the team then opens. There you can create a copy for the teams by pressing the “Copy” button. The mandatory fields are marked with a red star behind the identifier. They are highlighted in red as long as they are not sufficiently filled out. In the team dialog there are 4 tabs that can be used to edit a team. 

Basic data

The first tab “Basic Data” contains the following properties of the team:

• Name: The name of the team
• Description: optional short note
• Priority: Default priority for tickets to this team
• Completion time: Default turnaround time for tickets to this team
• Service level: The target service level for this team
• Responsible: The person responsible for this team
• Active: With the “Active” option you decide whether the team is active or blocked (logically deleted).

Permissions

The second tab, “Permissions,” is on the right side of the window. This is a table that shows all users of todo4teams. For each team you can set whether the user is allowed to send tickets to this team. It can also be determined whether the user is a member of this team. You can set this directly using the checkboxes in the table in the “Affiliation” and “Permission” columns. Enable or disable these to determine the affiliations and permissions of users on this team.

Scripts

In the "Scripts" tab you can configure five scripts for a team that will be executed over the lifecycle of a ticket addressed to this team:

• Select Action: This script is executed after a user selects this team in the list of addressees. This script can therefore be used, for example, to make a pre-selection of forms when creating a new ticket to this team, etc.
• Create Action: This script is executed before a ticket is created. It is therefore useful, for example, if you want to point out something when creating a ticket, or if the ticket to be created should be subjected to a consistency check (e.g.: Have you also attached forms X and Y, etc.). 
• Start Action: This script will be executed after submitting. For example, you could send an email or SMS informing about the creation of the ticket.
• Accept Action: This script is executed after a user has accepted a ticket in the incoming list.
• Send Action: This script is executed before a ticket is closed. This makes it possible, for example, to carry out consistency checks in the complete action. For example, you can check whether all relevant forms are attached.
• End Action: This script runs after an agent completes a ticket. In this script, for example, a follow-up ticket can be created using the script function routeToGroupByName.

Text modules

In the Text modules tab you can configure the text modules to be displayed for this team. These text modules are dynamically displayed when tickets are created and processed for this team:

The text modules are organized in a tree structure:

Once you have made all the settings for this team, you can press the “Save” button to set the team with these settings in the system. You can exit this dialog at any time by pressing the “Close” button.