What details should you 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, such as the library ID or document ID.

In some cases, you may need to collect HAR files and JavaScript console logs for Google Chrome and share them with the service team in order for them to resolve the issue.

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@aodocs.com

Where can you find IDs?
           Library ID
           Document ID
           Workflow ID
           View ID
           IDs of files in Google Drive
Open AODocs from Google Drive
Collect JavaScript console logs for Google Chrome
Collect HAR files for Google Chrome

Where can you find IDs?

Library ID

You can copy the library ID from the URL when you open your library in the AODocs interface.

The example below shows the library homepage.

image01.png

Document ID

You can copy the document ID from the URL when you open a document in the AODocs interface.

Tip: You can also access the library ID from the document URL.

image02.png

Workflow ID

1. Access the library administration interface.

2. Select Workflows.

3. Open the required workflow.

Tip: You can also access the library ID from the document class URL.

image03.png

View ID

You can copy the view ID from the URL when you open a view in the AODocs interface.

image04.png

IDs of files in Google Drive

To find the ID of Google files, open the file. 

image05.png

To find the ID of non-Google files:

1. Open the file in the file preview.

2. Select Open in new window in the More actions menu.

image06.png

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

image07.png


Open AODocs from Google Drive

If you’re working in the Google Drive interface, you can open AODocs to find the IDs in the AODocs interface.

Note: You must have the Smartbar installed 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, access 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, access 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.

image11.png

7. In the Network tab, right-click anywhere in the network log section and select Save all as HAR with content. Save the HAR file locally and attach it to your ticket. 

image12.png

Was this article helpful? 2 out of 2 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.