5.17.05.17.0

1. Web accessibility

This release, we have focused our accessibility progress on improving the keyboard accessibility of the Pure Portal. These changes allow keyboard users to more easily navigate the portal using the TAB key to access fingerprints, search filters, navigation and other aspects of the portal.These changes will greatly benefit visitors using assistive technologies such as screen readers to navigate and access the information on the portal.

In addition, we have also integrated the correct states of buttons, checkboxes and toggle buttons to let our assistive technology users know if a button or checkbox has been activated. We strongly believe that these changes will improve the overall experience for everyone using our Pure Portal.

We have updated our Pure Portal accessibility statement. It is a declaration in the form of a short information page which is available via a link from every page of the website, via the footer. This update brings us in line with current UK government advice on accessibility compliance, but more than that, it provides a clearer, more comprehensive picture of our compliance status for all users globally. You can also find on this page a link to our most recent Voluntary Product Accessibility Template (VPAT), which provides a comprehensive review of our accessibility provisions across multiple areas.

This statement replaces the previous version of this statement, and can be found in the footer, by clicking the link "About web accessibility". We have also taken the opportunity to update the URL of the page from ".../vpat" to ".../web-accessibility".

2. Privacy and personal data 

For customers with the Award Management module, Administrators can - via a configuration option - select which document types should or should not be attached to the email when applications when sent for peer review. This feature improves how potentially sensitive documents are shared from Pure to external entities.

Click here to expand...

Information	Screenshot
To configure which document types should NOT be attached, administrators should navigate to Administrator > Award management > Module configuration. In the Application peer review section, documents of specific types NOT be attached to emails can be selected from the list of optional file types.
When users upload documents to an application, they will be presented with a warning stating specific document types will not be included as an email attachment.
When a user requests an application be sent for peer review, a short warning is added to the summary screen stating that confidential document types will not be attached.

 

 

3. Pure Core: Administration

A new field has been added to the coversheet xml configuration. It is now possible to include the total count of authors on a given publication. The condition, "additionalSettings", has also been added to define that the count of authors field should be displayed if the count of authors exceeds the configured limit.

The funding opportunities content type, and how it is managed and shared in Pure, has been updated and improved. The primary goal of these updates is to improve how users work and interact with opportunities in Pure. Part of these improvements are to pave the way for Pure to move funding discovery features, currently found in the funding discovery module, to Funding Institutional, a product specifically developed to improve the discovery and dissemination of funding opportunities across and within institutions.

Click here for more details...

The introduction of improvements to the content type and the implementation of Funding Institutional will be phased. In this release, only improvements to the content type are included, and in subsequent releases, the integration with Funding Institutional will be introduced. The Funding Discovery module will be available until the integration with Funding Institutional is fully functioning. To gain access to the funding opportunity improvements, customers must be on the Unified Project Model (UPM).

The improvements included in this release are as follows:

3.2.1. Visibility

Visibility on opportunities

Visibility settings have now been added to funding opportunities. The default visibility setting is Public, so please be aware that any internal opportunities will be surfaced in the web service if they are made Public.

Information	Screenshot
To set the visibility of an opportunity, navigate to the end of the Metadata section of the opportunity. The desired visibility setting can be selected from the drop down. Users must click Save for the changes to take effect. Migration of existing opportunities Existing opportunities will be migrated to the new opportunity model. With this migration, the visibility will be set to Public.

Funding opportunities visible to all users

The funding opportunities content type is now visible to all users of customers with the funding opportunity module.

Information	Screenshot
The funding opportunities sub-menu tab can now be found in the Editor tab, rather than Master data. For personal users, it will be found under the Personal tab.
For customers (and their users) with access to the Award Management Module, a quick link to the funding opportunities has been added at the top of the AMM overview screen.

3.2.2. Display updates

Renders

The renders of funding opportunities have been updated to be more informative.

Information	Screenshot
The short render has been updated across the different viewing formats.	In list view: Short render explained:
The long render has also been updated to highlight fields with missing values.

Table view configuration

The available columns in the matrix/table view have been expanded.

Information	Screenshot
The count of entities with which the opportunity has been shared is now available. Clicking on the value opens the sharing tab of the relevant opportunity.
The visibility of columns can be changed by clicking on the gear icon and selecting which columns should be visible. Columns can be moved by dragging a column header in the table view.

Card view

The card view has also been updated with a more regular, consistent layout and shape of cards on the page.

Information	Screenshot
More information has been added to the summary block of the card. If important date fields are specified, they will be shown on the summary block. Limited submission flags have also been added if specified.

3.2.3. Model updates

The funding opportunities content type model has been extended to include new fields.

Information	Screenshot
Intent to apply An intent to apply section, with a date picker has been added. Additional fields related to the contact and submission aspects of the opportunity have also been added in this section.
Recurring opportunity tag To account for recurring opportunities, a Recurring radio button has been added to add a flag to the opportunity. This is especially relevant for assisting administrators with identifying what are genuine past deadlines, versus deadline shift due to the opportunity being a recurring opportunity.
Nature of activity A nature of activity selector has been added to funding opportunities.
Labels The option to add labels to opportunities is also included. Labels can be added by personal users, and are viewable to all users, even if personal users are not allowed to modify funding opportunities.	Example of read-only opportunity where labels can be modified or added.
Multiple funders on opportunities Users can now select multiple funders on all opportunities. The order of appearance of funders can be changed by using the ↑ or ↓ arrows, and can be removed from the list using the '-'.
Limited submission 'soft lock' For opportunities that are limited submission in nature, a soft 'lock' has been put in place to notify users that the opportunity they are trying to link to an application or award will exceed the number of specified submissions. Users may still relate the application or award to the opportunity, hence soft 'lock'. Administrators can filter on opportunities with more related content than is allowed. Additional warnings of exceeded limits can be found when trying to relate applications directly from the opportunity. Administrators can quickly view which applications have caused opportunities have exceeded their submission limit by clicking on the red application icon in the limited submission column of the matrix/table view of the opportunity content view.	Example of notification in application of limited submission count being exceeded Examples of notification in opportunity view screen of limited submission count being exceeded Examples of notification in opportunity edit screen of limited submission count being exceeded limited

3.2.4. Configuration options

Administrators can allow users to create, modify and delete funding opportunities.

Information	Screenshot
Administrators should navigate to Administrator > Funding opportunities. Funding opportunities can be created either by Everyone, Nobody or Administrators of opportunities only, and administrators can set whether personal users can modify or delete funding opportunities.

3.2.5. Role migrations

Editor of funding opportunities → Administrator of funding opportunities

Information

Screenshot

All Editors of funding opportunities have been migrated to the Administrator of funding opportunities role for the express purpose of administering funding opportunities. This global role can be assigned to any user via Master data > [User] > Roles > Global roles and rights, select Administrator of funding opportunities. The role will have the following rights for all opportunities in Pure:    Read Edit Update Delete Share The role is designed to enable sharing of opportunities across the institution, and with the eventual integration with Funding Institutional, serve as a administrative bridge between the two products. More information on this will follow with the integration.

3.2.6. Sharing of Opportunities

Funding opportunities can now be shared across multiple organisations and/or users. 

Information	Screenshot
Sharing individual opportunities
1. To share an opportunity, navigate to the Edit screen of an opportunity, and then the Share menu item. Share options across different roles Administrators and Administrators of opportunities will be able to share with both individual Users and Organisations. Personal users will only be able to share opportunities with other personal users.
2. To share with either a specific user and/or with all users in an organisation, click on the respective button and find and select the entities.	User selection: Organisation selection:
3. Once entities have been selected, press Save. Entities can be removed from their respective lists by clicking the "-" button. Once the opportunity has been shared users will receive notifications that the specific opportunity has been shared. For more information on notifications, please consult the notifications section in these release notes.
Bulk share of opportunities
Administrator of opportunities users can bulk share opportunities from the content list view by:
1. Clicking the multi-select button in the list view of opportunities
2. Once the appropriate opportunities to be shared have been selected, users must click Bulk edit
3. Users must select Share with users and organisations, then Next.
4. Specific users and/or organisations can be searched for and selected, and once selected, users must click Next.
5. A confirmation screen will be presented, and users must select Apply the changes for the opportunities to be shared.
6. A receipt of action is provided, and users may download and check the log file of this bulk share action. When an opportunity has already been shared with a user, the summary number in the receipt will display a lower number than the count of selected opportunities from the bulk share action. The log file will state that the opportunity has already been shared.
Rejection and re-sharing of opportunities
Opportunities that are shared with users either directly or via their organisation can be removed/rejected by users, typically when the opportunity is not relevant to their research interests. The list of users who have rejected a shared opportunity is provided in the Share tab of the opportunity, and is only visible to users with Administrator and Administrators of funding opportunities role . Administrators of funding opportunities can reshare the opportunity with the user if required by clicking on Reshare. If Administrators of funding opportunities try to share with a user who has previously rejected the opportunity, a small notice to this effect is shown in the search result list.

3.2.7. Filter updates

Filters on content view screens have been updated to account for model and feature extensions. The following filters have been added:

Information	Screenshot
Nature of activity type
Recurring opportunity
Shared with The Shared with organisations and users filters are new in both form and function. The Shared with filters are the first of our compound limit filters whereby a limit option is selected first, and can be extended by selecting specific entities. For example, if a user wants to limit the list of opportunities to those that were NOT shared with an entity, they can select Not shared with organisations/users, and then search for and select the specific entities. A simpler use case would be a user wanting to filter all opportunities that have NOT been shared with any entities. This can be achieved by only selecting Not shared with organisations/users. The new compound limit filters will, over time, replace the typical pair filters wherein two filters are necessary for the same action.
Deadlines The deadline filter has been extended to allow for a more fine-grained approach to selecting opportunities with specific or no specified deadlines, including within preset or specific time ranges.
Created by user This filter allows users to search for opportunities created by specific users.

3.2.8. Personal users and opportunities

All users in Pure will have access to all (non-visibility limited) opportunities if their institution is subscribed to the funding opportunity module.

Information	Screenshot
Navigating to list of funding opportunities For users with the Personal User Overview enabled, any opportunities shared with or created by the user will appear in the project/application/funding opportunity overview. Only users with access to the new personal user overview can access quick links to shared opportunities in their personal overview.	Example of funding opportunities in project inventory (with projects in timeline) Example of funding opportunities in inventory (with no projects)
Default filters when viewing funding opportunities The default filters in content list view for personal users include the Deadline filter and either the My content or Shared with users filter, depending if personal users can modify funding opportunities. The Deadline filter serves to filter opportunities that have a deadline in the future, and include opportunities with no deadline specified. The Shared with users filter is pre-configured to filter opportunities shared with that specific user, and the My content filter is pre-configured to only show opportunities that are editable by the user.	Example view with default filters
Viewing all opportunities in Pure By removing all filters, personal users will be able to view all opportunities within Pure, unless they are visibility-limited to Confidential.
Viewing shared opportunities Any opportunities that are shared directly with the user or indirectly via their organisation, will show in the pre-configured Shared with me, or Shared with my organisation filters. The Shared with my organisation filter will only show active affiliations. Confidential opportunities will only be visible to users if they have been shared with the specific users.
Removing (rejecting) shared opportunities Users can remove shared opportunities from their shared with me lists by clicking on the Not relevant - remove from my list button under each opportunity that was shared with them. If viewing all opportunities, only those that are shared with the user can be removed/rejected.

3.2.9. Notifications related to funding opportunities 

Sharing

Each user with which an opportunity is shared, either directly or via their organisation, will receive a notification that the opportunity has been shared with them.

Information	Screenshot
For each type of share (direct or via organisation), the user will receive a notification. Users can click on the link(s) to be taken either directly to the opportunity or the list of opportunities (if more than one opportunity is shared). For opportunities shared via organisation, only users with active affiliations will receive the shared opportunity, and notification. Note: Users must have logged in to Pure to receive these notifications.
Users can manage their notifications via Message settings in their user profile. By default, users will not receive opportunities shared with their organisation but can select the appropriate box if they choose to receive them.

Updates to funding opportunities

If important fields are changed in an opportunity, certain users, depending on the field and if any related content, will receive a notification.

Information	Screenshot
Deadline change
As introduced in 5.16, but repeated here for reminder purposes: Deadline changes on opportunity and effects on related applications If a deadline is changed, a notice is added to related content in multiple places stating that the deadline of the related opportunity differs from the related content. In the list view, the date and time of the change is provided in the notice. The notice can be dismissed if required. Note: A notification will only be sent to applicants on applications if the application has not been marked as sent to funder. The date and time of the new deadline is also shown in the content editor view and edit screens.
Notifications on related applications Specific criteria will trigger a notification being sent to users if the deadline on an opportunity is changed. Applicants and submitters will not receive notifications since they can only create and not modify applications. The user making the changes to the deadlines will also not receive any notifications.	1. When editing funding opportunity deadline IF application related to opportunity AND application not sent to funder (Awarded/Rejected/Pending) AND application deadline missing or different deadline to new opportunity deadline AND deadline in the future WHEN workflow is: Standard  AND validated  THEN notification of opportunity deadline change sent to Validators OR not validated THEN notification of opportunity deadline change sent to Editors, Assisting editors and Validators Customer defined THEN notification sent to Editors, Assisting editor and checking/Approving editors in current step Disabled THEN notification sent to Editors and Assisting editors 2. When creating new or editing existing application IF adding or replacing opportunity OR changing application deadline AND application not sent to funder (Awarded/Rejected/Pending) AND application deadline missing or different deadline to opportunity deadline AND deadline in the future WHEN workflow is: Standard  AND validated  THEN notification of opportunity deadline change sent to Validators OR not validated THEN notification of opportunity deadline change sent to Editors, Assisting editors and Validators Customer defined THEN notification sent to Editors, Assisting editor and checking/Approving editors in current step Disabled THEN notification sent to Editors and Assisting editors

3.2.10. Web service and Funding opportunities 

The Web service has been extended to cover the new and extended fields in funding opportunities.

New:

• natureTypes
• academicLabels
• labels 
• descriptionOfApplicationProcess
• urlToApplicationSite
• emailAddressForApplication
• recurring 
• associatedApplicationCount
• visibility
• confidential

Changes:

• fundingOrganisation is now List<fundingOrganisations>

 

 

4. Pure Core: Web services

The changes endpoint will no longer expose UPDATE events for content that is saved in Pure but with no field modifications or other changes. This was done in an effort to reduce the amount of noise coming through the endpoint. You can now trust that if you get an UPDATE entry for a piece of content, that content will have changes to it's data.

This change will affect the changes endpoints across all the available API's in Pure when upgrading to 5.17.X. 

The new Pure API will provide a backwards-compatible fully featured web services API for using and managing research information in Pure. As part of 5.17 we're releasing an early access version of the external organizations endpoint that all Pure customers can enable.

Click here for more details...

The Pure API is an evolution of the existing REST web services, to support a backward-compatible read and write REST JSON endpoint for using and managing research information data in Pure.

In order to achieve these objectives, we've made a number of changes to how the web service endpoints are structured and the format of the managed entities in the new API.

• The endpoints for an entity are structured so it is clear where you can expect REST or RPC semantics - this should make it easy for developers to interact with the API with a minimal upfront time investment
• The entity format is optimized in regards to JSON data modeling best practices and with an expectation of the model evolving in a backward-compatible manner in the future
• The API specification is defined and published as an OpenAPI 3 specification enabling service users to quickly generate a client while at the same time providing developers with useful documentation on the API and its semantics
• The entity API includes a number of helper operations that return the allowed values for the different parts of the entity model where this is relevant - this should make it easy for developers to submit valid changes to the write portions of the API
• All modification requests are made on behalf of a specified Pure user and clearly audit logged with both user and API key details
• As we expect the API to be able to support older clients updating against a newer version of the API all PUT requests have JSON merge patch semantics - this ensures that older clients do not inadvertently clear new properties that they don't know about

When the module has been successfully enabled a Swagger UI representation of the OpenAPI 3 specification will be available at https://{your Pure hostname}/ws/api/api-docs/index.html?url=/ws/api/openapi.yaml alternatively the latest API on the development community sandbox server can be found here. A sample Java client that can be used as a starting point for developing a client can be found here.

Information	Screenshot
The early access Pure API can be enabled in the Pure administrator section. Please note that enabling or disabling the Pure API module requires a restart of Pure in order to take effect.
All use of the new external-organizations endpoint requires an API key that is generated in the "User API Access" section of the "Pure API" administrator pages. The main difference from the existing web service API keys is that the new Pure API requires a user that the system using the API key will act on behalf of.

 

 

5. Integrations

With this release, we are very happy to introduce the integration with FECyT, The Spanish Foundation for Science and Technology, for the generation of Curriculum Vitae in a standardized format, CVN (Curriculum Vita Normalizado). With the CVN format and language, researchers belonging to Spanish institutions can complete their CV in their institution’s Pure once and when completed, a PDF file is generated containing all their CV information.

Through this integration researchers can also generate their CVs in an abbreviated format, CVA, in which they can include selected recent and most relevant research activities.

Click here for more details...

If you wish to enable the integration with FECyT, please submit a ticket with this request to Jira. 

 

To allow the use, and creation of, CVN and CVA format CVs, Administrators need to follow the instructions below. 

Information	Screenshot
In Administrator > Curricula Vitae > FECYT Configuration, set up the FECyT configuration. Select your root organization, i.e. the employing entity. A file containing the mapping between Pure classifications and FECyT codes is required. A default mapping file is already included and can be downloaded and visualized by clicking on the Download current mapping file button. If a different mapping is required for your institution, it is possible to upload a new or updated mapping file. Once the new mapping file has been uploaded you must save the new configuration.
Once the configuration has been saved, FECyT can be enabled in Administrator > Curricula Vitae > Curricula vitae types.
To generate your CVN or CVA go to Editor > Curricula Vitae and select FECyT CVs.
If you are an Administrators or CV Editor, select the name of the person you want to generate the CV for.
Select the type of CV to be generated; either CVN (standardized) or CVA (abbreviated), and select the language in which you want to generate the CV.
It is also possible to insert a personal ID and ID number. The following personal IDs are supported:
Once the form has been filled in, the CV can be created by clicking on the button ‘Send to FECyT’. A request is then sent to FECyT, where the CV is compiled based on data from Pure. Once the CV has been created, it can be downloaded in pdf format.

 

 

The DataSearch functionality has now been renamed Data Monitor. The functionality in Pure remains unchanged, and is described in this pdf and in the 5.16.3 release notes. 

In release 5.17.0 we have improved the self import from Web of Science (and Web of Science Lite). It is now possible for researchers and researcher managers to search for content using their ResearcherID.

Click here to expand...

In Editor > Research Outputs >Import from online source > Web of Science, search for content using ResearcherID as author ID.

 

 

6. Report Module

A new starting page for the report module has been introduced. The purpose of the landing page is to provide easier access to reporting functionality and reports. The new landing page also gives users access to reporting, without having access to other content in Pure. The new starting page also provides Pure a space where future versions can display various aspects of the report module.

The reporting landing page is a work in progress. Over the next coming releases we will continue working on the design and functionality of the page, and look forward to hearing your feedback.

When creating data tables that contains information on many different content types, you can easily lose sight on the different elements. In order to better structure your data, it is now possible to add multiple data tables to your report workspace.

Click here for more details...

Information	Screenshot
Additional data tables can be added, deleted and renamed in the at the bottom of the report workspace.
Renamed data tables will be reflected in the data story, when selecting Dimensions and Measures. This provides a better overview for selecting correct values. The individual layout can only contain dimension and measures from the same data table, but when adding multiple layouts to your data story, data from different data tables can be used.

 

 

With this release we've updated how filters are applied in the new reporting module. Filters and filter locations have been optimised to provide a better overview, allow the addition of more than one filter at a time, and are easier to use.

Click here to expand...

Other improvements are described here, and shown in the screenshots below. 

Filter grouping and behaviour

We've grouped the 'Add filter' and the 'Active filters' tabs into a new tab called 'Filters'. Once filters have been added and/or changed, an Apply Filters button will appear. Any changes will only be observeable after clicking the button, making it easier to make all desired changes needed for the report without providing un-necessary results and reducing load time in the reporting module.

Period filters

With this release the period filter have been completely redesigned to allow much greater flexibility. 

It is possible to select the type of period that should be used in the filter, such as 'calendar year', 'fiscal year', as well as a custom period. The period can also be either a specific range, which will not change, or an automatic range which will be updated, e.g. last year, last month etc.

Advanced filtering

The filters now also support an advanced mode, where it is possible to select the boolean operators AND, OR between each of the filters. This mode is by default off, but can be enabled by the appropriate link 'Enable advanced filters'

With advanced filter turned on, it is possible to create new types of filter queries. The filters should be read from the top and down to read how the AND and OR is used. The AND operator take precedence over the OR operator, e.g. X AND Y OR Z, reads as filter X and Y must be true, or Z must be true. Currently it is not possible to define groups in the filters. 

Any saved filters won't be affected by these updates

 

 

 

To provide even better flexibility in creating your data stories, it is now possible to add layouts and text to your data story where needed.

7. Pure Portal

The Portal team continuously monitor and review how discoverable Pure Portals are in search engines and make regular adjustments accordingly. In this release, we have focused on addressing large image file sizes - one of the biggest contributors to occasional poor page speed, which in turn can contribute to lower search engine ranking. 

For profile search results on desktop, this results in a 70% improvement on average page speed on Profile search results pages. For mobile, the improvement is over 400%.

We have made major changes to how the portal processes content updates, adding a priority queue for the most important changes. This should speed up the time it takes for you to see changes you make in Pure reflected in the Portal.

We've made some changes to the layout of the Pure Portal pages for two content types - "equipment" and "projects". These changes are primarily aimed at to improve the display of content related to these outputs, giving a cleaner, more user-friendly experience.

Click here for more details...

More than just providing a suboptimal user experience, the previous design meant that in cases where a large amount of content was related to a piece of equipment or a project, the display could look quite strange indeed, as in this example:
The new design is modeled on other pre-existing page types, such as department and profile pages, which already use a tabbed view and fuller content renderings to more effectively showcase the related content.
As on department and profile page pages, related content for equipment and projects is shown below the main output information, following the order of precedence which you have chosen for the Portal in the back-end of Pure, in the Portal "Configurations" section. The tabs will be displayed in this order also, from left to right.

 

 

We are constantly looking at how we can improve the accuracy of our research fingerprints, and better asist our clients in showcasing their institution's research assets. This improvement delivers on both these goals. 

On Persons, fingerprints are created based on signals from three separate sources:

• Research interest statement
• Prizes
• Research outputs

We are now expanding this output relation-based signalling to equipment content. We hope this will help you to better promote your equipment both internally and externally, while also helping to show the value of assets, to add to your research and reputation. We also hope that by including the related outputs as signals, we can add value to and incentivise maintaining these connections between your research and your research equipment. 

It has long been possible in Pure to make edits to a person's fingerprints. This functionality has now been extended to apply also on a research output level, giving you the option to remove individual concepts.

Click here for more details...

Specific fingerprints and thesuri can be removed or disabled. Below are descriptions and screenshots of how this is acheieved.

The fingerprint concepts applied to each research output by Elsevier's Fingerprint Engine (FPE) can be viewed by opening the output in Pure, and selecting "Fingerprints" from the left-hand menu.
Fingerprints are displayed separately for each thesaurus which has been applied. The FPE processes each output record and automatically applies fingerprints for the best-fitting thesauri. In the screenshot, you can see the fingerprint applied for an output based on our "Medicine & Life Sciences" thesaurus. As with any technology rooted in machine-reading, errors in detection can occur, usually due to either a limited data sample or a misunderstanding of the text by the algorithm. Moreover, some terms may be undesirable in some contexts, for example due to being too broad. In such cases, individual concepts can be removed from the fingerprint. To do this, simply hover over the concept you want to remove, and click on the red cross that appears. This will remove the concept from the research ouput, so it will no longer display on the Portal. It will also remove this concept tag from the search index, so this concept will no longer be found by searches on this term. The concept is not, however, gone forever. It is possible to see omitted concepts in a section below the included concepts. From here they can also be re-added if necessary.
In addition to making changes at a concept level, it is also possible to exclude entire thesauri. To the right of each automatically detected and applied thesaurus, is a togle. To exclude this thesaurus entirely for this research output, slide the toggle to "Off". This can also always be undone at a later date.

 

 

Pure has been updated to use the latest version of Elsevier's Fingerprint Engine, adding almost 60,000 new research concepts. The Fingerprint Engine mines the text of scientific documents – publication abstracts, funding announcements and awards, project summaries, patents, proposals/applications, and other sources – to create an index of weighted terms which defines the text, known as a Fingerprint visualization. These fingerprints are used to uniquely map content in the Pure Portal, Custom Portals and can also be accessed via the web services.

In the Pure editor for organisations, there has long been a field for an alternative "web name". Similar to the "Short name" and "Sort name" fields, the idea behind this field is that you can add an alternative name to be used on the Portal from the default name used within Pure. This could be useful if, for example, organsiation names are brought in from an external HR system and not editable in Pure.

Until now, however, this field was not enabled in the Pure Portal, and was onlyy used in older generation Custom Portals. This functionality has now been fully migrated into the Pure Portal.  

If a text string if entered in the "web name" field, this will take precedence over the "Organisational unit name" and be used in place of it for the Portal in all instances. It is also added to the search index.

With this release, we added a Portals integration for the Hotjar analytics suite. Hotjar facilitates a range of usage tracking and user engagement activities, and has both free and affordable premium plans. For more info on getting started with Hotjar, get in touch with us via our Support Team!

8. Country-specific features

In this release we have made a number of updates to the REF module, as always you can read more about the REF functionality in Pure on the REF module documentation page.