Smartstaff, administrator
686
edits
Changes
no edit summary
====Changed Behaviour and Updated List of Currency Fields====
Updated the list of available currencies, as well as behaviour of select input for various currency selectors throughout both admin configuration pages, a well as end user interface pages. Currency fields, including the UTA Level 1 Currency standard field, have been updated to a more recent listing of global currencies. The field has been updated to show you both the currency code as well as full name of the currency, also now allows you to search on either text, and lastly the sorting has been updated to be fully sorted alphabetically. The stored value of the field will remain the same, and it is only the display value seen on screen that has been updated. Note, that the currency for French Canadian has also been removed from the list, as this should instead be determined by a combination of Canadian currency, and the user's language and address locale.
<!--88659 - Expand the list of currencies available in the UTA L1 SF Currency-->
Enhanced the Password and Activation settings pages for improved navigation, ease of use, as well as stronger default security settings. The interface for these pages has been updated in line with a left navigation menu. Some settings now have updated labels, and descriptions, and may have been re-organized between tabs to be more intuitive to find. The password policy and complexity has been updated in order to easily configure your password complexity requirement. Previously, the password complexity would be a compiled logic statement, which can still be made via a custom policy, however now by default the password complexity is a set of toggles and options that is easy to both set as well as read. Also, with the new Default password complexity type, we've updated the interface to validate a user's password as they type to provide a better user experience when updating their password. We encourage you to review your password complexity settings and easily switch over to the new Default complexity type. Please note that the options for minimum character requirement have been updated from a minimum of 6 instead up to 8 characters now.
<!--109890 - Password and Activation Policies - Password Pattern-->
====Deprecated Support for Classic Interface====
Deprecated the Classic interface, and removed the ability to re-enable the Classic interface, and will no longer be supporting the Classic interface. A previous upgrade would have automatically converted any instances still using Classic interface to the current Arcadia interface so there should be no impact to most clients. This will however, force all instances to the newer Arcadia interface with no more ability to revert back to Classic interface. We have fully removed the option in Global Settings -> Classic Options -> Disable Classic Mode that would have allowed you to revert back to the Classic interface.
<!--113575 - QA Issue: Classic Interface on User Profiles-->
====New Portal Configuration Mode====
<!--96926 - configuration mode for portals phase 2-->
[[File:2020-07-ticket-96926-1.jpg|thumb|none|500px|Previewing and editing a 1) Enable Configuration Mode via the PortalPreview mode, with the new Portal 2) Indicator that Configuration Modeis enabled, making it easy 3) Click the gear icon to edit menusthe settings of a section, sections and 4) Click the pencil icon to directly edit the texton-screen.]]
====Enhanced Translation Functionality for Password and Activation Settings Page====
[[File:2020-07-ticket-90026-1.png|thumb|none|500px|After the upgrade the hierarchical navigation bar will appear on configuration pages such as the Level 1 Custom Field. Note you can navigate direct to the UTA List, the UTA Settings page and the list of Level 1 custom fields with a single click.]]
====Deprecated Pre-Built System Reports====
<!--101982 - Notification Broadcast - Targeted Notifications and Workflow Driven Notifications-->
====Extended Display of Record Type and Status Colour Color to Provider/Consumer List Views====
Extended more base functionality for Provider/Consumer list views to display type and status colours for the records listed, as well as advanced search functionality.
<!--53589 - Consistency in consumer/provider list view-->
New Form Completion Indicator feature allows you to display the current percentage completion of a form as the user fills it out. The setting can be configured granularly for UTA records, users, or organizations, for example in the UTA Settings -> Level 1 Settings -> you can define the user roles that see this indicator, and for which record types and statuses. This provides end users with a visual estimate of how much work they've completed and how much is left. This feature will automatically calculate the percentage complete based on the number of fields available for input by the user, and indicates both the overall form completion as well as per section as defined by fields contained within each custom field of type Layout - Tabbed Section. You may even adjust the default weighting of each Layout - Tabbed Section against the overall form completion.
<!--111287 - Improved tabs and record completion-->
[[File:2020-07-ticket-111287-2.png|thumb|none|500px|Form completion indicators as seen on a level 1 such as a grant.]]
====New Option to Configure Duplicate Check of Rows in Advanced Data Table Fields====
New ability to configure a duplicate check across columns within the sections of a Advanced Data Table custom field. This setting will allow you to enforce uniqueness across the rows of a section. You can select one or more columns to include in this by toggling the Enable Duplicate Check setting per column.
<!--91097 - Enable Duplicate Checking Configuration within dynamic XML sections-->
====Extended Language Translation Functionality for Advanced Data Table Sections====
Enhanced the Advanced Data Table custom field with the ability to configure language translations for each section. You can now configure different language translations for this field much more easily.
<!--85747 - Advanced Data Table XML sections with multi language support-->
====Extended Language Translation Functionality for Organization and User Signup Pages====
Enhanced the Organization and User signup pages with the ability to configure language translations. You can now configure different language translations for signup pages much more easily without having to create separate signup pages. The language selector previously located under the Description text area, has been moved up into the top left action bar and will function similar to more recent implementations of language translations for configuration pages. Note that existing configurations will still function as before, and this change will only apply to new signup pages.
<!--85834 - Ability to support multiple language on signup pages-->
====Extended Contact Invitations to be Available for UTA Level 3 Records====
New option in the Special - Linked Record List custom field type to be able to connect to contact invitations. You can now have a greater ability to configure the display, and access to invitations.
<!--91418 - Expand Linked Record List Field to Include Invitations-->
[[File:2020-07-ticket-91418-1.png|thumb|none|500px|Showing invitations on a level 1 such as a grant using the Special - Linked Record List custom field.]]
====Extended Quick Assignment to be Available for UTA Level 2 and 3 Records====
===Minor Updates===
====New Options for the Limit of User Lookup on UTA Records Based on Associated Organizations====
New date range input made available to search panels within a portal section. When you enable the search panel for a portal section, and make a date field available for searching, you now have the option of selecting Date Range as the comparison operator in order to easily create a prompt for both start and end date range.
<!--93193 - pick date range through single ui-->
[[File:2020-07-ticket-93193-1.png|thumb|none|500px|The new date range input option for search panels in list view portal sections.]]
====New Option to set Workflow Trigger Times Dynamically Based Upon Field Values====
