* [CHD-3405] [Worklists/Usability/Compose] Multiple compose popups may be opened from ticket worklists.
* [CHD-3418] [Addresses/Import] Fixed an issue that prevented CSV data from being imported on an address worklist if it included an organization field.
* [CHD-3409] [Mail/Parser] Fixed an error message in the parser from Virtual Attendant actions using certain kinds of worklists: "PHP Fatal error: Call to a member function getMemberships()"
* [CHD-3410] [Maintenance/Scheduler/Custom Fieldsets] Fixed a SQL issue in the maintenance scheduled job involving the deletion of orphaned custom fields from previously deleted fieldsets.
* [CHD-3412] [ACL/Permissions] Removed the 'Mail page' and 'Activity page' itemized permissions since those options no longer exist in versions 6.0+.
* [CHD-3413] [Pages/Mail/Wizard] The default 'Mail' page created by the 'Help me create a page' wizard now expands the subtotals sidebar on the ticket worklists and sets it to 'Groups' by default.
* [Devblocks/Plugins/Explore] The devblocks-dao.php helper script now generates 'explore mode' code for any new contexts.
* [CHD-3416] [Calendars/Availability/Usability] We've been receiving support requests from new users asking why they can't add events to their availability calendar, and Cerb wasn't providing any feedback about their calendar not being configured. When a worker doesn't have an availability calendar configured, viewing the 'Availability' tab on their profile now discloses this fact. A worker viewing their own non-configured Availability will be provided with the option to select or create their availability calendar. Viewing another worker's non-configured Availability will display a warning that they haven't configured the feature. This should provide a much better experience for new workers.
* [Calendars/Availability] Deleting a calendar will now remove it from use as any worker's availability calendar.
* [Virtual Attendants/Custom Scripts] All Virtual Attendant behaviors can now use a 'Custom Script' condition to determine outcomes.  A custom script allows conditional logic, basic math operations, and the evaluation of any combination placeholders.  Any output provided by the script is evaluated as the condition's result.  For example, a custom script can check the value of multiple placeholders in a single condition and output 'true' if any of them match the desired value.  Similarly, a custom script can perform mathematical operations (e.g. add, multiply) on a combination of placeholders and evaluate the result against a threshold (e.g. num_spam/(num_spam+num_nonspam) > 0.9).  Some Virtual Attendant actions also have the ability to set custom placeholder values; for instance, in response to an HTTP request, a record lookup, or a complex calculation.  A custom script can be used to evaluate the contents of these dynamic placeholders.  This feature was originally implemented so the JIRA plugin could create issues through JIRA's API as a Virtual Attendant action.  The VA behavior can then read the status from a custom placeholder to determine if the issue was created or if an error occurred. On error, the actual error from JIRA's API can be created as a notification to the VA's owner.
* [CHD-3420] [Calendars/Worklists] Fixed a bug that prevented calendars with worklist-based events from displaying long-running events on multiple days.
6.4.3-dev checkpoint
Merge branch '6.4.3' into stable