AyMINE – Technical documentation
Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Adminitration of areas, projects, calendars
Region / project / methodology
Change management process in a project
GDPR and record of qualifications
Qualification of user or contact
Right to Manage Qualifications
Task, project & quality management
Administration of the Task Management Module
System rights for the task management module
Methodology and Quality Management systems
What a methodology / QMS consists of
Collaborative Resolution of Multiple Problems
Customer Service Response Generation
Incident and Quality Issue Management
Objects affected by the problem
Problems, Incidents, Helpdesk Tickets
Return project plan by baseline
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
The person responsible for the task
Working procedure – task definition
Objects related to the task pattern
Contacts and directories module (CRM)
Order overview for customer groups
Contacts and directories module (CRM)
System Permissions and CRM Module Settings
Send bulk messages in compliance with GDPR
How to correctly forget a person's details
Unsubscribe and set preferences
for bulk mail
Web management and automation
Receiving a message from the web
Human resources
Personalistics – User Permissions
Human Resources module security
Manage department / division data
Overview of Personnel Information for pracov# Employment Contract
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
Finance management
Metrics and Measurements
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
Enterprise Architect connector
System Modules
The AyMINE Framework Module
AyMINE — Tips for Mobile Usage
Configure how your system looks and works
Gestures and Keyboard Shortcuts
More about how the system works
Private notes and tags for objects
Overview of Modules and Record Types
Filtering in the list of records
System Management
Securing posts and internal discussions
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Formatted texts in the application
Gateway settings for external messages
IMP gateway settings for email communication
Internet Call Gateway Settings
New task assignment
When a system creates a new task from a sample task, it assigns the right workers to be in charge of the task. The method of assignment varies depending on whether the task is a project task or a business area.
Assigning a Task to a Project Team Member
In a project, tasks do not usually arise automatically, but are created by the project manager as part of the job planning and assignment.
The project task should have a specification of what qualifications the staff should have for each team role for the task. Qualifications are set on the qualifications tab in the task detail. In creating a task, project team workers who have the qualifications are assigned to the team for the respective team roles.
If there is no worker with the necessary qualifications in the project, the team role will remain vacant. If it is not possible to fill even the position of the worker responsible for the task, the task is assigned to the worker who creates the task.
If there are more people with the same qualifications in the project team, the task is assigned to the one who is designated in the project team as the leader (and has the given qualifications), or to the one who has been in the team the longest.
Note: For project teams, the responsible role setting is not used.
Assigning a Task to a Business Area
A task, especially if it arises automatically, must be assigned to the person who is to be assigned to it for processing. Therefore, a task has a responsible role to which the task is assigned.
How does the assignment work?
- If only 1 worker has a role assigned, the task is assigned to him
- If multiple people have a role:
- If he/she has a leader role, the leader gets the task
- If he/she does not have a leader role, the task gets the first in the group
- If there is no role specified, or if no one has been assigned, the task is not created!
Note: Business area tasks do not yet use the qualifications for project roles. A business area task is assigned to only one person, the team is not created for him/her.
Tasks can arise in several instances
When a task is created, a whole task hierarchy can arise. If the pattern has subordinate additional patterns (on the Subtask Patterns ) tab page), when a new task is created, tasks are created directly for each subordinate pattern as well. The same rules apply to the creation of each subtask as for the main task, and the subtasks are subordinate to the task in the same structure as the model task with the subordinate patterns.
If the task is created automatically based on events, the task is created for each business area or project that has a methodology with a task pattern attached. A single event can therefore give rise to several identical tasks in different areas.