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
Message patterns
Message templates allow you to send frequent messages quickly.
Select a message pattern, and the client name or other details are filled to the template automatically. The whole email is ready much faster than if you had to type it yourself.
What data is added to the template
You can add the following placeholder variables to the template pattern and the system will look up the necessary data.
The variable can be inserted in the content and subject of the message.
You must insert the variable in full, including the leading @, and be case sensitive.
It is not always possible to trace the data – for example, if you use a template that contains a claim code and the claim cannot be traced to the recipient, the code will not be replaced. It is therefore important to look at the generated message before sending it.
Complementary variables
CRM data
Data is always tracked for the recipient of the message
- @clientFirstname – First name of the client (from the CRM directory)
- @clientSurname – Last name of the client (from the CRM directory)
Business process data
Data refers to the last offer/bypass sent to the recipient or the company to which the directory belongs
- @offerNo – Offer number
- @orderNo – Order number
Complaints data
The data refers to the most recent complaint. If a message is sent directly from a complaint, the data will refer to that complaint even if it is not the last one.
- @problemNo – Complaint ticket number (problem)
- @problemName – Brief description of the ticket (from the title)
Extensibility
Individual business processes may support additional variables within the associated communication that may not be described on this page.
Templates for automated emails
Some templates are so-called system templates – the system actively works with them. For example, if a reply template is attached to the gateway, the responder will receive an email confirmation that the message has arrived.