The ServiceMax connector for Jitterbit Harmony Cloud Studio provides an interface for entering user-provided input such as credentials to create an authenticated ServiceMax connection. That connection provides the foundation to configure associated ServiceMax connector activities that interact with the connection. Together, a specific ServiceMax connection and its activities are referred to as a ServiceMax endpoint.
As ServiceMax is a Salesforce application, and as this connector is based on the Cloud Studio Salesforce connector, Jitterbit Salesforce functions, variables, and wizards apply and can be used. This documentation references related Salesforce documentation as applicable.
Prerequisites and Supported API Versions¶
The ServiceMax connector supports using Jitterbit Harmony Cloud or Private Agents that are version 9.4.2 or higher.
A Salesforce account that does not have multi-factor authentication (MFA) enabled is required. To configure a Salesforce account without MFA, make sure that the Permission Set assigned to the Salesforce integration user does not have the selection Multi-Factor Authentication for API Logins. Integration user logins are exempt from Salesforce's MFA requirement, as described by Salesforce in their documentation Does MFA Affect API Integrations? and Salesforce Multi-Factor Authentication FAQ.
As ServiceMax uses the Salesforce platform, the ServiceMax connector uses the Salesforce API.
The API version that the connector uses for non-bulk activities depends on the Harmony Agent version:
|Harmony Agent Version||Salesforce SOAP API Version||Salesforce Release|
|11.7 or later |
10.69 or later
|11.0 to 11.6 |
10.55 to 10.68
|10.44 to 10.54||52.0||Summer '21|
|10.42 to 10.43||51.0||Fall '21|
|10.28 to 10.41||50.0||Winter '21|
|10.23 to 10.27||49.0||Summer '20|
|10.17 to 10.22||48.0||Spring '20|
|10.11 to 10.16||47.0||Winter '20|
|10.3 to 10.10||45.0||Spring '19|
|9.8 to 10.2||44.0||Winter '19|
|9.4.2 to 9.7||41.0||Winter '18|
The REST-based Salesforce Bulk API 2.0 is used for bulk activities.
Agent upgrades that skip Salesforce SOAP API versions implicitly include support for intermediate API versions.
Refer to documentation provided in the links above for information on the schema fields.
This connector is used to first configure a ServiceMax connection, establishing access to ServiceMax, and then used to configure one or more ServiceMax activities associated with that connection as a source or target within an operation.
Standard ServiceMax Activities¶
- Query: Queries data from a ServiceMax endpoint and is intended to be used as a source in an operation.
- Insert: Inserts new data in a ServiceMax endpoint and is intended to be used as a target in an operation.
- Update: Updates existing data in a ServiceMax endpoint and is intended to be used as a target in an operation.
- Upsert: Both updates existing data and inserts new data in a ServiceMax endpoint and is intended to be used as a target in an operation.
- Delete: Deletes data in a ServiceMax endpoint and is intended to be used as a target in an operation.
Bulk ServiceMax Activities¶
ServiceMax bulk activities are faster and scale better than non-bulk ServiceMax activities, but should be used only if you do not need to use a transformation to change data prior to reaching the target.
- Bulk Query: Queries a large number of records from a ServiceMax endpoint and is intended to be used as a source in an operation.
- Bulk Insert: Inserts a large number of new records in a ServiceMax endpoint and is intended to be used as a target in an operation.
- Bulk Update: Updates a large number of existing records in a ServiceMax endpoint and is intended to be used as a target in an operation.
- Bulk Upsert: Both updates a large number of existing records and inserts a large number of new records in a ServiceMax endpoint and is intended to be used as a target in an operation.
- Bulk Delete: Deletes a large number of records form a ServiceMax endpoint and is intended to be used as a target in an operation. Deleted records are stored in the ServiceMax Recycle Bin prior to being permanently deleted.
- Bulk Hard Delete: Hard deletes a large number of records form a ServiceMax endpoint and is intended to be used as a target in an operation. Hard deleted records automatically become eligible for deletion.
Accessing the Connector¶
The ServiceMax connector is accessed from the design component palette's Connections tab (see Design Component Palette).
Create a ServiceMax Custom Field / External ID for Jitterbit¶
It is recommended to use a custom field in ServiceMax to associate records with an external ID for Jitterbit. These steps show how create a custom field in ServiceMax on the Account object to create an external ID called "Jitterbit_Account_ID":
Log in to your ServiceMax instance with your credentials.
Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
From the Object Manager tab, select the standard Account object.
From the Account object view, go to the Fields & Relationships section, and click New in the top right.
- In Step 1. Choose the field type, select Text as the data type and click Next.
- In Step 2. Enter the details, configure your new custom field as follows. Then click Next.
- Field Label: Jitterbit_Account_ID
- Length: 50
- Field Name: Jitterbit_Account_ID
External ID: Checked (very important)**
- In Step 3. Establish field-level security, accept the default settings by clicking **Next.
- In Step 4. Add to page layouts, accept the defaults by clicking Save.
You should be returned to the Fields & Relationships screen for the Account object. Verify that you see the new custom field with the same parameters as shown below.
For more information, refer to Salesforce's documentation for Create Custom Fields.
Salesforce Functions and Jitterbit Variables¶
A number of Salesforce functions can be used within scripts to provide login and session information and lookups for ServiceMax instances, including these:
In addition, certain Jitterbit variables are provided specifically for use with ServiceMax and Salesforce endpoints, including these:
For details on using these functions and variables, see Salesforce Functions and SFDC Jitterbit Variables, respectively.
If you experience issues with the ServiceMax connector, these troubleshooting steps are recommended:
Ensure the ServiceMax connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can check the agent logs for more information.