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
Pocketbook
Pockets are a primer on how to keep important objects organized for yourself. Pockets are a private container where you can put objects you want to keep together for whatever reason.
Example use:
Preparing important objects for meetings. You can put objects you want to have available in a pocket so you don't have to search for them when the need for them becomes apparent.
Working on requests. You can put requests (or any other objects) that you are currently working with, but that are from different projects, for example, in a private pocket. This way, you have them together for your work and putting them in your pocket does not affect other people's work.
What you can do with your pockets
You can create pockets for your own use, name them as it evaluates and put objects in them.
When a pocket stops making sense, you can easily delete it. Deleting a pocket has no effect on the objects that were in it.
Don't forget
- No one can see your pockets. This has its advantages and disadvantages. For example, no one else can find an object by the fact that it is in your pocket.
- A pocket doesn't protect an object. The fact that an object is in your pocket does not prevent someone else from changing or removing it (if they have the rights to do so). If it is important to you that no one deletes the object, you need to lock the object (not all pockets support this).
- Pockets are not meant to replace the proper organization of objects. Pockets create an order that is useful to you, but you need to put objects where they belong – especially in the right area. Pockets are a tool for storing current information, not a long-term archive. This is also why the pocketbook is limited in size – you can create up to 30 pockets but no more.