Affects: Documentation (Ref Guide, User Guide, etc.) Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008RT5S project_key: JBEPP The UIUserInfoPortlet shows the full name of login user[1] and the full name is fixed to given-name-first order[2]. Like Japanese name, It's not always true that the full name of user is given-name-first order. So, display name should be configurable. [1] EPP_5_1_0_GA/portlet/exoadmin/src/main/webapp/groovy/admintoolbar/webui/component/UIUserInfoPortlet.gtmpl line 11: <a href="$accountSetting"><%=uicomponent.getUser().getFullName()%></a> [2] exocore/2.3.6-GA/exo.core.component.organization.api/src/main/java/org/exoplatform/services/organization/impl/UserImpl.java line 137: public String getFullName() line 138: { line 139: return getFirstName() + " " + getLastName(); line 140: }
Release Notes Docs Status: Added: Not Yet Documented Primary SME: Added: theute Forum Reference: Removed: https://na7.salesforce.com/500A0000008RT5S Added: https://na7.salesforce.com/500A0000008RT5S
Help Desk Ticket Reference: Added: https://na7.salesforce.com/500A0000008RT5S Forum Reference: Removed: https://na7.salesforce.com/500A0000008RT5S
Need more info, logic can easily be changed in the groovy file by customer. We can't tell if a name is Japanese or English and order firstname/lastname accordingly as a generic rule.
The customer requested this requires editable display name. In my opinion, it would be better to add "display" field like addressbook of thunderbird. https://wiki.mozilla.org/Thunderbird:Help_Documentation:Using_the_Address_Book#Contact_Tab I agree that there is no generic rule. On the the other hand, in case of mixed name style, I cannot change groovy template easily.
Labels: Removed: portal Added: EPP_5_2_1_Candidate portal
Labels: Removed: EPP_5_2_1_Candidate portal Added: EPP_5_2_1_Candidate
An additional 'display name' field for each user would be required to meet these requirements.
Labels: Removed: EPP_5_2_1_Candidate
Marek Posolda <mposolda> made a comment on jira GTNPORTAL-2358 I am adding new patch GTNPORTAL-2358-fullName.patch as previous patches can work only with "displayName" support in OrganizationService API on interface User, which is not option for now. New patch is using fullName as temporary persistent field, so fullName is placeholder for non-existing displayName. What exactly is done in patch is: - Adding new UI field with name "displayName" to all UI forms, where you can create or edit user ( UIRegisterInputSet, UIAccountProfiles, UIAccountInputSet, UIAccountEditInputSet ). So name of UI field is "displayName" and name of localization label is also "displayName". I added localizations only for "en" and "cs" properties bundles as I don't know other languages :) - UI components are communicating with User interface via "setFullName" and "getFullName". So fullName is now used as temporary placeholder until methods "getDisplayName" and "setDisplayName" will be available in Organization API. I added "TODO: GTNPORTAL-2358" in all pieces of code, which needs to be changed once displayName will be available in Organization API. This will allow us to use getDisplayName and setDisplayName and get rid of fullName as temporary placeholder. - IDM integration is changed to support persistent implementations of "getFullName" and "setFullName". For this purpose I forked class UserImpl from Organization API (I made a subclass of eXo UserImpl class with overriden methods getFullName and setFullName). Again, name of new attribute at DB level is "displayName", which will assure compatibility with future versions (after support for displayName in Organization API will be added).
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: CAUSE: When user login, he can see his fullname in right top corner. This is his fullName according to format "firstName lastName" and it's hardcoded so that users can't use different format. It is also quite bad for some languages like Japanese, where is common to use opposite order as fullName. FIX: There is new field "Display Name" in UI in all screens where is possible to create or edit user. So user is able to fill his displayName and this displayName will be used in right top corner instead of fullName. DisplayName is not mandatory and when user is not using it, it fallback to fullName (old behaviour). This also ensure backward compatibility with older versions of EPP. Name of new attribute in Picketlink IDM database is "displayName" but as said before, attribute is not mandatory.
Marek Posolda <mposolda> updated the status of jira GTNPORTAL-2358 to Resolved
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1 @@ -CAUSE: When user login, he can see his fullname in right top corner. This is his fullName according to format "firstName lastName" and it's hardcoded so that users can't use different format. It is also quite bad for some languages like Japanese, where is common to use opposite order as fullName. +The way the display name of authenticated users presented in portal screens used the firstName lastName format (commonly referred to as Western Order). Customers in regions where Eastern Order is prevalent reported issues with configuring upper-name requirements in portal UI screens. The fix introduces the Display Name (displayName) field, which is available in all UI screens. When configuring a user account, the user can specify their preferred display name, which overrides the fullName value retrieved by default.- -FIX: There is new field "Display Name" in UI in all screens where is possible to create or edit user. So user is able to fill his displayName and this displayName will be used in right top corner instead of fullName. DisplayName is not mandatory and when user is not using it, it fallback to fullName (old behaviour). This also ensure backward compatibility with older versions of EPP. Name of new attribute in Picketlink IDM database is "displayName" but as said before, attribute is not mandatory.
Nothing to add on the technical note, what should I do ?
verified: There is new input field "Display Name" when creating or editing user. The field is mandatory and if you leave it blank the display name is constructed from first name and last name. The display name is shown in right top corner when user is logged.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.