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
Directory list and management
Directories are used to store business and people contacts. You can create any number of directories on your system and control access rights to each one.
The ability to use multiple directories allows you to have, for example, a business contact directory visible only to the business department and another business contact directory created for a specific project.
A directory is a business area and can contain tasks in addition to contacts. This allows you to log the tasks that need to be done with the contacts directly in the directory (e.g. their repairs, new menu calls, etc.)
Directory view
Directories are not usually managed by a company, so you will typically see all directories that you have access to in the directory list.
An area administrator has the ability to view all directories, not just those that it has access to. This gives it the ability to check and update user permissions. However, it does not have access to the data in the directory – individual people and businesses.
Directory Management
Creation
Use the New button to create a new directory. Required data is minimal – name and brief description.
Contact Access Permissions Settings
An important part of setting up a directory is to set the right permissions.
After each directory, you can create your own group of people who can access the directory. However, it is preferable to define a group for the directory to which you put roles or sections with access rights.
Remember:
- When you assign rights to individual people, you will also have to remove them. People who start new will not automatically get access rights
- When you assign the right directly to a department or role, everyone who starts the department or role will automatically get access rights. When they leave the department, they will automatically lose it again. Setting up roles will therefore make automation much easier.
Preview-only access
It is usually not advisable to give many people the right to interfere with directories. In directories, therefore, you can set who has read-only access to the directory and who can change contacts.
For workers, roles, or teams that should have read-only access, type in the Readers
Project Directory
It is often advisable to create a directory of people involved in a project. You create a directory for a project the same way as a normal directory, but set it up as a group of active users, a group set up for a project.
When you use a project group, each project member will automatically get access to the necessary contacts. With the end of the project or its departure from the project team, access to contacts will be automatically removed. As a result, sharing complies with GDPR requirements for contacts to be processed and accessible to people only for as long as it takes for services to be implemented – in this case, a project.
Why not give access to everyone
While it is convenient at first glance to make read directories available to all workers, there are a number of reasons why not to:
- Contrary to GDPR rules
- People can accidentally write or call someone they didn't want to originally.
- Business contacts are a significant value of a company and you should protect them from being stolen. It's not just the employees themselves, but someone else can access their account.