|
NOTE: Before you compile a process, you should carry out a validity check of the process and process steps. |
To check a process
The result of the check is shown in the view Validity Check and is retained until the next validity check.
Icon | Meaning |
---|---|
No error found. | |
Error | |
Warning, information. |
|
TIP: If you double-click on an error message in the Validity check view, you jump to the corresponding entry in the process document which you can then edit. |
|
TIP: Process or process step elements are highlighted in yellow to indicate a warning or information. If a error occurs, the elements are highlighted in red. |
Error Category | Possible Cause |
---|---|
Error |
The process does not have a name. No base object given. The given generating condition does not correspond to required notation (value =). |
Warning |
The process does not have a base process step. The process has no event. |
Information | The option Do not generate is set. |
Error Category | Possible Cause |
---|---|
Error |
The process step does not have a name. No process task assigned. The given generating condition does not correspond to required notation (value =). No execution server specified (server selection script or server mask). Process step name not unique. Process step has no parameters. The given parameter value does not correspond to required notation (value =). |
Warning | Process step not linked into the process. |
Once you have created, imported or made changes to a process, you need to compile it. The process cannot be generated until it has been compiled.
|
NOTE: Before you compile a process, you should carry out a validity check of the process and process steps. |
Compiling takes place for each base object, that means that all processes that belong to a base object are translated. The assemblies are created and placed on the workstation where generating will take place. During translation, the source is checked for errors. This process may required some time.
There are two methods for compiling a process in the Process Editor:
Use this method to compile a process for testing.
To compile a process for testing
If the process has been test compiled, use this method to add assemblies that are generated into the main database after compiling the process. Once the changes have be integrated the altered processes are immediately available in the system.
To compile a process and save the assemblies to the main database
Select Process | Compile and save to database from the menu.
Error messages during compiling are displayed in the "Compiler errors" view. The source code is displayed if errors occur during compilation. This view is only for displaying the source code.It cannot be edited here.
|
NOTE: If several users edit processes of the same base object, any error messages are also sent to other users. However, these cannot be changed by the current user. A double-click on the error message in the "Compiler error" view takes you straight to the corresponding line in the process. Here, you can edit it. When you double-click on a message in the "Compiler errors" view, it jumps to the corresponding row in the source code view. |
Set up process plans to execute cyclical processes to put into effect, for example, regular synchronization with a target system environment. Process plans are connected to schedules and can therefore be executed at regular intervals.
The following steps are necessary to execute processes automatically:
A process plan contains the basic configuration for automatically running a process.
A schedule include the configuration of execution times for executing processes regularly.
A separate editor is used for creating process tasks. The editor is started from the program "Designer" and opens in the document view. Only additional Process Editor functions are described in the following.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy