For more information about the Compliance Calendar, visit our blog post here.
The Compliance Calendar is a new widget on your Tasks page that shows tasks created from the Action Items widget or in your inspection forms, as well as frequency requirements from Logs in the Environmental Data Platform. Here, you can see your past and future Tasks and Logs for up to a year in the future.
Note: The Compliance Calendar does not show inspections.
You can now see if a Task or Log is overdue, completed, or coming up in the future with a glance.
The red 'X' means that the due date of the task has passed and is now overdue.
The green check mark means that the task has been marked as completed.
The blue '-' means that the task is neither overdue nor completed.
Creating and Viewing Tasks
Tasks created from the Action Items widget or inspection forms will be on the calendar. To add an ad-hoc task to the compliance calendar, create a task in your Action Items by clicking on the three dots and selecting "Add a Task."
Here, you'll be able to add details to your task, such as the title, assignees, and due date. Once you have added the required information, click 'Create Task' to submit.
💡 To visually signify the type or importance of a task in the compliance calendar, you can use emojis.
You'll then be able to view your task in the compliance calendar. For more information about Tasks, click here.
Viewing Environmental Data Platform Log Events
Logs created in the Environmental Data Platform can now be viewed as calendar events with due dates in the Compliance Calendar. Clicking on 'Add New Entry' will also allow you to enter data into the Environmental Data Platform manually or via file upload.
These calendar events are grouped by Log per day - if multiple entries are due for the same Log on the same day, only one calendar event will appear. For example, if three generators need readings taken once a month, only one calendar event will appear on the Compliance Calendar. Clicking the event shows all the frequency requirements due for that Log for that day.
If any requirement is not met, the overall status icon for the calendar event will appear incomplete (or missed if the due date has passed).
As-needed Log entries will appear as calendar events after they are submitted. As-needed Logs, by definition, don’t have due dates, so they won’t appear on the Compliance Calendar before they are submitted.
💡When uploading data, there is an upper limit of 200 rows of data allowed to be uploaded via file upload at a time.
Log completion statuses are “sticky” when their frequency requirements change. If a new required Log field is added, past log entries for that Log will not be considered incomplete; i.e. they will still show up on the compliance calendar as 'completed.'
If you edit any field value of a past log entry, that entry's completion status will recalculate. So, in this case, if you edited a past log entry, but the new required field was not filled out, that entry will now be considered incomplete. If you remove a required log field from a log, a past entry that did not have a value for the required field that was removed will still be considered incomplete unless any value from that log entry is updated. When the entry is updated, the completion status will be recalculated. This matches the behavior seen in Forms.
💡 You can view all the data submitted into a Log by clicking on 'View Log Records' in the modal that pops up when you click on an event in the calendar.
Clicking on the arrows at the top of the calendar will allow you to view your past and future tasks. Tasks that are due more than a year into the future will not be visible on the calendar until the task is due within a year. We recommend going to your organization's task analytics pages to see further than a year.
End of Article
If you have any questions or need further assistance, please e-mail firstname.lastname@example.org or call (800) 553-7420 ext.