Operations that could cause harm should have a confirmation prompt, much like EB did.

For example:

• Clear connector.
• Delete anything.

Scrolling to the right will rubber-band back to the left for the CSV file path.

Confirm that the ChangesAvailable interface performs as expected and will work correctly with the current version of Event Broker 3.

Currently the scheduler that is used for most operations is not the one that is controlled by the user. This needs to be corrected so that the scheduler is of any use.

Also, please check how Event Broker notified the user that the scheduler is disabled, if at all. I imagine we didn't allow things to be triggered if the scheduler was stopped.

See the attached screenshot for an error currently occurring when attempting to install the service with the new database option selected.

Can Unify Management Studio show versions of installed Unify Software in about screen?

Eclipse Example: http://www.permadi.com/wordpress2/wp-content/uploads/2010/11/eclipse-version1.png

Being able to copy this info into clipboard would also be useful.

Matt

The stored value collection fails when more than one item is added.

This is due to the event that is called when the collection is updated. It adds the collection to a HashSet of collections to be updated in the context, which then fail when submitting the context.

Correct the behaviour of EB-473 for the Identity Broker schedulers.

From the documentation that will be created on IDB-352, the UI should warn people trying to configure three or more keys or relationships for a transformation. This is because they can cause performance to degrade considerably due to the increased complexity or the algorithm to perform the comparison.

When attempting to add more than one field to the placeholder connector, additional fields after the first are blocked by the message "An item with the same key has already been added." The first field may be removed and a new field added, but any after the first cannot be added.