Project

General

Profile

Actions

Task #1272

closed

Eav attribute - default value as placeholder

Added by Radek Tomiška over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Radek Tomiška
Category:
Eav
Target version:
Start date:
09/26/2018
Due date:
% Done:

100%

Estimated time:
Owner:

Description

Default value configured in eav form attribute will be used as placeholder only - user has to select value manually.
This automatism with default value confused the user (and developer) - default value was shown as saved (and she was prepared for save only).

The second step - value generator will be implemented for save eav values with configured default value. This generator will save eav values, when owner (entity) is created.


Related issues

Related to IdStory Identity Manager - Task #1259: Generate values during create entityClosedOndřej Kopr09/18/2018

Actions
Related to IdStory Identity Manager - Defect #1314: "Required confirmation by the implementer" should be checked by defaultClosedRadek Tomiška10/11/2018

Actions
Actions #1

Updated by Radek Tomiška over 5 years ago

  • Related to Task #1259: Generate values during create entity added
Actions #2

Updated by Radek Tomiška over 5 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Radek Tomiška over 5 years ago

  • Assignee changed from Radek Tomiška to Ondřej Kopr
  • % Done changed from 0 to 60

I implemented it a little differently - default value not make a sense as placeholder from mz point of view, so it's not mixed - provided localization or placeholder is used as placeholder.
I've added new property to FE components rendering eav attributes, if default value can be used or not. Default value is still used for reports, authorization policies etc., where form submission is required.
Default value is not used in entities detail - "more information" tab.
I removed sending read only (~disabled) extended attribute values from FE to BE - read only attributes can be secured and this check worked only if value is not changed in the meantime (update and security check was skipped). Now it will be more transparent.

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/7440bff6b7d1f5b9e71fb535f7a9b067a163c4bb

Could you do a feedback please together with implementation value generator for saving eav values with configured default value, when entity is created?

Actions #4

Updated by Ondřej Kopr over 5 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Ondřej Kopr to Radek Tomiška
  • % Done changed from 60 to 100

Nice, works perfectly. Default value isn't used on entities next information tab.

Actions #5

Updated by Radek Tomiška over 5 years ago

  • Status changed from Resolved to Closed
Actions #6

Updated by Radek Tomiška over 5 years ago

  • Related to Defect #1314: "Required confirmation by the implementer" should be checked by default added
Actions

Also available in: Atom PDF