What's new in Version 5.21!
| Table of Contents |
|---|
New Features
Easy Calendar: Allow to enter only Accounts
You can now enter just Accounts (no Second Record required) on the Easy Calendar! This was previously just a feature Batch Entry and Stop Watch. With this change, please review https://fosteringllc.atlassian.net/wiki/spaces/TTKB/pages/3185344524/Considerations+for+Easy+Calendar#Record-selections-in-the-Choose-Records-modal to understand how time gets logged to just Account Records and the same Account Records with Second Object selections.
...
Restrict Second Records to the Account Master
Do you want to restrict second records, to display only the record related to the Account chosen? Now you can for the Batch Entry and Easy Calendar! See the documentation below to enable and considerations.
...
User Capacity VS Actual Report and Report Types
Are you trying to report on User Capacities and compare it to the actual users time logged on Time Tracking Summaries? You always could but to took some creative report type creation and a joined report. We added two report types in our package, one called User Capacities with User and another called Time Tracking Summaries with Entered For User. With these two report types you can create a joined report that will allow you to use any fields on the User object as a common field. Note: you may need some tricky formula or bucketing done in your report to make it look like you are expecting.
We recommend you utilize the Manage User Capacities Overview user interface vs this joined report.
...
Stopwatch: Field with same API name impacting the App
We refined the code and presented a better error messaging on the Stop Watch if you have created a custom field on the Time Tracking Summary object that matched an existing field name. This is a known issue from Salesforce. Previously the Stop Watch would simply stop creating a new time card to log your time. Now, with this message it will help user and admin more easily diagnose and resolve the issue.
...
...
Version 5.21 was created with the features listed above. There was a bug reported that an Apex Class was not included in the Time Tracking permission set. This was fixed within the same day and version 5.22 was pushed to subscriber orgs.