- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Ahoy SN ninjas!
Do you know if it is possible to move existing components (particularly sidebar panel items) from one page to another?
There was a page that has been deprecated by ServiceNow and I need to take the existing customisations from the deprecated one and move it to the new one. From "Record default" to "CSM Default record page".
Is there any chance to do so by a script or insert/stay or updating the parent?
What is needed, to move from deprecated (red) to the new one (green)
Before replacing the page and after, goal is to get from red to green
Do I need to create duplicate variants and then somewhere change the parent? or is it possible just to update it in some backend table?
And then eventually bring the same experience with buttons, related lists and everything to be as 1:1 as possible.
So many questions... Thank you in advance!
Where the rules are real, you'll find me
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
It is quite a lot of manual copy pasting of sys IDs but I managed to move the variants as needed.
First of all, I want to explain the difference between the deprecated and the new page.
You can locate the sections in the UI Builder > CSM Experience > CSM Default record (eventuall Default record) > right > Tab sidebar Legacy or Contextual sidebar
The difference between the 2 in backend:
Difference between the new variant and page collections, the legacy page goes with "viewport"
The CSM default record page was read-only so I created a duplicate of that page called "CSM default record page [new]", navigated to the path in the UI Builder editor mode and created the Viewports clicking the button below:
It converts the existing variants.
Then to move the variants from legacy/deprecated page, go to that page, settings mode and not editor:
Create a duplicate in the legacy page:
Go to the [sys_ux_screen] and locate that record to update its Parent macrocomponent and Screen Collection
https://yourinstance.service-now.com/sys_ux_screen_list.do
- Parent macro is the newly created CSM page >>> CSM default record page [new], that can be easily identified by its name.
- Screen collection is difficult to find as it holds the same name, so it is better to change it by sys_id.
To get sys ID of "Virtual agent" screen collection, locate that record in the UIB Settings, click the triple dots on the right (you might need to hover over, not always visible), select View settings:
Open records > Variant collection
New page is opened and it is a record that its sys ID you will be copying to the screen collection:
And after that, it is moved as needed:
sys_ux_screen
sys_ux_screen_type
If you want to know more details, let me know. Perhaps it could have been done in some automated way, I was doing it one by one to be sure that I have not missed any of the sections. You can also move the variant between pages directly as the legacy page will be deactivated afterwards but I decided to duplicate and move it instead.
Moving the variants worked good, some of them just missed the icon and changed the order.
To change the icons and/or order of the variants you can update it in [sys_ux_app_route] table, you might need to add the columns to the list vew.
Where the rules are real, you'll find me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
It is quite a lot of manual copy pasting of sys IDs but I managed to move the variants as needed.
First of all, I want to explain the difference between the deprecated and the new page.
You can locate the sections in the UI Builder > CSM Experience > CSM Default record (eventuall Default record) > right > Tab sidebar Legacy or Contextual sidebar
The difference between the 2 in backend:
Difference between the new variant and page collections, the legacy page goes with "viewport"
The CSM default record page was read-only so I created a duplicate of that page called "CSM default record page [new]", navigated to the path in the UI Builder editor mode and created the Viewports clicking the button below:
It converts the existing variants.
Then to move the variants from legacy/deprecated page, go to that page, settings mode and not editor:
Create a duplicate in the legacy page:
Go to the [sys_ux_screen] and locate that record to update its Parent macrocomponent and Screen Collection
https://yourinstance.service-now.com/sys_ux_screen_list.do
- Parent macro is the newly created CSM page >>> CSM default record page [new], that can be easily identified by its name.
- Screen collection is difficult to find as it holds the same name, so it is better to change it by sys_id.
To get sys ID of "Virtual agent" screen collection, locate that record in the UIB Settings, click the triple dots on the right (you might need to hover over, not always visible), select View settings:
Open records > Variant collection
New page is opened and it is a record that its sys ID you will be copying to the screen collection:
And after that, it is moved as needed:
sys_ux_screen
sys_ux_screen_type
If you want to know more details, let me know. Perhaps it could have been done in some automated way, I was doing it one by one to be sure that I have not missed any of the sections. You can also move the variant between pages directly as the legacy page will be deactivated afterwards but I decided to duplicate and move it instead.
Moving the variants worked good, some of them just missed the icon and changed the order.
To change the icons and/or order of the variants you can update it in [sys_ux_app_route] table, you might need to add the columns to the list vew.
Where the rules are real, you'll find me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
@Maria Gabriela shared a whole series about various UI Builder topics, check her article HERE.
For example:
UI Builder Essentials: Configuring Appointment Calendar Component
UI Builder Essentials: Checklist - Advanced configuration
UI Builder Essentials: Checklist Component Basic configuration
UI Builder Essentials: Using the Attachment Component
UI Builder Essentials: Client Scripts in UI Builder
UI Builder Essentials: Adding Declarative Actions - List Action Decorator
UI Builder Essentials: Next Experience Developer Tools Profiler Tab
UI Builder Essentials: Next Experience Developer Tools Inspector Tab
UI Builder Essentials: Next Experience Developer Tools Overview
...
Where the rules are real, you'll find me