Changes

Jump to: navigation, search

Template:May2018Upgrade

899 bytes added, 20:29, 11 May 2018
no edit summary
===Major Updates===
 
<!--[[File:2018-02-ticket-61124-1.png|thumb|none|middle|500px|Simplified user access and roles options]]-->
====Updated Configuration Pages====
New ability to identify custom fields as personal data and display the reason for collecting it. When configuring a custom field you will be able to flag it as a personal data field and enter in a description text for why you are collecting this data. This will be surfaced to end users as they enter the information, and allows them to easily review a summary of personal data that the system is collecting from them. This feature can be used for compliance with new GDPR guidelines.
<!--66423 - GDPR #1 PII field Identification-->
 
[[File:2018-05-ticket-66423-1.png|thumb|none|middle|500px|Editing a custom field and classifying it as personal data]]
 
[[File:2018-05-ticket-66423-2.png|thumb|none|middle|500px|Tooltip describing to the user why that data is being collected]]
 
[[File:2018-05-ticket-66423-3.png|thumb|none|middle|500px|Summary of all the personal data fields that are being collected]]
====New Ability to Attach Privacy Policies and Agreements to Sign Up Pages====
New data retention policies allow you to set a retention time frame after which the system will purge a specified set of data. You can set different retention policies for different field sets through the Data Categorization feature. Do this by specifying the date field with which to compare the policy against. Please use with caution!
<!--63877 - ABAC Data Retention Policies-->
 
[[File:2018-05-ticket-63877-1.png|thumb|none|middle|500px|Data retention policy configured to delete data after a lifespan of 3 years]]
====New Impact Quadrant Chart====
New custom field type introduced, Question Set Builder in order to allow users to create their own customized field sets without being an administrator. This field type can be attributed to a UTA Level 1 record, and allows a user to edit the Level 1 record and define a set of customized questions that will then appear and manifest as regular fields on Level 2 records added to that Level 1. Consider an example use case, when you have different users that run their own Level 1 Programs, and they wish to define their own set of questions or metrics for their reporting milestone Level 2 Activities. All you have to do is create this single Question Set Builder custom field, and this will allow non-admins to create their own individual question sets that apply just to their Programs, don't affect other Programs, and don't require any further administrative configuration.
<!--66009 - Question Set Builder-->
 
[[File:2018-05-ticket-66009-1.png|thumb|none|middle|800px|Regular user interface of editing a record and their own question set]]
====New Custom Field Display - Instructions====
New custom field type introduced, Display - Instructions in order to easily create stylized blocks of instruction text. These fields will also have the added ability of being able to be hidden or shown in bulk so that users familiar with your system may hide beginner tips.
<!--62757 - Consistent Instructions you can hide to aid new users-->
 
[[File:2018-05-ticket-62757-1.png|thumb|none|middle|800px|Easily create great looking instruction blocks]]
====New Custom Field Text - Date and Time====
<!--66246 - Guidestar Charity Check Scheduling-->
====New Ability to Upload Pictures Images for Portal Shortcuts and Sections====New ability to upload your own pictures images for use as portal shortcuts or section backgrounds. This gives you even more ability to customize and brand your portal.
<!--66996 - Image shortcuts-->
<!--66998 - Sections with an image background-->
 
[[File:2018-05-ticket-66998-1.jpg|thumb|none|middle|500px|Example look of a new portal with custom images set as the section and icon backgrounds]]
====Added Ability to Configure New Button For Portal Sections====
Updated the configuration of portal sections with the ability to add a button to create new records. In appropriate portal sections such as list views, you may now configure a New button to allow end users to create new records.
<!--57551 - Have an add button to create level 1 in the section in the portal-->
 
[[File:2018-05-ticket-57551-1.png|thumb|none|middle|800px|You can now add New buttons into your portal sections]]
 
====Enhanced UTA Security Matrix with more Granular Organization Permissions====
Smartstaff, administrator
686
edits

Navigation menu