What details to share with the AODocs Support team when you open a ticket?

When you open a ticket for an issue relating to an AODocs document or library, you’re recommended to indicate the relevant IDs. For example, the library ID or document ID.

You may also need to collect HAR files and JavaScript console logs for Google Chrome and share them with the service team.

This helps the AODocs Support team resolve your issue quickly.

Note: AODocs support agents don’t have access to any of your files in Google Drive. 
If you want to share specific Google Drive files to our Support team, share them to: support-team@altirnao.com.

Automatically generated table of contents


Where can you find IDs?

Library ID

Open your library in the AODocs interface. Copy the library ID from the URL.

The example below shows the library homepage.

image01.png

Document ID

Open a document in the AODocs interface. Copy the document ID from the URL.

Tip: You can also access the library ID from other URLs.

image02.png

View ID

Open a view in the AODocs interface. Copy the view ID from the URL.

image03.png

Workflow ID

1. Open the library administration.

2. Select Workflows.

3. Open the required workflow.

image04.png

Document class name or ID

The document class name and library ID are usually enough for troubleshooting. However, you may need to provide the document class ID.

New library interface

image05.png

Legacy library administration interface

If you need the document class ID, there are two places where you can find the document class ID in the legacy library interface.

In libraries with a workflow:

1. Open the library administration in a library with a workflow.

2. From the workflow configured for the document class (if one is configured):

  • select Workflows
  • on the required workflow, open the corresponding document class
image06.png

You can find the document class ID in the URL.

image07.png

In Document Management libraries only:

1. Create a new document in the required document class.

2. Before saving the document, recover the document class ID.

image08.png

Relation ID

1. Open the library administration.

2. Select Relations.

3. Open the required relation.

image09.png

Version ID

Open a previous version of a document in the AODocs interface. Copy the version ID from the URL.

IDs of files in Google Drive

To find the ID of Google files, open the file in Google Drive. The ID is in the URL. 

image05.png

1. Open the file in the file preview.

2. In the More actions menu select Open in new window.

image06.png

You can find the ID of the non-Google file.

image07.png


Open AODocs from Google Drive

You can open AODocs from the Google Drive interface. You can then find the IDs in the AODocs interface.

Note: You must install the Smartbar to do this.

1. Open your library In Google Drive.

2. Right-click the library root and select Open with > AODocs.

image08.png


Collect JavaScript console logs for Google Chrome

1. In Google Chrome, go to the page where there is an issue.

2. In the More actions menu, select More tools, then Developer tools.

image09.png

3. In the Developer tools panel, select the Console tab.

4. Reload the page and reproduce the issue you were having on the Google Chrome page.

5. In the Console tab, right-click anywhere in the console log section and select Save as. Save the console log file locally and attach it to your ticket.

image10.png


Collect HAR files for Google Chrome

1. In Google Chrome, go to the page where there is an issue. 

2. In the More actions menu, select More tools, then Developer tools.

3. In the Developer tools panel, select the Network tab.

4. Activate the Record network log button.

5. Select the checkbox Preserve log.  

6. Reload the page and reproduce the issue you were having on the Google Chrome page.

7. Click the Export HAR (sanitized) button. Save the HAR file locally and attach it to your ticket.

image16.png

Was this article helpful? 6 out of 7 found this helpful
If you didn’t find what you were looking for, don’t hesitate to leave a comment!
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.