When you change your action or condition, any entries that you may have had previously that can be
carried over will be.
When Policy Builder asks for an input that has a type of numeric, it will now validate that the input actually is either numeric or is an appropriate DirXMLScript variable (like $variable$ or ~gcv~). These numeric types occur in the Condition Editor, and in the following tokens:
|
When Policy Builder asks for an input that has a type of NMTOKEN, it will now validate that the input conforms
to the NMTOKEN standard. This is done in the following places:
|
Everywhere within Designer where you can browse schema, you can now browse the application schema as well as the
eDirectory Schema.
You can now insert tokens as well as append tokens into the list in Argument Builder.
DirXMLScript tracing can now be set on all policies contained in a Subscriber, Publisher, Policy Set, Driver,
Library, Driverset, or Identity Vault. This makes setting up your DirXML Script tracing a whole lot easier.
Tracing is on by default for everything which can create a lot of clutter in the trace logs that has to be
sorted through when you are trying to track down a specific bug. Now, you can set all of the trace to off
and then just turn on the trace for a specific item.
The GCV Browser will now select the GCV that you entered in
the text field when you clicked the browse button.
Error variables that can be set during certain actions are now available in the variable selector.
The GCV Browser now allows you to create GCV's on the Driver or the Driver Set.
The Local Variable Selector dialog will now parse through the policy linkage and containment looking for local
variables that are set with scope=driver. These local variables will then be available in the Driver tab of the
local variable selector.
When turned on in the preferences, the Policy Builder will display the name of the project before the name
of the policy in the title. To access this preference, go to Window -> Preferences -> Designer for IDM -> Policy Builder.
if-then-else actions and do-while's will no longer slow down the performance of Policy Builder.
![]() |
Key Bug Fixes & Other Enhancements |
|