Scheduler Settings

In the main system setup Chronicle gives you some control over how the calendar will work for all users.

Can users create events that aren’t assigned to any resource?

When you create an event, more often than not, you will associate that event with a job. Sometimes you do not know who will be available to work on that event until the day before. Using this setting, Chronicle will allow you to create events that are unassigned i.e. you have not yet told Chronicle which employee will be going out on that job but the event is schedule. If you choose to not allow unassigned events, you must also associate at least one employee to the event. In the scheduler, you are able to view all unassigned events.

Workday

You can set the length of your workday. The scheduler will then display a lighter color on the calendar gird for those hours of the day.

Warn if changing an event

These settings affect how you want to be notified if an event on the scheduler was changed. This is critical when you are importing labor hours from the scheduler into the labor manager for job costing purposes.

• Do you want to be warned if an event was changed after it was imported into labor? If  an event was imported into labor before it was corrected to reflect the actual time on the job, then the labor hours in the labor manager would not be correct. Whether users can edit imported events is also controlled by the security context
  CALENDAREDITIFIMPORTEDTOLABOR
• Do you want to be warned if a past event was changed? This will merely tell you that a past event was changed. Whether users can edit past events is also controlled by the security context
  CALENDAREDITFORPASTDATE
• Tell Chronicle what makes an event a "past event" by setting a time frame. You can use the scheduler to accurately record all labors hours. Employees can correct the event to reflect the actual times they were on the job so that when importing from the scheduler into the labor manager the times are accurate.  Employees will always make these changes "in the past", for example, that night or the next day. However, for the purposes of telling you that a past event was changed, when do you want to know? Is 24 hours sufficient for employees or office staff to make changes? After that you want to know? How about 48 or 72 hours later? This setting tells Chronicle when to "see" an event as a past event for the purpose of letting you know it was changed.