AyMINE – Technical documentation
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
Task, project & quality management
Administration of the Task Management Module
System rights for the task management module
Methodology and Quality Management systems
What a methodology / QMS consists of
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
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
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
Relatios between objects
Relatios are used to document user-defined relations between object. They do not supply or alter regular relations, but allow deep documentation of the real world.
What to related
Relatios are typically used in accordance to the internal methodology. Methodology is important because without that relatios and espcially information stored in the relations easily confuse other users that might not understand relation or not foung information hidden in unexpected field – relation description.
In a nutshell: use relation in scope an in purpose that is ashared among users.
Relation documentation
Relations are always beteen two object and cannot exists without that.
Except object, relations should have name, to make clear, why they are there. Other feilds are optional.
Name You can put whatever name you want. Nevertheless – for better clarity it is important to use the same name for relation type everywhere. That's why you can set name from pre-defined list. If list does not fit your needs, contact your administration. It is easy to update the list, when it makes sense.
Version Version is used in case that you have updates of model like releases, change analysi etc. It allows prepare new version and change old and new versoin after analysis and decision about the change.
Lock
Lock allow lock the relations and prevents delete. You shall unlock relations before delete.