- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-29-2024 09:13 AM
I'm trying to set up a new Page Collection (UX Extension Point) within my UIB Workspace with multiple controllers. I would like to include both the Form and List Controller. The UX Extension Point form consists of the ability to do this but I'm not following how to. There is a field for the Controller and one for Controller Dependencies with the following message:
"If page collections require data from multiple controllers, all controllers must be defined as a dependency map using JSON. Each dependent controller requires an 'id,' 'name,' and 'depKey.' If you add a controller that depends on another controller, include both in the JSON. Data can be bound to preset-enabled components from defined controllers using the unique depKey for a specific controller."
From this, I believe the format to include the List Controller would be this:
[
{
"id": "list_controller",
"name": "List Controller",
"depKey": "5865e308432021105571609dc7b8f23b" // The sys_id of the List Controller sys_ux_controller record
}
]
However, this doesn't expose the Controller within the Data Brokers sections. Does anyone know the proper way to use this field?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2024 08:16 AM
Hi @DJ Wolfson,
I think you are on the right way. However, the JSON needs to look a little different. If you check the extension points that have two controllers defined, for example, SOW - Record tabs left, you see how it should look like:
[
{
"definition": {
"id": "5c4bbb0f43687110cc25ff53e9b8f24e",
"name": "SOW Record Ctrl"
},
"depKey": "sowrecordctrl"
},
{
"definition": {
"id": "029f04e053610110ac9bddeeff7b1294",
"name": "Form Controller"
},
"depKey": "record"
}
]
The id and name need to go to an object with "definition" as the key. The id is the sys_id of the controller. The name is displayed in the Data Resources section.
I'm not sure what the depKey is but it looks like an arbitrary value. Probably everything will work as long as you do not use the same key for a second controller. The sys_id might work.
Hendrik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2024 08:16 AM
Hi @DJ Wolfson,
I think you are on the right way. However, the JSON needs to look a little different. If you check the extension points that have two controllers defined, for example, SOW - Record tabs left, you see how it should look like:
[
{
"definition": {
"id": "5c4bbb0f43687110cc25ff53e9b8f24e",
"name": "SOW Record Ctrl"
},
"depKey": "sowrecordctrl"
},
{
"definition": {
"id": "029f04e053610110ac9bddeeff7b1294",
"name": "Form Controller"
},
"depKey": "record"
}
]
The id and name need to go to an object with "definition" as the key. The id is the sys_id of the controller. The name is displayed in the Data Resources section.
I'm not sure what the depKey is but it looks like an arbitrary value. Probably everything will work as long as you do not use the same key for a second controller. The sys_id might work.
Hendrik