Difference between revisions of "Template:July2024Upgrade"
Mark Bridger (talk | contribs) (→August 1st 2024 ( 202407.02)) |
Ann Vincent (talk | contribs) m (→October 30th 2024 (202410.03)) |
||
(58 intermediate revisions by 2 users not shown) | |||
Line 22: | Line 22: | ||
===Major Updates=== | ===Major Updates=== | ||
+ | ====Upcoming Change to Object Email/Email Anything Feature==== | ||
+ | On October 24th at 10:00 PM (local server time), we will be transitioning the email services for the '''Object Email (Email Anything)''' feature from the <code>@smartsimple.com</code> domain to the <code>@smartsimplecloud.com</code> domain. | ||
+ | |||
+ | This change will impact all users of this feature, regardless of your upgrade schedule including clients on dedicated servers and managed dedicated servers. | ||
+ | |||
+ | [[File:object-email-2024.png|thumb|none|800px|The domain for object emails will change on October 24, 2024. Object emails sent to the old domain will not be delivered unless they are updated to the new domain, smartsimplecloud.com.]] | ||
+ | |||
+ | The '''Object Email/Email Anything''' feature allows users to forward emails to a unique address associated with a specific record. This email address is typically found at the Level 1 record, and the forwarded emails are stored as Level 2 records, accessible from the Level 1 record. | ||
+ | |||
+ | After the domain transition, any emails sent to the old <code>@smartsimple.com</code> domain will no longer be delivered (you may receive a bounce back email saying 550 Invalid recipient). For instance, if someone replies to an email thread containing the old domain, the reply will not be received. Moving forward, please ensure all emails are sent to the new <code>@smartsimplecloud.com</code> domain, and existing object email threads are updated accordingly. | ||
+ | |||
+ | The variable <code>@objemail@</code> within the system will automatically be updated to the new domain for people beginning new email threads. | ||
+ | |||
+ | We recommend informing your colleagues and any external users to avoid disruptions in service. | ||
+ | |||
+ | <!-- 166360 - Object Email Domain Change --> | ||
+ | |||
====Improved Annotation Mode Experience==== | ====Improved Annotation Mode Experience==== | ||
<!-- 144147 - Annotation mode improved UI and UX --> | <!-- 144147 - Annotation mode improved UI and UX --> | ||
Line 46: | Line 63: | ||
To learn more, read [[Field Revision Annotations|the revised wiki article on '''Annotation Mode''']]. | To learn more, read [[Field Revision Annotations|the revised wiki article on '''Annotation Mode''']]. | ||
− | ====New AI | + | ====New AI Assisted Search Tool for List Views==== |
<!-- 159915 - AI Search / Natural Language Processing search --> | <!-- 159915 - AI Search / Natural Language Processing search --> | ||
− | We’ve introduced a new search option where users can enter plain text and have the AI generate filter criteria for list views. The AI | + | We’ve introduced a new search option where users can enter plain text and have the AI generate filter criteria for list views. The '''AI Assisted Search''' allows for fuzzy searches, meaning it can return results even if you've misspelled a user's name or another term. To use this feature, click on the "Enable AI Assisted Search" button (robot icon) and type the desired criteria using natural language to filter the results. For example, you could type "Search for all records with the status 'Draft'." |
− | <u>'''Note:'''</u> | + | <u>'''Note:'''</u> Only data in the list view will be searched. You may opt to control the visibility of the '''Enable AI Assisted Search''' toggle by going to '''Global Settings''' > '''+AI''' Tab. |
[[File:2024-07-ticket-159915-1.png|thumb|none|800px|Activate the new Natural Language Processing (NLP) NLP search filter option by clicking the <strong>Enable AI Assisted Search</strong> icon, represented by a robot head, located in the search input of the list view. This action enables NLP mode.]] | [[File:2024-07-ticket-159915-1.png|thumb|none|800px|Activate the new Natural Language Processing (NLP) NLP search filter option by clicking the <strong>Enable AI Assisted Search</strong> icon, represented by a robot head, located in the search input of the list view. This action enables NLP mode.]] | ||
[[File:2024-07-ticket-159915-2.png|thumb|none|800px|After enabling the Natural Language Processing (NLP) search mode, enter your desired criteria and initiate the search. To disable NLP mode, click the <strong>Disable AI Assisted Search</strong> icon (represented by a robot head) in the search input of the list view.]] | [[File:2024-07-ticket-159915-2.png|thumb|none|800px|After enabling the Natural Language Processing (NLP) search mode, enter your desired criteria and initiate the search. To disable NLP mode, click the <strong>Disable AI Assisted Search</strong> icon (represented by a robot head) in the search input of the list view.]] | ||
− | |||
====Stronger Security Configuration of Web Servers==== | ====Stronger Security Configuration of Web Servers==== | ||
<!-- 162685 - increase the strength of web server CSP --> | <!-- 162685 - increase the strength of web server CSP --> | ||
Updated the Content Security Policy of web servers with a stronger configuration for improved security. One change included in this is that the platform will now begin blocking attempts to include executables such as script libraries sourced directly from external systems. The perceived behavior of this may be an inability of a user's web browser to load or run script content that is being imported directly from an external source. An example error message thrown by a web browser may make reference to the server's Content-Security-Policy which has blocked the loading of a resource. If you encounter any issues due to this change, SmartSimple may be able to make custom but temporary adjustments to your local SmartSimple environment to again allow the inclusion of the affected external resources. A permanent solution to this issue would be to avoid the inclusion of external resources into your SmartSimple system, but instead to store a copy locally within your system and reference the local copy of the resource. | Updated the Content Security Policy of web servers with a stronger configuration for improved security. One change included in this is that the platform will now begin blocking attempts to include executables such as script libraries sourced directly from external systems. The perceived behavior of this may be an inability of a user's web browser to load or run script content that is being imported directly from an external source. An example error message thrown by a web browser may make reference to the server's Content-Security-Policy which has blocked the loading of a resource. If you encounter any issues due to this change, SmartSimple may be able to make custom but temporary adjustments to your local SmartSimple environment to again allow the inclusion of the affected external resources. A permanent solution to this issue would be to avoid the inclusion of external resources into your SmartSimple system, but instead to store a copy locally within your system and reference the local copy of the resource. | ||
[[File:refused-to-load-script.png|thumb|none|800px|An example of a blocked script displayed in Google Chrome's Developer Tools (accessible via the F12 key).]] | [[File:refused-to-load-script.png|thumb|none|800px|An example of a blocked script displayed in Google Chrome's Developer Tools (accessible via the F12 key).]] | ||
+ | |||
===Minor Updates=== | ===Minor Updates=== | ||
====From Address in Group Email Now a Dropdown==== | ====From Address in Group Email Now a Dropdown==== | ||
Line 148: | Line 165: | ||
We've made it easy to change the submit button label on organization or user sign-up pages to something more specific like “Submit Registration”. Simply navigate to the desired sign-up page under '''Global Settings''' > '''Organization''' or '''User''' tab, and enter your desired value in the '''Submit Button Label''' input field. Remember to define translations for all supported user languages. | We've made it easy to change the submit button label on organization or user sign-up pages to something more specific like “Submit Registration”. Simply navigate to the desired sign-up page under '''Global Settings''' > '''Organization''' or '''User''' tab, and enter your desired value in the '''Submit Button Label''' input field. Remember to define translations for all supported user languages. | ||
==Notes for Admins== | ==Notes for Admins== | ||
− | ==== | + | ====Enhanced SMTP Relay Integration with OAuth 2.0 Authentication==== |
<!-- 144982 - OAuth2 for SMTP relay --> | <!-- 144982 - OAuth2 for SMTP relay --> | ||
Added support for OAUTH 2.0 authentication within the SMTP Relay integration functionality. This will allow you to now configure this alternative authentication method instead of the basic authentication that was previously the only option available. To do this, go to '''Global Settings''' > '''Integrations''' tab > '''Integration Key Management''' > Click the plus icon to create a new Integration Key. In the '''Type''' dropdown, you will see two new options under the keystore category: "Basic Authentication" that represents the previously existing method for SMTP relay and the new "OAuth 2.0". | Added support for OAUTH 2.0 authentication within the SMTP Relay integration functionality. This will allow you to now configure this alternative authentication method instead of the basic authentication that was previously the only option available. To do this, go to '''Global Settings''' > '''Integrations''' tab > '''Integration Key Management''' > Click the plus icon to create a new Integration Key. In the '''Type''' dropdown, you will see two new options under the keystore category: "Basic Authentication" that represents the previously existing method for SMTP relay and the new "OAuth 2.0". | ||
+ | |||
+ | ====SMTP Relay Settings Moved to Integration Key Configuration==== | ||
The settings for existing configurations of SMTP Relay have been updated and moved. Where previously the authorization credentials were stored in the block of SMTP Relay settings in the '''Global Settings''' > '''Communications''' tab, these have now been moved into the Integration Keys configuration area to better separate the management of credential secrets versus the integration behavior. After this update, you can find your authentication credentials located in the Integration Keys area as a keystore, and in the '''Global Settings''' > '''Communications''' tab. You simply need to select the appropriate keystore and authentication mechanism to easily manage this integration. | The settings for existing configurations of SMTP Relay have been updated and moved. Where previously the authorization credentials were stored in the block of SMTP Relay settings in the '''Global Settings''' > '''Communications''' tab, these have now been moved into the Integration Keys configuration area to better separate the management of credential secrets versus the integration behavior. After this update, you can find your authentication credentials located in the Integration Keys area as a keystore, and in the '''Global Settings''' > '''Communications''' tab. You simply need to select the appropriate keystore and authentication mechanism to easily manage this integration. | ||
Line 193: | Line 212: | ||
Clients may now manage the inclusion of archived records in SmartConnect API calls. Use the parameter <code>{"includearchive":0}</code> to exclude archived records and improve performance. By default, archived records are included in API calls. | Clients may now manage the inclusion of archived records in SmartConnect API calls. Use the parameter <code>{"includearchive":0}</code> to exclude archived records and improve performance. By default, archived records are included in API calls. | ||
When using the update function via the SmartConnect API, the values sent will now be validated based on the field type. For example: | When using the update function via the SmartConnect API, the values sent will now be validated based on the field type. For example: | ||
− | |||
* Numeric value for a '''Text Box - Number''' field | * Numeric value for a '''Text Box - Number''' field | ||
* '''YYYY-MM-DD''' format value for a '''Text Box - Date''' field | * '''YYYY-MM-DD''' format value for a '''Text Box - Date''' field | ||
Line 203: | Line 221: | ||
==Service Packs== | ==Service Packs== | ||
− | ====August 8th 2024 ( 202407.03)==== | + | ====October 31st 2024 (202410.03)==== |
+ | * Fixed an issue affecting report properties triggered by a P3 script that failed to return data. | ||
+ | <!-- 166914 - Shopping Cart donation orders NOT showing in the cart (happening on most client sites) --> | ||
+ | |||
+ | ====October 24th 2024 (202410.02)==== | ||
+ | '''Upcoming Change to Object Email/Email Anything Feature''' | ||
+ | |||
+ | On October 24th at 10:00 PM (local server time), we will be transitioning the email services for the Object Email (Email Anything) feature to the <code>@smartsimplecloud.com</code> domain. After the domain transition, any emails sent to the old <code>@smartsimple.com</code> domain will no longer be delivered. We recommend informing your colleagues and any external users to avoid disruptions in service. | ||
+ | |||
+ | This change will impact all users of this feature, regardless of your upgrade schedule including clients on dedicated servers and managed dedicated servers. | ||
+ | |||
+ | See the following link for more information: [[#Upcoming_Change_to_Object_Email.2FEmail_Anything_Feature| Upcoming Change to Object Emails]]. | ||
+ | |||
+ | '''Other Changes''' | ||
+ | |||
+ | * Fixed an issue with submission on the payment scheduler tool. | ||
+ | |||
+ | <!-- 166503 - Payment Scheduler throwing an error --> | ||
+ | ====October 10th 2024 (202410.01)==== | ||
+ | * Fixed an issue where shortcuts to portal list views with a record limit were not displaying all records as expected. | ||
+ | <!-- 162637 - Shortcut to LV section doesn't honor the record limit setting--> | ||
+ | |||
+ | * Fixed an issue with '''Impact Maps''' affecting auto zoom, aggregate panel, and location markers. After the upgrade, click the button labelled '''Generate HTML and JSON files''' to apply the fix. '''Impact Maps''' can be found by navigating to the desired UTA > '''Configuration Settings''' > Level 1 or 2 tab > '''Impact Maps'''. | ||
+ | |||
+ | <!-- 165973 - Resolving addresses message when using impact map with auto zoom on --> | ||
+ | * Fixed an issue where expired files appeared as File Export dropdown options when exporting reports. | ||
+ | |||
+ | <!-- 165021 - SmartFolder File Expiry --> | ||
+ | * Fixed an issue with the '''SmartConnect API''' that affected listing and updating associations for Level 3 contacts or companies. | ||
+ | |||
+ | <!-- 165299 - L3 Associations and API --> | ||
+ | * Fixed an issue with '''Advanced Data Table''' custom fields where column totals appeared editable instead of read-only. | ||
+ | |||
+ | <!-- 165698 - Advanced Data Table Has Total Formatting --> | ||
+ | * Fixed an issue where line breaks were being retained in the header of report exports and affecting the styling of column headers in some scenarios. | ||
+ | |||
+ | <!-- 165539 - Glitch with Requests History Fields Formatting --> | ||
+ | * Fixed an issue where you could not update a '''Text Box - Number''' custom field to the value of zero if there were also zeroes after a decimal point using an API call. | ||
+ | |||
+ | <!-- 165828 - Diverse Scholars Application- Budget Tool --> | ||
+ | * Fixed an issue where captions were missing a colon when the corresponding input was read-only. | ||
+ | |||
+ | <!-- 165945 - Missing colons? --> | ||
+ | * Fixed an issue where table rows and columns were not rendering properly from MS Word Merge custom fields. | ||
+ | |||
+ | <!-- 166013 - Letter Merge/Template Not Pulling in Data --> | ||
+ | * Fixed an issue where some captions were not receiving the font weight of bold. | ||
+ | |||
+ | <!-- 166074 - WPV fields need bold captions --> | ||
+ | * Fixed an issue with Multi-Factor Authentication (MFA) affecting the session timeout process. | ||
+ | |||
+ | <!-- 166152 - 2 Factor Authentication bypass without entering code after session timeout --> | ||
+ | * Updated Azure AI integration settings to indicate that a subscription account is required and that trial accounts are not supported. | ||
+ | |||
+ | <!-- 165342 - Azure AI --> | ||
+ | * Updated Medical Subject Headings (MeSH) to 2024 version in relation to PubMed. | ||
+ | |||
+ | <!-- 165507 - please, update mesh tree to 2024 version --> | ||
+ | * Added support for a new "onlyFullname" search parameter for the LexisNexis integration when trying to run a watch list check using [[SsGet|ssGet variable syntax]]. Additonally fixed an issue with the LexisNexis integration where running a watch list check did not return all results. | ||
+ | |||
+ | <!-- 161530 - Issue with our Lexis Nexis watch list results --> | ||
+ | * Updated the field history log to include updates from the payment allocation process. | ||
+ | |||
+ | <!-- 161048 - History - Total Grants Paid not Working --> | ||
+ | * Updated the display of checkboxes and radio buttons in PDFs for improved contrast. | ||
+ | |||
+ | <!-- 162665 - Accessibility of options in PDFs --> | ||
+ | * Updated API to return a notification if a file uploaded through the API was removed due to a potential virus detection. | ||
+ | |||
+ | <!-- 163545 - Extend virus scanning to API uploaded files --> | ||
+ | ====September 19th 2024 (202409.02)==== | ||
+ | * Fixed an issue where transactions were not rendering on open. | ||
+ | <!-- 165521 - Due Diligence screen not showing --> | ||
+ | |||
+ | * Enhanced the autoloaders to handle larger files by optimizing the process to efficiently manage CSV files without overloading memory. | ||
+ | |||
+ | <!-- 165116 - HR FEED SFTP Autoloader Interrupted --> | ||
+ | ====September 12th 2024 (202409.01)==== | ||
+ | * Fixed an issue with '''Impact Maps''' using KML files where search was not working as expected. Maps must be regenerated for the fix to be applied. | ||
+ | |||
+ | <!-- 164407 - Impact Maps --> | ||
+ | * Fixed an issue where tooltips were not appearing as expected on iPhones and iPads. | ||
+ | |||
+ | <!-- 160091 - Tooltip flashes on tablet/phone with touch screen --> | ||
+ | * Fixed an issue with generated PDFs using the web page view custom fields to preserve line breaks for enhanced readability. | ||
+ | |||
+ | <!-- 160918 - Improve formatting of PDF in Reviewer Development Scheme task --> | ||
+ | * Fixed an issue where fields updated by the field formula from an '''Advanced Data Table''' became editable. | ||
+ | |||
+ | <!-- 162750 - Continuation of 157537 - xml Field Formula is unlocking the field on the page --> | ||
+ | * Fixed an issue where some field captions for "Display - Text" and "Display - Text and Variables" custom fields were wrapped in a label tag when there was no corresponding input. | ||
+ | |||
+ | <!-- 163134 - The label element is blank --> | ||
+ | * Fixed an issue where clicking on the logo (as a logged in user) closed all open tabs in the '''Tab Bar'''. | ||
+ | |||
+ | <!-- 163518 - YorkU | Home button closes all tabs for users --> | ||
+ | * Fixed an issue where CSS files stored in a web-enabled configuration folder were not accessible. | ||
+ | |||
+ | <!-- 163573 - CSS file stored in configuration folder is not accessible by refencing the file path in HTML Link tag --> | ||
+ | * Fixed a validation issue for "Upload – Multiple Files Storage" custom fields when the '''Media Library''' is enabled and minimum number of files is set to 1. | ||
+ | |||
+ | <!-- 164102 - Media Files and Virus Scan Feature Questions --> | ||
+ | * Fixed an issue where archived records were appearing in provider/consumer list views. | ||
+ | |||
+ | <!-- 162768 - Consumer list view showing archived applications --> | ||
+ | * Fixed an issue with the display of the '''Annotation Mode''' panel when the '''Zoom Web Conference''' integration was enabled. | ||
+ | |||
+ | <!-- 164335 - New Annotation option does not appear to work with Zoom integration --> | ||
+ | * Updated the behavior of resolved items in '''Annotation Mode''' so that if a user replies to a resolved annotation thread, the status of the annotation changes from "Resolved" to "Active". | ||
+ | |||
+ | <!-- 164759 - New Annotation mode - User can reply on a Resolved annotation, but annotation status does not change --> | ||
+ | * Updated the default GPT model from GPT4 to GPT-4o. | ||
+ | |||
+ | <!-- 161742 - Change default model to GPT-4o --> | ||
+ | * Updated the system to allow support staff and administrators to login via the '''Authenticated Servers''' link even after the maximum number of concurrent user logins has been reached. | ||
+ | |||
+ | <!-- 161313 - Allow PAC authentication to bypass concurrent user limits --> | ||
+ | * Updated the name of the "UK Charity Commission" option verification service found on organization signup pages. The option was renamed "Charity Commission for England and Wales" for accuracy. The ability to sort results on signup pages using verification services was also added. | ||
+ | |||
+ | <!-- 162231 - Relabel UK Charity Commission option --> | ||
+ | * Updated the name of the "Disable Recent / Action Bar" setting to be "Hide Recently Visited and Back Buttons" for clarity. This setting is located at '''Menu Icon''' > '''Global Settings''' > '''Security''' tab > '''System Feature Permissions''' > '''Features''' tab. | ||
+ | |||
+ | <!-- 151759 - Change name of setting used to hide recent and back buttons for clarity --> | ||
+ | * Updated tables with the role of "presentation" to improve the experience on screen readers. | ||
+ | |||
+ | <!-- 163922 - Role presentation on table --> | ||
+ | * Updated email notifications to send an email a day if there are emails in the on-hold queue. | ||
+ | |||
+ | <!-- 164061 - Emails in on hold queue without email notification --> | ||
+ | * Updated the "Text Box - Text Multiple Lines" custom fields to preserve line breaks when values are being copied from one field to another for enhanced readability. | ||
+ | |||
+ | <!-- 164436 - Multiline field value reference converting linebreak into br html tag --> | ||
+ | * Updated the behavior of the database query optimizer to improve performance within certain areas of the system such as retrieving list view results. | ||
+ | |||
+ | <!-- 165035 - update MariaDB optimizer_switch configuration setting --> | ||
+ | * Updated the notification check interval from 2 minutes to 5 minutes to enhance system performance. | ||
+ | |||
+ | <!-- 164589 - System running Slow and Timing out --> | ||
+ | * Updated the Albanian language code to be "sq" in accordance with W3C and ISO standards. | ||
+ | |||
+ | <!-- 152703 - Albanian language code --> | ||
+ | * Updated various areas of the system in accordance with most recent vulnerability report. | ||
+ | |||
+ | <!-- 163286 - BreachLock Web Application penetration test vulnerabilities (2024-07-02) - Low --> | ||
+ | ====August 23rd 2024 (202407.04)==== | ||
+ | * Fixed an issue where web page views containing linked record lists were not displaying correctly when the web page view was set to generate a PDF directly from the workflow. | ||
+ | <!-- 164747 - ORCID - Error impacting live review process --> | ||
+ | |||
+ | * Fixed an issue where filters incorrectly displayed excluded statuses by fixing the NOT condition in the search functionality for '''Status''' or '''Type''' in Level 1 and Level 2 list views. | ||
+ | |||
+ | <!-- 164452 - Our ResAs see all their projects/report quality check --> | ||
+ | * Fixed an issue where dropdown fields using dynamic content incorrectly triggered a "cannot be empty" validation error despite being populated. | ||
+ | |||
+ | <!-- 164417 - Campaign Year Issue --> | ||
+ | ====August 8th 2024 (202407.03)==== | ||
<!-- 164171 - Annotation mode changes for global release --> | <!-- 164171 - Annotation mode changes for global release --> | ||
* Updated the behavior of the '''Annotation Mode''' permissions. Users with roles that have '''Edit Field''' permission will be able to edit the value of fields with existing annotations without needing '''View and Create''' permissions as long as the user has a role with '''View''' permission. This means existing permissions for annotations will no longer need to be modified as part of the July upgrade. Tooltips clarifying annotation permissions were also added. To see these changes, go to UTA '''Configuration Settings''' > '''Level 1''', '''2''', '''3''' tab > '''Statuses''' > Select the desired status > '''Permissions and Availability''' tab > See the settings under the “Annotation System Role Permissions” section. | * Updated the behavior of the '''Annotation Mode''' permissions. Users with roles that have '''Edit Field''' permission will be able to edit the value of fields with existing annotations without needing '''View and Create''' permissions as long as the user has a role with '''View''' permission. This means existing permissions for annotations will no longer need to be modified as part of the July upgrade. Tooltips clarifying annotation permissions were also added. To see these changes, go to UTA '''Configuration Settings''' > '''Level 1''', '''2''', '''3''' tab > '''Statuses''' > Select the desired status > '''Permissions and Availability''' tab > See the settings under the “Annotation System Role Permissions” section. | ||
Line 209: | Line 381: | ||
* Fixed an issue with the advanced search where leading or trailing semicolons in the options were preventing proper display. | * Fixed an issue with the advanced search where leading or trailing semicolons in the options were preventing proper display. | ||
− | ====August 1st 2024 ( 202407.02)==== | + | ====August 1st 2024 (202407.02)==== |
<!-- 163412 - Google marker clusterer depricated on Impact Map --> | <!-- 163412 - Google marker clusterer depricated on Impact Map --> | ||
* Due to Google Maps deprecating support for older versions, we have updated the '''Impact Maps''' to use new versions of the marker clusters. To ensure your '''Impact Maps''' function correctly, you must manually generate the HTML and JSON files after the upgrade is applied. To do this navigate to the desired UTA > '''Configuration Settings''' > '''Level 1''', '''2''', or '''3''' tab > '''Impact Maps''' > Edit the desired map > Click "Generate HTML and JSON files" to recompile the map. | * Due to Google Maps deprecating support for older versions, we have updated the '''Impact Maps''' to use new versions of the marker clusters. To ensure your '''Impact Maps''' function correctly, you must manually generate the HTML and JSON files after the upgrade is applied. To do this navigate to the desired UTA > '''Configuration Settings''' > '''Level 1''', '''2''', or '''3''' tab > '''Impact Maps''' > Edit the desired map > Click "Generate HTML and JSON files" to recompile the map. | ||
<!-- 162710 - Layout - Title Bar --> | <!-- 162710 - Layout - Title Bar --> | ||
− | * Fixed an issue with the | + | * Fixed an issue with the "Layout - Title Bar" custom field where records did not display correctly in 2 columns under some scenarios. Title bar custom fields set to 2 columns will now correctly render in 2 columns as intended regardless of the caption location. If you wish to display a record in single column, make sure the number of columns is set to 1. |
Latest revision as of 14:23, 30 October 2024
Contents
- 1 Overview
- 2 Upgrade Highlights
- 3 Global System Upgrades
- 4 On-Demand System Upgrades
- 5 Notes for Admins
- 5.1 Enhanced SMTP Relay Integration with OAuth 2.0 Authentication
- 5.2 SMTP Relay Settings Moved to Integration Key Configuration
- 5.3 Advanced Search and Filters Using Status and Type Criteria
- 5.4 Enhanced Filter List View
- 5.5 SmartCheck Validation List View Enhancements
- 5.6 Improved System Design Summary
- 5.7 Adobe Acrobat Sign migration
- 5.8 Signority Updates
- 5.9 Updated Stripe Integration
- 5.10 Added Ability to Report on Subject Line Data for Notes
- 5.11 New Reauthorization Option for Adobe Sign and DocuSign
- 5.12 Updated Work with +AI Feature
- 5.13 Updated SmartConnect API
- 6 Service Packs
Overview
Watch this video to get a general overview of the new features in this release.
To watch this video in full screen, please click on the full screen button on the bottom right.
Upgrade Highlights
- The new Privacy and Security Policies feature improves configuration efficiency, enhances user experience, facilitates tailored policy creation, and strengthens compliance management to foster greater user trust.
- The Annotations feature has been refined with a new interface, improved process flow, and the ability to mark annotations as resolved, creating a better and more intuitive collaboration experience.
- The new option for AI-powered Natural Language Processing Search lets users enter plain text to generate filter criteria for list views, making it easier to find what you need naturally.
- The new Activity Scheduler feature streamlines bulk creation and scheduling of Level 2 activities with customizable recurrence rules, offering simplified and timely activity management.
- The new Follow Organization feature for following organizations automates notifications to alert users about new opportunities, enhancing user engagement.
- The +AI Insights feature enables users to upload and manage training files for effortless AI model creation.
- To prevent email spoofing, the "From" address in the group email feature is now only selectable from a dropdown menu.
- We've incorporated the capability to display notes within the "Special – Linked Record List" custom field, enhancing user interaction and workflow efficiency.
- The new PDF Text Export feature allows extraction of text from PDF files into a multiline text custom field, facilitating integration with +AI functionalities for tasks like translation and summarization.
Global System Upgrades
The new features listed below are enhancements to the SmartSimple system and will be immediately available to SmartSimple users upon the application of the upgrade to their server:
Major Updates
Upcoming Change to Object Email/Email Anything Feature
On October 24th at 10:00 PM (local server time), we will be transitioning the email services for the Object Email (Email Anything) feature from the @smartsimple.com
domain to the @smartsimplecloud.com
domain.
This change will impact all users of this feature, regardless of your upgrade schedule including clients on dedicated servers and managed dedicated servers.
The Object Email/Email Anything feature allows users to forward emails to a unique address associated with a specific record. This email address is typically found at the Level 1 record, and the forwarded emails are stored as Level 2 records, accessible from the Level 1 record.
After the domain transition, any emails sent to the old @smartsimple.com
domain will no longer be delivered (you may receive a bounce back email saying 550 Invalid recipient). For instance, if someone replies to an email thread containing the old domain, the reply will not be received. Moving forward, please ensure all emails are sent to the new @smartsimplecloud.com
domain, and existing object email threads are updated accordingly.
The variable @objemail@
within the system will automatically be updated to the new domain for people beginning new email threads.
We recommend informing your colleagues and any external users to avoid disruptions in service.
Improved Annotation Mode Experience
Annotations serve as a collaborative tool allowing users to add notes and responses directly to specific fields within a record. With field-level annotations, users can modify individual fields and respond to comments without affecting the rest of the record. In this upgrade, we refined the interface by hiding the left navigation panel and implementing color-coded messages:
- Blue indicates comments made by you.
- Yellow indicates comments made by others.
- Green denotes resolved annotation sets.
Note: In the July upgrade, users needed to be assigned to the View and Create role permission to reply to or edit the field value of an annotation. This requirement will be reverted in the August 8th service pack so no changes to the configuration of permissions will be required.
Additionally, when the Open in Annotation Mode setting is enabled, users will now directly enter annotation mode when changing to the defined status. The comment field is now mandatory when a user edits a field value.
Users can easily view the list of annotations in the right column, facilitating navigation to specific annotation fields and drilling into the collaboration conversation. Reply and edit functionalities for unlocked fields are conveniently accessible through a modal window.
Users also have the ability to mark an annotation set as resolved. To set this permission, go to UTA Configuration Settings > Level 1 tab > Statuses > Select the relevant status > Permissions & Availability tab > Enter roles in the Mark as Resolved field.
To learn more, read the revised wiki article on Annotation Mode.
New AI Assisted Search Tool for List Views
We’ve introduced a new search option where users can enter plain text and have the AI generate filter criteria for list views. The AI Assisted Search allows for fuzzy searches, meaning it can return results even if you've misspelled a user's name or another term. To use this feature, click on the "Enable AI Assisted Search" button (robot icon) and type the desired criteria using natural language to filter the results. For example, you could type "Search for all records with the status 'Draft'." Note: Only data in the list view will be searched. You may opt to control the visibility of the Enable AI Assisted Search toggle by going to Global Settings > +AI Tab.
Stronger Security Configuration of Web Servers
Updated the Content Security Policy of web servers with a stronger configuration for improved security. One change included in this is that the platform will now begin blocking attempts to include executables such as script libraries sourced directly from external systems. The perceived behavior of this may be an inability of a user's web browser to load or run script content that is being imported directly from an external source. An example error message thrown by a web browser may make reference to the server's Content-Security-Policy which has blocked the loading of a resource. If you encounter any issues due to this change, SmartSimple may be able to make custom but temporary adjustments to your local SmartSimple environment to again allow the inclusion of the affected external resources. A permanent solution to this issue would be to avoid the inclusion of external resources into your SmartSimple system, but instead to store a copy locally within your system and reference the local copy of the resource.
Minor Updates
From Address in Group Email Now a Dropdown
To prevent email spoofing, the From Address field in the group email feature is now a dropdown menu and is no longer accepting free-form text input. Users can select the default From Address if configured, or choose their own email address. If no default email address is set, "donotreply@smartsimplemailer.com" will be available as an option. Users can add additional email addresses to the From Address dropdown by navigating to User Menu > Personal Settings > Enter additional email addresses into the Email From Address field. If you are using an SMTP relay, any additional email addresses must use a domain accepted by your mail server or use a domain such as @smartsimplemailer.com. Otherwise, the email may be blocked or sent to spam.
Asynchronous Loading of List Views
We've updated the loading of list views to be asynchronous, allowing you to interact with certain elements before all list data is fully loaded. Additionally, we've changed how we load shortcut list view aggregate numbers to reduce performance impacts.
Enhanced Virus Scanning
Files uploaded to your SmartSimple system are now subjected to automatic virus scanning. Files larger than 100MB are queued for scanning; you may see a message indicating the scan is in process. During this period, users cannot download or rename files being scanned, and files being scanned are not visible in list views. If a virus is detected, the file is deleted, and a notification triggered. The option to enable real-time virus scanning on custom fields has also been removed. System Administrators can navigate to Menu Icon > Global Settings > Security tab > Click the Virus Infected Files link to see a list of files that were deleted from where, when and who uploaded them.
On-Demand System Upgrades
The following features are available immediately with the application of the upgrade, but must first be enabled or configured by a Global Administrator:
Major Updates
New Privacy and Security Policies Feature
Privacy and security policies are crucial for aligning your system with regulations, mitigating risks, and fostering user trust by detailing how user privacy and data will be protected. Our latest update to this feature simplifies the configuration and enhances the user experience of this compliance checkpoint within your system. Some key features include:
- Tailored Policy Creation: Develop custom policies with distinct sections and translations to meet regulatory requirements, mitigate risks, and build user trust by clearly explaining how privacy and data will be safeguarded.
- Scope, Timing, and Audience Specification: Define the collection points, such as login pages, registration forms, or specific application processes, and outline enforcement mechanisms for each policy.
- Policy Builder: Use this new tool to create customized sections of a policy, addressing specific compliance needs. For example, a privacy policy might include sections like 'Information Collection', 'Data Processing', 'Data Sharing', etc.
- Version Management and Compliance Tracking: Manage different versions of your policies, monitor compliance, and view detailed records of user acceptance for accountability.
To activate the new Privacy and Security Policies feature, system administrators need to navigate to: Menu Icon > Global Settings > Classic Options tab > Disable the classic privacy and security policies.
Note: Existing policies will not be migrated to the new feature and must be rebuilt. Existing policy acceptance information will still be retained.
For more information, visit our wiki article on privacy and security policies.
New Feature to Follow Organizations
Have you ever wished to receive notifications when an organization you're interested in posts new opportunities? We've introduced a feature that allows users to follow organizations, enabling automated alerts for new opportunities as they become available. From the user's perspective, you can follow organizations in bulk by visiting the organization list view and selecting your desired organizations. Alternatively, you can go to a specific organization's record and click the follow button. For system administrators interested in enabling this feature, navigate to Menu Icon > Global Settings > Organization tab > Toggle on Allow users to follow organizations. Additionally, system administrators need to set up a UTA Level 1 workflow with an acknowledgment task to notify followers of organizations. Please ensure that the organization is assigned in the Level 1 Customer field.
New Feature for Creating and Scheduling Activities in Bulk
Ever needed to efficiently schedule multiple activities, such as events or shifts, in bulk? We've introduced a customizable wizard that simplifies the creation of Level 2 activities using recurrence rules.
From the user's perspective, navigate to the desired Level 1 record, access the tools dropdown, and select the appropriate Level 2 creation wizard. Alternatively, the wizard can be accessed inline as a button on the record.
Specify your criteria and set recurrence rules, then click Preview to review the bulk activities to be created. Adjust the activities inline as needed, and then click Create to finalize the creation of scheduled activities in bulk.
For System Administrators looking to activate this feature, navigate to the desired Universal Tracking Application > Configuration Settings > Level 2 tab > Click the Activity Scheduler link to configure one or more wizards.
To display a button that launches the activity scheduler on a Level 1 record, create a custom field of the type display text and variables. In the content input, enter @ssGet(ACTSCHEDULER,activity_scheduler_name)@
, replacing "activity_scheduler_name" with the name you specified for your activity scheduler.
+AI insights Training Files
With the +AI Insights feature, you can create a custom AI model tailored to your needs. Use the Training Files tab to upload and manage files that can contain data from outside your system. Upload organization or community-related documents such as call guidelines and compliance documentation, enabling users to query the model for better understanding. Additionally, upload your research and project outcomes to facilitate easy sharing and allow the AI to respond to questions about your impact. Users can access Instance and Global level models in the header of your system. System Administrators can configure a +AI Insight model by navigating to Menu Icon > Global Settings > +AI tab
Note: You will need an OpenAI license to use AI features on SmartSimple. Contact your account manager or sales@smartsimple.com for further information on billing and implementation. To learn more about all our AI features, visit the wiki at https://wiki.smartsimple.com/wiki/AI
Minor Updates
New Language Translations for System Variables
The System Variables feature allows administrators to define a value in one place and display it throughout different areas of the system. This simplifies maintenance, as an administrator can update a value in one location and the change will take effect across the entire system. With this upgrade, you can now specify language translations for system variables. Instead of creating separate variables, you can create a single variable and display different values based on the user's language. If no translation is defined, the system will display the English language value.
New Support for Notes in Linked Record List Custom Field
The "Special – Linked Record List" custom field enables you to view and add related items to a record directly within the interface, eliminating the need to navigate to other areas of the system. This feature simplifies the process of managing organizations, users, activities, and invitations. With this upgrade, you can now view and add notes using this custom field, for an improved user experience.
Added Ability to Display Additional ORCID Information on User Profiles
Systems utilizing the ORCID integration to showcase researcher information on user profiles can now display additional information in a new tab. System Administrators can select which new information to display by navigating to the user standard field named "ORCID" and toggling on the additional data they wish to show on user profiles.
If you have implemented the new feature for research clients to acknowledge reviewer contributions to peer review activities by sending participation data from review panels to ORCID profiles (available since May 2024), direct researchers to click the "Re-Import ORCID Data" button on their user profile to display these peer reviews acknowledgments.
New Feature PDF Text Export
We've introduced the capability to extract text from PDF files and store it in a multiline text custom field. Once the data is extracted into this field as plain text, it can be utilized with our +AI features for tasks such as translation, summarization, and manipulation. System Administrators can enable this feature by navigating to the desired "Upload - Multiple Files Storage" custom field, toggling on Enable PDF Text Export, and specifying the multiline text custom field under the "Value Storage" section where the extracted content should be stored.
Added Ability to Change Submit Button Label
We've made it easy to change the submit button label on organization or user sign-up pages to something more specific like “Submit Registration”. Simply navigate to the desired sign-up page under Global Settings > Organization or User tab, and enter your desired value in the Submit Button Label input field. Remember to define translations for all supported user languages.
Notes for Admins
Enhanced SMTP Relay Integration with OAuth 2.0 Authentication
Added support for OAUTH 2.0 authentication within the SMTP Relay integration functionality. This will allow you to now configure this alternative authentication method instead of the basic authentication that was previously the only option available. To do this, go to Global Settings > Integrations tab > Integration Key Management > Click the plus icon to create a new Integration Key. In the Type dropdown, you will see two new options under the keystore category: "Basic Authentication" that represents the previously existing method for SMTP relay and the new "OAuth 2.0".
SMTP Relay Settings Moved to Integration Key Configuration
The settings for existing configurations of SMTP Relay have been updated and moved. Where previously the authorization credentials were stored in the block of SMTP Relay settings in the Global Settings > Communications tab, these have now been moved into the Integration Keys configuration area to better separate the management of credential secrets versus the integration behavior. After this update, you can find your authentication credentials located in the Integration Keys area as a keystore, and in the Global Settings > Communications tab. You simply need to select the appropriate keystore and authentication mechanism to easily manage this integration.
Advanced Search and Filters Using Status and Type Criteria
The advanced search and filters for “Type” and “Status” standard fields now consider both the type/status caption in the user's language and the type/status name (language independent) when these values are used as search criteria. This ensures more accurate search results across different languages.
Enhanced Filter List View
We have enhanced the filter list view to clearly indicate which filters are designated as configuration-only and thus not visible to end users. You can now easily identify these filters without needing to open each filter. To view the new configuration only indicator column, navigate to the desired Universal Tracking Application > Configuration Settings > Level 1 tab> Click on the Search Filters link to access the updated list of filters, featuring the "Configuration Only" column.
SmartCheck Validation List View Enhancements
We've enhanced the SmartCheck Validation list view by adding columns for “Last Updated”, “Modified By”, “Attached Submit Buttons”, and “ID”. These additions allow you to search based on this information, making it easier to find and troubleshoot SmartCheck Validation.
Improved System Design Summary
We have introduced the ability to include custom fields for organizations and users within the System Design Summary. This summary can be accessed via Menu Icon > Global Settings > System tab and generates a comprehensive document outlining the current system design.
Adobe Acrobat Sign migration
The Adobe Acrobat Sign service for e-signatures will be upgraded from Adobe Acrobat Sign API version 5 to version 6. Clients currently using the service have the option to enable webhooks. To do so, you will need to grant the necessary permissions within your Adobe account and contact the support team for help with the transition.
Signority Updates
We’ve introduced the ability to use the Signority Smart Tags feature by using anchor text within the webpage view, providing more control over the position of signature elements. The e-signature configuration for Signority has also been updated. New clients using this integration must set up an integration key under Global Settings > Integrations tab > Integration Key Management. For existing clients, the integration key will be automatically transitioned. Additionally, a new option has been added to allow the use of a sandbox Signority key for testing and troubleshooting during the implementation process.
Updated Stripe Integration
The Stripe integration for payments has been updated to use the latest version of the Stripe API. You can also now enable the Stripe Connect feature, which streamlines online payment processing across all system-wide Stripe payment methods, including credit card and ACH debit. Enabling this feature removes the need to manually enter Stripe keys for each payment form. Administrators can enable the Stripe Connect feature by navigating to: Menu Icon > Global Settings > Integrations tab > Toggle on Enable Stripe Connect under the “Service Settings” section.
Added Ability to Report on Subject Line Data for Notes
Added the ability to report on the Subject Line of the Notes feature. To enable this feature, navigate to Global Settings > System tab > Toggle on Enable Subject Line for Notes.
New Reauthorization Option for Adobe Sign and DocuSign
If you use Adobe Sign or DocuSign as your e-signature provider, you now have the option to reauthorize (sign out and sign back in). This is useful if you need to change the user account used for authorization, for instance, if your current account lacks the necessary permissions. To access this new feature, navigate to the Menu icon > Global Settings > Integrations tab > Click the "Check Adobe Acrobat Sign/DocuSign Access" button.
Updated Work with +AI Feature
Updated the Work with +AI interactive interface to support markdown formatting. Responses will now properly render lists, bold text, and other formatting elements.
Updated SmartConnect API
Clients may now manage the inclusion of archived records in SmartConnect API calls. Use the parameter {"includearchive":0}
to exclude archived records and improve performance. By default, archived records are included in API calls.
When using the update function via the SmartConnect API, the values sent will now be validated based on the field type. For example:
- Numeric value for a Text Box - Number field
- YYYY-MM-DD format value for a Text Box - Date field
- YYYY-MM-DD HH:mm:ss format value for a Text Box - Date and Time
- XML format data for a Special - Advanced Data Table
- JSON format data for a Special - JSON field
If content is sent with invalid data format, it will be ignored. A new field error node will list the fields that failed validation for record creation and updates.
Service Packs
October 31st 2024 (202410.03)
- Fixed an issue affecting report properties triggered by a P3 script that failed to return data.
October 24th 2024 (202410.02)
Upcoming Change to Object Email/Email Anything Feature
On October 24th at 10:00 PM (local server time), we will be transitioning the email services for the Object Email (Email Anything) feature to the @smartsimplecloud.com
domain. After the domain transition, any emails sent to the old @smartsimple.com
domain will no longer be delivered. We recommend informing your colleagues and any external users to avoid disruptions in service.
This change will impact all users of this feature, regardless of your upgrade schedule including clients on dedicated servers and managed dedicated servers.
See the following link for more information: Upcoming Change to Object Emails.
Other Changes
- Fixed an issue with submission on the payment scheduler tool.
October 10th 2024 (202410.01)
- Fixed an issue where shortcuts to portal list views with a record limit were not displaying all records as expected.
- Fixed an issue with Impact Maps affecting auto zoom, aggregate panel, and location markers. After the upgrade, click the button labelled Generate HTML and JSON files to apply the fix. Impact Maps can be found by navigating to the desired UTA > Configuration Settings > Level 1 or 2 tab > Impact Maps.
- Fixed an issue where expired files appeared as File Export dropdown options when exporting reports.
- Fixed an issue with the SmartConnect API that affected listing and updating associations for Level 3 contacts or companies.
- Fixed an issue with Advanced Data Table custom fields where column totals appeared editable instead of read-only.
- Fixed an issue where line breaks were being retained in the header of report exports and affecting the styling of column headers in some scenarios.
- Fixed an issue where you could not update a Text Box - Number custom field to the value of zero if there were also zeroes after a decimal point using an API call.
- Fixed an issue where captions were missing a colon when the corresponding input was read-only.
- Fixed an issue where table rows and columns were not rendering properly from MS Word Merge custom fields.
- Fixed an issue where some captions were not receiving the font weight of bold.
- Fixed an issue with Multi-Factor Authentication (MFA) affecting the session timeout process.
- Updated Azure AI integration settings to indicate that a subscription account is required and that trial accounts are not supported.
- Updated Medical Subject Headings (MeSH) to 2024 version in relation to PubMed.
- Added support for a new "onlyFullname" search parameter for the LexisNexis integration when trying to run a watch list check using ssGet variable syntax. Additonally fixed an issue with the LexisNexis integration where running a watch list check did not return all results.
- Updated the field history log to include updates from the payment allocation process.
- Updated the display of checkboxes and radio buttons in PDFs for improved contrast.
- Updated API to return a notification if a file uploaded through the API was removed due to a potential virus detection.
September 19th 2024 (202409.02)
- Fixed an issue where transactions were not rendering on open.
- Enhanced the autoloaders to handle larger files by optimizing the process to efficiently manage CSV files without overloading memory.
September 12th 2024 (202409.01)
- Fixed an issue with Impact Maps using KML files where search was not working as expected. Maps must be regenerated for the fix to be applied.
- Fixed an issue where tooltips were not appearing as expected on iPhones and iPads.
- Fixed an issue with generated PDFs using the web page view custom fields to preserve line breaks for enhanced readability.
- Fixed an issue where fields updated by the field formula from an Advanced Data Table became editable.
- Fixed an issue where some field captions for "Display - Text" and "Display - Text and Variables" custom fields were wrapped in a label tag when there was no corresponding input.
- Fixed an issue where clicking on the logo (as a logged in user) closed all open tabs in the Tab Bar.
- Fixed an issue where CSS files stored in a web-enabled configuration folder were not accessible.
- Fixed a validation issue for "Upload – Multiple Files Storage" custom fields when the Media Library is enabled and minimum number of files is set to 1.
- Fixed an issue where archived records were appearing in provider/consumer list views.
- Fixed an issue with the display of the Annotation Mode panel when the Zoom Web Conference integration was enabled.
- Updated the behavior of resolved items in Annotation Mode so that if a user replies to a resolved annotation thread, the status of the annotation changes from "Resolved" to "Active".
- Updated the default GPT model from GPT4 to GPT-4o.
- Updated the system to allow support staff and administrators to login via the Authenticated Servers link even after the maximum number of concurrent user logins has been reached.
- Updated the name of the "UK Charity Commission" option verification service found on organization signup pages. The option was renamed "Charity Commission for England and Wales" for accuracy. The ability to sort results on signup pages using verification services was also added.
- Updated the name of the "Disable Recent / Action Bar" setting to be "Hide Recently Visited and Back Buttons" for clarity. This setting is located at Menu Icon > Global Settings > Security tab > System Feature Permissions > Features tab.
- Updated tables with the role of "presentation" to improve the experience on screen readers.
- Updated email notifications to send an email a day if there are emails in the on-hold queue.
- Updated the "Text Box - Text Multiple Lines" custom fields to preserve line breaks when values are being copied from one field to another for enhanced readability.
- Updated the behavior of the database query optimizer to improve performance within certain areas of the system such as retrieving list view results.
- Updated the notification check interval from 2 minutes to 5 minutes to enhance system performance.
- Updated the Albanian language code to be "sq" in accordance with W3C and ISO standards.
- Updated various areas of the system in accordance with most recent vulnerability report.
August 23rd 2024 (202407.04)
- Fixed an issue where web page views containing linked record lists were not displaying correctly when the web page view was set to generate a PDF directly from the workflow.
- Fixed an issue where filters incorrectly displayed excluded statuses by fixing the NOT condition in the search functionality for Status or Type in Level 1 and Level 2 list views.
- Fixed an issue where dropdown fields using dynamic content incorrectly triggered a "cannot be empty" validation error despite being populated.
August 8th 2024 (202407.03)
- Updated the behavior of the Annotation Mode permissions. Users with roles that have Edit Field permission will be able to edit the value of fields with existing annotations without needing View and Create permissions as long as the user has a role with View permission. This means existing permissions for annotations will no longer need to be modified as part of the July upgrade. Tooltips clarifying annotation permissions were also added. To see these changes, go to UTA Configuration Settings > Level 1, 2, 3 tab > Statuses > Select the desired status > Permissions and Availability tab > See the settings under the “Annotation System Role Permissions” section.
- Fixed an issue with the advanced search where leading or trailing semicolons in the options were preventing proper display.
August 1st 2024 (202407.02)
- Due to Google Maps deprecating support for older versions, we have updated the Impact Maps to use new versions of the marker clusters. To ensure your Impact Maps function correctly, you must manually generate the HTML and JSON files after the upgrade is applied. To do this navigate to the desired UTA > Configuration Settings > Level 1, 2, or 3 tab > Impact Maps > Edit the desired map > Click "Generate HTML and JSON files" to recompile the map.
- Fixed an issue with the "Layout - Title Bar" custom field where records did not display correctly in 2 columns under some scenarios. Title bar custom fields set to 2 columns will now correctly render in 2 columns as intended regardless of the caption location. If you wish to display a record in single column, make sure the number of columns is set to 1.