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
Website Block
Blocks are the building blocks of websites and allow pages to be composed of blocks using a template
A website in CMS can be composed of individual blocks. In order to utilize blocks, the entire page must have a template defined. The template defines which blocks should be inserted into it.
Block Names
A block has two names – Custom Name and Template Name
Custom Name
The custom name identifies the block in the overview of all blocks. The name should be unique for the portal so that you can navigate blocks easily.
Template Name
The template name is the designation used for the field name in the template where the block should be inserted. It is the name of the field in the template to which the block belongs.
Examples of names in the template are topmenu, leftmenu, footer, etc.
Warning:
- The template name is a field filled from the client's dictionary
portal-UserType. Don't forget to fill in the dictionary or insert standard values into it. Without a filled dictionary, it won't be possible to fill in this field and use blocks. - Do not use the name
bodyfor any field. This name is reserved for inserting the body of the page.
How to Work with Blocks
Blocks can be inserted into individual pages, but also into sections. All blocks inserted into the page and all blocks assigned to the section are used for the page.
If a block with the same Template Name is assigned to both the section and the page, the block for the page will be used (it takes precedence over the block for the section).