Request Module Roles like Resolving Request, Closing Request, and Allow Stop Timer will not be considered for showing Status Allowed Values in Add/Edit Form and Details Page of the Maintenance Module.
Request Module Role Assigning Technician will not be considered for filling Group and Technician fields in the Add/Edit Form and Details Page of the Maintenance Module.
Entries will not be logged into the System Log Viewer for CRUD operations performed on maintenance tasks. However, any failures while executing a schedule will be logged.
The template change will not be available while editing preventive maintenance tasks.
Site Restricted Technicians can only operate on preventive maintenance tasks that fall under their Site Scope or the preventive maintenance tasks for which the Requester is filled with technicians.
Template Default Site will be allowed during preventive maintenance task creation only if the technician has access to that site.
After the release of the Maintenance module, the schedule data will not be migrated from On-premises to Cloud as many schedule configurations introduced in On-premises as part of the Maintenance module are not available in Cloud yet.
Created By field will not hold any value for preventive maintenance tasks created before migration.
The Title field, which is a newly introduced unique field, will have the value as PMTASK_<ID> post-migration. Users can change it as per their requirements.
Periodic schedules will be migrated as Daily schedules.
Monthly schedules will be migrated as Yearly schedules.
Migration will fail if the SDMaintenanceManager role is created before migration.
Future events rendering will be improper for the preventive maintenance tasks created before migration and are running on the last day of the month.
Technicians having access to preventive maintenance tasks before migration will not be able to create/update maintenance post migration if their machine's time zone/personalized time zone/department site's time zone is different from the server time zone.