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 locks
Object locks are used to protect against duplicate simultaneous object editing by two or more users. They are automatically closed or expires, if user do not edit. In practice, they do not need any administration.
Locks are stored long time and allow save modifications event when user has no access for a long time, but only in case that no one else access object for editing.
If user does not edit object continuously, lock expires in ten minutes and user can lose right to store its work. However, system recommends saving changes before the time limit expires.
Administration
As mentioned, administration should not be necessary. Nevertheless, administrator or developer can kill the lock manually.
__Kill lock means that someone loose right to store his/her work. Use the function only when you really know, why to do that.!
Protocol of all kills
All kills are stored in the list of kills. That list in used only for documentation purposes in case that someone reports wrong system behaviour.