Scenario "Functional Teams"
A functional team is a flexible organizational structure tool that enables grouping employees by a common goal, regardless of their department, job responsibilities, or position. It is created to implement specific business tasks, projects, or processes where cross-functional collaboration is essential.
The purpose of a functional team is to:
- ensure effective interaction between specialists from different areas, allowing faster response to changes in the business environment;
- implement projects that go beyond the standard departmental hierarchy;
- optimize resources without being tied to the formal company structure.
The functional team card is the central element for managing its composition, status, and hierarchical relationships within the system.
«Actions on the functional team card»
The card provides the following actions to manage the team's status and composition:
- Open – activates the record, allowing the team title to be edited.
- Approve – locks the team parameters, restricting further changes to the title. Team lines remain active for updates.
- Close – completes the team’s activity, changing its status to «Closed». The "End Date" field becomes mandatory.
- Add employees – opens a dialog page for automatically adding participants to the team.
«Action Add employees»
This action opens a report dialog page where the user can quickly and conveniently add new participants to the functional team. The page includes the following parameters:
- Employee – selection of one or more employees.
- Role – functional role each participant will perform.
- Rate – individual rate for the participant (if needed).
- Price – cost indicator of participation (if needed).
- Currency Code – currency in which the price is expressed (if needed).
- Start Date / End Date – participation period in the team (if needed).
If the user selects only employees and roles without filling in other parameters, then Price and Currency are automatically pulled from the role settings, and Start/End Dates are filled in according to the period specified in the team header.
Section «General» This section consists of a header and a table area where team member data is recorded. Header includes:
| Field | Description |
|---|---|
| Code | Team code – a unique identifier, up to 20 characters. |
| Name | Functional team name, up to 100 characters. |
| Name (English) | Functional team name in English, up to 100 characters. |
| Parent Code | Reference code to the higher-level team in the hierarchy. Used to build the hierarchical structure. |
| Type | Has two options: Header and Unit. Teams with type "Header" are created solely for visual structure representation. On the list page, such rows are displayed in bold, helping to navigate the hierarchy. Field values defined in a "Header" type record are not inherited by subordinate levels. |
| Manager Number | Non-editable field filled automatically. This field is populated with the employee code when approving a line with type "Manager" and the "Main Team" checkbox selected. Only one such record is allowed, as only one main manager is permitted per functional team. |
| Manager Full Nameи | Non-editable field filled automatically. Populated with the employee's full name when approving a line with type "Manager" and the "Main Team" checkbox selected. Only one such record is allowed. |
| Start Date | Start date of the functional team’s work. Mandatory field. |
| End Date | End date of the team’s work. Optional field, required only when closing the team. Upon closure, all related employee records are also closed and updated with the end date. |
| Blocked | Can be used to block the team from changes and usage in other hierarchical links. |
| Status | Displays the current status of the functional team: Open – the team is created and can be edited. |
| Approved – the team becomes active, and header fields become non-editable. If needed, the team can be reopened and re-approved; previously approved lines remain unchanged. | |
| Closed – the team has completed its function and serves informational purposes only. |
Table section contains rows with records about team members:
| Field | Description |
|---|---|
| Team Code | Team code from the header. |
| Line Number | Unique line number, filled automatically. Technical field. |
| Type | Two options: Manager and Team Member. |
| Employee Code | Editable field where the employee code is entered from the employee list. Search can be done by code or full name. |
| Employee Name | Non-editable field automatically filled with the employee’s full name based on the Employee Code. |
| Functional Role Code | Code of the role performed by the team member. Linked to the functional roles directory (section Functional Roles). |
| Rate | Rate value performed by the team member. Can be 1 or less. |
| Main Team | A team member can participate in multiple functional teams but only one can be marked as the main team. When adding a new line, this checkbox is automatically set to Yes if the employee has no main team, and No if such a record already exists. |
| Status | Current line status. Automatically filled when the user runs the corresponding function: Open, Approved, Closed. |
| Price | Cost indicator. Can be filled individually for each participant or automatically pulled from the default value set for the role. |
| Currency Code | Used to define the currency in which the Price is expressed. Can be selected manually or set by default based on the chosen role settings. |
| Start Date | Indicates the start date of the employee’s participation in the functional team. Cannot be later than the team’s start date or the employee’s hire date. |
| End Date | Indicates the end date of the employee’s participation. If not filled, participation is considered active. Filled when the team or the line is closed. |
Section «History»
This section ensures transparency of changes by recording:
- Author and creation date of the functional team.
- User who approved or closed the record.
- Team approval/closure date.
Section «Hierarchy»
Displays structural links between functional teams. Shows which teams are subordinate to the current one based on the parent code specified in their records. This allows:
quick navigation through the multi-level structure of functional units; visualization of team relationships in the desired form (Collapsed/Expanded).
Scenario "Functional Roles"
Functional roles are a structural element of a functional team that defines the typical participation of an employee within it. A role contains a set of parameters used for automatically populating data when adding participants to the team.
Main role fields:
| Field | Description |
|---|---|
| Code | Unique role identifier. |
| Name | Text label of the role. |
| Name (English) | Text label of the role in English. |
| Status | Indicates the current state of the role (Open, Approved, Closed). |
| Start Date / End Date | Role validity period. |
| Blocked | Checkbox indicating editing restrictions. |
| Occupied Roles | Number of participants currently performing this role. That is, their team line record has the status Approved. |
| Default Price | Base cost for the role. |
| Currency Code | Currency in which the price is expressed. |
| Approved by / Approval Date | Information about the user who approved the role and the date of approval. These fields are filled automatically. |
| Closed by / Closure Date | Information about the role’s deactivation. |