Skip to main content
Solved

slow network mode related to attached pdf file


Forum|alt.badge.img+6
  • Do Gooder (Customer)
  • 18 replies

A few users are getting this error, when trying to view attachments in Apps 10

 

the attachment shows that it’s there, but they cannot view it. 

 

“ slow network mode click here to view attachments”

Best answer by Charith Epitawatta

Hi @dlyon6,

The users probably have slow network optimization enabled in IEE. Please ask the users to try below steps.

  1. Login to IEE and press ’Alt’ key. This will show the IEE menu bar at the top.
  2. In the menu bar, go to Tools->Options
  3. Go to 'Server' tab
  4. Uncheck 'Optimize for Slow Network' check box and press OK.

See if the issue persists after performing above steps.

Hope this helps!

View original
Did this topic help you find an answer to your question?

3 replies

Charith Epitawatta
Ultimate Hero (Employee)
Forum|alt.badge.img+31

Hi @dlyon6,

The users probably have slow network optimization enabled in IEE. Please ask the users to try below steps.

  1. Login to IEE and press ’Alt’ key. This will show the IEE menu bar at the top.
  2. In the menu bar, go to Tools->Options
  3. Go to 'Server' tab
  4. Uncheck 'Optimize for Slow Network' check box and press OK.

See if the issue persists after performing above steps.

Hope this helps!


Forum|alt.badge.img+6
  • Author
  • Do Gooder (Customer)
  • 18 replies
  • January 24, 2023

That did not work fully, now I get another error  “No attachment types enabled” 


Charith Epitawatta
Ultimate Hero (Employee)
Forum|alt.badge.img+31

Hi @dlyon6,

1. Please see whether following Permission Sets are granted to the users:

  • DOCUMENT_ATTACHMENT - Grants permission to use the Document Attachment Pane in IFS Enterprise Explorer
  • DOCUMENT_ATTACHMENT_VIEWER - Grants read-only permission to use the Document Attachment Pane in IFS Enterprise Explorer

If not, grant them.

2. Go to Refresh Server Cache window in IEE and do a Security and Object Connection cache refresh. 

​​​​​​​3. Ask the users to restart the application and see if the issue persists. 

Please perform steps 2 and 3 regardless of the result of step 1.

Hope this helps!

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings