AyMINE – Technical documentation
sys
- Translations
- System module
- User Administration
- System User
- Documents and files
- sysrole
- Record Relationships
- Client
- Dashboard
- Public link to the document
- moduleclientoptions
- Revisions and comments
- User administration
- Copying and moving files between objects
- Object location on the board
- Additional functions with files
- Client items
- Picture presentation
- Secure login to the sytem
- Configure gateways for external messages
- Connecting users to VOIP PBX
- Call directly from CRM
- Send SMS directly from CRM
- formattedtexts
- Secure business communication
- System Configuration
- User Processes
- Processes in use
- Message with the outside world
- Email messages
- Relation types
- Securing posts and internal discussions
- Recent Files
- Crypto Wallet
- digiSign
tsk
- Required qualifications
- Package definition
- Phrases and terms
- Data Area
- Test
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Meeting
- Problems, tickets and their management
- 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
- Project definition
- Activity log
- eventinstances
- tskdefusertask
- Methodology and Quality Management systems
- My Tasks
- tsktask_batasks
- Project Team
- Events and meetings
- areamethodologies
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
- Manage your marks
- Region / project / methodology
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- Assigning a new task
- 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
- Requirements waiting for you
- Notification events
- List of business areas
- Qualification of user or contact
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- My projects
- task_taskobjects
- Project
- Reminders and Messages
- eventobj_raisingevents
- decision_decobjects
- eventobj_startingevents
- Sample tasks and methodologies of the area
- eventobj_eventbuttons
- Records managed by a project
- Timesheet
- Project role
- What makes up the methodology / SMJ
- dragdrop
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Type of tests
- The person responsible for the task
- Deals / Contracts
- Customer Service Response Generation
- 8D report
- Task Scheduling
- 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
- tskproblem_terminology
- Notice – example of use
- FMEA - Detection
- FMEA - Features
- FMEA Methodology | AyMINE
- FMEA - Occurence analysis
- FMEA Severity analysis
- FMEA
- Management of responsibilities - RACI Matrix
- RACI Matrix for Project
- Improvements and Preventive Measures
crm
- Directory or people and companies
- Address books
- Contact per person or company
- Order overview for customer groups
- Customer Order Overview
- Message patterns
- Quickly available contacts
- Contacts and directories module (
- Address book list and management
- Privacy policy
- Groups of contacts
- System Permissions and CRM Module Settings
- Contracts
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Bulk Emails
- Partner in a contract
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
am
- Product Categories
- Analytical model
- Products, assets and sales
- Products and Goods
- Tendering and purchasing
- Product Supplier
- Product status and change
- Project Goal
- Business Offer
- Recalculate bid
- Pricing
- Pricing – volume discounts
- Offers summaries
- Order Reports
- Quality criteria
- Creating and processing orders
- Product or Product Property
- Why are the Quality criteria usefull
- DFMEA - Product FMEA
- Hara | Hazarad & Risk Analysis
- Offer and Price Access Rights
- Product Units
- System order status query
frm
- list
- AyMINE intro
- releases
- introhelp
- AyMINE Modules
- Object locks
- introhelp_settings
- list_filtering
- introhelp_icons
- introhelp_deleting
- introhelp_dashboard
- introhelp_objectlist
- introhelp_generalinfo
- introhelp_objectdetail
- introhelp_privateobjectnotes
- cliplink
- introhelp_keyshortcuts
- introhelp_dragdrop
- System rights
- frmobjectextension
- versioninfo
- introhelp_shortcuts
- AyMINE access security
- AyMINE User Rights Control
- introhelp_aplikace
- introhelp_mobile
- AyMINE modules and basic types
hr
- Human resources
- Worker
- modulesafety
- Personalistics – User Permissions and roles
- Manage department / division data
- Synchronizing staff and system users
- Responsible HR Manager
- roles
- Registration of job seekers
- An overview of your staff
- hrstcontract
- Digital Personnel Archive
- Job Position
- Worker overview
Event activation buttons
From a task, you can activate an event using a button. The button will be offered to the user in the task detail if the condition for the occurrence of the event is User Button. Depending on the type of condition, the option will affect how the task behaves.
Every Event Activation
User Button
The user will be offered a button with the name entered in the Button field and the interim event generation icon. If specified, the help will be displayed when the mouse hovers on the button.
The user will generate this event by pressing the button and the task will continue; its status is unchanged. The object state attribute from this setting is irrelevant to this option (it is not reflected anywhere in the system behavior).
End User Button
As in the previous case, the button will be offered with help, if applicable. The icon will indicate the end event.
After the user invokes the event, the event itself is activated, but the object state is also changed to the state specified in the Object state. The specified state should be the end state (Completed, Cancelled).
What to use the event-related buttons for
The definition of the event together with the button creates the possibility to control the processing of follow-up steps directly from the task. By terminating a specific action instead of the "normal" end of the task, the user can directly activate the follow-up task.
Example (end event): The manager receives a draft document from the employee for approval. The task can be terminated with the accept or reject buttons, and depending on the option, another follow-up step is activated. In addition, the worker's decision given by the button option is archived as an event for the task.
Example (running event): Within the task that the worker receives based on the pattern, there will be an option to "report a problem" (escalation). With this button, the worker can start solving the task at the level of his or her manager. At the same time, however, the task remains open and active for him or her to process. The manager will be given a new task on the basis of which he or she can engage in solving the problem or otherwise react.