Defect #3050
openFiltering by "Identifier in system" on provisioning archive doesn't work correctly
0%
Description
The filtering by column "Identifier in system" probably filters by UUID not by UID. The result looks strange.
But filtering on archive table works good.
Files
Updated by Roman Kučera almost 3 years ago
- Sprint set to Sprint 12.2-2 (Mar 02 - Mar 16)
Updated by Tomáš Doischer almost 3 years ago
- Status changed from New to In Progress
Updated by Tomáš Doischer almost 3 years ago
This is true but it seems that this is quite deliberately done this way:
FYI,
<Advanced.Column property="systemEntityUid" header={ this.i18n('acc:entity.SystemEntity.uid') } sort sortProperty="systemEntityUid" face="text" rendered={ isArchive && _.includes(columns, 'systemEntityUid') }/> <Advanced.Column property="_embedded.systemEntity.uid" header={ this.i18n('acc:entity.SystemEntity.uid') } sort sortProperty="systemEntity" face="text" rendered={ !isArchive && _.includes(columns, 'systemEntityUid') }/>
But I don't really see why, since if you try to create an account without a UID, the event will fail, and the account will not be created and it will not be in the table. Therefore, you should always be able to filter by a UID. I will make the change and test it.
Updated by Tomáš Doischer almost 3 years ago
- Sprint deleted (
Sprint 12.2-2 (bře 02 - bře 16)) - Target version changed from 12.2.0 to 298
This is currently impossible to do. Provisioning operation does not have a field (column in database) that contains an identifier in a system so it does not support sorting by it.
We will add the column in the next major version because this will not be backward compatible. (Current operation will not have the value and sorting will not work for them.) Making it backward compatible would be really challenging.
Updated by Tomáš Doischer about 2 years ago
- Target version changed from 298 to 13.1.0