- When setting up an automation, many customers add a delay to triggered actions in response to an event or change. You may also want to ensure that the conditions that would trigger the automation still apply after the delay. You can now recheck the conditions that would have triggered the automation (and its delay) after the delay period. This reduces the risks that the conditions have changed over the delay period and the automation is no longer applicable.
- With the change:
- A new option will appear in an Automations “Advanced Settings”, giving you the option to “Recheck conditions” after a set delay period
- Delay period and Priority remain as separate options but you are now required to choose one or the other. Previously you had the ability to select both which caused conflicts
- If a site had both a Delay and a Priority specified on an automation prior to this update, the automation will treat the Delay as more important
- For new automations, Delay can be set under Advanced Settings. Previously you were able to set them when setting up an email Action. You will no longer be able to find the Delay settings there.
- For more information on Automation Advanced Settings, visit here
- Within Forms, customers can use Branching Rules to establish changes in form behaviour based on the responses provided by a user. For example, you might ask if a user is from California and then provide them with different form questions or other differences to form behavior. Editing Branching Rules with Multi-Column Grid questions was a bit broken. Now it’s fixed!
- Learn more about our Advanced Branching here
- Some customers have reported that, when creating reports, they were not able to see their recommendation forms in the datawell (the list of data points you can drag and drop onto the canvas from the left side of the screen). This issue has been addressed.
- Learn more about our reporting capabilities here.
- To further increase the security of our OAuth Single Sign-on (SSO) integration option, we have added a custom “state” parameter
- With the change
- There is no change to you if you already use OAuth for SSO
- Please see https://auth0.com/docs/protocols/oauth2/oauth-state for more context on the application of this parameter
- Learn more about our Single Sign-on here.
- With the change
- Pull in data from Person Accounts objects in Salesforce: Person Account objects store information about individual people by combining certain account and contact fields into a single record. From time to time, organizations that integrate Salesforce and Apply data want to pull information from Person Accounts into Apply. We now allow Admins to configure their Salesforce integration to pull this data into Apply. This gives you an even greater opportunity to streamline the application process by leveraging data that already exists in your Salesforce environment.
- Note: Pull functionality is only available in Version 4 of the Salesforce-Apply Integration. We also do not support data pushes back into Salesforce Person Account objects.
- Learn more about our Salesforce integration here.
- For customers using Apply Connect, our API, we’ve added more detail to our Applicant Task endpoint. Users can now map the form question ID with application responses to better identify which questions are associated with which responses.
- Learn more about Apply Connect here.
- For customers who wanted to export all of their site data into a single file, we addressed a bug that caused an error when initiating the export from the Reports area.