Project

General

Profile

Actions

Defect #3040

closed

Cannot create automatic role by attribute with the condition "not empty identity EAV" of type Text

Added by Alena Peterová about 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Low
Assignee:
Tomáš Doischer
Category:
Automatic roles
Target version:
Start date:
01/18/2022
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

Description

Version 11.2.1.

I would like to create an automatic role by attributes, where the rule is "identity EAV attribute xxxxx is not empty". The EAV is of persistent type Text.

Saving fails, developer console displays:

Uncaught TypeError: this.getValue() is undefined


Files

is_not_empty.png (28.6 KB) is_not_empty.png Alena Peterová, 01/18/2022 06:29 PM

Related issues

Related to IdStory Identity Manager - Defect #1210: Cannot set automatic role on read-only attributeClosedOndřej Kopr08/13/2018

Actions
Actions #1

Updated by Peter Štrunc about 2 years ago

  • Target version set to 12.2.0
Actions #2

Updated by Roman Kučera almost 2 years ago

  • Target version changed from 12.2.0 to 13.0.0
Actions #3

Updated by Tomáš Doischer almost 2 years ago

  • Status changed from New to In Progress
  • Assignee changed from Peter Štrunc to Tomáš Doischer
  • % Done changed from 0 to 30

You cannot use EAV attributes of the type Text in general (see #1210). I don't really know the reason but after consultation with Peter the reason may be that there is no index over TEXT field which would lead to performance issues. For other comparison types, a warning is shown but not for this one.

Actions #4

Updated by Tomáš Doischer almost 2 years ago

  • Related to Defect #1210: Cannot set automatic role on read-only attribute added
Actions #5

Updated by Tomáš Doischer over 1 year ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Tomáš Doischer to Roman Kučera
  • % Done changed from 30 to 80

Just to update, you cannot use TEXT values because it is represented as text in the database which JPA cannot use.

I added the information about this to the frontend which was previously shown for every comparison type with the exception of (not) empty.

During testing, I noticed that switching between attributes and comparisons leads to values disappearing. This happens in older versions as well but it is unlikely you would notice it because it only happens sometimes. I fixed it as well.

PR: https://github.com/bcvsolutions/CzechIdMng/pull/229

@kucerar, can you please give me feedback?

Actions #6

Updated by Roman Kučera over 1 year ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Roman Kučera to Tomáš Doischer
  • % Done changed from 80 to 100

LGTM, works nicely.
merged into develop

Actions #7

Updated by Tomáš Doischer about 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF