Shikha

Context Service

Contextual, scalable, and effortless
data abstraction

Enable extensible yet performant capabilities to source & serve business data in any digital process for any industry.

Context Service admin UI mapping business data, shown on an illustrated hillside with team avatars

The 1-2-3 of using
Context Service

A flexible data abstraction service to source & serve business data in digital processes at scale, that is super easy to embed in any CRM application and extensible by customers and partners.

Jobs To Be Done (JTBD)

I want to streamline the sharing and consumption of business application data so that the system can seamlessly supply data needed by the procedure at both design and runtime.

Step 1 (Flow) Step 2 (BRE) Step 3 (Flow) Step 4 (Apex) Context Service
  1. 1

  2. 2

  3. 3

Key Capabilities

Create Structure screen: visual hierarchy of nodes and attributes

Create Structure

Utilising a visual hierarchical structure for clarity that enhances the understanding of node and attribute relationships.

Add Attributes screen: fields with relevant data types

Add Attributes

Click and create attributes, and relevant data types, to ensure each one carries the necessary data.

Add Tags screen: context tags on nodes and attributes

Add Tags

Allowing users to create context tags, ensuring that each node and attribute gets what it needs.

Information Architecture

Everything an admin needs sits under a single Setup entry point. From there the app splits into context definitions, types, and templates, and the definition itself is built in four steps before it opens into a detail view where structure, data, and mappings live side by side.

Setup Context Setting
  • Context Definition
  • Context Types
  • Context Templates
  1. Definition List View
    • Name
    • Description
    • Status
    • Created By
  1. New Definition
  2. Step 1 (Definition Details)
    • Name
    • Description
    • Effective from (Date & Time)
    • Effective to (Date & Time)
  3. Step 2 (Create Structure) Add Node
    • Add Child Node
    • Add a Sibling
    • Delete
    • Mark As Transposable
  4. Step 3.1 (Add Attributes for standard node)
    • Add new
    • Search
    • Bulk delete
    Step 3.2 (Add Attributes for disposable node)
    • Attribute Name
    • Attribute Type
    • Attribute Data Type
    • Key/Value
  5. Step 4 (Add Tags – Multiple nodes)
    • Add tags for node
    • Add tags for attributes
  1. Context Detail
  2. Details Tab (Default open)
    • Name
    • Status
    • Effective From
    • Effective To
    • Created By
    • Last Modified By
    • Description
  3. Structure along with attributes
    • Parent Node
    • Child Node
    • Sibling Node
    • Transposable Node
  4. Map Data
    • Mapping Name
    • Description
    • Mapped Attributes
    • Unmapped Attributes
    • Status
    • Action – Delete, Edit, Activate
  5. New Mapping (Action)
    • Name
    • Description
  6. Mapping Builder Toolbar Actions
    • Undo
    • Redo
    • Collapse all (toggle)
    • Activate
    • Save
    Panels
    • Left side panel (Fixed structure, created by user)
    • Right side – Add SF objects for mapping along with attributes
    • API

How It Works?

The service sits between the data and the processes that need it. An admin describes the shape of the business data once, points each field at wherever it already lives, and every downstream process binds to that same definition instead of to the source.

Outcome

Context Service