Changes

==Notes for Admins==

You may now pick an encryption certificate for service provider initiated single sign-on (SSO) and the certificate will be displayed in the '''Service Provider (SP) Metadata''' field. If enabled, incoming assertions will be decrypted using the selected certificate. If you opt to use this feature, you will be required to upload the identity provider (IdP) encryption certificate to '''Integration Key Management''' and select the certificate in your SSO setting. This will be used to decrypt incoming assertion.

<!-- 144700 - SSO encrypted assertion support? -->

You can now report on the '''Data Exchange History''', making it easier to report on details around package exchanges. Within the '''Report Builder''' you can choose the new dataset option called '''Data Exchange History''' and add columns for related details such as when the package was sent and received and what the status of the package is.

<!-- 132667 - Dataset for Data Exchange History Reporting -->

====Updated API to Allow Update and Get/List for Profile Model Field Data====

We updated the API to allow update and get/list for '''Profile Model''' field data. When updating the sf_Profile Model, data should be a jsonobject where the "node" is the profilemodel jsonnode name. This is an example of how to update the '''Profile Model''':

<!-- 152787 - Profile Model JSON data update via SmartConnect API -->

If you have multiple environments and promote changes from development to staging to a live environment using the T2P tool, you will no longer encounter the ID mismatch issue related to the '''Question Set Builder''' when moving fields between environments.

<!-- 148162 - Question Set Builder and T2P -->