AyMINE – Technical documentation
User Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Region / project / methodology
Change management process in a project
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Customer Service Response Generation
Objects affected by the problem
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)
Web management and automation
Receiving a message from the web
Human resources
Human Resources module security
Manage department / division data
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
System Modules
The AyMINE Framework Module
Configure how your system looks and works
Gestures and keyboard shortcuts
More about how the system works
Private notes and tags for objects
Filtering in the list of records
System Management
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
Object detail 
Terminological note
We refer to everything you work with in the system as an object. An object is used for tasks, information, meetings, etc. We understand that the word is very general, but somehow we have to name all these different objects together.
Often the term record is used. We will use it here sometimes, too, because it is closer to many people – and maybe even to you. But the meaning of record is different and much narrower. In AyMINE, for example, there are operation records. Therefore, we will stick to the more general concept of object.
Object detail
Object detail is the basic view for editing data that is in the system:
To work with an object, it must be stored in the system. Therefore, you always have the buttons
– save changes, close the window and return to the previous page
– save changes but do not close the window and continue editing. After saving, the page will re-evaluate what edits and features can be used, so other features may be offered
– leave page
– discard edits and exit the page
Once the object is saved, other changes may take place and your permissions to edit certain fields may change, or certain functions and fields may no longer be visible. Therefore, after saving, the system will evaluate all of this and may change what you see accordingly.
Recommendation: When you create a new object, enter the required information – typically at least the name – and save the object. Then you can get on with the rest of your work. Required information is highlighted in the details.