If new requests are saved in bulk in the database a timeout may occur, after importing data, for example.
Probable reason
By default, the approvers responsible are determined during saving. This delays the saving process. No more actions can take place in One Identity Manager until all requests are saved and, therefore, all approvers have been found. Depending on the system configuration, this may cause a timeout to occur when large amounts of data are being processed.
Solution
-
In the Designer, disable the QER | ITShop | DecisionOnInsert configuration parameter.
Effect
-
The requests are saved and a calculation task for determining approvers is queued in the DBQueue. Approvers responsible are determined outside the save process.
-
If the requester is also the approver, the approval step is not automatically granted approval. Approvers must explicitly approve their own requests. For more information, see Automatically approving requests.
-
Automatic approval decisions are also met if necessary, but are delayed. This affects requests with self-service, for example.