Users can now see attributes on the person and organization core view at a glance without expanding groups. Attributes are categorized in tabs and can quickly be found by using the new search bar.
Additionally a tab named Important will be displayed when quick access attributes for persons and organizations are configured.
The action for adding attributes is no longer required because all attributes are accessible when editing which reduces the time to set the values for attributes.
Enhance Consent (User Reset)
Users are now able to simply "recollect" consent even if there already is a collected consent state. Whether this behaviour is allowed or not can be configured per consent type.
In the consent type configuration select "User reset/recollection allowed y/n".
- user can recollect consent in any state
- no consent: user simply collects consent
- consent accepted
- user can recollect to "rejected"
- user can recollect to "accepted" e.g. with updated email
- consent rejected
- user can recollect to "accepted"
- user can recollect to "rejected" with updated date
Consent Type Data availability in List Management
Add more selectable criteria and columns (calculated per defined consent type)
- consent "action at" date
- consent communication data types
→(each calculated per consent Type)
Offline - Mode
65% of the existing aggregates were refactored to be used in the abstraction layer to handle the offline and online commands.
Meeting conflicts 2
After some user feedback we have come to the conclusion that we need to adapt a couple of things regarding meeting conflicts like: planned vs. closed activities, my activities vs. a colleague's activities and the visibility of the information in general.
We now only show conflicts when a user plans an activity, not when the user is closing an activity. Additionally the user's own activities are not displayed as a conflicts.
When editing: Unless the user changes the date, time & attendee(s) of an activity the notification won't be displayed again.
planned & my activity
planned & colleague's activity
closed & my activity
closed & colleague's activity
Here the conflict is shown in a more prominent way but there is also an option to have no confirmation checkbox. By clicking on "Plan" the user accepts the meeting conflict.
Possible combinations of activities that can be configured to be checked:
org + persons
|only org||check org||
|org + persons||check org||check org + persons||check person|
|one person||none||check person||check person|
Pers. E-Mail Statistics (optional)
When using pers. E-Mail data for email statistics like click, open rate and bounces are stored in the system. Data can be embedded and used in reports and transferred to other systems. It can be configured for which template the tracking should be active.
What is being collected:
- was the mail delivered or did it bounce, eg. type of bounce
- was the email opened
- which links were clicked
- tracked per receiver
Tracking can be activated optionally for any ysura platform.
Centralized logging for reporting
- statistics for Operating System and Browser
- session length