Polishing functions in the Privacy module
(MGNLPRIV-20)
|
|
| 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: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Kromeriz 151, Kromeriz 152 | ||||||||
| Description |
|
(Originally the second part of 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. |