Context:
If Optimize is configured to not import user meta-data with import.identitySync.includeUserMetaData:false the name property of a user entity is currently null. This leads to issues like broken greeting messages (see screenshot).
AT:
- if no first or lastName is available the value of the name field of a user should contain the user id
This is the controller panel for Smart Panels app
[OPT-3418] If no user meta-data is available user.name should contain the user id
Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |
Status | Original: In Specification [ 10000 ] | New: In Development [ 10312 ] |
Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | New: Joshua Windels [ joshua.windels ] |
Description |
Original:
*Context:*
If Optimize is configured to noy import user meta-data with {{import.identitySync.includeUserMetaData:false}} the {{name}} property of a user entity is currently {{null}}. This leads to issues like broken greeting messages (see screenshot). *AT:* - if no first or lastName is available the value of the {{name}} field of a user should contain the user id |
New:
*Context:*
If Optimize is configured to not import user meta-data with {{import.identitySync.includeUserMetaData:false}} the {{name}} property of a user entity is currently {{null}}. This leads to issues like broken greeting messages (see screenshot). *AT:* - if no first or lastName is available the value of the {{name}} field of a user should contain the user id |
Mentioned Roles |
Mentioned Groups |
Status | Original: In Review [ 10212 ] | New: In Development [ 10312 ] |
Assignee | Original: Joshua Windels [ joshua.windels ] | New: Sebastian Bathke [ sebastian.bathke ] |