Patch release notes for Workarea 3.4.3.
Create Configuration for Insight Model Classes
Admin::InsightViewModel::MODELS to a configuration value called
config.insights_model_classes so it can be extended, and new insights
can be added for display on the dashboard.
Update App Template for Upgradability and Rails 5.2
Some errors were observed when using the
rails app:template task with
the built-in app template for upgrade purposes, since there are a
significant amount of changes in the app template for v3.4 (like
auto-configuration). Workarea has replaced the usage of
#app_name method to ensure that it's set before attempting to
perform text processing operations, and the template will no longer
Gemfile if it doesn't have to. Additionally, the
has been cleaned up by removing extra whitespace.
Prevent Logging Controller Parameters in Logstash
Logstasher was previously configured to send controller params in Logstash logs, but this caused errors in Elasticsearch as each new param became a new mapping as it was indexed. This very quickly exhausted the amount of mappings allowed within the Elasticsearch index. Workarea no longer enables this field out of the box, so that logstash will continue to work as normal.
Fix Occasionally Failing Test Around Marking Discounts Redeemed
Specify a sort so that MongoDB doesn't use its own default sort, causing entries in the collection to appear out-of-order and the test to fail inconsistently.
Fix Slow Export Samples for Large Collections
skip that is done to get random samples can be quite slow if
MongoDB needs to page. Instead, Workarea now grabs the first N entries
in the collection, since they don't really need to be random.
Remove "@" in Activity Time
Remove this character preceding the time of timeline activity so that it reads better.
Inherit from ApplicationController Consistently
All admin controllers now inherit from
Some autoloading edge cases caused this indented module reference to not
get picked up properly.
Fix Bulk Edit/Delete Entries Not Appearing in Trash
A carry-over from the v2.x days,
Mongoid::AuditLog entries were not
recorded when performing within background jobs. Since bulk actions
occur in the background, entries for documents edited/deleted in this
manner were not appearing in the trash, and therefore not possible to
restore without developer intervention. This constraint is now removed,
and items deleted/edited within a bulk action will now appear as
individual items in the trash, and attributed to the user who performed
the bulk action.