A360 Maintenance Plan Process
A360 Maintenance Plans offer a schedule-based processing engine for reviewing maintenance plans and generating work orders for covered assets on those plans. This engine is informed by Maintenance Plan Processes, which are stored in this object. The A360 Maintenance Plan Process object stores process details such as when a process should run, what information will be mapped to the work orders generated by the process, who is assigned the work orders, and how the execution of the process should be logged.
API Name: SVMXA360__SM_MaintenancePlanProcess__c
Number of Fields: 20
FIELD LABEL
FIELD NAME
DATA TYPE
DESCRIPTION
Custom Relationship Fields
​Mapping Asset to Work Order
SVMXA360__SM_MappingAssettoWOId__c
Lookup(Object Mapping)
Mapping to be applied from Asset on the generation of Work Order.
Mapping MPlan to Work Order
SVMXA360__SM_MappingMPlantoWOId__c
Lookup(Object Mapping)
Mapping to be applied from Maintenance Plan on the generation of Work Order.
Standard Fields
Maintenance Plan Process Name
Name
Text(80)
The auto-generated record name.
Custom Fields
Active
SVMXA360__SM_isActive__c
Checkbox
This flag indicates if the maintenance plan process is active or not.
Assign To
SVMXA360__SM_AssignTo__c
Picklist
User value to be fetched from to assign Work Order generated from the Maintenance Plan process.
Assign To Object API Name
SVMXA360__SM_AssignToObjectAPIName__c
Text(255)
API name of the object on which the user field is configured.
Assign To Value
SVMXA360__SM_AssignToValue__c
Text(255)
Based on the Assign To Selected, this field will hold the value of the User/Queue/User Field API name of the selected object.
Days In Advance
SVMXA360__SM_DaysInAdvance__c
Number(5, 0)
The number of days in advance the Work Order needs to be created.
This setting is specific to time-based Work Rule Conditions, whereas the Threshold field on the Condition supports the Frequency and Criteria-based Work Rule Conditions.
Description
SVMXA360__SM_Description__c
Long Text Area(32768)
Description of the Maintenance Plan Process.
Developer Name
SVMXA360__SM_DeveloperName__c
Text(255)
Process unique developer name.
Enable Detailed Logging Notifications
SVMXA360__EnableDetailedLoggingNotifications__c
Checkbox
If checked, engine detailed log notifications will be enabled.
SVMXA360__SM_GenerateNewWorkOrder__c
SVMXA360__SM_GenerateNewWorkOrder__c
Checkbox
If the MP Process has qualified a maintenance plan and created a work order for a criteria-based condition, users may not want the MP Process to generate another work order for that criteria until the existing work order has been closed/completed. Set this checkbox to true to ensure that the MP Process Engine will not create new work orders for conditions where a work order already exists and is not closed.
Last Run Date
SVMXA360__SM_LastRunDate__c
Date/Time
This field indicates the date/time of when the process last ran. It provides a link to the process log for the most recent run.
Last Run Status
SVMXA360__SM_LastRunStatus__c
Picklist
This field indicates the status of the last run performed for this process. Values include Success and Failed.
Recurrence Pattern
SVMXA360__RecurrencePattern__c
Text(255)
Contains the frequency and duration governing the generation of work orders for a Maintenance Plan. This field is populated by a rule generator that is provided as part of the component for creating Work Rule Template records.
Run At
SVMXA360__SM_RunAt__c
Text(20)
Time of the day at which the process to be triggered.
Send Failure Email To
SVMXA360__SM_SendFailureEmailTo__c
Email
Email address to which email to be sent on the failure of the Maintenance plan process.
Send Success Email To
SVMXA360__SM_SendSuccessEmailTo__c
Email
Email address to which the email to be sent when the Maintenance Plan runs successfully.
Standard
SVMXA360__SM_Standard__c
Checkbox
If true, signifies the standard/default process.
This field can only be checked for one process at any given time since only one process can considered the standard process.
Time Zone
SVMXA360__SM_TimeZone__c
Text(80)
Time Zone to be considered for running the process at the scheduled time.
Was this helpful?