Smartstaff
2,357
edits
Changes
m
→Notes for Admins
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==
====New Support for OAUTH Authentication for Enhanced SMTP Relay and Migration of Credentials to Integration Keyswith OAuth 2.0 Authentication====
<!-- 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".
====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.
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:
* Numeric value for a '''Text Box - Number''' field
* '''YYYY-MM-DD''' format value for a '''Text Box - Date''' field