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
Formatted texts in the app
The application supports two document formatting styles and in some cases gives you a choice of which to select.
It is possible to save formatted texts for many records in the application. Working with them is more convenient and usually safer than saving information in embedded files,
In a nutshell: Markdown or HTML?
If you don't need styles and font colors, Markdown is preferable. But if you can't do without colors, you'll have no choice but to choose HTML.
It's a choice
The app usually doesn't give you a choice - simply because the different formats would create confusion that would outweigh the benefits. By default, Markdown is used everywhere, albeit with a number of extensions.
Currently, the HTML format is used by default only for emails. The reason for this is that HTML is the standard in email, and formatting an incoming email into a reply requires HTML elements.
Optionally, HTML can also be used for writing information. Other objects with HTML can define modules.
Formáty textů
Texty je možné ukládat ve formátu Markdown nebo HTML. Standardně je používán formát Markdown, protože má mnoho výhod.
Markdown a jeho vlastnosti
Markdown je standardní formát, jeho struktura je jednodušší a neobsahuje tzv. párové značky. Díky tomu nehrozí, že se rozpadne jeho struktura, jak se to snadno stane u HTML, když do něj zabloudí např. nějaké <div>
navíc. I když se to nezdá, tak např. pro automatické překlady jde o výhodu zcela zásadní
Není všechno čisté
Markdown ve své čisté podobě bohužel neumožňuje např. vložení obrázků nebo tabulky. Aplikace proto využívá rozšířenou syntaxi, která tyto reálně nezbytné možnosti doplňuje.
HTML a proč má někdy návrh
Pokud potřebujete detailnější formátování nebo uložit vstup z internetu, bude "tzv. ruční formátování" vhodnější.
Ručně formátovaný text je uložen ve formátu HTML, používá jiný editor, který dává další možnosti:
- Zarovnávat text
- Lépe pracovat s tabulkami a bloky
- Používat barvy písem
- Používat fonty
Risks and disadvantages of HTML
HTML has disadvantages that make it not used by default. It is good to keep them in mind:
Font colors
Font colors are fine, but only as long as everyone views the text on equal terms. But remember that half the people use light backgrounds and half use dark ones. If you give some text a red or bright blue color, it's fine. But if you force, for example, black or, conversely, light gray or any color on the edge of light and dark, half of the readers will have a problem with it.
Note: The reason for not using colours is quite fundamental to not using them in e.g. requirements. There is a great risk that the solver may not notice parts of the text. Therefore the application does not support the use of colors in requirements.
Font style
Font styles help to highlight certain passages, but as with colours, what you see may not be seen by the reader. For example, mail doesn't use fonts, or most browsers don't use them by default. Styles in email should therefore not be used at all.
Styles don't carry over to generated PDF documents either; the generator has its own font sets. Therefore, the highlighting you have on screen will look different in the document.
Styles may not even be available to the reader who receives the information - their browser may not download the fonts; this is common on mobile phones, for example.