Consider the potential for updating relational data through a single core adapter. Need to consider:

• Adds vs. Updates
• If adds, default values
• User expectations
• What it means if Join criteria aren't met (adds or exception)
• Supported transformations
• 1:1 vs. 1:many

Currently the extensibility options for log writers involves a new product life-cycle.

It could be of benefit to create a PowerShell log writer.

It would be good if it kept around the PowerShell context and the script (if possible) for a certain amount of time or activity, in a similar way to the transformation on IDB-839.

It would be extremely helpful to be able to select an object in base connector and run previews when creating transformations that show what the transformation will do.

To allow for the order of the schema to not be important (as it can't be changed), and so that the schema can be manually set up, the CSV connector should look at the header to determine the order of attributes as entries are exported.

When editing a once off timing that has already run, going in to edit the timing takes the edit control to 31/Dec/9999, even though the display says that it "Ran once at a certain time". It would be easier to edit these once offs to run again if the edit screen retained the time that was set

The polling timing on the home page/dashboard always appears as 1 minute in the demonstration. The timing itself is every minute, but it should be going down into the remaining seconds.

In the regression test 2.9.4 states that the SchemaKey part can only be used when fields are required.

Validation for all parts should check that the fields are required if used, and @@Key needs to iterate through each key field to assert that they're required.

The adapter schema is saved to the base connector. To reproduce, add a join transformation, restart the service, and the mapped attribute will be in the connector schema.

The "Path" attribute of the CSV Connector is not a required field, and it is possible to create the connector without specifying one. The connector screen reflects the error "The schema for the CSV Test was not updated for the following reason: The path is not of a legal form. "

If an attribute in the schema of an adapter has the same name as one of the reserved LDAP attribute names (e.g. objectClass, etc.), a warning should be produced and preferably a button to trigger an automatic rename.