What are the UI Builder tables?

gjz
Mega Sage

I'm new to UI Builder and I'm learning it by copying an Experience from my personal developer instance in my company's dev instance.  However, I've run into some road blocks and need some help.  I tried finding the UI Builder tables to look for myself, but I can't find the tables.  Does anyone know what they are?

Here is why I was looking for the table - and are short-comings IMHO.

1. For read-only experiences or elements within the experience, there isn't anything that lets you know what scope it was built in - which means I'm unable to trace certain elements.

2. There isn't a field or property in UI Builder that tells you what component was used.  For example, the experience I'm copying has a component that is read only called "default-slot", but because it's read only I can't see the configuration nor do I know what type of component it is.

3. I can't figure out how to get components arranged horizontally.  I can add components vertically, but not horizontally.  I haven't seen how to do that anywhere: video, documentation, community, no where have I found that answer!

4. The documentation doesn't have any information on sub-pages and how to hook them up.

Any help is appreciated!

 

1 REPLY 1

Travis Woods
Tera Expert

You can see a majority of the tables under the Now Experience Framework module. However, this does not contain the tables that contain scripts or the script includes. Those are in sys_ux_client_script and sys_ux_client_script_include tables respectively. In Rome, the inline scripts you set for properties or for events were stored inside the macroponent JSON but as of San Diego, they are all now stored in sys_ux_client_script as <component name>_<property name>. There is also a sys_id that the macroponent JSON references from that table.

For the layout, you can use a container and configure it's layout on the right side under the "Styles" tab. You can specify rows, columns and many other ways to organize everything and it has some helpful information next to each element.

For anyone's future reference, you can always create an Experience in a scoped app and then look at the sys_update_xml table to see what records were created for it.