In ISC, "Next Processing Date" identity Attribute is not working as expected

Identity Security Cloud (ISC) ISC Discussion and Questions
1

We are trying the “Next Processing Date” identity Attribute for the first time, but Identity is not getting refreshed as per the time assigned to the “Next Processing Date”. We are trying to use “Next processing Date” to trigger the LCS change (Prehire to Active & Active to Terminate) as the user’s time Zone

2

Welcome @OviyaLoganathan . Have you made sure that the date is indeed in ISO8601 format as suggested in Processing Identity Data - SailPoint Identity Services ?

3

Yes we used ISO8601 format only. Can you please suggest us with some sample code

4

@OviyaLoganathan Have you tried something like this maybe, or any similar logic for calculating the nextProcessing?

This transform will evaluate the “startDate“ attribute from your HR source, and if it’s greater than the current date (in the future), nextProcessing should be populated with that date.

Replace "inputFormat": "yyyy-MM-dd" in BOTH places with the actual format your source provides.

{
  "type": "static",
  "name": "Next Processing Date Transform",
  "attributes": {
    "isStartDateInFuture": {
      "type": "dateCompare",
      "attributes": {
        "firstDate": {
          "type": "dateFormat",
          "attributes": {
            "input": {
              "type": "accountAttribute",
              "attributes": {
                "sourceName": "HR Source",
                "attributeName": "startDate"
              }
            },
            "inputFormat": "yyyy-MM-dd",
            "outputFormat": "ISO8601"
          }
        },
        "secondDate": "now",
        "operator": "gt",
        "positiveCondition": "true",
        "negativeCondition": "false"
      }
    },
    "formattedStartDate": {
      "type": "dateFormat",
      "attributes": {
        "input": {
          "type": "accountAttribute",
          "attributes": {
            "sourceName": "HR Source",
            "attributeName": "startDate"
          }
        },
        "inputFormat": "yyyy-MM-dd",
        "outputFormat": "ISO8601"
      }
    },
    "value": "#if($isStartDateInFuture == 'true')$formattedStartDate#end"
  }
}

Or do you have a problem with the way your lifecycle state is calculated using the nextProcessing (the transform that calculates the lifecycle state), in case your nextProcessing indeed gets populated correctly?