Getting help
The different options currently available are:
- eLearning platform with self-paced tutorials
- Read the online manual
- Watch these short videos
- Send an email to open a support ticket to support@hackolade.com
When opening a ticket
It is useful to share precise and detailed information in order to speed up troubleshooting and resolution:
- context: provide information about your situation, what you’re trying to accomplish
- steps to reproduce: list the different steps leading to the error message, and ideally provide the data model file. If necessary, you may mask information in the model file with File > Save Obfuscated As…
- current behavior: describe what happened. In most case, it is useful to provide screenshots or a short movie capture.
- expected behavior: explain what result or output you would expect for the operation. In some cases, it may help to illustrate with a mockup.
- additional information : provide other details that might help with troubleshooting and a speedy response to your request.
- log files: information from the application logs can be immensely helpful for our development team to diagnose and resolve the issue, ideally captured immediately after the issue occurred. Log files can be found:
-- Windows: in the C:\Users\%username%\AppData\Roaming\HackoladeLogs directory
-- Mac/Linux: in the Users/$USER/Documents/HackoladeLogs folder.
The XY problem
When creating a ticket for support, it may also be helpful to take into consideration the following...
The XY problem arises when someone attempts to solve problem X, and uses solution Y in an attempt to solve problem X, then also faces challenges with solution Y. Instead of seeking help for problem X, they request support for solution Y, obscuring the root cause and leading to miscommunication, wasted time, and suboptimal solutions.
The XY problem is further described here: In particular, it describes what to do about it:
- Always include information about a broader picture along with any attempted solution.
- If someone asks for more information, do provide details.
- If there are other solutions you've already ruled out, share why you've ruled them out. This gives more information about your requirements.
The kind of answers you will get to your technical questions depends as much on the way you ask the questions as on the difficulty of developing the answer.
Support response times and Service Level Agreement
Hackolade provides maintenance and support for its products according to the following Maximum Response Times and Maximum Resolution Times. The Maximum Response Time and Maximum Resolution Times identified below are calculated using standard business hours and days:
| Ticket Priority | Maximum Response Time | Maximum Resolution Time | Definition |
|---|---|---|---|
| 1 – Urgent | 15 minutes | 4 Hours | Critical Business Impact, production line down |
| 2 – High | 1 Hour | 8 Hours | Major Business Impact, multiple users affected, no workaround available |
| 3 – Medium | 2 Days | 2 Weeks | Moderate Business Impact, single user affected, workaround available |
| 4 – Low | 8 Days | 4 Weeks | Low Business Impact |
| 5 – Project | Timeframe to be decided through coordination between the Project Manager and development, based on resources available, requirements and time estimates. |