AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
Business excelenece
Balance Scroecards
Task & Project Control
- Send customer answer in regards to the complaint
- Test
- Qualification of user or contact
- Project role
- What are the parts of the QMS documentation and model
- dragdrop
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Processing time sheets
- Project management items
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- task_taskobjects
- Project
- Reminders and Messages
- eventobj_raisingevents
- decision_decobjects
- eventobj_startingevents
- eventobj_eventbuttons
- Hierarch of testing and developing tests from requirements
- Deal management
- FMEA criteria for detection evaluation
- FMEA system functionality analysis
- Methodology how to conduct FMEA
- FMEA analysis of the failure occurence
- Analysis of the FMEA Severity
- FMEA Analysis
- Management of responsibilities - RACI Matrix
- RACI matrix for project
- Improvements and Preventive Measures
- Notice – example of use
- tskproblem_terminology
- 8D report - quality problem resolution
- Task Scheduling to the right time and scope
- Administration of the Task Management Module
- Adminitration of areas, projects, calendars
- Discussion
- GDPR and record of qualifications
- System rights for the task management module
- Project Planning
- Employee Tasks
- Incident and Quality Issue Management
- Collaborative Resolution of Multiple Problems
- List of business areas
- Required qualifications
- Plan template / strategy
- Decision
- Configuration Package
- Record template
- Change management process in a project
- Task list
- Requirements
- Team Member
- Right to Manage Qualifications
- Input requirements
- Obligation
- Competencies and Skills
- Problems, tickets and their management
- Meeting
- Package definition
- Phrases and terms
- Data Area
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Project definition
- Activity log
- eventinstances
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- Assignment of a New Task According to Methodology
- Objects related to the task pattern
- Effect of the task on the right to modify the atta
- Level of Competence
- Manager approval with the task report
- Region / project / methodology
- Manage your marks
- Task patterns saves work and improve quality
- Quality Management System (QMS)
- Task planning both in project and daily business
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
- Notification events
Interprocess management
Human Resources
- roles
- Staffer / Worker Management
- Human resources
- Digital Personnel Archive
- Personalistics - User Permissions and roles
- Candidates Management
- Manage department / division data
- Job Position
- Worker overview
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- Management of the staffer contracts
- Safety of the HR module
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Manage projects by goals
- Create offer for premium or B2B clients
- Offers summaries
- Create and recalculate offer using price lists
- Offer and Price Access Rights
- Creating and processing orders
- System order status query
- Order Reports
- Pricing
- Pricing – volume discounts
- Products and Goods
- Product status and change
- Product Units
- Quality criteria
- Why are the Quality criteria usefull
- DFEMA - FMEA of the product design
- HARA for product
Customer Relationship - CRM
- Contacts and directories module (
- System Permissions and CRM Module Settings
- Customer Order Overview
- Address books
- Address book list and management
- Privacy policy
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
- Bulk Emails
- Contracts
- Partner in a contract
- Message patterns
- Group of contacts from address books for better management
- Directory or people and companies
- Contact per person or company
- Quickly available contacts
Finance management
System modules
System management
- moduleclientoptions
- Electronic sign even on mobile device
- formattedtexts
- System Configuration
- Processes in use
- Client
- Public Client
- Configure gateways for external messages
- Corporate email and communication processing
- Email messages
- Rules for external messages
- Secure business communication
- Send SMS directly from CRM
- Call directly from CRM
- Documents and files
- Additional functions with files
- Copying and moving files between objects
- Picture presentation
- Public link to the document
- Recent Files
- Dashboard
- Object location on the board
- Client items
- Revisions and comments
- Securing posts and internal discussions
- Translations
- Record Relationships
- Relation types
- System Groups and Teams for rights settings
- User Processes
- System module
- System User
- User administration
- User Administration
- Connecting users to VOIP PBX
- Secure Key Wallet - Safe storage for digital keys
- Data vault | Company secret & Classified data storage
Framework
- frmobjectextension
- introhelp
- introhelp_mobile
- introhelp_aplikace
- versioninfo
- releases
- AyMINE modules and basic types
- cliplink
- introhelp_settings
- introhelp_deleting
- introhelp_dragdrop
- list_filtering
- Short AyMINE framework introduction
- AyMINE Access control and security
- AyMINE Modules
- Object locks
- System rights
- AyMINE Gestures and Keyboard Shortcuts
- AyMINE icons are language for fast orientation
- list
- introhelp_generalinfo
- introhelp_objectdetail
- introhelp_objectlist
- introhelp_privateobjectnotes
- AyMINE User Rights Control
- introhelp_dashboard
Customer Service Response Generation
AyMINE supports the generation of an email response within the helpdesk ticket (issue) solution.
- How to send messages to a helpdesk ticket
- Edit the template for the helpdesk message to the client
- Key Shortcuts
Helpdesk tickets are managed within Customer Service Support. Problem reports can be received directly from the form from the web, transferred from the e-shop or brought in by the trader. Emails are mostly further communicated and AyMINE supports their generation.
How to send messages to a helpdesk ticket
For each helpdesk ticket, the communication about its solution is kept on the communication tab.

The system creates a new email where the addressee is the one who reported the problem. If the client changes where the problem is solved, modify the person in charge in the ticket (issue).
If the template for the new message is prepared, the email will be automatically pre-filled.
Edit the template for the helpdesk message to the client
The message template can be defined separately for each helpdesk area. However, if the area does not have its own template, any template will be used. Templates are defined as other templates for email messages – more about them here. Only templates of the Auto Pattern type are used to automatically prepare the email.
Key Shortcuts
The template is automatically filled in. Always use the key field with @ before the word to complete the field from the problem / ticket.
Key Shortcuts about the problem
- _@reportedBy – Who reported the problem
- @problemName – Name under which the problem is registered
- @shortDesc – Brief description or name (if the brief description is not filled in)
- @problemDesc – Complete description of the problem
- @mark – Mark under which the problem is solved
- @company – Name of the organization / company that reported the problem (applies mainly to 8D reports, not to the regular helpdesk)
- @created – When it was reported
- @status – When it was closed
- @status – Current processing status
Key abbreviations about the worker who reported the problem
- _@salutation – Salutation (either stored in CRM or derived from name and language)
- @firstName – First name
- @name – Last name
- @titleAfter – Title after name
- @titleBefore – Title before name
- @subjectMark – The tag (only if you register tags with people in CRM)
Example of the message template:
Sample of the pattern in html. You can of course use the wysiwyg editor for editing.
<p>@salutation,</p><p>we are responding to your request @mark from @created</p>
<blockmark>
<p>@shortDesc<br>
</blockquote>
<div>Processing status: @status</div>
<div quote><br>
</div>
<div>We see the situation as follows:</div>