Monitor security request execution

Some security requests are processed by batch jobs, for example when the request has a defined From date or To date.

The Security request execution log shows the execution status of these batch jobs. Use the log to:

• Monitor the progress of security requests that Security and Compliance Studio processes asynchronously.

• Confirm whether scheduled or delayed security actions completed successfully.

Steps

1. Click Security management.

2. On the Requests tab, in the list, click the link of the desired security request.

3. Click Security request execution log.

   The Security request execution log page opens. The page shows the batch jobs that process the security request, organized into these sections:

   • General: The request ID, name, and type.

   • Started: The batch jobs that made requested security change effective based on the From date. For example, a job that enabled a user's access on the From date.

   • Ended: The batch jobs that made the security change ineffective based on the To date. For example, a job that disables a user's access on the To date.

4. Sub-task: Clean up the security request execution log.
   You can clean up the security request execution log manually or in a recurring mode.

   1. Click Clean-up security request execution log.

   2. In the History log retention (Days) field, type the number of days to keep execution log entries.

   3. Click OK.

   4. Sub-task: Set up batch processing.

      Usually, you clean up the security request execution log in batch in recurring mode.

      1. Expand the Run in the background section.

      2. Select Yes in the Batch processing field, and fill in the fields as desired.

      3. Click Recurrence, and fill in the fields as desired.

      4. Click OK.

      5. Click OK.

Note

• The cleanup permanently removes execution log entries older than the specified retention period.

• Set up batch processing only if you want the cleanup to run automatically and repeatedly.