Skip to main content
sanjuktab2257
July 21, 2025
Question

Insights on scimPatchGroup() appian function

  • July 21, 2025
  • 2 replies
  • 0 views
Hi everyone,

We're working with the scimPatchGroup() function from Appian's SCIM User Management application and would appreciate some clarification on the expected inputs for each parameter based on our current configuration.

Here’s what we have so far:

  • scimGroupType: We're passing 1, which corresponds to the Group Type ID for our SCIM-managed groups (1 - SCIM). This is the group type under which the group (from which users are being removed) is defined.

  • jsonBody: We're using the following format:

    {
      "schemas": "urn:SCHEMA",
      "Operations": [
        {
          "op": "remove",
          "path": "members",
          "value": [
            {
              "value": "abc@gmail.com"
            }
          ]
        }
      ]
    }
    
  • attributeMappings: We're using the default mappings from the SCIM application:
  • [
      {
        "appianAttribute": "ExternalId",
        "scimAttribute": "externalId",
        "jsonPath": "$.externalId"
      },
      {
        "appianAttribute": "GroupName",
        "scimAttribute": "displayName",
        "jsonPath": "$.displayName"
      },
      {
        "appianAttribute": "Members",
        "scimAttribute": "members",
        "jsonPath": "$.members"
      }
    ]
    
  • On passing these parameters, we are getting Error 500: 

  • Can anyone please help what we are missing?

    Thanks in advance for your help!

2 replies

harshas2775
July 22, 2025

A SCIM API returning a 500 Internal Server Error indicates a problem on the server-side, preventing the request from being fulfilled. And your request looks alright as long as you are providing appropriate user id corresponding to the value. So I suggest to check on the server end whether its up and running as expected first. 

sanjuktab2257
July 22, 2025

Thank you, Harsha!