Drag and drop Attachment Not working in workspace form.

[jss teja]

Hello Team,

I am facing an issue with file attachments in my custom workspace.

When I try to drag and drop a file into the attachment section, I get this popup message: 

"For our security , file drag and drop may not have been allowed . Please use the file upload option instead ."
However , my colleague is able to drag and drop files into the same form without any issue. To check further , my colleague impersonated me and tested again - and drag and drop worked fine for them under impersonation.

So the problem happens only when I try directly with my own login. I also have admin role.

Has anyone faced this issue before? is there any setting i need to check in ServiceNow or is this related to browser / system restrictions.

Thank in Advance

[GlideFather]

Hi @jss teja,

are you both trying to upload the same file format? Check the MIME type and the attachment size if both of these are acceptable.

Alternatively, navigate to System properties > Security:

and review following properties:

And/or this:

https://YOURINSTANCE.service-now.com/sys_properties_list.do?sysparm_query=nameLIKEmime_type&sysparm_view=  

Let me know what you've found..

EDIT: added the last screenshot and URL

[GlideFather]

@jss teja and another idea - it might be due to different browsers and/or extensions...

So to observe the behaviour:

• try to drag and drop on your laptop with your account,
  • mark the result
• try to drag and drop on your laptop impersonated for your colleague
  • mark the result
• ask your colleague to drag and drop in their laptop for their own account
  • mark the result
• ask your colleague to drag and drop in their laptop impersonated for yourself
  • mark the result

From these steps you might be able to spot any difference and find out whether it is related to particular role or browser/laptop...

[jss teja]

Hello @GlideFather,

Thanks for the solutions. We have already checked all the system configurations and performed the tests you mentioned, but we are still facing the same issue. That’s why we have raised a Hi ticket—let’s wait and see what they suggest.

[GlideFather]

@jss teja oki oki, please let me know about the solution from the HI Case