AyMINE – Technical documentation
Modules
Integration with ERP Abra Gen
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
Failure Analysis for an Individual Property of a Component or Process
FMEA – Probability of Detection
FMEA – Probability of Occurrence
Task, project & quality management
Administration of the Task Management Module
System rights for the task management module
Improvements and Preventive Measures
Methodology and Quality Management systems
What a methodology / QMS consists of
Problems, tickets and their management
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 and roles
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
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
Message with the outside world
Keyword
Keyword is an important tool for document automation
- How keywords help you automate documents
- Where keywords can be used everywhere
- How to define keywords
- Good to know
Keywords allow you to automatically add keywords in documents of various kinds.
Keyword examples:
- Project name
- Document author name
- Methodology name
- Document origination date
How keywords help you automate documents
Because keywords are defined at the level of a methodology, project (subordinate project) or area, you can easily pre-fill forms, plans and other regularly created documents. Names, dates, responsible staff and other default values are automatically filled in by the system when a document is created.
Where keywords can be used everywhere
Methodology content
You can use general keywords and keywords valid in a given methodology directly in the methodology documents. You can use a keyword instead of the name of the methodology to which it belongs, for example, in a directive
Documents created according to a template
For documents generated from the methodology - plans, protocols - it is possible to use keywords defined by the methodology from which the template comes. However, the keywords used for this case allow to refer to both the values set by the methodology and the project into which the document is created. Thus, for example, for a new project document it is possible to use keywords with the content given in the project (typically the name of the project, the name of the project manager, etc.)
How to define keywords
Keywords are part of the methodology, so the methodology is necessary for their use. Some keywords are transferred to the area / project where it is possible to define a value. But even in this case, they are words defined in the methodology
Keyword types
Within the methodology, keywords are defined that:
- Apply directly to documents in the methodology (e.g. date of approval)
- Apply to a document created according to the methodology model based on a value in the methodology.
- Transfer to the area or project where it is possible to set their value. Apply to a document at the time of creation of a document with values valid within the area/project.
Good to know
Keyword rights
The right to define keywords is linked to the methodology, so the permission of the methodology editor is required. Typically, this will be the quality manager.
The use of keywords takes place in the background and does not require any rights. It is of course necessary to have the right to perform the operation in which they are used - e.g. create project plan, but it is not necessary to have the right to work with keywords that are used in the template plans.
Keywords can be used for documents that use both markdown and HTML templates. In both cases, the same notation is used, i.e. {@