FAQs: LabKey Server Redesign
In the 17.2 release of LabKey Server, we included an experimental feature that allows teams to explore the beta version of the redesigned LabKey Server UI (scheduled for full release as part of v17.3). The key priorities for this redesign are to transition the platform to using modern technologies that will increase its stability and ease of use, and to respond to user feedback about areas of the platform that needed to be reworked to better support today’s users.
As you explore the new UI, we encourage you to provide feedback about the design and any technical bugs you come across. This will help us make adjustments during the next few months of active development before the initial release. Below are the answers to some common questions you may have when testing the new UI on your LabKey Server. We will continue to add to this list as we receive additional feedback.
Do we have to transition to the new interface or can I keep using the old one?
In 17.2, you’ll have the option to turn on the new look and feel by going to the experimental features listed under the Admin Console and enabling “Core UI Migration.” This will be opt-in, but we recommend you take a look now and provide feedback!
Since this turns the new interface on for all users, and this is still undergoing significant development, we recommend that you turn this on first on your test and/or staging server(s) and not yet on production.
With the 17.3 release, all installs will be moved to the new interface and the old UI will no longer be available for use.
What will happen to my custom CSS when we switch to the new UI?
To support the redesigned UI we are utilizing the standard Bootstrap framework and refactoring a good portion of our own CSS in order to make it easier to maintain the platform in the long run. It is likely that your custom CSS will need updating as a result of these changes.
We recommend that you move your staging server over to the new UI as soon as possible in order to evaluate and update any custom CSS that does not render correctly in the interface. If you are a Premium Edition client, contact your LabKey account manager if you need support making these changes.
Why does my site logo look broken?
By default, the 17.2 release uses the Seattle theme, which has a dark blue bar at the top of the header. Logos that use transparency may look wrong if they were previously on a white background. To fix this, you either upload an alternate version of your logo that will render well on dark background or you can switch to the Seattle Light theme which has a white top bar by going to Admin Console and adjusting your Look and Feel Settings.
Can I change the colors used in the interface?
In the beta release of the interface with v17.2, there are two default theme options to choose from: Seattle and Seattle Light. With 17.3, we expect to have the full suite of themes available for use, with a light and dark version of each. Additionally, you will still have the option of writing custom CSS.
We plan to introduce additional customization options as part of future releases that will allow you to more easily change change specific variables without writing your own CSS.
How do I add webparts to my pages in the new UI?
In order to streamline our page controls, we decided to make those that are used less often only show up conditionally. Most of our administrative controls are now available only when you go into admin editing mode. To turn this on, you can go to the admin dropdown and select “Page Admin Mode” (provided you have administrator permissions):
While this editing mode is on, you have the ability to add, move, or remove webparts and adjust page tabs just as you did in the previous versions. You can exit this mode by clicking on “Exit admin mode” in the header or in the admin dropdown.
I found a bug with the new UI. How do I report it?
You can report bugs using the “Give Feedback” link in the top right corner of the new UI. This link will redirect you to a feedback form on the LabKey Support Portal where you can report issues as well as general feedback. Please provide clear steps on how to reproduce bugs you encounter so that we can appropriately investigate and prioritize changes to be implemented in the 17.3 release and beyond.
I use ExtJS 4.x in my applications, why does my view not show up in the new UI?
With the introduction of the new UI we were able to move away from ExtJS 4.x for rendering menus. This was the last “site-wide” dependency we had on ExtJS, however, we still continue to use it throughout the product in different views, reports, and dialogs. To manage these usages we use our dependency framework to ensure the correct resources are on the page. The framework provides a variety of mechanisms for module-based views, JavaServer Pages, and Java.
If your applications do not declare their dependencies, it is likely they will fail to load when they are loaded independently (without other views/apps on the page that might be declare the same dependencies).