As discussed. The add transformation button should add to the end of this list of transformations, using the context of the final transformation.

Additionally, there will have to be buttons for each transformation to add a transformation previously, to allow for adding a transformation to the end.

I received the following error message. Please note that

{0}, {1)..{n} in the error message. It looks like a String.Format issue. (note: JIRA seems to have an issue with this code block)

20130304,21:17:11,Modify anchor for entity {0}

to

{1}

from connector

{2}

failed with reason

{3}

. Duration:

{4}

,Connector,Warning,"Modify anchor for entity af369b4d-adb3-4c76-9b93-bf467f56f920 to ef7d936d-e793-462d-a215-616aeb8e4fa1 from connector User Placeholder failed with reason Connector User Placeholder does not support anchor modification.. Duration: 00:00:00
Error details:
System.NotSupportedException: Connector User Placeholder does not support anchor modification.
at Unify.Framework.ConnectorToModifyAnchorConnectorBridge.get_MultiKeyedModifyAnchorConnector()
at Unify.Framework.ConnectorToModifyAnchorConnectorBridge.ModifyAnchor(MultiKeyValue oldKey, MultiKeyValue newKey)
at Unify.Framework.EventNotifierModifyAnchorConnectorDecorator.ModifyAnchor(MultiKeyValue oldKey, MultiKeyValue newKey)
at Unify.Framework.Adapter.<>c_DisplayClass37.<CheckAnchorChangeOnSave>b_32(KeyValuePair`2 keyValue)
at Unify.Framework.Visitor.<>c_DisplayClass1`1.<Visit>b_0(T item, Int32 index)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`1 visitor)
at Unify.Framework.Adapter.CheckAnchorChangeOnSave(IEntitySchema connectorSchema, IEnumerable`1 entitiesToSave, IEntityPartitionUpdatableContext connectorContext, IEnumerable`1 entityIds)
at Unify.Framework.Adapter.SaveEntities(IEnumerable`1 entities, Boolean reflect)
at Unify.Framework.Adapter.SaveEntity(IAdapterEntity entity, Boolean reflect)
at Unify.Framework.AdapterNotifierDecorator.SaveEntity(IAdapterEntity entityToSave)
at Unify.Framework.LDIFAdapter.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
at Unify.Framework.LDIFAdapterServiceHostDecorator.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
at SyncInvokeExportAdapterEntity(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)",Normal

I'll investigate the actual error separatly, but as far as this issue is concerned, I don't want the anchor modification to be reviewed. Just wanted to bring the formating of the error itself to light.

In a scenario where multiple imports occur within a connector group and the system time enters an exclusion period whilst there are still operations which are queued, Which has precedence over whether or not an import operation will occur?

The connector group queue or the dailyExclusion.

Hi Product Team,

On some import change imports from MA to Adapter, the import on the adapter keeps status is marked as running regardless if it has been completed

Screenshot attached

Schedules not running as shown to Tony.
May be related to TATTS-25, however the configurations were changed as advised.

Logs to be uploaded shortly.

Placeholder connectors with no key set will fail during export due to a ArrayOutOfBoundsException.

Instead, the service should not start if there is no key.

I know we've had issues with this one in the past, but as FIM/TeamCity are two prominent examples of it seeming possible and we generally only target 2008 R2 + these days we should take another look.

Custom actions may also have been a problem before because of 2008 certification, but 2012 only suggests the following is not allowed:

Nested install custom actions (type 7, 23, and 39)

EDIT: This would be in the form of a checkbox where people can opt out.

IdB provides meaningless GUIDs instead of name when reporting errors in UI. Need to provide name of connector or adapter.

Example:
Adapter import all entities for adapter e14dde8a-73ff-4723-acbd-b34f5cb38ac0 failed with reason EMAIL_ADDR is not a valid LDAP attribute name Parameter name: attributeName. Duration: 00:00:01.1860000

Test file connector imports data which contains start and an end date. An adapter is configured with this as it base connector and applies Is Operative Transformation as follow:

A full import brings in the changes to the Is Operative Column (Active) on changes are shown using a delta.

General UI:

I think the aim should be to have as much above 'the fold' as possible. I dont like having to scroll down to see essential info. The Logo takes up waaay to much space. Approx 1/3 of the screen is wasted on the logo & white space.