Project

General

Profile

Actions
Copy link

Defect #3050

open

Filtering by "Identifier in system" on provisioning archive doesn't work correctly

Added by Ondřej Kopr about 2 years ago. Updated 6 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Tomáš Doischer
Category:
Filters
Target version:
13.1.0
Start date:
02/03/2022
Due date:
% Done:

0%

Estimated time:
Affected versions:
10.8.3, 11.0.0
Owner:

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

uid.png (131 KB) uid.png Ondřej Kopr, 02/03/2022 11:03 AM
Actions
Copy link
 #1

Updated by Peter Štrunc about 2 years ago

  • Target version set to 12.2.0
Actions
Copy link
 #2

Updated by Roman Kučera about 2 years ago

  • Sprint set to Sprint 12.2-2 (Mar 02 - Mar 16)
Actions
Copy link
 #3

Updated by Tomáš Doischer about 2 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #4

Updated by Tomáš Doischer about 2 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.

Actions
Copy link
 #5

Updated by Tomáš Doischer about 2 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.

Actions
Copy link
 #6

Updated by Tomáš Doischer over 1 year ago

  • Target version changed from 298 to 13.1.0
Actions
Copy link

Also available in: Atom PDF