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
Variant decision-making
Decision options are used to select the best possible solution or for voting.
A decision that is not a direct decision by one person (typically an ordinance) should have at least 1 option to vote on or multiple options to choose from.
Option description
The basic description is the title, which is often sufficient. Especially if it is clear to everyone what is being decided and voted on.
The decision proposal is used to give a complete description of what is being decided (e.g. a new version of the treaty). It is an important part of the description, especially for decisions that are not preceded by discussion, but also for documentation.
The Reason explains:
- Why the option was included in the ballot (e.g. most advantageous price)
- Reasons for voting for the option
- Reasons not to vote for the option
In particular, the reasons are important for the formal decision-making process that precedes the analysis. They are the result of the analysis of the options and the basis for the vote.
Voters (if voting is part of the decision-making process) should find in the reasons for the decision all the evidence needed for decision-making and voting. By placing them in the description of the option(s), they also become part of the documentation of the decision.