Tasks to complete before applying the pattern
-
Check which operations you wish to be included in this pattern instance. The four possible interactions
may be combined in a single pattern instance but they operate independently and could be implemented as separate pattern instances.
-
The pattern requires a message set which defines the SOAP operations defined by the Salesforce enterprise wsdl. Use the pattern "Resources"
to down load the SFWSDL message set and then modify this as required.
-
Ensure that the external key fields are added to your Salesforce record:
- Using the Salesforce UI add the field AccountExternalId to the Account record, selecting the options
required, unique and ExternalId. This key holds the unique key from the source system and is used to determine
whether an Account already exists in Salesforce.
- If you have included operations on contacts then add the field ContactExternalId to the Contact record, selecting the options
required, unique and ExternalId. This key holds the unique key from the source system and is used to determine
whether a Contact already exists in Salesforce.
- Note that custom fields such as those above always have the suffix __c when used in service calls to Salesforce.
-
Using the Salesforce UI add any additional fields in the Salesforce Account and / or Contact record that you require to meet your business requirements.
-
Download your enterprise service wsdl. This will be required to update the message
set generated by the pattern instance.
-
Determine the degree of customisation of the data format required. If you need only to add new fields to the default XML input
format used by the pattern then this can be done as part of pattern instantiation. You will just need to know the names and type of the fields to be added.
If you need to make significant changes to the data format used for input, or you wish to use a non-XML format,
you should select advanced customisation
and will need to prepare your own message set to define the input message format.
With advanced customisation you will also need to identify which fields contain the unique local identifiers which map to
the Salesforce fields .
- Decide if validation of the incoming request messages is required.
If your source applications generate correct messages, validation might
not be required.
-
Decide whether you require logging of request messages.
-
Decide if you want to handle errors by rolling back the input message or by writing
the message to an error queue. If messages are rolled back, all error events
are recorded in the event log.
- Decide if you want to write error notification which contain a summary of the exception data.
Back to the overview