Identity Lifecycle State Changed trigger not firing when updated via aggregation

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

HR data was updated, and the change was reflected on the identity through account aggregation.

In the workflow:

  • Identity Attributes Changed trigger fires correctly.

  • Identity Lifecycle State Changed trigger does not fire.

Both workflows are enabled.

The lifecycle state (cloudLifecycleState) was changed automatically from inactive to active via aggregation.
However, the Identity Lifecycle State Changed trigger only fires when I manually update the lifecycle state in the UI.

Below is the event payload captured from the workflow execution:

{
  "type": "WorkflowExecutionStarted",
  "timestamp": "example",
  "attributes": {
    "input": {
      "_meta": {
        "invocationId": "example",
        "subscriptionId": "example",
        "triggerType": "FIRE_AND_FORGET"
      },
      "changes": [
        {
          "attribute": "cloudLifecycleState",
          "newValue": "active",
          "oldValue": "inactive"
        }
      ],
      "identity": {
        "id": "example",
        "name": "example",
        "type": "IDENTITY"
      }
    }
  }
}

My understanding is that the lifecycle state change is correctly reflected on the identity, but the trigger is not firing when the change comes from aggregation.

Does this mean that lifecycle state changes coming from aggregation / correlation cannot be used with the Identity Lifecycle State Changed trigger?
Or is there any additional configuration required to make this trigger fire for automatic updates as well?

Thanks.

2

Hello @sxxnex , do you have any filter being applied for ā€œIdentity Lifecycle State Changedā€œ trigger?

3

hello @JackSparrow , No, thereā€™s no filter applied to Identity Lifecycle State Changed trigger.

4

I tried this in my env and strangely Identity Lifecycle State Changed trigger is not working for both manual change in UI and change via aggregation. I think this trigger is not able to capture LCS change events. Moreover, it looks like a bug to me.

5

@sxxnex better use attribute change trigger and filter the LCS.Also you can raise a support ticket for the same as it should trigger as it was created only for such use cases

6

can you make sure case is matching. maybe your old state is ā€œinActiveā€ not ā€œinactiveā€ and same with new value.

after the change in in LCS in UI, find that event in users ā€œeventsā€œ and see what exactly the new and old values are.

7

@sxxnex Can you update LifecyleState as ā€˜Inactiveā€™ from ā€˜Activeā€™ ? (case sensitive) try hope this can trigger.