Supported Objects
Only a select set of Salesforce standard objects are supported (source/target header/child). These are Technical Feature Description, Account, Asset, Case, Contact, Event, Lead, Opportunity, Opportunity Product, Product, Quote, Task, User, and BusinessHours.
* 
Note:
Support for some of these objects such as Case depends on the ServiceMax license. All of these are supported for ServiceMax license type Enterprise. To know more about ServiceMax license types, contact your ServiceMax admin.
All other objects, including child objects such as Activity History object and Notes & Attachments object, are not supported
All custom objects are supported, except for the following ServiceMax objects, which are special objects used by the ServiceMax application for managing the application configuration:
Allocated Stock, Booking Window
Code Snippet, Code Snippet Manifest, Counter Details
Dispatcher Access, Field Default Rules, Location Covered
Offline Dataset Expression, Offline Log, Offline Object, Offline View
Page Layout, Page Layout Detail, Process Bottlenecks, Route Card, Route Stop
Service/Maintenance History, ServiceMax Config Data, ServiceMax Configuration
ServiceMax Job, ServiceMax Job Log, ServiceMax Job Stats
ServiceMax List, ServiceMax Process, ServiceMax Properties, ServiceMax Property Elements, ServiceMax Tag
SFM Event, SLA Details, Stock History, Sync Request, Sync Request Records
Territory Coverage, User GPS Log
Some of these are blocked only for selection as target header or child objects. Some examples of such objects are Counter Details, Dispatcher Access, and Entitled Contacts.Supported custom objects include objects that are part of the managed package ServiceMax or any other package, and objects directly created in subscriber orgs
Some of these are blocked only for selection as target header or child objects. Some examples of such objects are Counter Details, Dispatcher Access, and Entitled Contacts.
Supported custom objects include objects that are part of the managed package ServiceMax or any other package, and objects directly created in subscriber orgs
Both parent and child objects in a master-detail relationship can be source / target header objects
List of child objects displayed in the source and target child sections consists of these objects:
Objects with master-detail relationship with the header object selected
Objects with lookup relationship to the header object selected
Child objects are displayed using the related list label for the lookup / master-detail field that connects them to the header object
For example, Work Detail object is displayed with the label Work Detail (Work Order), when Work Order is the header object.
Work Detail object is displayed with the label Work Detail (Work Detail), when Work Detail is the header object.
The business hours field is supported on the designer layout.
* 
BusinessHours object is not available for configuration in Look-up Editor, Expressions, and Mappings.
Was this helpful?