Record page to standard record page migration and its impact on the New SIR Analyst WorkspaceSummaryDuring the ServiceNow Tokyo family release, the Platform Team developed the standard record page and empty record page to make use of the new Voltron preset/controller work developed within UXF and UIB. The standard record page is a new page template that supports the functionality of the San Diego Record Page and new features designed to provide flexibility to the UIB developer persona. Terminology SRP - Standard Record Page. The SRP is a new page template designed to provide flexibility to customers to build/maintain new record pages in Now experiences using the new preset/controller technology. Presets - A description in metadata of how any given component may be auto-configured, so the page author does not have to set up all the boilerplate configurations. Controller - A module that encapsulates logic and functionality for use by preset-enabled components and regular components as well. A page can have multiple controllers or no controllers at all. Layout - The components on a page and their arrangement. What the user sees and interacts with. Advantages of moving to the new standard record page Simplified Page Creation - Component presets will automatically configure a component, so it's ready to work as soon as it's added to the page. Reduced Cost of Page Ownership - Component preset configurations are managed outside of page configurations and owned by the team that created the preset. Anyone can use the presets on their pages without having to own the underlying configuration. Ease of Page Maintenance - Component presets auto-wire components, and the configurations are owned by the preset author. The page author using the component presets doesn't have to worry about the long-term maintenance of the preset. Upgrade-Safe - Component preset ownership lives with the preset author. Template overrides of preset properties are owned at the template level. How does this impact the SIR Workspace released in February 2023? Standard record page will be supported in the new SIR Workspace starting from April 6th, 2023 and the minimum Platform Version would be Tokyo. What you need to do Start planning. Here are the three scenarios: If you are currently on the San Diego or Tokyo platform version and do not have any customizations listed in the Section-A in your current environment, you can start using the new SIR Workspace released in February 2023. However, to maximize the benefits provided by the platform and to get the latest features of SIR workspace released after April 6th, 2023, we recommend you upgrade to the minimum platform version Tokyo and the minimum SIR Workspace app available after April 6th, 2023.If you are currently on the San Diego or Tokyo platform versions and have customizations listed in Section-A in your current environment, you can explore the product capabilities, but we recommend you migrate to the new SIR Workspace after upgrading to the minimum platform version Tokyo and the minimum SIR Workspace app available after April 6th, 2023. This will allow you to utilize the benefits provided by the platform, and all the existing and new features of SIR Workspace released after April 6th, 2023, will be available. Also, all the customizations are preserved in future upgrades.If you are a new customer and want to start using the new SIR Workspace, we recommend you start with the minimum platform version Tokyo and the minimum SIR Workspace app available after April 6th, 2023. Section-A What customization you can get started immediately? Related lists to a record.Modification of form view of a record.Modification to list view of records.UI actions on list view.Any server side scripts. Section - B The following customizations should wait for standard record page support, which will be available after the release on 6th April 2023: Action bar entriesUI Actions on recordRecord Page Tabs (Playbook tab, Overview tab, Details tab)ViewportsContextual SidebarModals It is recommended to wait for standard record page support to avoid having to re-work these customizations later.