AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
CalDav, WebDav using Sabre
Business excelenece
Balance Scroecards
Task & Project Control
- Helpdesk ticket - reply to customer
- Test
- Qualification of user or contact
- Project role
- What makes up the methodology / QMS
- 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
- Records managed by a project
- 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
- Type of tests
- Deal management
- 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
- Notice – example of use
- tskproblem_terminology
- 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
- 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
- QMS and Task Management
- 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
- tskdefusertask
- Quality Management System (QMS)
- tsktask_batasks
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
- Notification events
Interprocess management
Human Resources
- hrstcontract
- roles
- Human resources
- Digital Personnel Archive
- Personalistics – User Permissions and roles
- Registration of job seekers
- Manage department / division data
- Job Position
- Worker
- Worker overview
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- modulesafety
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Project Goal
- Business Offer
- Offers summaries
- Recalculate bid
- 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
- DFMEA - Product FMEA
- Hara | Hazarad & Risk Analysis
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
- Groups of contacts
- Order overview for customer groups
- Directory or people and companies
- Contact per person or company
- Quickly available contacts
Finance management
System modules
System management
- moduleclientoptions
- digiSign
- formattedtexts
- System Configuration
- Processes in use
- Client
- Configure gateways for external messages
- Message with the outside world
- Email 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
- sysrole
- User Processes
- System module
- System User
- User administration
- User Administration
- Secure login to the sytem
- Connecting users to VOIP PBX
- Secure Key Wallet
Framework
- frmobjectextension
- introhelp
- introhelp_mobile
- introhelp_aplikace
- versioninfo
- releases
- AyMINE modules and basic types
- cliplink
- introhelp_settings
- introhelp_deleting
- introhelp_dragdrop
- list_filtering
- AyMINE intro
- AyMINE access security
- AyMINE Modules
- Object locks
- System rights
- introhelp_keyshortcuts
- introhelp_shortcuts
- introhelp_icons
- list
- introhelp_generalinfo
- introhelp_objectdetail
- introhelp_objectlist
- introhelp_privateobjectnotes
- AyMINE User Rights Control
- introhelp_dashboard
Public link to the document
If you need to insert a link directly to a document or, for example, to a bulletin board post, you can insert a link directly to the document that can be downloaded and opened without opening the document window detail.
Access rights protection
The link is still protected by AyMINE and the document can only be downloaded if the person who wants to download the document has the necessary permissions. The permissions are set by selecting Access permission in the document detail:
- Object related – the user will be able to download the file if he has the right to open the detail where the document is and download the file as follows.
- For the company – The document is published as public within the company. Therefore, anyone who is logged into the system (and is from the same company) can download the document. Without logging in, the file cannot be retrieved
- Public – The document is available to anyone and anyone who gets the link can download the file.
Even public links are safe
Often companies need to send a document safely to someone. Email attachments are not suitable for this (see notes at the end) and infrequently used public repositories are an even worse case. A public link is a more suitable solution for this. Send a link that is impossible to detect, so that only those who know the link can get to it. By the time you cancel a document's publication in AyMINE, no one can get to it, and so even an email link is not an afterthought.
Unlike public repositories, you still have control over where the document is stored and therefore its security is much higher.
What the link references
A public link gets you to the document, with the implication that it downloads the saved file directly. But it is still a link to the document. If you replace the file, the link remains valid and will return the newly saved file.
The link is not a public link to the image
A public link, even if an image is stored in the document, cannot be used as a link to a publicly available image. The link does not point directly to the file. AyMINE first evaluates the right to download the file. Programs that can download the image after inserting the link and e.g. immediately insert it into the document (e.g. Freeplane, editors, etc.) cannot handle the link and insert the image.
For the ability to insert images into documents, AyMINE offers use direct link to image.
You should know
Publishing a public document may violate your duty to protect the document. Never set a document to public if it is not intended to be public.
The public link you get can be used to download the document, but it is also a link that indexing programs are unable to use. Files linked in this way will not be found by Internet search engines.
While a link generally works on the Internet, it may not work in some companies' environments because their strict Internet access policies prevent it. AyMINE can do nothing about this; it is a company issue that prevents access to unknown links.
If you delete a document in AyMINE, or change its publishing rights, the link is no longer valid and the system will not provide any document.
If you use a link to a file within the information on a publicly available bulletin board, you should also mark the document as public. Otherwise, the system will redirect the bulletin board reader who is not a logged-in system user to a login page.
Why not put documents in email attachments
You should not put documents you send to someone in an email unless they are completely "public." While this is common practice, it is not good practice:
- The vast majority of people do not use encrypted emails. Therefore, a document goes through the Internet without any security. The principle of unsecured communication means that you cannot be sure who will get the document.
- Many email servers use unsecured communication with each other. Even if your organization is security conscious, you do not know how the other party's email is doing. In the event of a temporary communication failure, emails can also be stored on backup servers and remain there – even in long-term backups.
- Documents remain in your and the other party's email inbox in sent mail, archived in a folder or in a trash bin. They are thus stored in several other places, including long-term backups. They are also readily available in copies of folders on local computers (Exchange and other email programs also store emails on local drives) and are thus available for viruses, for example.
- Long-term storage of a document in an email increases the risk that an attacker who hacks into an email will get hold of documents. They can also be accessed by, for example, a service technician who gets hold of a computer during a repair.
- If there is personal data in the file – e.g. supporting documents for an external payroll accountant, sending them by email directly contravenes the GDPR. Such documents should never be sent by email.
- Documents in attachments are also expensive in the way they increase overall IT requirements. Your inbox and the recipient's are swelled by this and either much larger volumes of data must be backed up, or you have to delete your inbox more often and dedicate more time to it.
For all of the above reasons, using a document link is a preferable solution to a document in an email attachment.