After deploying a job, Designer issues a command to the eDirectory server
to determine if the job is correctly configured. Results from the command are displayed in
the Deployment Result dialog box. The following image shows an example of an incorrectly configured job.
In this case, the Driver object is disabled.
The job definitions for drivers and driver sets are imported into Designer when you
import from an Identity Manager 3.5 server. These definitions then appear in
the New Job dialog box.
The Import dialog box now has an Import History button, which is to the right of the Browse button.
Selecting this button shows a list of previously imported objects. The list is filtered to show only
objects that can be imported into the current context. For example, policies are displayed if you are
importing drivers into a driver set.
Certain statements or verbs within DirXML Script can contain references to other DirXML Script
or Mapping Table objects. This version of Designer has been improved to handle these references
during an import or deploy operation. For example, the "include" statement causes the rules from
the policy referenced by the name attribute to be included at runtime into the including policy
as if they were part of the including policy at the point of inclusion. The import and deploy code
detects these references and includes the referenced object in the operation.
For example, if policy P1 has an include statement that references policy P2 when P1 is deployed,
P2 is also deployed. Likewise, if P1 is imported into Designer, P2 is imported. References
are also detected for the "token-map" verb, which references a Mapping Table object. Mapping Tables were
introduced in Identity Manager version 3.5.
Previous versions of Designer allowed only a single e-mail template
to be imported at a time. This version of Designer has been improved
to support importing multiple e-mail templates in a single operation.
Other Enhancements and Bug Fixes | |
|