I did wonder though Olga, why does everything else work fine and not need the edge agent (printing, etc.) when using a smart client + Kinetic Form, but attachments do need it…
1 Like
same with client printing - when you just want to print you have to use Edge Agent. Without it your report can be downloaded and you can print it manually, but nobody liked it either.
So if I am on prem and I launch the smart client and open a form in kinetic, I need the edge agent to print? I didn’t see that happening, that’s why I asked the question. Why did I need it ONLY for attachements?
No, only when you launch Kinetic in browser. No smart client.
Right, my question is in the context of using the smart client. Why when I use the smart client do I get that exact same error about needing the edge agent to use attachments? I think the answer or wanting to not have the edge agent is futile, I just found it odd and now this post got my curiosity going again.
Probably because it does not check if it runs in embedded browser or not, what was done for printing much earlier.
Embedded browser is going away, anyway. Browser first is way to go.
3 Likes
No doubt!
And now it’s worse.
ANY type of link attachment, is being opened with the edge agent.
Internet type link attachments, ie with an url handler (Contains “://”), should be opened with the browser, not shoved off to the edge agent.
This broke a few things that worked perfectly fine in classic.
Non internet url attachments, ie, local links etc, should obviously still be fed to the edge agent.
2 Likes
Yep, even https://epicor.com. 
Make Attachment Links consistent when requiring when requiring Edge Agent - 6005
1 Like
this is a bug, you should report it. https:// were supposed to be opened in the browser
1 Like
Kind regards 
3 Likes
Mark, i am looking into this. I dont believe it is working as designed!
4 Likes
Thank you, Tim!
1 Like
I do. What I don’t believe is that is good design. 
Thanks for checking Tim.
3 Likes
Support re-opened the case and it now has a PRB assigned: PRB0296435
6 Likes
it is still for links like https:// only
2 Likes
Be nice if we could use contains → ://
Or make that optional, then we could use url handlers in the browser.
more details please
Well obviously http:// & https://
But you can set up custom url handlers in browsers to handle things
like
mysupercoolhandler://
or msteams:// etc
That does stuff.
If we could choose all that are LIKE %://% then the browser could handle those seamlessly if we wanted.
The browser then asks if you want to open the link in an external app that is registered for that handler.
Obviously exclude stuff like file://
The browser should filter that anyway, but I would lol.
2 Likes