Troubleshooting errors in the IT Shop
Timeout on saving requests
If new requests are saved in bulk in the database a timeout may occur, after importing data, for example.
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.
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.
Bulk delegation errors
You have the option to delegate all your responsibilities to one person in the Web Portal. If you have a lot of responsibilities, it is possible that not all the delegations are carried out. A delegator can send a notification to themselves if an error occurs.
An error occurred processing delegations. VI_ITShop_Person Mass Delegate was stopped, although only a fraction of the delegations has been applied.
Configure the notification procedure.
Run all remaining delegations again in the Web Portal.
Process monitoring for requests
For more information about process monitoring in One Identity Manager, see the One Identity Manager Configuration Guide.
To configure process monitoring for requests
In the Designer, check whether the Common | ProcessState configuration parameter is set. If not, set the configuration parameter.
If this configuration parameter is set, a process monitoring entry (DialogProcess table) is created when the request is created.
In the Designer, check the Common | ProcessState | UseGenProcIDFromPWO configuration parameter.
If this configuration parameter is set, the GenProcID of an IT Shop request is retained for the entirety of the approval process.
If the configuration parameter is not set, a new GenProcID is used for each approval decision.
In the Designer, check the QER | ITShop | GenProcIDBehavior configuration parameter
Set the configuration parameter and use the value to specify how many GenProcIDs should be generated for a shopping cart's requests.
- MultiID: Generates a new GenProcID for each shopping cart request.
- SingleID: Generates one GenProcID for the entire shopping cart. All requests created through the shopping cart are given the same GenProcID.
If the configuration parameter is not set, a separate GenProcID is generated for each shopping cart request.