UI Builder page disappears after adding parent_macroponent_composition_element_id

Casper6060
Mega Sage

I set up a button on a related list to open a UI Builder page inside a modal.

 

Part of doing this has you add the modal id inside the field parent_macroponent_composition_element_id on the sys_ux_app_route record. But when doing this, the page does not show up in UI builder, so anytime i need to make changes to the page i need to find that sys_ux_app_route record and remove the value modalContainerViewport from the parent_macroponent_composition_element_id field.

 

I tested in Washington release and still had the same experience, has it not been fixed yet or have i misunderstood something and configured something incorrectly?

1 ACCEPTED SOLUTION

Casper6060
Mega Sage

At first i thought this was a bug that was now fixed since when playing around with things in Xanadu, everything was working correctly.

However after setting up another button on a customers instance running Vancouver where i initially had the issue.

I found out the actual issue was the source of learning i was using.

I was using this youtube video https://www.youtube.com/watch?v=E9FhNpk0Mwk as a step by step guide.

The issue in the video, is at 6:40 where he edits the existing / system created UX App Route configuration.

 

Changing this is actually what causes the UI Builder page to dissapear.

 

If you leave it and instead create a brand new one, both functionalities will work just fine.

View solution in original post

In this video I show you how you can configure a button in a Configurable Workspace to open a modal with a Next Experience component or page which you've designed in UI Builder. #servicenow #uibuilder Blog post: https://jessems.com/opening-modal-from-a-record-in-configurable-workspaces Preceding ...
2 REPLIES 2

Casper6060
Mega Sage

At first i thought this was a bug that was now fixed since when playing around with things in Xanadu, everything was working correctly.

However after setting up another button on a customers instance running Vancouver where i initially had the issue.

I found out the actual issue was the source of learning i was using.

I was using this youtube video https://www.youtube.com/watch?v=E9FhNpk0Mwk as a step by step guide.

The issue in the video, is at 6:40 where he edits the existing / system created UX App Route configuration.

 

Changing this is actually what causes the UI Builder page to dissapear.

 

If you leave it and instead create a brand new one, both functionalities will work just fine.

In this video I show you how you can configure a button in a Configurable Workspace to open a modal with a Next Experience component or page which you've designed in UI Builder. #servicenow #uibuilder Blog post: https://jessems.com/opening-modal-from-a-record-in-configurable-workspaces Preceding ...

I tried this and it didnt quite work for me. I was also previously removing and adding modalContainerViewport every time i wanted to edit the uibuilder page and testing the modal. What does work is this:

Create two ux app routes that are the exact same except for one has Parent Macroponent Composition Element ID = modalContainerViewport and one does not have it set.

This way you are mapping both the modal and the ui builder page at the same time.