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
Web Page Description
Description defines what is on the web page, what it consists of, and where it is located on the portal
- Building a Complete Page
- Creating a Page with a Script
- SEO Support for Pages
- URL Addresses for the Page
Building a Complete Page
CMS is very flexible in the ways it can create a web page. Some methods are intended for regular users, while others require the cooperation of administrators. A page is created from:
- Content described directly by the page
- Blocks attached to the page, composed of parts
- A script that generates it and is stored on the server
- Data outside the CMS, with the CMS used to determine which page to generate based on the request
Creating a Page with a Script
Generic Script for Page Creation
A page can be created by a generic script designed to create multiple pages, typically using blocks inserted into the page.
Setting up a page for a shared script:
- Assign a script to the page
- Assign blocks to the page that the script will work with. The script description indicates which blocks are needed and whether the script also works with the content of the page itself.
Page Created by a Script
A page can be created by a script designed specifically for that page. A typical example is a PHP script that generates HTML code.
Creating a page created by a script:
- Create the page
- Insert the relative address of the source script into the path. The system administrators will provide you with the address, as they have inserted the script on the server.
Note: Do not modify the path to the script, or the page will not function. All scripts for one client are located in a special area, and the script address is only within this area. It is not possible to call a script other than the one designated for generating the page.
SEO Support for Pages
CMS provides strong options for achieving the best position for a page in search engines – so-called SEO optimization.
For all the data described below, filling them in is optional, but they help search engines understand the page well.
Data Transmitted to the Sitemap
- Page Priority – Informs search engines about the importance of the page.
- Change Frequency – Indicates how often it is appropriate to check if the content of the page has changed.
- Include in Search – Allows search engines to prevent the page from being offered in search results. However, it is entirely up to the search engine whether to follow this or not.
The date of the last update of the page is automatically passed to the sitemap.
Data in the Page Header
Descriptive data used by search engines and partially by browsers are listed in the page header:
- Page Title – Title displayed in the browser toolbar and in search engine results.
- Web Description – Page description used by search engines. Limited to 160 characters. If not filled in, the description from the brief page description is automatically used.
- Keywords – Can help search engines correctly classify the page.
URL Addresses for the Page
Multiple addresses can be assigned to each page, which are redirected to.
Use redirection if the page previously had a different location and you want to ensure that it can still be found from the original addresses.
CMS automatically redirects the browser to the current address when one of these addresses is requested.