Details of a process step's parameters
After selecting a process step, the passing parameters of the process step are displayed with their names and their values. If the selected node does not represent a process step, the parameter view is cleared.
To display process step parameters
-
In the Job Queue Info, select a process step and select the View > Parameter menu.
This shows all the parameters of the selected process step.
TIP: In the parameter view, you can copy the data selected parameter and its value into the clipboard using Ctrl + C. The data format is column name value.
Parameters that contain an object key are displayed as a link in the parameter view.
-
You can display the objects by clicking on the link or using the Show object properties context menu.
-
Use the Open in Object Browser context menu item to start the Object Browser and display the object.
-
For object keys that refer to a synchronization project, use the Open in Synchronization Editor context menu item to start the Synchronization Editor and load the synchronization project.
To support provisioning analysis, the CausingEntityPatch parameter is shown as a link. This parameter contains the patch that contains the changes to be provisioned.
-
Double-click on the link to open a separate dialog with the change information. You can also reach the dialog over the Show patch item of the parameter's context menu.
The change information lists the properties of the object before the change (old value) and after the change (new value). Changed properties are highlighted in color.
OUT parameters
Parameters of the OUT or INOUT type are parameters that a process component can use to output a value. This value is then available in all subsequent process steps in the process and can be used as a value for parameters of the IN type.
The Job Queue Info program is not technically capable of determining the point at which or for which process step these parameters are valid. For this reason, OUT parameters are added to the list of parameters of a process step and are highlighted in blue.
They cannot be seen in the view of the process step under <ParamIN> of a process step because this view presents the data structure of every process step at compilation time. However, the OUT parameters are created in the context of the process.
The time at which the process is loaded into the Job Queue Info is important. If a parameter is overwritten several times, only the state at the time of data query is displayed.
Example:
|
Step 1 |
OUT parameter: X=1 |
|
Step 2 |
IN parameter: X=1 |
|
Value changes: X=2 |
|
OUT parameter: X=2 |
|
Step 3 |
IN parameter: X=2 |
If the process is loaded into the Job Queue Info before step 2 is processed, the Job Queue Info displays the X=1 value for the OUT parameter. If the process is loaded after step 2 is processed, the X=2 value is displayed for the OUT parameter.
For more information about each process step and how the parameters are filled, see the One Identity Manager Service log file.
Related topics
Show hidden parameters
Parameters in the One Identity Manager Service log file and in the Job Queue Info program that are not to be displayed are labeled with the Hidden option. Values for hidden parameters are shown as <HIDDEN>.
The following users can view hidden parameters in Job Queue Info.
Related topics
Re-enabling process steps and processes
The maximum number of times a process can appear in the Job queue can be limited in order to prevent mass modifications.
If the limit is exceeded, the process steps are set to Overlimit status and are therefore no longer collected for processing. You can enable these process steps be run again.
Critical process steps that have failed to be processed are given Frozen status. You can also re-enable these processes after correcting the error.
To re-enable process steps
To re-enable a process step
Sometimes a rerun of the failed process step is not desired. This might occur when the action to be carried out by the process has been carried out manually, for example, an expected directory has been manually added in the meantime. Even so, it may just happen that the process should be rerun even though the error has not been fixed, for example, for a rollback of already processed steps. In this case, to continue with the process, the next process step in the success or failure branch can be handled.
To run the subsequent process step
