Ticket #1925 (closed defect: fixed)
Maestro - Oracle Test Validation Invalidates Resource
|Reported by:||crispinatime||Owned by:||jng|
When opening a .FeatureSource? to an Oracle connection and then hitting the "Test" button, the Maestro UI updates to show that the resource has changed and needs a save.
This is even on the same schema where no changes have occurred. This is confusing and misleading to users as the impression is that there has been an edit or change that needs to be saved.
Maybe a goo idea for a new Maestro command would be a 'diff' like listing showing what in the XML (or data) has changed allowing an optional review before hitting Save.