How You Manage Calendar Patterns

Use calendar patterns to define how often a work requirement forecast is due. Calendar patterns are useful to model recurring maintenances that aren't impacted by when a maintenance is accomplished. For others, a day-based work requirement method is more useful. You can define calendar patterns uniquely for a maintenance program. If you have enabled Redwood opt-in, you can create them globally, allowing their use across all programs. Patterns are selected in a work requirement that's enabled for the calendar work method.

On the existing page, you can only create a new pattern within a work requirement, or directly for a program using REST or File-Based import. You can’t edit, disable, or delete a pattern after it's created.

Using the Redwood page, you can manage calendar patterns under the Calendar Patterns tab. When you create a new pattern, you can select if it's global or only associated and usable in a program. You can then define its frequency and create it.

Note: Global patterns can only be created using the Redwood page. Only program-based patterns can be created using REST or File-Based import. However, once created, they can be manage all the patterns under the Calendar Patterns tab.

The filters show all options for filtering on a chip but won't filter by values in the search results. Therefore, when using a filter chip value, you may end up with no matching results rows.

You can edit or delete a pattern:

• If it's created as Global and not referenced in a requirement.
• If it's created for a program and not referenced in a requirement.
  Note: You can't edit or delete a pattern that's referenced in a requirement, however, you can disable it. You can re-enable a pattern to associate it afresh with a work requirement.