Sage 2023 - Shut off WebView in application

We run Sage 2023 in a terminal server environment. I want to shut off the web/internet on the dashboard.

Simply starting Sage 2023 creates 8 instances of WEbView per user.

This is absolute bs. How do we shut this off.

Just because you CAN do it, doesn't mean you should do it.

The architects of this software are clueless.

Parents Reply Children
  • 0 in reply to sevendogzero

    Everything needs a user ID and password, it is not just Sage Software portals.  

  • 0 in reply to StefanouM

    Stefanoum,

    You are absolutely correct. When I read your reply, I just realized how this business (most businesses) have changed to

    fit the internet/web way of operating.

    I've been in this business for 40 years, I remember calling Borland in 1987 while in Amsterdam. On the phone, no username, no passwords. Just needed some compiler support. Sure miss those days.

    When my customers call me on the phone, there's no better way to communicate.

    But I'm on the forum, and the suggestion box needs it's own username and password.

    If that's how Sage wants to manage it's suggestion box, whatever. Hopefully Sage has employees that read and recognize good ideas.

    The forum can't operate without members like you, and I thank you for your time and advice.

    Bret Stern

    ps. maybe I should retire Ha

  • 0 in reply to sevendogzero

    It's all good.  :)   Yes, Sage does monitor the Idea Site, and a large number of enhancements over the past few years have come from that site.  https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/  Almost 500 ideas have been incorporated in recent years. 

  • 0 in reply to StefanouM

    Indeed.  There is a tab for Planned ideas, for a preview of ideas that are in development... with a big list of ideas that are already implemented / completed.

    I don't think Sage owns the Ideas website itself, which would explain the separate login.

  • 0 in reply to Kevin M

    I find all those Edge WebView tasks annoying as well. I'll vote for it if you add it.

    Funny story, I was doing an install on a new server a few months ago and I was getting a new and unusual (for me) error. It made some reference to Edge and/or WebView, and there was KB with a bunch of steps to correct - and I finally looked and Edge wasn't even installed (yes, Windows server). I installed Edge and no more errors. Oddly enough, the KB never thought to mention it would be a good idea to check to see if Edge was installed.