As a part of the new desk UI refresh, there are certain parts that are being planned on refactored on the roadmap for v13.
Routing: Currently the “desk” (admin) interface has hash based routing. Example the route for ToDo list is:
/desk#List/ToDo. In v13 the routes will be full routes, beginning with
app, so the url for to-do list will be
/app/list/todoand all urls will be prettier, like
/app/list/sales-order. (Edit: will try and drop the view identifier, so
Web Forms will be removed: The desk (app) interface will now be the common UI for all form based entries. Web Forms always had second class treatment, and the expectation from Web Form is of the full form. Also most of the code of Web Forms was patch work. Web Forms will now be accessible from the
/app/interface, so all Web Forms will start with the url
/app/form. Next questions is, will all users have access to all the desk features?
Restricted UI: Most of the standard desk elements will be optional and can be set via role. You can turn off the search bar, notifications, sidebars, timeline in forms. Most of the other features are already permission controlled.
DocType Layout: To allow for alternate layouts, there will be a new concept “DocType Layout” where you can arrange fields in different ways, these can be exposed to the user based on their preference. (PR)
Faster boot: There is also a plan to break up the current “boot” process inside the desk so it is much faster to load. This means that permissions and other objects will be fetched when required.
Why are we doing this? Web Forms is a half baked implementation of the Form object with a lot of features that are lacking. Instead of having two implementations, it seems a better idea to collapse it into one.
Why refactor routing? Since we are in the process eliminating Web Forms, it means that the “desk” which is a massive Single Page Application (SPA) needs to be opened up and made more modular. Also clean URLs are much nicer to read!
Is it worth it? Maybe. This seems like a risk, but these are all improvements in the overall architecture, capability and performance.