Changes

Template:April2016Upgrade

132 bytes removed, 15:18, 29 April 2016

no edit summary

===New Disable User Account After Inactive Period===

This enhancement enables user accounts to become disabled after a specified period of inactivity. Controlled by the Password Policy settings, an account can become disabled, requiring a password reset to regain access.<br />:* [[Disable User Account After Inactive Period - Why?|Why?]]<!-- :* | [[Disable User Account After Inactive Period|How]]

42897 - Disable Account (i.e. expire account if unused) -->

==Beta Previews==

===New Field Revision Annotations===

Revision Annotations allows you to mark up field add annotations at the field level and allow edits to be made to specific fields while keeping the rest of the record locked. Flexible security allows you to configure role-based permissions to allow different users the ability to make add annotations to fields and while others the ability to edit the field value, for example when requiring users to make revisions to their forms.

<!--

This feature enables organizations who receive applications and forms to add field-level comments for applicants to review and revise. This feature allows organizations to better communicate feedback with applicants by enabling them to add comments to specific fields on submitted applications and forms. This process allows the annotated fields to be editable only.

[[Image:Annotation_add_new_anno_icon.png]]<br /><br />

[[Image:Annotated_field_ex.png]]<br />

-->:* [[Field Revision Annotations - Why?|Why?]] <-- | [[How]]-->

<!-- 42199 - Revision comments -->

===New Contact Invitations===

This new The Contact Invitation feature introduces simplifies the ability to invite process of inviting contacts to collaborate on a system record through an email invitation. It also allows for the invitation of new contacts that do not currently exist in the system. To facilitate this, invited contacts can accept or decline the invitation to associate them to the record. Contacts who are new will be directed to a contact sign-up page where you can then control their registration behaviour. This simplifies the process of inviting contacts to participate in system activitiesbehavior.<!-- :* [[Contact Invitations - Why?|Why?]] <!- - | [[How]]

46588 - L1 invitation functionality -->

• ← Older edit
• Newer edit →

Alvin Thompson

2,004

edits