AyMINE – Technical documentation
User 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
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)
orderSVG Order overview for customer groups
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
Finance management
Metrics and Measurements
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
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
Activation buttons
An event that activates a task, can be linked with a button in another task. Task, that has defined activating event and the event is marked to be a button for user, can be activated by user directly and manually from the task by the button.
If field Button is filled, button will be a part of the task and responsible / assigned person can use it. Task behaviour depends on the setting of the raise condition.
Button for user
Has got option to use button and activate event. When used, event is raised and task is not modified and remain open.
Final button for user
As well as in former case, use has got button in the task, but in this case, button also changes the task state to the state defined in the field Status raising. It is recommended set up end state (Complete or Rejected).
How to use the buttons
Buttons are principal way to automate task processing. Use makes decision by using appropriate button and system automatically raise a new event and starts operation linked to that event.