Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Contents

Overview

With the Easy Calendar component, you can log time for records over an entire month, specifying information such as who time is being entered for, the month and year, and the specific days.

User Interface

The Easy Calendar component interface has various elements to control aspects of the functionality. Let’s take a tour of the component and view each element.

  1. Entered For: Specify the user which time is being entered for. The specified user will show as the creator of the Time Tracking Summary records which the component creates.

  2. Month: The month which time should be entered for.

  3. Year: The year which time should be entered for.

  4. Days: Specify whether the component should display only the weekdays in the month, or the full week.

  5. Choose Records: When clicked, a modal opens and allows the user to select and Account record and a secondary lookup field. The selectable secondary lookup fields available are any custom lookup field on the Time Tracking Summary object. The selections are saved to a field on the User record selected in the Entered For input. By default, five rows will be available to populate, but you can add more rows if necessary by clicking the plus icon

  6. Calendar: The calendar displays a column for each weekday or full week in the month, depending on the Days selection. For each record pair selected in the Choose Records interface, a row is displayed.

Component Use

To use the component, first enter a value in the Entered For input. After the Entered For User has been specified, select the month, year, and days which should be displayed. If different records need to be displayed in the calendar or this is the first time your tracking time for the User specified in the Enter For input, then click the Choose Records button and enter your account and secondary lookup pairs, otherwise, past selections will default into the calendar.

Now that the selections have been specified, begin populating the columns with the time that needs to be logged for each pairing on each day of the month. The total time for a column will be displayed at the bottom of the column. Consider the following when entering time:

  • If any Time Tracking Summary records exist, with the Created By field set as the Entered For User and the Created Date being set a specific day of the month column, time may be prepopulated into a row column based on the Hours (As Number) field from that Time Tracking Summary.

  • By default, time cannot be entered for dates in the future. Time can be entered only for past dates and the current date.

Once you have completed entering the time for the various days of the month, click the Save button. Once clicked, the component will update any existing Time Tracking Summary records if they existed and changed, while new Time Tracking Summary records will be inserted for new entries.

Considerations

When using the Easy Calendar component, keep the below information in mind.

Time isn’t rounded

Time entered in the Easy Calendar isn’t rounded using the Time Tracking app’s Time Rounding feature. The entered time is saved as is.

One Summary per day

If the Entered For User has more than one existing Time Tracking Summary record for a particular day, the time for that day can’t be edited in the Easy Calendar. Time can be edited only if there aren’t any existing Time Tracking Summary records or exactly one Time Tracking Summary record exists.

image-20240424-191625.png

Hover over a date’s warning icon to display clickable links to the “duplicate” Time Tracking Summary records.

image-20240429-192140.png

Dates & Time Zones

In Salesforce, dates are stored in GMT (Greenwich Mean Time) format. In the UI, they are converted to the time zone specified in a user’s personal settings. The component uses the GMT format of the CreatedDate on a Time Tracking Summary when determining which existing records to pull into the component.

image-20240110-152845.png
  • No labels