NERM workflow expiration time period

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

In the NERM is there any default workflow expiration time period that if any request is pending in the approver list then workflow will expire after a certain time period if approver does not take any action and can we modify that workflow expiration time period also?

2

In NERM system, workflows are designed to manage various processes, including approvals. By default, there isn’t a predefined expiration time for pending approval requests within these workflows. However, administrators can configure timeout settings and customize workflows to handle scenarios where approvers do not take action within a desired timeframe. Administrators can set session timeout durations to ensure that users are logged out after a period of inactivity. This setting helps in maintaining security but does not directly impact workflow approval timeouts.

3

I don’t believe there is a built-in option within the workflow to automatically handle expiration. However, you could consider creating an automated workflow that calls the api/workflow_sessions endpoint to identify open workflows and close them if necessary.

4

Consider moving this thread to the ISC Discussions & Questions sub-category.

5

Hi Sunny,

Please suggest, how we can close the workflow through the Rest API.

Regards,
Vikas

6

You can try the following approach:

  1. Retrieve sessions
    Send a GET /workflow_sessions request to fetch all workflow sessions.
  2. Filter sessions
    From the response, select only those sessions that were created in the last 30 days (or otherwise meet your expiration criteria).
  3. Terminate or close
    For each of the filtered session IDs, call PATCH /workflow_sessions and update the session’s status to either Terminate or Closed.
7

Hi Sunny,

Thank you for your response.

When we change the status of a workflow session through the REST API, it only updates the status but does not actually terminate or close the session. This means the session can still be revived by setting its status back to “Pending Fulfillment” through the API.

Please let me know if there’s an alternative approach or is there a way to programmatically invoke the workflow session and terminate it using the “Close Session” action.

Looking forward to your insights.

Best regards,
Vikas

8

I will check, what status have you tried setting for the workflow session?