v1.4.6 Release Notes

  • Core: Fixed the display of line breaks in Rock Shop ratings.

  • Reporting: Fixed the person giving filter and select in reporting so that the end date range is inclusive.

  • Workflow: Fixed issue with not being able to remove a workflow type from a connection opportunity if requests have already been created that use that workflow type.

  • Check-in: Fixed issue with check-in configuration not clearing cache for the areas (i.e. which labels are associated with area).

  • Connection: Updated Connection Request so that members of a campus-specific connection group can now add connection requests.

  • Core: Fixed column headers not being responsive.

  • Communication: Updated Mailgun component to deal with bounced events having incorrect formatting.

  • Check-in: Updated the Device Detail block to prevent and warn when attempting to add a new device with same name as an existing device instead of causing an error.

  • Group: Fixed exception that would occur when trying to delete a group type that was a child of another group type.

  • Finance: Updated the Benevolence Request Detail block to list case workers in alphabetical order.

  • CRM: Fixed the message that is displayed on the Merge People page when user navigates directly to page (instead of initiating request from a grid). Message will not indicate that they are not authorized to submit a request.

  • CRM: Fixed Spouse name field on reports to exclude any deceased spouses.

  • Group: Updated Group Member List block so that the Group setting is not required (typically group is passed on the query string).

  • CRM: Fixed issue when adding a known relationship to an inactive person and it not creating the inverse relationship.

  • CRM: Fixed issue with new family block saving phone numbers without a country code and added migration to fix all missing country code values.

  • Communication: Fixed issue where only first recipient would receive email when it included one or more attachments and the default binary file type was using a custom storage provider.