The 14.5 Release delivers a timesaving feature for creating new roles that share similar permission settings to existing roles, as well as several fixes to several customer-found issues.

 

Cloning roles 

You can now save time when creating new roles by cloning a similar, existing role. Cloned (or copied) roles inherit all the permission settings of the role you cloned. 

 

To clone a role:

1. Go to Community Admin > Users > Permissions.
2. Find the role you want to clone in the Roles list and click Clone.
   
   
   
   
3. Enter a name for the new role and click Save.
4. Click Edit next to the newly created role.
5. Change the permission settings as needed and click Save.

Cleanup of customer-facing text strings

In the 14.5 release, we completed a sweep of several hundred customer-facing UI texts strings to make sure we used terms like “username”, “login”, “signin” consistently across the desktop and mobile community experiences. As a result, several text strings were changed (though their underlying text keys have remained the same). Here's a summary of the changes:

 

Old Term         Used to mean...                                                                                                              New Term

login      the act of signing in to a site                       sign in

login      the unique userID                                     username

logout     the act of signing out of a site                      sign out

logins     the number of times a user has signed in to a site    signins

logouts    the number of times a user has signed out of a site   signouts

 

Note: If you run any custom reports that key off of columns that use the old terminology, you should update these reports to use the updated text strings.

New APIs

Create users by SSO ID

You can now create users by SSO ID using: [rest-api/bd-p/developers-rest-api?leaf-id=Community.users.add#Community.users.add]community/users/add by passing the user’s SSO ID, login name, and email.

You Found It. We Fixed It.

• @mentions now supports user names that include spaces (for example, "John 3").
• When using Internet Explorer 8 or 9 to perform an Advanced Search on a community site, the Advanced Search box didn’t appear. This issue has been fixed.
• When performing a search, articles that included the word “public” in the subject displayed the word “public” in the search results page, even when the word “public” was not the term being searched for. This display issue has been fixed.
• Anonymous posts flagged as spam and sent to the Spam Quarantine no longer produce the error that made the Spam Quarantine page inaccessible.
• When uploading videos for Contests using the “From my Computer” options, the video upload process no longer freezes.
• Previously, with pre-moderation enabled, uploaded avatars still requiring moderation would display in a user’s profile before the avatar had been approved or rejected. This display problem has been fixed.
• Normally, when you go to a community topic and choose the Email to a Friend option, you are returned the original topic page. However, if you opened additional browser tabs and navigated to other community pages and then returned to the tab and clicked Email to a Friend, instead of taken back to the originating topic page, you’d be taken to the last page viewed in the other browser tab. This behavior has been fixed, and you are now returned to the originating topic page.
• For Products and Reviews, the threaded API call (/threads/id/103/messages/threaded) now returns a threaded response instead of throwing an error, which it did previously.