Polishing functions in the Privacy module (MGNLPRIV-20)

[MGNLPRIV-22] On submit form displays labels and descriptions for personalFields names rather than their parent nodes (group names) Created: 31/May/18  Updated: 16/Apr/20  Resolved: 15/Jun/18

Status: Closed
Project: Privacy
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Sub-task Priority: Neutral
Reporter: Martin Drápela Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2018-05-24-14-43-57-206.png     PNG File image-2018-05-24-14-49-50-704.png     PNG File image-2018-05-24-14-51-46-024.png     PNG File image.png    
Issue Links:
Cloners
clones MGNLPRIV-18 Exclude empty input fields from consent Closed
Template:
Date of First Response:
Sprint: Kromeriz 151, Kromeriz 152

 Description   

(Originally the second part of MGNLPRIV-18)

The constructor of the templates.form.consent.not.given message iterates over the fieldNames themselves instead of just personalFields.

See the "not.given" message with two "name" consent-to-be-given items in the below screenshot for the following config:

 

 

 

 



 Comments   
Comment by Roman Kovařík [ 11/Jun/18 ]

 

As the validator doesn't have access to translations of the fields titles, we could fix the issue by preventing duplication of consent groups in the error message.

Generated at Mon Feb 12 10:30:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.