Frequently Asked Questions (FAQ) for New UI

related readings about cet new ui docid\ f2tg jo1hj6hh3ijzy06b for an overview of the new ui changelog docid\ iwa76uv4j2sm rsuq1iql for a summary of changes new ui adoption info docid 6gt6if5vsp9epg7g9cpig for suggested timeline for migration general why new ui? at configura, we care deeply about the overall user experience and we strive to be the world's most intelligent platform for designing sustainable, efficient, and beautiful spaces the new ui aims to provide a more modern and visually appealing design, improving the usability of the system and consistency of the platform, while we will incorporate user feedback and industry best practices to ensure that it meets the needs and expectations of our users the new design guidelines aims to align everyone working on the cet platform to improve quality, design cohesion, and consistency this reflects our commitment towards the cet ecosystem and our developer community why release the new ui with a toggle? why let users choose which ui they want? major ui updates often carry risks, as users may need retraining or time to refamiliarize themselves with the new interface the new flow might not suit all use cases, and some users may resist change altogether although the updated design is guided by ux research and best practices, cet is a large platform, and it's impossible to account for every scenario and user need therefore, the toggles offer a safe way for users to experiment with the new design, while allowing us to gradually roll out the ui this approach helps us test, validate, and adjust our assumptions based on user feedback what is the timeline to deprecate the old ui? the tentative plan is for the old ui to live on until 16 0 (2025 may), and during this transition period, the user will have the choice of which ui they want to use how much of cet will be updated? in 15 0, just the main window, and 4 core tabs other cet tabs and functionalities will be updated with future releases partner/manufacturer will have to update their own extensions (optional for 15 0) please refer to the about cet new ui docid\ f2tg jo1hj6hh3ijzy06b for summary of changes, and new ui adoption info docid 6gt6if5vsp9epg7g9cpig for suggested timeline for migration what support will there be for learning the new interface? will there be updated user documentation? we will have our regular what's new webinars with the 15 5 release trainings and help articles will be updated over time as the new user interface is solidified after user feedback and iteration are there any changes with hardware or system requirements with new ui? no, there are no changes to system requirements to use the new ui who do i contact with any bugs/issues, questions or feedback for the new ui? partners and developers can contact us through the same channels provided by developer support, while end users should contact cet support as usual partners / manufacturers please refer to new ui adoption info docid 6gt6if5vsp9epg7g9cpig for scope of work and timeline i am an extension owner / partner / developer, what do i need to do for the upcoming 15 0 (may 2024) release? for the upcoming 15 0 (may 2024) release the new ui will be released as an opt in setting, the default ui is still the old ui, so you are not expected to adopt the new design or do anything with it however, we invite you to try it out, read the new design guidelines, pre plan your efforts, and provide as much feedback as possible for us to improve! on the other hand, you will still have to perform a basic migration for 15 0, which means fixing bugs or code breakages as documented according to the migration guide for a major release, just as usual we recommend for you to verify that your ui is still working normally in the old ui i am an extension owner / partner / developer, what do i need to do for the upcoming 15 5 (nov 2024) release? for the upcoming 15 5 (nov 2024) release the new ui will be released as an opt out setting, i e the default ui is the new ui while you're expected to start reviewing the new design guidelines and plan towards an adoption, you're not expected to release your extensions with an updated ui however, we invite you to try it out, read the new design guidelines, pre plan your efforts, and provide as much feedback as possible for us to improve! on the other hand, you will still have to perform a basic migration for 15 5, which means fixing bugs or code breakages as documented according to the migration guide for a major release, just as usual we recommend for you to verify that your ui is still working normally in the old ui how much more time will i need to plan for 15 0 migration with cet facelift compared to my regular migration? for 15 0, you are not expected to adopt the new ui however, in addition to regular migration work, you should verify that your old ui is still working normally and report any issues to us we recommend to budget an extra 10 20% time on top for such work when can i start migrating my extension to adopt the new ui? the new features will be available starting 15 0 beta end of march 2024, while the new guidelines will be released as a beta in may 2024, so you are free to check out the new code and functionalities to assess the new ui's impact on your extensions however, please note that you are not expected to adopt the new ui or actually start any ui work in the 15 0 (may 2024) release when must my extension be migrated by (adopt the new ui)? overall timeline of migration 15 0 (may 2024) cycle you are not expected to adopt the new ui 15 5 (nov 2024) cycle you should review the guidelines and plan necessary work 16 0 (may 2025) cycle your extensions should complete the adoption of the new ui please note that you can decide your plans and release cadence (for example one toolbox at a time, or all at once) of new ui adopted, based on product vision, ambition level and budgetary concerns what is the suggested adoption timeline? 15 5 (november 2024) is when configura recommends partners to start adopting the new ui in their extension toolboxes this means august 2024 partners should plan ahead to review changelog and the new ux design guidelines, and identify necessary adoption work september 2024 (15 5 feature freeze) review beta changelog, update the plan for necessary migration and perform adoption work 16 0 (may 2025) is when configura plans to phase out the old ui, so adoption of new ui should occur before it is important to note that partners can decide on the cadence of their updates, so they can decide to work on and release the new ui changes anytime between september 2024 to may 2025 what happens if i decide to not adopt the new ui for my extensions by 16 0 (may 2025)? while currently we do not foresee any major breakages with such a decision, the old ui will no longer be supported after its end of life over the long term, we still strongly encourage that you review the design guidelines and adopt the new style, so that your extension and your users will be able to reap the benefits of a standardized user experience and take advantage of the new features provided in core please provide us with as much feedback as possible for us to help smoothen the transition should i support the old ui? do i need to maintain two versions of my extensions now? while configura will still maintain necessary functionality for the old ui, the old ui will be deprecated after 16 0 (may 2025), and new ui is the future while the transition period is ongoing, if you have an existing old ui toolbox, we recommend to maintain two versions of the toolbox, but any new work is expected to target the new ui it is also acceptable if you do not want to maintain the old ui anymore and go all in with the new ui, as new ui toolboxes will work in the old ui (albeit imperfectly, with a tighter spacing in its layout) migration / adopting new ui what is the difference between adoption and migration? basic migration refers to the mandatory effort that partners perform every release to update their code to work in the new major version according to the migration guide, regardless of old or new design for example, code changes, compile errors, bugfixes adoption of new ui refers to the optional effort to rework the extensions to fit the new design guidelines e g update partner extension component libraries to comply to the new guidelines with new icons will there be an icon library? can configura help us with making new icons? there will be standard icons included in the development environment that developers will be able to utilize to update your extensions, and we have released an icon library docid\ ufrg7rrlofpuun mlb67d that partners can download if you require any expertise to create custom icons or redesign of toolboxes, please reach out to customer delivery or our design service partners for options will there be a migration qa guide? yes, we will be releasing a testing guide to help partners assess quality work for the 15 0 release do we need to follow the same icon style / visual aesthetics like configura? e g flat line illustration style can i still use an image or renderings of my products? for actionable or standard system operation icons (e g save/load/help), we encourage you to use the same icons or pattern in the core application, to promote consistency among extensions for specific, real products, you may still use rendered icons (product renderings) or custom icons in any case, try to adhere to the icon sizes specified in the guidelines do i need to update all my custom dialogs and functionalities? we only expect you to adopt the new look for your extension component tabs we understand that there may be a lot of custom dialogs and functionalities developed by partners that will take more work to update, so while we encourage you to review the design guidelines to maximize user experience, you are not expected to update all custom dialogs do note that you can decide based on product vision, ambition level and budgetary concerns, when and how much you want to adopt the new ui guidelines for these custom functionalities how much effort will it take for me to update to the new look? read the overview at new ui adoption info docid 6gt6if5vsp9epg7g9cpig here's some estimated figures from a developer point of view effort / target level what none ("get for free") new font new dropdown/button/menu styles (if using 100% standard control) minimal adoption (size s / 2 6h) new toolbox header and sections look new button frame style adjusting margins and grid layouting updating new icons (if icons existing) average (6 24h) updating new icons to match new requirement of sizes (re render all icons) adjustment of custom functionality or custom controls in toolboxes (50% standard functionality) implementing tool groups to reorganize your product variants unknown (depending on level of customization and ambition) recreating icons to fit a particular style (e g flat design) or due to lack of larger resolutions / vector originals any 90 100% custom toolbox functionality study design guidelines and rethink in terms of usability compliance please contact developer support for more specific questions and feedback