Skip to main content

How to Configure the Use Case in UNICONNECT AI

Configuration › CRM › Service Cases

Here is the detailed configuration implemented for the AUS Bank use case. It serves as the technical companion to the CRM Use Case Scenario, translating the business narrative into a working solution.

Creating the Module​

A new internal module named Service Cases was created from Configuration → CRM, carrying the description used throughout the scenario.

  1. Go to Configuration → CRM, and click Create. Opens a blank new module form.
  2. Enter the Module Name and Module Description. Named Service Cases, with a description covering card disputes, fraud alerts, loan servicing, and account access.
  3. Leave Source Type set to Internal, and click Save. Internal is the default; this module's data lives entirely inside Uniconnect, unlike the external connection covered later.

New module form filled in with Module Name Service Cases and a description covering card disputes, fraud alerts, loan servicing, and account access

Module Name and Module Description filled in, Source Type left at Internal.

CRM Modules list filtered to Service Cases, showing the newly created module card with its description and an active status indicator

Service Cases appears in the CRM Modules list immediately after saving.

Adding the Fields​

Three fields were added on the module's Fields tab, matching the scenario exactly:

FieldTypeConfiguration
Case TypeEnumerationCard Dispute, Fraud Alert, Loan Servicing, Account Access
Case ReasonEnumerationUnauthorized Transaction, Billing Error, Suspected Identity Theft, Suspicious Login
Assigned AgentRelationshipRelated Module: Contacts; Relationship Type: Many to One

Case Type​

  1. Open the Fields tab, and click New Field. Opens the field type picker, listing every available field type as its own tile.
  2. Pick Enumeration from the field type picker.
  3. Name it Case Type, and add the four values. Card Dispute, Fraud Alert, Loan Servicing, Account Access, each added with its own Add Enumeration Value click.
  4. Click Save.

Field type picker open, showing tiles for Text, Boolean, RichText, Json, Number, Email, Date, Enumeration, Relationship, PhoneNumber, Media, and more

The field type picker, opened from New Field; Enumeration is one tile among many.

Case Type enumeration field being created with four values: Card Dispute, Fraud Alert, Loan Servicing, Account Access

Case Type, with all four values entered before saving.

Case Reason​

  1. Click New Field again, and pick Enumeration.
  2. Name it Case Reason, and add its four values. Unauthorized Transaction, Billing Error, Suspected Identity Theft, Suspicious Login.
  3. Click Save.

Case Reason field reopened for editing, showing its four saved values: Unauthorized Transaction, Billing Error, Suspected Identity Theft, Suspicious Login

Case Reason, reopened after saving to confirm all four values.

Assigned Agent​

  1. Click New Field, and pick Relationship.
  2. Name it Assigned Agent, and set Related Module to Contacts.
  3. Set Relationship Type to Many to One, and click Save. A small diagram confirms the direction: one Contact can be linked to multiple Service Cases, but each Service Case has a single Assigned Agent.

Assigned Agent relationship field with Related Module set to Contacts and Relationship Type set to Many to One, showing a diagram of one Contact linking to multiple Service Cases

Related Module and Relationship Type both set, with the relationship direction shown beneath them.

Fields tab showing all three custom fields saved: Case Type, Case Reason, and Assigned Agent, alongside the module's system fields

All three fields, saved and listed alongside the module's system fields.

Linking Case Type to Case Reason​

A Dropdown Dependency was configured on the module's Dependencies tab so that Case Type narrows Case Reason, with all four pairings from the scenario added to the schema.

  1. Open the Dependencies tab, staying on the Dropdown sub-tab.
  2. Pick Case Type then Case Reason from the Fields selector, and click Add Fields to Order. Locks in the chain direction: Case Type controls Case Reason.
  3. Map each Case Type value to its Case Reason values, one pairing at a time. Card Dispute paired with Unauthorized Transaction, then again with Billing Error; Fraud Alert paired with Suspected Identity Theft, then again with Suspicious Login. Each pairing is added with its own Add to Schema click.
  4. Click Save.

Value Selection panel with Case Type set to Card Dispute and Case Reason set to Unauthorized Transaction, before adding to schema

The first pairing, Card Dispute to Unauthorized Transaction, before being added to the schema.

Selected Order tree showing Card Dispute expanded into Unauthorized Transaction and Billing Error, with a Fraud Alert branch below it

All four pairings built up in the tree: Card Dispute → Unauthorized Transaction, Billing Error; Fraud Alert → Suspected Identity Theft, Suspicious Login.

Dropdown Dependencies panel showing a single collapsed Case Type entry after saving

Once saved, the whole chain collapses into a single Case Type entry.

Reopening that entry with its edit icon brings back the full tree, with a per-node delete icon on every branch, for correcting a single pairing without rebuilding the whole chain.

Dropdown dependency reopened for editing, showing the full tree expanded with Card Dispute and Fraud Alert branches, each value carrying its own delete icon

Edit mode: the complete tree, every node with its own delete icon.

For the full walkthrough of this feature, see Configuring CRM Dependencies.

Designing the Case Detail Screen​

A Detail Page Layout named Case Detail was built with two sections: Case Type and Case Reason grouped together, and Assigned Agent in its own section below, exactly as described in the scenario.

  1. Open the Layout Builder tab, and click New Layout. Offers a choice of four layout types.
  2. Pick Detail Page Layout.
  3. Name it Case Detail.
  4. Click Section, then + Fields, and add Case Type and Case Reason. Both fields land in the same first section.
  5. Click Section again, then + Fields, and add Assigned Agent. Kept in its own, second section, separate from Case Type and Case Reason.
  6. Click Save Layout.

New Layout menu open showing Detail Page Layout, Index Page Layout, Form Layout, and Summary Layout

New Layout offers four types; Detail Page Layout is the one used here.

Empty Detail Page Layout builder with the Layout Name field, Side-by-Side toggle, and a row of block buttons, before any block is added

The builder starts completely empty: a name field and a row of block buttons.

A new empty Section block added to the layout, with a delete icon and a plus Fields link, before any field has been added

An empty Section block, immediately after clicking Section and before adding any fields.

Case Detail layout with a first section containing Case Type and Case Reason fields, and a second section containing Assigned Agent

Two sections: Case Type and Case Reason together, Assigned Agent on its own.

Layout Builder tab showing the saved Case Detail layout card, tagged Detail and Default

Case Detail, saved and listed on the Layout Builder tab.

For every layout type and block in detail, see Configuring CRM Layouts.

Connecting an Outside System​

The Core Banking Platform connection described in the scenario was built as a real External source type module, pointed at the bank's account API.

Setting up the API connection​

  1. Go to Configuration → Integrations → API Integrations, and click Create. Opens a new, empty API collection.
  2. Name the collection, and set its Base URL. Named Core Banking API, pointed at the bank's account endpoint.
  3. Open the collection, click Create, and point the new GET request at an endpoint. Named Get Account Records, a GET request returns the account list.
  4. Send the request, and check the response shape. The response included a data array, but used a plain total field instead of the pagination.totalRecords shape Uniconnect requires.
  5. Add a Post Script reshaping the response, then edit the Res Schema to match. The script sets response.pagination = { totalRecords: response.total }; the Res Schema was then set to detect data (array) and pagination.totalRecords (number).
  6. Save the request.

GET request returning a 200 response with page, per_page, total, total_pages, and a data array

The account API's response: a data array already present, but total instead of pagination.totalRecords.

Post Script editor containing a script that sets response.pagination to an object with totalRecords from response.total, then returns the response

The Post Script reshaping the response.

Res Schema tab showing 2 fields detected: data as an array, and pagination.totalRecords as a number

The Res Schema, matching exactly what the External Module configuration requires.

Building the External Module​

  1. Go to Configuration → CRM, click Create, and set Source Type to External. Named Core Banking Platform, with the same description used throughout the scenario.
  2. Set Select Collection to the Core Banking API, and Get All API to the saved request.
  3. Click Save.
  4. Open the Fields tab, and click Fetch Schema Response. Automatically created five fields from the connection's response: id, email, firstName, lastName, avatar.
  5. Mark id as the primary field. A confirmation prompt appears first, since changing the primary field can affect existing records; this module had none yet.

New module form with Source Type External, Select Collection set to the Core Banking API, and Get All API set to Get Account Records

Source Type, Select Collection, and Get All API all configured.

Fields tab showing five fields automatically created from the API response: id, email, firstName, lastName, avatar

Fetch Schema Response created all five fields in one click.

Confirmation prompt asking to change the primary field to id, warning that this affects existing CRM records

Marking id as primary; confirmed since no records existed yet on this new module.

Core Banking Platform module page with no warnings, Source Type set to External, and every required field configured

The completed module: no Primary Key warning, fully usable.

Setting Up the Two Roles​

Two roles were created under Configuration → User Management → Roles, with CRM Module permissions set on Service Cases to match the scenario.

RoleCreateUpdateViewDelete
Contact Center SupervisorYesAllAllAll
Service AgentNoOwnAllNo access
  1. Go to Configuration → User Management → Roles, and click Create. Opens a blank Create Role panel: Role Name is required, and every permission category starts at 0 permissions set.
  2. Name the Role, and expand CRM Modules under Permissions.
  3. Find the Service Cases row, and set Create, Update, View, and Delete. Create is a plain Yes/No switch; Update, View, and Delete are each their own dropdown offering Own, Group, or All.
  4. Click Save. Repeated once for each role: Contact Center Supervisor got Create switched on and every dropdown set to All; Service Agent kept Create off, Update set to Own, View set to All, and Delete left at No access.

Blank Create Role panel with an empty Role Name field and a Permissions list showing 0 permissions set for every category

A brand new Role: nothing is granted until Permissions are explicitly set.

Update access dropdown open on the Service Cases row, showing three options: Own, Group, and All

The Update dropdown on Service Cases, open to show Own, Group, and All.

Contact Center Supervisor role with Service Cases Create, Update, View, and Delete all set to Yes or All

Contact Center Supervisor: full access.

Service Agent role with Service Cases Create set to No, Update set to Own, View set to All, Delete left at No access

Service Agent: scoped to records assigned to them.

For every permission category and field-level options, see Configuring CRM Permissions.

Creating and Viewing Records​

With the module, fields, dependency, screen, and roles all in place, logging a case works the same way as any other CRM module, from an empty list through to a saved record.

  1. Open Service Cases from the CRM menu. Starts empty, with no records yet.
  2. Click New Service Cases. Opens a blank intake panel with all three fields.
  3. Select a Case Type. Card Dispute, in this example.
  4. Open Case Reason. Already narrowed to only the two values that belong under Card Dispute, Unauthorized Transaction and Billing Error.
  5. Select a Case Reason, then search and select an Assigned Agent.
  6. Click Save.

Service Cases list view with no records yet, showing New Service Cases, Import, and Export buttons above an empty table

Service Cases before any record has been logged.

New Service Cases panel with empty Case Type, Case Reason, and Assigned Agent fields

The intake panel opened by New Service Cases.

New Service Cases panel with Case Type set to Card Dispute and the Case Reason dropdown open showing only Unauthorized Transaction and Billing Error

Case Reason narrowed to the two values that belong under Card Dispute.

New Service Cases panel fully filled in: Case Type Card Dispute, Case Reason Unauthorized Transaction, Assigned Agent Liam O'Connor

The completed intake panel, ready to save.

Service Cases list view showing one saved record with Case Type Card Dispute and Case Reason Unauthorized Transaction

The list view immediately after saving, with the new case now appearing as a row.

Service Case detail view showing Case Type and Case Reason in the first section, and Assigned Agent Liam O'Connor in a second section

Opening the record shows the Case Detail screen built earlier: Case Type and Case Reason together, Assigned Agent in its own section.

Viewing data from the external connection​

The Core Banking Platform module, built earlier in this same way, works the same way too: opening it from the CRM menu pulls the account records directly from the connection, no different from any other CRM module's list view.

Core Banking Platform list view showing twelve fetched account records with id, email, firstName, lastName, and avatar columns, paginated across two pages

Account records fetched directly from the connection, displayed in the module's own list view.