The Team submodule allows an easy definition, structuring and assignment of Ticketing System teams.
A team can be only assigned to a specific ticket if the origin of the ticket has been defined or allocated by a Support Module Administrator.
For example: the users of Support Module have two independent projects X and Y. The project X has an inquiry form in place. This form and its email address (projektX@companyXY.de) is then set up as an origin for the project X. A specified number of users is assigned to an origin X = a team X. If the project X generates an inquiry, the ticket is solely issued and assigned to the team X.
A table with all origin sources is available upon opening the submodule. A full-text search, advanced filtering and a specified item-per-page display can be performed.
Following parameters can be defined: team name and team leader.
It is also possible to choose a specified action per item such as:
- DISPLAY
- EDIT
- DELETE (only admin functionality)
New team and bulk actions can also be performed within the Team Submodule with a NEW TEAM or BULK ACTION buttons (remove is only admin functionality).
An EDIT TEAM window is displayed after pressing NEW TEAM or EDIT buttons. Parameters of the team can be set up at this instance.
A NAME attribute can be defined for an easier identification.
It is not possible to save any changes without an allocated name attribute. Another parameter is a FORM ID (a hash), accessible through a selector menu. This parameter is set up by a NexGen development team during the collaboration with the Support Module user.
The TEAM LEADER and TEAM MEMBERS can also be allocated through the selector menu.
After filling out all fields it is important to save all changes. A SAVE or a SAVE AND RETURN buttons can be used to save the last set of actions.
An important note: the RETURN button in the BROWSER will abort the saving process and will NOT SAVE the last performed action.
