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
Address book list and management
Directories are used to store business and people contacts. You can create any number of directories on your system and control access rights to each one.
The ability to use multiple directories allows you to have, for example, a business contact address book visible only to the business department and another business contact address book created for a specific project.
A address book is a business area and can contain tasks in addition to contacts. This allows you to log the tasks that need to be done with the contacts directly in the address book (e.g. their repairs, new menu calls, etc.)
Address book view
Directories are not usually managed by a company, so you will typically see all directories that you have access to in the address book list.
An area administrator has the ability to view all directories, not just those that it has access to. This gives it the ability to check and update user permissions. However, it does not have access to the data in the address book – individual people and businesses.
Address book Management
Creation
Use the New button to create a new address book. Required data is minimal – name and brief description.
Contact Access Permissions Settings
An important part of setting up a address book is to set the right permissions.
After each address book, you can create your own group of people who can access the address book. However, it is preferable to define a group for the address book to which you put roles or sections with access rights.
Remember:
- When you assign rights to individual people, you will also have to remove them. People who start new will not automatically get access rights
- When you assign the right directly to a department or role, everyone who starts the department or role will automatically get access rights. When they leave the department, they will automatically lose it again. Setting up roles will therefore make automation much easier.
Preview-only access
It is usually not advisable to give many people the right to interfere with directories. In directories, therefore, you can set who has read-only access to the address book and who can change contacts.
For workers, roles, or teams that should have read-only access, type in the Readers
Project Address book
It is often advisable to create a address book of people involved in a project. You create a address book for a project the same way as a normal address book, but set it up as a group of active users, a group set up for a project.
When you use a project group, each project member will automatically get access to the necessary contacts. With the end of the project or its departure from the project team, access to contacts will be automatically removed. As a result, sharing complies with GDPR requirements for contacts to be processed and accessible to people only for as long as it takes for services to be implemented – in this case, a project.
Why not give access to everyone
While it is convenient at first glance to make read directories available to all workers, there are a number of reasons why not to:
- Contrary to GDPR rules
- People can accidentally write or call someone they didn't want to originally.
- Business contacts are a significant value of a company and you should protect them from being stolen. It's not just the employees themselves, but someone else can access their account.