...
In this
...
article
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Overview
This Snap creates a new object or updates an existing object in Xactly Incent app
...
. This Snap uses an account class called XactlySoapAccount, which stores the WSDL file and the credentials to connect to the Xactly server. It also caches the Session ID that is required for subsequent CRUD operations. To perform create, do not supply any value for xobj:id field. To perform update, supply Object-ID of existing object to xobj:id field.
- Expected upstream Snaps: CSV Generator / File Reader and so on
- Expected downstream Snaps: File Writer.
- Expected input: The name of the Xactly object to be created such as PersonWSO or BonusWSO and the property values of the object to be matched.
- Expected output: Confirmation of the object's creation.
...
Prerequisites
None.
Limitations and Known Issues
None.
Support for Ultra Pipelines
Works in Ultra Task Pipelines.
...
This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. It uses an account class called XactlySoapAccount which stores the WSDL file and the credentials to connect to Xactly server. It also caches Session ID that is required for subsequent CRUD operations. See Configuring Xactly Accounts for information on setting up this type of account.
...
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
|
| The Snap has exactly one input view which contains properties to be used while performing the save operation. |
...
The name of the Xactly object to be created such as PersonWSO or BonusWSO and the property values of the object to be matched. We recommend you to use these properties (employeeId, version, name, description, prefix, firstName, lastName, region, personalTarget, personalTargetUnitTypeId, paymentCurrencyUnitTypeId, user, isMaster) at the minimum for performing successful save operation. The properties user, paymentCurrencyUnitTypeId and personalTargetUnitTypeId must have well-defined values as per Xactly User web page. | ||||
Output | Document |
|
| This Snap has exactly one output view that contains the contains the outcome of the save operation. Confirmation of the object's creation. |
Error |
...
This Snap has at most one error view and produces zero or more documents in the view.
...
Settings
...
Label*
Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:
Learn more about Error handling in Pipelines. |
Snap Settings
| Info |
|---|
|
Field | Field Type | Description |
Label* Default Value: Xactly Upsert | String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline. |
Xactly object |
...
Default Value: PersonWSO | Dropdown list | Choose the type of object to be saved. Once defined, the input view will provide the schema of the object so that field values can be defined for the save request. |
Default Value: PersonWSO
Example: CustomerWSOExample: CustomerWSO
Default Value: Execute only | Dropdown list |
|
Troubleshooting
| Multiexcerpt include macro | ||||
|---|---|---|---|---|
|
Snap Pack History
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|