We are proud to announce that we have released a new version of Boomi JIRA REST connector. This connector helps to reduce the complexity of authenticating and constructing the API request (using JSON format) to JIRA and it works well with any JIRA version 5 and above.
Feel free to check out our the office documentation here for more details.
The client is using SalesLogix to handle credit/loan deals. When the deals are approved, the deal (and the deal related information) need to be in return track in the Sungard Avantgard Integrity system
||To sync approved deals from Saleslogix into Avantgard Integrity system.
||Sage SalesLogix CRM
Sungard Avantgard Integrity
||SalesLogix On-Premise version 8.0.0
Integrity Version 8.4.1
||SalesLogix Deal Roles > Integrity Counter Party
SalesLogix Deal Roles > Integrity BU Exposure Limit
SalesLogix Deal > Integrity Agreement
SalesLogix Deal > Integrity Facility
SalesLogix Deal Tranches and Fees > Integrity Tranche, Fee and Covenant
||JSON and XML
||When a SalesLogix Deal (Custom) is approved, it in return creates an agreement in Integrity. All children information from deal such as contact roles, tranches and fees will create a corresponding Integrity record respectively as well.
||Every 2 minutes
In Boomi, we often design the integration process to run in a serial mode by having a Parent process that invokes Sub process.
This is really helpful if we have a business flow which we need to make sure that the parent record (e.g, Customer) is synced into the target system before the related record (e.g, Sales Order) is being synced. However, this design is not that handy when it comes to retrying error document. As you all know that Boomi allows you to retry an error document in the Process Monitoring console. This only works for the document that is related to the Boomi process that is attached to an environment directly and deployed.
As a workaround, you will need to attach and deploy the related Sub process to an environment and just let it sit there without having any scheduler.
In Boomi Marketo connector, you can query a list of leads by using the static list which gives you the option of either using:
1. Static List Name
2. Static List Id
Static List Name
You can do this by simply providing the name of the List that you have created in Marketo. However, if the list is created under a campaign, you have to provide the name of the campaign and the list. For example:
if you have the setup as shown in the screenshot above, the name that you should provide is “Campaigns for Activity Extract.Leads with Web Visits”.
Static List id
If you would like to use the list Id, you can retrieve the Id:
– click on the list
– look at the URL in browser
– retrieve the number between ST and A1
For example: https://app-abd.marketo.com/#ST1234A1, the Id for the list would be 1234.
In the latest release, Boomi has included a very important feature in the HTTP connector. The HTTP operation can now capture the value of the response header and store it into a dynamic document properties. This is very useful as some of the applications require a certain cookie value returned in the first call to be used in the subsequent call.
To use this feature, you just need to:
1. edit a HTTP operation
2. scroll to Response Headers Mapping
3. add the specific response header that you want to capture
For more information, please refer to the official documentation.
When transforming data through map, there may be situation where you need to query some information from a specific record (i.e. from source) and to map it for the destination.
If you need to perform query from a specific instance (i.e. Salesforce), you can do so by utilizing the Connector Call function.
If you are trying to retrieve information from a database instead, you may not be able to see the Database option available in the connector list!
Don’t be panic, as you can still query database table information via the SQL lookup function available in the lookup category:
Last time, we discussed about the usage of Program Command shape in Boomi. The shape is very useful especially it allows us to invoke a system command/shell script from a Boomi process. However, did you know that the shape will use the system command exit code to determine the status?
0 – success
1 – fail
This will not work correctly if you want to execute a system command that has different exit code than the standard one.
For example, the Robocopy in Windows uses different exit code (e.g, 1) other than 0 to indicate a success copy operation. This will cause an error execution in Boomi. To overcome this, you can write a system command script to alter the exit code to make it compatible with Boomi Program Command shape:
robocopy D:from D:to filetocopy.txt /is
IF %ERRORLEVEL% EQU 1 (
) ELSE IF %ERRORLEVEL% EQU 0 (
) ELSE (
Have you ever having difficulties to view the raw data that is being sent out or received in Boomi platform? Here are the options that you use to overcome this:
This is a very useful networking traffic capturing tool. You can refer to our previous post to find out more on how this works.
In the latest release, Boomi has introduced a new Atom property “connector.trace”. This Atom property has to work together with a Java JDK built-in utility, JVisualVM (this can be found in JDK_HOME/bin or download from here).
To enable the debugging mode, you will need to:
1. add the “connector.trace=true” to the Atom via Atom Properties screen
2. enable Remote JMX on the Atom
3. configure JVisualVM to monitor the Java activities
In Boomi, you have two sub processes that are configured to run asynchronously. If you plan to share the value between the sub processes in this mode, you will need to be aware of the behavior of the process property as it is not feasible.
For example, in Sub Process 1, you have a Set Properties shape that will set a value to a process property, and you want to get the value of the same process property in Sub Process 2. At this point, Boomi will return you a null value in Sub Process 2. This is because both of the sub processes execution are considered running in different threads.
If you want to share the value of a process property between processes, you can configure the process to run synchronously.