Technical support rules
Support resolves tickets faster when all information is in the first message. Follow these rules when creating one.
One ticket per question
Create one ticket per question, problem or request. Do not combine two questions, problems or requests. Otherwise support closes the ticket and asks for one per issue, delaying resolution.
Application
Select the relevant application in Application. Its support specialist receives the ticket.
Subject
Write a subject identifying the issue without opening the ticket.
Valid examples:
- How do I create a camera file for the attached certificate?
- Add a command to locate entities with an odd number of vertices.
- Problems exporting the attached file to .shp.
Invalid examples:
- Error in Digi3D.
- Question.
- Request.
Problem description
Describe the question, problem or request as precisely as possible. If support cannot reproduce the problem from it, more information will be requested, delaying resolution.
Valid examples:
- Opening in GlobalMapper the .shp generated from the attached drawing with the attached code table shows entities on the "Viales" layer stored as closed polygons instead of 3D polylines.
- The program always exits unexpectedly when I measure an absolute orientation, finish measuring all points and start clicking Delete point. Deleting the last point exits the program. This is not random: it happens 100% of the time.
Invalid example:
- The program crashed.
Support cannot reproduce the problem with so little information.
Attachments
Attach every file needed to reproduce the problem. There is no size limit: attach flight images or complete .las files. See Attach files to a technical support ticket.
Examples:
- For a drawing export problem with .shp, attach the drawing and code table.
- If an orientation cannot load, attach its file.
- For an absolute orientation problem, attach ground control points.
Missing files will be requested, delaying resolution.