Difference between revisions of "Template:July2021Upgrade"
Ann Vincent (talk | contribs) m (→Major Updates) |
Ann Vincent (talk | contribs) m (→Global System Upgrades) |
||
Line 34: | Line 34: | ||
<!--123610 - System Design Summary--> | <!--123610 - System Design Summary--> | ||
+ | === === | ||
===Minor Updates=== | ===Minor Updates=== | ||
====Updated Chart-type Portal Sections with Ability to Open Records==== | ====Updated Chart-type Portal Sections with Ability to Open Records==== |
Revision as of 13:41, 21 June 2021
Contents
- 1 General Details
- 2 Overview
- 3 Global System Upgrades
- 3.1 Major Updates
- 3.1.1 Updated the Address Field to use the Google Location API for Auto-Population of Standard Fields
- 3.1.2 Updated Registration Forms to Pre-Populate with Invitation Data
- 3.1.3 New Setting to Suppress the Display of Portal Pages in the Header
- 3.1.4 Added Custom Field Permission Data to System Design Summary Reports
- 3.2
- 3.3 Minor Updates
- 3.1 Major Updates
- 4 On-Demand System Upgrades
- 5 Beta Previews
- 6 Notes for Admins
General Details
Upgrade Dates
Public Cloud Production release date: July 8 2021
Public Cloud Backup release date: ???
Private Cloud Production (Managed Upgrades) release date: ???
Private Cloud Backup (Managed Upgrades) release date: ???
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.
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
Updated the Address Field to use the Google Location API for Auto-Population of Standard Fields
Typing into the address standard field will now provide the user with a list of verified address options. Upon selecting a verified address option, the other address standard fields (like country) will be auto-populated, saving the user time and helping to ensure addresses entered are accurate. This ability is available on signup pages, as well as user and organization profiles.
Updated Registration Forms to Pre-Populate with Invitation Data
When a new user registers after accepting an invitation, the information in the invitation will now auto populate the signup page to save the user time. Specifically, the standard fields for Prefix, First Name, Last Name, and Email. The invitations feature can be configured by going to the desired UTA > Configuration Settings > Level 1 > Invitations Template.
New Setting to Suppress the Display of Portal Pages in the Header
Added the ability to suppress portal pages from appearing in the top header bar. This will vastly improve portal configuration time if your system was configured using the Deny permissions on Portal Pages (formerly called “Main Menu” items) and your intent was simply to hide items from the main menu bar. After this upgrade, you will need to remove the deny permission on those pages and enable the new setting called Display As Menu on Portal Header. To configure a portal page, go to Menu Icon > Global Settings > Users tab > Portals > Edit the desired Portal > Edit the desired Portal Page > Permissions tab.
Added Custom Field Permission Data to System Design Summary Reports
Added additional information to system design summary reports when custom fields are included. Specifically Custom Field Role Permissions, Status and Type Permissions have been added to the report. Navigate to Global Settings > System Design Summary and toggle ON the option to include "Custom Fields" for the desired UTA and Generate the Summary".
Minor Updates
Updated Chart-type Portal Sections with Ability to Open Records
Updated chart-type sections within a portal to allow you to drill down, and open up individual records. This will now function similar to the table-type sections allowing you to navigate to and open individual records for review.
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 Shopping Cart Feature
New Shopping Cart feature allows for the tracking as well as processing of payments from users. When this feature is configured, it will allow users to process payments towards organizations, or UTA Level 1 records. This feature was designed with end user donation purposes in mind and will allow you to process payments directly via our integration with our partner Stripe, or through an integration with your own financial system by way of payroll deduction. Users may choose from one-time payments to multiple payment plans. For system administrators, this feature can be enabled in the Global Settings area through settings called Shopping Cart. You can define what system objects are available to for inclusion within an order, and multiple payment forms as well to specify different attributes for different methods of payment. For example, you can include a flat processing fee, and either choose to display or hide this from the user's order summary screen. For end users, when they navigate the records made available for payment towards, they will be presented an option to add to their shopping cart, from which they may check out when done.
Minor Updates
Extended Bulk File Download Function for use With Consumer Provider List Views
Extended bulk file download functionality to be available for Consumer Provider list views. You may now configure Consumer Provider list views with the ability to download file uploads from the records returned in the list.
Beta Previews
No features are available for beta preview this upgrade.
Notes for Admins
Added New Parameters to SmartConnect API for Pagination of Records
Added additional parameters to the SmartConnect API to allow for pagination of record sets. For List action API calls, new parameters recordcount, recordstart, and recordend will now be returned to you. New parameters recordsperpage, recordstart, and pageofrecord will be available for you to pass to the calls to page through the result set. You may pass just the recordstart to indicate which record to start from, for example, given a recordsperpage 100, you could pass recordstart 1, 101, and 201 in order to obtain records 1-100, 101-200, 201-300 respectively. Another example, given a recordsperpage 100, you could pass recordstart 1, 1, and 1, in combination with pageofrecord 1, 2, and 3 in order to obtain the same record sets 1-100, 101-200, 201-300 respectively.