Step-by-Step - Copying a Boomi Process
This is a step-by-step recipe to copy a Boomi process to make a new one. This is a very common task in Boomi, as many Boomi integration processes are similar to ones that you have already built.
But, there are definitely best practices and potential pitfalls in copying a Boomi Process. Here is the step-by-step, with comments. Contact us at Kitepipe for integration, migration, and boomi training services.Goal - Create a new Boomi Process from an Existing One Steps:
- Create a new Folder to hold the new process set. An integration at the business level often contains multiple processes. These processes will use common components, and should be housed in a single folder. An example is a Customer integration which might contain both customer level and contact level processes.
- Expand the Component Explorer panel on the left, if it is not already expanded
- Find the Folder which should contain the new folder in the component explorer panel on the left
- Pull down the blue tab, and select New Folder
- Name the new folder
- Copy the Process most like the one you want to build. Boomi processes have patterns, and you are looking for the one that has a similar pattern of Connectors, maps, and error handling. Processes with the same endpoints (Netsuite and SQL, for example) often have the same step pattern.
- Find the source process in the Component Explorer
- Pull down the blue action tab on the process, and select Copy
- UNCHECK the Copy component Dependents. A Boomi process contains a hierarchy of components, can be 15 or 20 in one process, many of them shared across processes. Usually you DO NOT WANT copies of them, you want to reuse existing components. If you Copy component Dependents, you will end up with duplicate connectors, connector operations, profiles, etc. Instead, you will carefully copy just the ones you need to change. This is especially true if you are copying a Process from the same folder, as you will end up with duplicates of everything in the folder.
- Fill the Destination folder with your newly created folder location
- Click OK to Copy the Process
- Change the Basics on your new Process
- Find and open (double click) the new process
- Immediately change the name in the blue header, and click save. Until you do this, you have two processes with the same name - dangerous!
- Unlink the destination connectors by dragging in Stop Steps, and moving the flow connection arrow from a post or update connector to the stop step. This will make sure nothing gets updated until you are done with changes and ready to reconnect the end points. It also visually shows you that you are looking at a process in progress. When you have three or four processes open that all look alike, you can get confused. Save the process.
- Swap out the Connector Steps: Connectors, Operations, Profiles
- Open each Connector configuration, and review the Connector and the parameters. Swap out the Connector , if needed.
- Open the Connection operation. Unless you are pulling the same table, view or object, the Connector Operation must be new. Use the plus sign to create a new operation
- Name the new operation, and save (should save into your new folder, but check the path on the upper right).
- Use a common profile, or make a new one. In most cases, the table, view or API will let you import a profile definition to create a new profile.
- Best practice with APIs and Tables is to profile the entire record. Fewer changes later when you need another field. Use a subsequent map to pare down the fields to those you want.
- If you have to create the profile by hand, look for an example file (csv or xml) to import - complex xml profiles are tough to build by hand.
- Do the same with the other connectors, and build the operations and profiles you need
- Review each map, and update
- Maps look like Process steps, but they are not, they are separate objects. A common error is to modify a shared map accidentally. The maps in your new process also belong to the copied process, so they must be replaced.
- Open up each map and review it - you will either use it as a shared component, copy and modify (if it contains useful mapping and logic), or make a new one.
- To use as a shared component, do nothing. The Map should be in a shared or common components folder if it is shared
- To make a new Map, use the configure tab from the existing map and the Plus button to start an new map. Add profiles, and save
- To copy and modify A Map:, Update Process Steps - many steps in the process (decisions, program, properties) live with the Process, and get copied with the process. Open up each one, and modify. Program steps can have connectors as well, so swap those out if needed.
- go find the Map in the explorer, and copy it using the blue actions tab to your new folder.
- Do not use the Copy tab on the map in the process layout, this makes a duplicate step on the map, but does not copy the object.
- Leave the copy components checked - this will copy any map functions, and the profiles. Go back to the process, and use the Configure tab on the old map step to replace it with the new map, which you will find in your new folder with the same name. Open the new map, check the path to make sure it is the copied one, and rename it and save.
- Immediately find and delete any copied components you won't use. Probably one or more of the profiles that were copied. Look at the profiles in the explorer in your new folder, and delete unused ones with the blue action tab. If you don't do this immediately, it is easy for you to end up with five or ten profiles, and have to undertake a where used analysis to determine which ones are the extras.
- Open the copied map, and replace profiles, modify mappings, and change Map functions.
- Take particular care to open each function or lookup, and change out the connectors and operations. Maps often lookup using connector components, and a common error is forgetting to change out the connectors or operations in the maps.
- Update query logic to match the new profiles and operations
- Turn off extensions - I do this to make sure I don't end up running a deployed process without looking at the extensions. You will have to turn these back on if you are using process extensions before deployment.
- Run a unit test, and see what happens!
Thats a step-by-step recipe for copying a Boomi Process. I have tried to point out options, choices, and potential pitfalls - I have made them all! If you have been working in Boomi for some time, you have done this dozens of times. If you are a newbie, copying a process can be intimidating.
I was working in a big account as a Boomi rookie, and was scared to change any common components, so I made duplicates of everything - I ended up with dozens of duplicate connectors and profiles that I needed to replace later.
Good luck! Here's a link to boomi Bootcamp.