AyMINE – Technical documentation
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Region / project / methodology
Change management process in a project
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Objects affected by the problem
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
Objects related to the task pattern
Contacts and directories module (CRM)
Address book or people and companies
Web management and automation
Receiving a message from the web
Asset management module
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
The AyMINE framework module
Configure how your system looks and works
Gestures and keyboard shortcuts
How the system works and how it protects data
Private notes and tags for objects
Filtering in the list of records
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Manage your marks
Mark management is used to set how objects will be marked when they are created in an area, project or methodology.
The settings must follow the purpose of the area and the methodology that will be applied in the project or area.
Abbreviation for marks
An acronym is a textual abbreviation that identifies an area, project or methodology. The abbreviation is then a standard part of the marks (within the template it is a placeholder for @amark).
If the marks are intended for user use only and no rules for reliable object identification are specified, it is most convenient to leave editing enabled.
Under this option, new objects will be assigned marks, but the user has the right to modify them if necessary. This allows, for example, to change the mark of a new object to an old one and to delete the old one. Most importantly, it allows you to set important objects with marks that are easy to remember.
With this setting, the system does not assign marks and they are fully under the control of the users. This setting is particularly useful when objects receive marks outside the system and are transferred to AyMINE.
It is recommended to use the mode e.g. temporarily when external objects need to be entered (e.g. user requests entered by a customer). The settings can then be changed and internal objects can be numbered system-wide.
Modifications not allowed
The marks are assigned by the system and cannot be changed by the user. This mode ensures that once a mark is assigned, it always identifies the same object.
This mode is particularly useful in situations where you generate text documentation from the system, e.g. for suppliers. They receive your marks and it is important that they cannot be changed once they have been handed over.
Cannot be unblocked
This is a mode very similar to the previous one – Modifications not allowed. This mode, moreover, once set, cannot be changed. The goal is to block the setting and prevent anyone from being able to disable it, even temporarily.
If this mode is set, only a staff member with project area administrator privileges can make changes.
Marks cannot be entered in this mode.
Lock marked objects
Check-box sets that objects that have a mark cannot be deleted.
The lock check-box setting, together with the Cannot Unlock mode, creates a mode according to the file service rules – once an object is inserted into an area (file), it cannot be renumbered or deleted.
The lock makes sure that nothing in the area is accidentally removed.
If the Cannot unlock mark mode is set, it is not possible to change the settings of this check-box either.
Setting marks in the area hierarchy
The mark mode setting always applies to the area, project or methodology in which it is set.