Supported profile tab (perspective) types

Use the class field to define each profile tab. Tabs appear in the order they’re listed in the profile[] array.

Entity-type–specific layouts and logic

Tabs with class = "Profile" support per-entity-type configuration using an entityTypes object. This allows you to define views, layout, authoring steps, and optional side panels.

"entityTypes": {
  "configuration/entityTypes/HCP": {
    "views": [...],
    "layout": [...],
    "sidePanelViews": [...],
    "profileBand": {...},
    "authoring": [...]
  }
}

[{ "id": 
"attrView", "component": "Attributes", ... }]

[{"id":
"attrView","x":0,"y":0,"width":3,"height":1}]

[{"id":"History"},{"id":"Workflow"},{"id":"D&B", views: [<custom view1>, ...]}]

"profileBand": {
  "cloneAction": [
    {
      "entityTypeUris": ["configuration/entityTypes/HCP"],
      "attributeReplacementMapping": {
              "attributes/TextField": "Copy of {value}",
              "attributes/AZCustomerID": null
        },
      "relationshipTypesToCopy": ["configuration/relationTypes/HasAddress"]
    }
  

"frozen": true

workflow :{"assignee":"...","

processTypes":["dataChangeRequestReview"],

"showClosedTasks":false}

Result

The profile screen adapts based on the entity type being viewed.

Validation

Open a profile for each configured entity type and confirm that the correct layout, views, and components appear.

Nested profile tab

Similar to the Profile view, Nested profile tab is a separate tab in the main profile that displays additional views or attribute groups, configured with the same layout options as the main profile. Configure tabs with class = "NestedProfile". Refer to the previous section for more details to configure this tab. Here's a sample screen:

Here's a sample:

 {
            "visible": [
                "configuration/entityTypes/Contact",
                "configuration/entityTypes/PriceSpecification",
                "configuration/entityTypes/Organization",
                "configuration/entityTypes/Individual",
                "configuration/entityTypes/IndividualPerson",
                "configuration/entityTypes/Policy",
                "configuration/entityTypes/Property"
            ],
            "label": "Profile: Other",
            "class": "NestedProfile",
            "entityTypes": {
                "configuration/entityTypes/Contact": {
                    "sidePanelViews": [
                        {
                            "id": "History"
                        },
                        {
                            "id": "Discussion"
                        },
                        {
                            "id": "Workflow"
                        }
                    ],

Profile view tabs

Interactions tab

Tab with class as Sources doesn't support additional parameters beyond the standard configuration fields. Use it to define a list of data sources visible for a specific entity type. Here's a sample:

{
  "class": "Sources",
  "label": "Data Sources",
  "visible": ["configuration/entityTypes/Person"]
}

Relationships tab

Tab with class as Relationship requires the following optional parameters:

{
  "class": "Relationships",
  "label": "Person Relationships",
  "defaultRelationshipType": "configuration/relationTypes/HasAddress",
  "visible": ["configuration/entityTypes/Person"]
}

Graph tab

Tab with class as Graph doesn't require any additional parameters beyond the standard fields. It defines a graph-based view for a specific entity type. Here's a sample:

{
  "class": "Graph",
  "label": "Graph Exploration",
  "visible": ["configuration/entityTypes/Person"]
}

Activity Log tab

Tab with class as Activity requires the following optional parameters:

Tab with class as PotentialMatch requires the following optional parameters:

Each matchActions entry supports:

• createRelation: Defines outgoing (outRelations) and ingoing (inRelations) relationships

• allowMerge: Boolean that enables or disables merge for the match group

Here's a sample:

{
  "class": "PotentialMatches",
  "label": "Potential Matches",
  "visible": ["configuration/entityTypes/HCP"],
  "allowMergeAll": true,
  "matchActions": {
    "*": {
      "allowMerge": false,
      "createRelation": {
        "inRelations": ["configuration/relationTypes/HasSomething"],
        "outRelations": ["configuration/relationTypes/HCPisAffiliatedWithHCO"]
      }
    }
  }
}

Configure profile authoring pages

Authoring allows you to build multi-step profile creation flows. Each authoring step includes a label, an array of views, a layout, and optional canRead.

{
  "label": "Basic Info",
  "canRead": ["ROLE_EDITOR"],
  "views": [
    {
      "id": "main-attr",
      "component": "Attributes",
      "includeUris": [
        "configuration/entityTypes/HCP/attributes/Name",
        "configuration/entityTypes/HCP/attributes/Address"
      ]
    }
  ],
  "layout": [
    { "id": "main-attr", "x": 0, "y": 0, "width": 3, "height": 1 }
  ]
}

"label": "Authoring: Basic Info"

"views": [ { "component": "Attributes", "id": "main-attributes-view", "canRead": ["USER_ROLE"], "includeUris": ["configuration/entityTypes/HCP/attributes/Address"] } ],

[{"id":"main-attributes","x":0,"y":0,"width":3}]

{
      "point": "com.reltio.plugins.ui.view",
      "id": "com.reltio.plugins.entity.org.EmployeesView",
      "class": "com.reltio.plugins.entity.RelationsView",
      "caption": "Employees",
      "content": {
        "inRelations": [
          "configuration/relationTypes/Employees"
        ]
      },
      "canRead": {
       "roles": [
         "ROLE_A360_STEWARD"
       ]
     }
   }

Result

Users can complete the profile creation process in a structured, step-based flow.

Validation

Initiate entity creation and verify each authoring step appears in order with the expected fields.

Enable cloning

Use the profileBand section to configure the Clone button behavior. You can specify which attributes and relationships to copy or exclude.

"profileBand": {
  "cloneAction": [
    {
      "entityTypeUris": ["configuration/entityTypes/HCP"],
      "attributeReplacementMapping": {
        "attributes/Name": "Copy of {value}",
        "attributes/ID": null
      },
      "relationshipTypesToCopy": [
        "configuration/relationTypes/HasAddress"
      ]
    }
  ]
}

For more information about cloning profiles, see topic Configure profile cloning.

Users can clone a profile, with selected values auto-filled or excluded.

Validation

Open an entity of the defined type, click Clone, and verify expected fields and relationships are pre-populated.