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
Icons in the AyMINE system
Icons – as well as traffic sings – provides you by the solution. Although icons looks simple, they creates coherent and deliberate language.
The icon is an image that belongs to each object and function. Icons are on buttons and window headers and are the visual language of the entire system, making it easy for you to read quickly. In every situation, icons give you intuitive navigation what you are working with.
Icons are often paired in the same picture, just like a noun and a verb in a sentence. For example, the icon is a conjunction of task-new and indicates that you are using the function to create a new task. In general, verb icons are in circles in the lower right of the image, while the object is in the upper left. (The icon logic is completely managed by the application and so the icon language is not visible in documentation outside the system.)
Objects
Note: If you don't see icons for some objects, you have no rights for them.
The most commonly used icons are:
Notice. We've already written about it above.
File. You can attach files to many objects, so you can keep them for yourself and share them with others. For objects where this is possible, there is a files tab with this icon.
SystemArea. The system breaks down all content into areas, and for each one, there is separate control over who works with it. Therefore, it is likely that you will only see some areas and not others than your colleagues.
System User. This is you and everyone else who works with the system. Sometimes you may come across a user named anonym. This is a user whose name you are not allowed to show for some reason, such as GDPR protection.
Supervisor/Manager. The system allows you to define teams and their managers. The manager then has different rights to manage the team.
Role. Each user can have roles set that further modify what rights they have.
Role. A piece of work that you look forward to doing something with.
Task. From task patterns, specific tasks are created. Patterns make it unnecessary to always re-write what needs to be done.
Empty list When there is nothing to show in the desktop drawer or in the list, the empty icon is there instead.
Interface elements
Workspace The workspace is
- Your main dash board or
- Desktop for a system area or object that contains a lot of components
Warning: The option is not available on mobile devices and on computers requires you to enable popups. Otherwise, it will block your browser from opening. So when you click on the icon, enable windows and that's it.
Object Detail for editing (if you can edit the object)
Administration view Access to settings (e.g. areas) that are not used for normal day to day work, but where you edit, how the system behaves and most importantly who has access to what.
Operations
Create a new object. Examples include creating a new task, or creating a user group.
Add Assign an object. Assignment means that you logically associate an existing object with a new one. An example is to assign a task to a meeting, or to assign a user to a group._
Detach an object from another. The button with this icon does not delete objects, but the relationships between them. An example is to remove a user from a group. The user is still a user and nothing changes except that he is no longer in the group.
Dump to Trash Dumping an object to the trash; it is also used in object lists for objects in the trash (when you view deleted files.)
Delete Dumping without putting it in the trash. What you delete in this way is never undone.