All of the Designer application icons have been given a new look, which is lighter,
more glossy, as well as other cosmetic changes; some were completely changed. The following is a SAMPLE
of some of the changes:
Old | New | Old | New | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() | |
![]() |
![]() |
![]() |
![]() |
When you drop an Identity Vault into Designer, it will no longer include all 169 E-mail Notification templates. This will keep your projects much smaller and this will allow saves, version control, copy, etc. to all go faster out of the box. If you need Notification Templates, you can pull them through the "Import Template From File" or the "Update Templates" operations.
The notification templates are heavily used by the User App, so missing templates will be pulled in as you configure the User App.
The "Update Templates" operation will pull in all
templates that are part of the Designer install image and put them in the selected Template
Collection in the project. If you have existing templates, it will give you the option whether
or not you want them overwritten. If you say "Yes", it will bring them all
in and overwrite any existing templates you may already have in the template collection. Otherwise, it will only bring in templates that you don't currently
have in the collection.
You're now able to include servers as you search for objects and properties
across a Designer project.
Designer M2 has a new server mapping dialog that allows users
to copy server-specific information from a server in one Identity Vault to a
server in another Identity Vault. The Map Identity Vault Server dialog launches
during cut, copy, and paste operations, and only for operations that cross Identity
Vault boundaries. Mapping information includes server-specific information,
such as driver Global Configuration Values and driver settings.
This mapping is necessary because servers can only be contained by a single Identity
Vault. During a copy operation, you might want to maintain any server-specific information
and map these values from a server in the source Identity Vault to a server in the destination
Identity Vault.
In the following graphic, a copy and paste action of a driver with server-specific
information from the Outline view launches the Map Identity Vault Servers dialog. The
driver that is copied contains server-specific information for both the stage1 and stage2
servers in the source Identity Vault under the Source Server heading.
The mapping dialog allows you to map the stage1 source server to the prod1
destination server. The Mapping page also allows you to ignore the server-specific
information of the stage2 source server, as shown under the Destination Server
or Mapping Action heading. You can also create a copy of the source server in the
destination Identity Vault.
The OK button of the mapping dialog will be disabled until a mapping action
has been selected for each source server. Once you select a server or action,
click OK to finish the operation.
Designer does a better job of detecting what the driver type is when importing drivers from eDirectory that are set up with Remote Loader. The detection works on the following drivers types (where it wasn't before):
|
![]() |
Key Bug Fixes & Other Enhancements |
|