CX Service: Drag-and-Drop Relation Object Tables for SR Pages

System implementors can now use the cx-svc-custom-relation-objects-list fragment to build and configure UI tables for service request-related objects — including custom and standard objects — directly within the extensibility interface. The fragment supports create, edit, and delete actions out of the box, and reuses the same UI patterns available in the Jumpstart tool, ensuring design consistency for customers that are migrating from Classic UI.

Implementors can drag and drop this fragment onto Service Request Details Page, wire it to the relevant object, and configure table layouts, create forms, and edit forms using Visual Builder Studio — all while maintaining Redwood-aligned drawer and navigation patterns.

Example Use Cases

  • Order tracking on SR pages — Show a related Orders table directly on a Service Request detail page, allowing agents to create, view, and delete linked orders inline.
  • Case-to-contact relationship tables — Display related Contacts on a Case page with drill-down navigation and action menus for quick edits.
  • Custom object extensions — Embed a custom object (e.g., Warranties, Entitlements) as a related table on SR or CustomerWorkOrder pages with full create/edit support.

  • Faster delivery — Reusing pre-built fragments reduces configuration effort and accelerates project timelines.
  • UI consistency — Fragments align with Redwood design standards, reducing fragmentation across implementations.
  • Greater flexibility — Implementors can extend SR pages for custom and standard objects without heavy development work.

Steps to enable and configure

Leverage the Visual Builder Studio to expose your applications. To learn more about extending your application using Visual Builder, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

  • In App Composer, note the object's APIName, Name, SourceId, and RelationFieldAPIName.
  • For custom objects, create a Service Connection in Visual Builder (name it cx-service-custom to use defaults).
  • Create three layouts: tableLayout, createLayout, and detailLayout for the object.
  • Add the two required templates ( recordDrillDownLinkTemplate, actionTemplate ) to enable edit and delete row actions.
  • Optionally, create a custom App UI (cx-service-custom) with create/edit/list pages for the object.
  • Drag and drop the cx-svc-custom-relation-objects-list fragment onto the target page and configure its parameters.

Tips and considerations

  • Name your layouts using the default IDs (tableLayout, createLayout, detailLayout) to avoid passing them explicitly as fragment parameters — this saves time.
  • For standard objects (ServiceRequest, Case, Contact, etc.), set extensionId to oracle_cx_serviceUI. For custom objects, use your project's own Extension ID from Settings.
  • Enable enableObjectsToOpenInSameTab = true on SR Detail pages to match the expected Redwood navigation pattern.
  • The RecordName field is mandatory in the create layout — missing it will cause errors.
  • When using multiple tables on the same page, assign unique IDs to HTML templates to avoid conflicts.

Key resources

Access requirements