One of the bug fixes that we have implemented this week is in relation to the blogs dashboard.

The problem that was occurring was that when a user with the select permissions would navigate to the blogs dashboard on the intranet. They would not be able to see all of the appropriate cards. This issue has since been resolved an is no longer occurring. Now when a user navigates to the blogs dashboard they will be able to see all of the appropriate  cards displayed.

For more information, please see our documentation:

Blogs

Support Site

One of the bug fixes that have been resolved this week is in relation to the directory apps.

The problem that was occurring was that when a user with the select permissions would access any of the directory apps (Locations, Teams & People) then they would observe that the users username was being displayed instead of their forename and surname. As a result this could cause some confusion for users. This issue has since been resolved and is no longer occurring.

For more information, please see our documentation:

Support Site (Directory)

Another bug fix that we have implemented this week is in relation to the body widget.

The problem that was occurring was that when a user with the select permissions would navigate to the blogs homepage on the intranet and then select the hashtag that had the same as one or more blogs posted. Then the user is relocated to the global search screen. This should not be the case. As a result this issue has since been resolved and is no longer occurring.

For more information, please see our documentation:

Blogs

Support Site

One of the features that have been implemented this week is in relation to the user management app.

The problem that was occurring was that when a user with the select permissions (admin) would go the user management screen then they would only be able to see a limited number of users. They were not able to see all of the roles on the intranet. This has now been updated and an admin can now access the user maangement screen and view all users.

For more information, please see our documentation:

Administration

Support Site

Another new feature that we have implemented this week is in relation to the search functionality.

The feature that we have added is that now when a user goes to use the search functionality on the intranet. Then interact with the filters on the LHS (left-hand side) they will see a count for the number of results depending on that particular filter. 

For more information, please see our documentation:

Search

Support Site

One of the bugs that were resolved this week was in relation to the all content widget.

The problem that was occurring was that when someone with the select permissions would go to implement a widget. Then select the all content widget and choose the 'all content' option and then choose to display blogs; then unpublished blogs were being displayed. This should not be the case and as a result was causing confusion for some users. This issue has since been resolved and is no longer occurring.

For more information, please see our documentation:

Blogs

Support Site

Another bug fix that we have resolved this week is in relation to the Teams app.

The problem that was occurring was that when a user with the select permissions would go to view teams on the intranet; they would still be able to see any teams that were classed as unpublished or archived. As a result this was causing confusion for some users. This issue has since been resolved and is no longer occurring.

For more information, please see our documentation:

Teams

Support Site

One of the bug fixes that we have implemented this week is in relation to users.

The bug that was occurring was that when a external user was granted access to the intranet then they would be able to select and view the profile of other users on the intranet. This should not be allowed and as a result has since been resolved and is no longer occurring.

For more information, please see our documentation:

Users

Support Site

One of the bug fixes that we have implemented this week is in relation to teams.

The problem that was occurring was that when a user with the select permissions navigates to teams and then archives a selected team they should no longer be able to see a team. However this is no longer the case and the issue has since been resolved. Now when a user archives a team the expected actions occur.

For more information, please see our documentation:

Teams

Support Site

Another bug fix that we have implemented this week is in relation to widgets.

The problem that was occurring was that when a user with the select permissions goes to implement a widget.  and then add a piece of published content; when you then go into administration and change a piece of content to unpublished the widget still displays the now unpublished content.

For more information, please see our documentation:

Widgets

Support Site

One of the bug fixes that we have implemented this week is in relation to Groups.

The problem that was occurring was that when a user with the select permissions of a moderator role and would join a public group as a member then their permissions would not reflect the spec. As a result this was causing some confusion for users. As a result this issue has since been resolved and is no longer occurring.

For more information, please see our documentation:

Roles/permissions

Groups

Support Site

Another one of the features that we've added this week is in relation to the dashboard screen on the intranet.

Now when a user goes to the dashboard screen on all the different areas of the intranet they will now be able to see the timestamp/date on all the cards so that the user can see when it was last updated. The affected areas from this new implementation are:

• Message Wall
• Blogs
• Groups
• Group
• Ideas
• Queries
• Team
• Location
• Engagement stats (admin)

For more information, please see our documentation:

Support Site

One of the new features that we have implemented this week is in relation to the WYSIWYG.

As a result of this update to the WYSIWYG now when a user on the intranet goes to create or edit content depending on their permissions will see a particular view of the WYSIWYG. This is because a user with less permissions will see only limited areas of the WYSIWYG. Whereas a user with more permissions will be able to interact fully with the WYSIWYG.

For more information, please see our documentation:

WYSIWYG

Support Site

One of the new features that we have implemented this week is in relation to the WYSIWYG.

The feature we're adding is abbreviation settings. Now when a user with the select permissions interacts with the WYSIWYG they will be able to see a floating edit menu to use for editing abbreviations. By adding this feature we believe that it will help to improve the user experience when interacting with the WYSIWYG.

For more information, please see our documentation:

WYSIWYG

Support Site