Improvements, improvements, improvements …
The Agillic release 18.4 is focusing entirely on improvements, and you can look forward to updates in app push templates, the new app push editor as well as minor feature and usability improvements across the application.
Hope you will enjoy it and we welcome feedback at email@example.com
Get to know Agillic 18.4
New capabilities in App Push channel for both templates and editor
We have added several new possibilities for App Push template developers to design their templates to cater for the specific needs of the company's App Push Server setup as well as improving the user experience for editors.
- New parameter types: Number, Integer, Boolean
- Add display names and descriptions for each parameter making it more intuitive for editors
- Create enumerated dropdowns/picklist for parameters, headers, endpoint URL - this increases the usability for editors and limits the risk of human errors
Tie specific header fields (e.g. credentials and regex) to a specific endpoint url. Together with the new capability of creating dropdowns and display names, this enables template developers to create a drop down with different endpoints written in an easily, non-technical manner (e.g. test server, production server, etc.). And the editor never needs to worry about credentials or regex when choosing a new endpoint
- Mark parameters to be "read only" in the editor - show editors what value will be sent to the server, but prohibit them for editing it
- Differentiate between person- and global data parameters
Read more in our developers portal here.
Apart from the changes that these new possibilities will have on the editing experiencing, we have also added the following improvements:
- Clear indication if there are unsaved changes or not
- Automatically search across all recipients in staging when entering recipient ID to test push message
- See references and information on created/updated by and when in messages
Finally, when sending a push message to a recipient the following person data will be updated:
- LAST_PUSH (timestamp)*
- PUSHES_THIS_WEEK (number)*
New default password requirements
As part of our commitment to customer data security we have increased the default minimum requirements for new passwords created for Agillic users.
This will take effect for all new Agillic solutions, as well as all solutions where you have not changed the default values initially set by the system. For customers who have already adjusted the settings e.g. to fit their organisations policy, we are not changing anything.
After your organisation have been upgraded to 18.4, we recommend you visit System settings → Security and review the minimum requirements for your user passwords.
New log-in page
We are introducing a new log-in page in this release. This change is part of our implementation of a new front-end architecture, which is the foundation for a faster and more intuitive user experience.
Improvements to the ETL (Extract, Transform, Load) feature
By popular request we have made improvement to the ETL feature which was introduced last year. This release introduces several improvements allowing users to automate additional actions:
- Apart from setting the schedule for the ETL, you can now activate or inactivate the script
- Apart from inserting new propositions, you can now update, set or delete propositions via ETL
- Tag propositions with target groups
- Tag proposition links with events
Read the article in Knowledge Base for further details.
All sent emails, print-outs and SMS's will automatically be stored for future reference
Before 18.4 you had to remember to actively enable "store a copy" on the flow step for email, print or SMS to save a version of how an email looked for individual recipients when sent out. This is an important feature for future customer dialog and investigations. Many of our users have requested that we enabled this as an "always on" feature, to avoid the situation where a configurator has forgotten to enable "store copy" and thus can not see what was sent to an individul customer. This setting is now default on from release 18.4 and the option to deactivate has been removed form the UI.
Activities in paid media integrations for Facebook and Google now available in activity export, recipient investigator and -snapshot widget
We have consolidated our paid media integrations even more for Facebook and Google with our general feature set for channels. Meaning that you can now see when recipients have been added or removed from certain lists in either Facebook Custom Audiences and Google Add Customer Match. The data is available for individual recipients in-app in the investigator and snapshot feature. Also, the data can be added to an activity export for analysis in tools externally of Agillic.
Set ‘time of day’ when configuring a ‘wait for date step’
When using a wait for date step in a flow, it is now possible not only to choose the date, but also the exact time of day the recipients will continue in the flow. You can e.g. configure a wait for date step to “Wait for the 25th of February and for it to be 12:00”.
New GDPR export for all recipient data
Now you can choose to export all data for a recipient on production via the ‘Recipient Snapshot’ widget on your start page. All generated files will be zipped in a .zip file with ‘recipient_’ and the recipient ID as the name. This will be added to your a GDPR folder in your instance’s Export folder.
Read the article in Knowledge Base for further details.