Integrating Boomi flow with boomi atmosphere and MDM

In this document, we are going to work on use case to upload contact details of customers into MDM. Customer contact details will be in .csv file, which we are going to upload by using Boomi flow.

Prerequisites:-

  • Access to Boomi Flow, Atmosphere and MDM.
  • Boomi Atom cloud needs to be install.

We will start building this integration by creating process to accept the data from the flow.

1. Create a process and configure Flow service server in the connector.

 

 

2. Click on the ‘+’ symbol in the operation tab and name it as List File operation. Select the file resource operation as List files.

 

 

3. Now create request and response profiles as show in below screenshots.

Request profile:-

 

 

Response profile:-

CSVListContents should be in repeating array.

 

 

4. Connect the flow service server connector to the stop shape . And then save and close the process.

 

 

5. Create another process and configure Flow service server in the connector.

 

6. Create new operation and service type should be File resource & File Resource operation should be File Upload.

 

 

7. Create a Response file as shown below.

 

 

8. Click on the ok to continue with integration process.

 

 

9. We need create a Flow Service component, because those components .

 

Create FS Component

 

10. Provide external name as ‘upload’ for your flow service.

 

 

11. In the File Resources tab Add a File Resource. Give it a path of /file.
For the required List Files Process select the process named “Filler List Files Process.” For the Upload File Process select the process named “File Upload,” as shown below:

 

Flow Service

 

12.Deploy the contents of the imported “File Uploads” folder, and your newly created Flow Service component, to your own atom.

13. The atom Shared Web Server should have Basic auth and Intermediate API. The shared web server URL needs to be accessible to the cloud, so the public atom cloud is often easiest.

14. In Boomi Flow – navigate to Services. Find and hit the Edit pencil on the “Atom Upload Service.”

15. Populate the appropriate atom Shared Web Server base URL ahead of /fs/upload (replacing https://connect.boomi.com in the screenshot below).

16. Populate Your username and token from the “User Management” tab of your atom Shared Web Server.

17. Finally, hit Update Service.

 

 

18. Now navigate to the boomi atom sphere component.

19. In the Flow Service component, under the File Resources tab, selecting Add File Resource will prompt a developer to define a path (e.g. /file ).

20. It will also require a process be populated in each of the two selection fields (Upload & List). More details on the Flow Service component configuration can be found in the Quick setup instructions above.

 

 

21. In the start shape of the process library sample, you’d notice that the Flow Services Server Operation Service Type is File.

22. The File Operation is Upload File. If you’re configuring this from scratch there is a useful Import button that will automatically create the standard “File Upload” profile for you.

 

 

23. In the sample, when the decision shape does indicate that the file is a CSV, the map has a comma delimited Flat File profile to interpret the contents.

24. The CSV line items map into the Array(Repeating) profile entry to be returned to Flow.

 

 

 

25. After deploying the process and the Flow Services Server component, the file handling integration process will be available for “installation” in Flow.

26. A current known issue is that the Flow file types aren’t automatically being generated by the atom service installation; so a developer currently needs to create these type(s) manually.

27. This type can be generated either via the point-and-click type creation dialogue, or via the API feature in the Flow build tool.

28. The name of your type will need to be something like $File RESPONSE – Object. The only available variation would be the final word, which is Object in the default imported atom start shape profile.

29. If a developer modifies the profile object name (which is recommended) to e.g. “CappFile”,  then the appropriate type name would be $File RESPONSE – CappFile.

api/draw/1/element/type

 

Type post

 

The end result should look like this:

 

Manual Default

 

30. Adding a nested Array(Repeating) entry inside the ‘base level’ file response profile (and corresponding flow type) allows the integration process to return a list of data as is seen in the sample.

31. This requires the creation of an additional Flow type. It has a similar naming convention to the ‘base level’ file type. An example can be seen here:

 

 

32. A list property would then be added to the ‘base level’ File type. When prompted to select a type for this list property, it should be the custom type described above. Screenshot:

 

 

33. The file upload shape on the flow page layout has a few key configurations.

 

 

34. Now import the email service in flow by following below steps.

35. Click Shared Elements.

 

https://docs.manywho.com/wp-content/uploads/2016/11/Screen-Shot-2017-01-13-at-12.55.17-AM-minishadow-1024x545.png

 

36. In the Shared Elements dialog box, click Services.

 

https://docs.manywho.com/wp-content/uploads/2016/11/Screen-Shot-2017-01-16-at-9.42.03-AM-minishadow-1024x543.png

 

37. Click Import Existing. This lists all the services available in your tenant. The ManyWho Identity Service is available to all tenants by default.

38. Click the Import button next to the service you want to use.

 

https://docs.manywho.com/wp-content/uploads/2016/11/Screen-Shot-2017-01-13-at-1.15.58-AM-minishadow-1024x546.png

 

39. Click Close to close the dialog box.

 

https://docs.manywho.com/wp-content/uploads/2016/11/Screen-Shot-2017-01-13-at-1.07.31-AM-minishadow-1-1024x539.png

 

The service is now imported, and ready to be used.

40. Drag a Message element to the canvas. To Build Email Approval logic

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-21-at-6.58.04-PM-minishadow-1024x557.png

 

41. This opens a configuration panel for the element.

42. Copy-paste To be or not to be in the Name field.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.11.25-PM-minishadow-1024x558.png

 

43. Click New Message Action. This opens a screen that lets us select the service we want to use.

44. Select ManyWho Email service as the service to send the message.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.13.38-PM-minishadow-1024x559.png

This shows us all the actions possible with the email service.

45. Click the Select button under Actions for the Send Email with Decision Request option.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.15.16-PM-minishadow-1024x557.png

This lets us configure the message action.

46. Click Select or create a new Value for From.
We already have the email service install. We will use the From value configured in the email service. This value contains the email address that will be used to send the mail.

47. Click Select or create a new Value for HTML Body

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.17.54-PM-minishadow-1024x556.png

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.22.23-PM-minishadow-1024x567.png

 

48. Click Create a new Value.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.35.47-PM-minishadow-1024x559.png

 

49. Copy-paste Email approval app: HTML Body in the Name field.

50. The What kind of value is this field should say Content.Copy-paste this text in the Body field: Hi Admin,Could you please provide approval to Insert staging account records.

51.  If we like, we can also style the text, or attach an image or two. Now. This is just one example of a sample approval request.. We can update this value based on our unique needs. For example, we can request a purchase authorization, or a business triprequest, paid time off, and so on and so forth.

52. Click Save.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.41.36-PM-minishadow-1024x558.png

 

53. Click Select or create a new Value for Subject.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.43.31-PM-minishadow-1024x558.png

 

54. Click Create a new Value. 54. Click

55. Copy-paste Email approval app: Subject in the Name field.

56. Copy-paste Approval request in the Default Value field.

57. Click Save.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.45.37-PM-minishadow-1024x558.png

 

58. Click Select or create a new Value for To.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.48.03-PM-minishadow-1024x559.png

 

59. The To value contains the email of the person we want to send the approval request to. Typically, we would have created this value when we were installing the email service to our tenant. Of course, if we like, we can edit/update the To value while we are creating the flow as well.

60. Click Apply Message Action.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.49.55-PM-minishadow-1024x557.png

 

61. Click Save Message.

 

https://docs.manywho.com/wp-content/uploads/2018/02/Screen-Shot-2018-02-23-at-10.51.29-PM-minishadow-1024x559.png

 

62. This is the screen looks like now:

Alright! Now comes the fun part. We will create two steps and two outcomes for the message action. Let’s go with a simple Yes/No scenario. The  outcomes will be automatically included in the email as links for the receiver to click.

If the user approves the request, the flow can take the Yes path and continue right from the user’s Inbox. If the user does not approve the request, the flow is routed to the No path.

Once user approves the request we will route the request to Boomi by using Flow listener.

Boomi will execute the API call which will commit all the staged records in MDM.

MDM Setup:-

1. Now we are going configuring our MDM Solution: creating the Repository.

2. Navigate to the upper right hand side of the platform and hover the cursor over the white Atomsphere dropdown menu.

3. Select the MDM field from the options to switch into the MDM Platform

4. The Repository Tab is the defafult screen for the MDM Platform. Select the ‘Create a Repository’ button to begin.

5. You will be prompted to select an Atom/Cloud to create your MDM repository on and to name it. Select the ‘MDM Cloud’ for the Cloud option and type ‘Contact’ into the Repository Name field.

6. Once you click OK you are now inside the contact repository.

 

 

7. To see the Contact Reposistory from the repository screen, click on the Repositories.

 

 

8. Create a contact model.

9. Click in the Model Name field to create a model name. Enter Contact in to the field.

 

 

10. Click the Add Your First Field button

 

 

11. Once again, since this is the first time you are creating a field, you will be presented with a description of some key information about the fields subtab.

12. Import from Profile, MDM Suggest, and manual entry. It was mentioned earlier we will be basing our Model off of our Contact Record structure imported from flow service.

 

 

13. You will be able to select an XML Profile from your AtomSphere Component Explorer. Navigate through the folder structure and select the MDM contact UPSERT Request Profile and click the Next button.

 

 

14. Next you will be brought to the Choose Model Fields screen. This is where we can select the fields we want to bring in from our data.

 

 

15. You will want to select the checkbox next to Name to deselect all.

16. Reselect the following fields by clicking on the checkbox next to it:

 

 

17. Click Finish when you have selected all the correct fields. Be sure to click the Save as Draft button in the top right of the screen.

18. Set Match Rules

19. By navigating to the Models Tab and select the Match Rules Subtab. Since this is your first time adding a match rule it will provide a small description for you. Click Add Your First Match Rule located at the bottom of the description window. A new window will appear.

20. Confirm that the Top Level Operator is set to AND (this is the default) in the new window.

21. Click the Add an Expression link

 

 

22. Click the Choose field with the magnifying glass to access the drop down menu.

 

 

23. For your first expression select the Name element.

 

 

24. Repeat steps 3 to 5 to match on the Email field for the second expression. Once complete, your Match Rules should look like the image below. Click Save.

 

 

25. Finally be sure to click the green Publish button in the top right of the Model screen. Enter the note of Initial Deployment.

 

 

26. Deploy Model

 

 

27. From the summary window, click the Deploy Your First Model button.

 

 

28. Select the Contact Model for ‘Model Name’ and the most recent version. Once complete click the OK button.

 

 

29. You can confirm that your model has been deployed to your Contact Repository once it appears under the contact repository icon in the left side menu, and within the Summary Sub-Tab screen shown below.

30. Select the Sources tab and click on the Create Your First Source button

 

 

31. The Name field should be populated with MyFlow and the Source ID field should be populated with MyFlow. You will not be using the Entity ID URL field for this exercise.

 

 

32. Now Attach source to contact model

33. Select the Repositories tab and click on the Contact Repository.

34. Next select the Contact Model located on the far left of the screen.

35. Click on the Sources Sub-tab.

36. Click on the Attach a Source button.

 

 

37. You will now be presented with the Attach a Source Screen. Select MySQL for the Source Name and choose the Contribute Data option. Once completed, click Save.

38. Click on the Attach a Source button on the Contact Model screen to configure your MyFlow Source.

 

 

39. Select MyFlow for the Source Name and choose the Both option. Ensure that Channel Updates Contain is set to All Fields. Once completed, click Save.

 

 

40. Click on the Action button next to MyFlow and select the Configure option in the drop-down menu.

 

 

This will make quarantine any records coming into our MDM from MyFlow source.

41. Navigate to the Repository tab, select the Contact Domain, and Sources Sub-Tab.

42. Click the Action button for the MySQL Source and select Enable Initial Load.

 

 

43. Once completed the circle next to the MySQL Source will become blue.

 The status of the source with regard to the domain to which it is attached:

(gray) — neither loaded nor enabled for loading.

(blue) — Initial Load mode is enabled.

(green) — loaded and in a normal, operating state.

(red) — loaded but an error occurred in the processing of a source record update or the propagation of a request on the channel.

44. Navigate to boomi atmosphere Click on the Connector Shape.

45. Click in the search area and search for MDM.

46. Drag the MDM connector to the process canvas. This will open the Connection Shape window.

47. Set the Connector Type to MDM, set Action to Upsert, and click on the green plus sign in the Connection field to create a new MDM Connection.

 

 

This will open up a new connection component window. This is where we will connect our AtomSphere process to our MDM Contact Repository.

48. Rename the connection component: MDM Connection

49. Set the URL field to https://mdm.boomi.com/mdm

 

 

In order to fill out the Username and Token fields, you will need to navigate back into your MDM Repository.

50. Navigate back to the MDM platform and open your MDM Contact Repository. Click on the Configure Sub-Tab.

51. Copy the Username and paste it into the username field in your MySQL MDM Connection Component.

 

 

52. Use the copy button on the right of the MDM Authentication Token field and paste it into the Token Field in your MDM Training Connection Component.

 

 

53. Click Save and Close to return to the MDM Connector shape configuration window.

54. Next, you need to configure the MDM Connector Operation. Click the green plus sign located on the right of the Operation field

 

 

55. Rename the Operation to: MyFlow Contact Upsert and click the blue Import button.

 

 

56. The Import Wizard will appear. Choose the MDM Training connection by clicking the Magnifying Glass and choosing it from the dropdown menu.

57. Type MyFlow into the Source field and click Next

 

 

58. Keep the default values on the next screen, and click Next.

59. Click Finish on the confirmation screen to navigate back to the MySQL Operation screen.

 

 

60. Confirm that your fields match the values shown in the screenshot below. Once complete, click Save and Close.

 

61. Click OK on the final MDM Connector Shape and Save your process on the process canvas.

By here our MDM connection is established now we are going to build integration in atom sphnere.

62. Now we will see how to insert data into MDM repository which was received from boomi flow.

63. Navigate to the File Upload process, which we built in the starting steps.

64. Configure start shape with Flow listener.

 

 

65. Configure the flow operation with below options.

  • Service type :- File Resource
  • File Resource operation :- Upload file
  • Response File :- Select the response file which we used in Filler List Files Process

 

 

66. Drag the map shape into process canvas and click on the +button to create new map.

 

 

67. Create new flat file profile as shown below.

 

 

68. Load MDM Contact request profile on the right side of the map.

 

 

69. To add a new function, click on the blue plus sign in the Functions Title Bar.

 

 

70. Within the Add a Function screen, click on the Category dropdown menu and select String. Look through the Functions that appear and choose String Concat. Click OK once complete.

 

 

71. Keep the Delimiter and Fix to Length fields empty.

72. Click on the plus sign right above the Inputs area.

73. Type First Name and click Add. Repeat and add a Last Name input.

74. Once complete, click the green OK at the bottom of the screen.

 

 

75. Click OK on the following screen.

76. Once complete, it will return you to the MySQL to MDM Map Component.

The function you have just created will take the two inputs mapped to First Name and Last Name and concatenate them together. You can map the result from the Result output to the Destination Profile.

77. The final step is to set up the mappings. Map the following fields from the Source to Destination elements.

 

 

78. Map LAST_NAME to the Last Name element in your function.

79. Map the Function Result to name.

 

 

80. Final process will be looks like below

 

 

Now we have posted the data into staging of MDM. In the next step we are going to develop process, which will convert records from staging to golden records.

 

81. Create a new process and configure the start shape with Flow Listener

 

 

82. Create new listener operation with below values

Service Type :- Message action

Sync Type :- 30 sec

Request profile

 

 

Response profile

 

 

83. Drag a message shape into process canvas and paste the below data in message shape.

 

 

84. In set properties shape you need to configure accountID, Repository ID and UniverseID.

 

 

85. Drag http client into process canvas and create new connection with below details.

 

 

86. Configure the operations like below.

 

 

87. And add the resource path as below.

Account ID, Repository ID and Universe ID should be replaceable values

 

 

Now we need to attach all the shapes from flow listener to http client. And place a return document shape at the end where http client will be connected to return document shape.

Now we are going to test how it is going to work.

Step :1

Go to the URL below

https://flow.manywho.com/78bd8b75-0a44-4ed2-ad49-9a9234c2c0cd/play/default?flow-id=96e6a402-20f5-4bf1-b3f9-ae22adff015e&flow-version-id=57f5c41c-117e-4d35-ab2c-7aa020b6fb99

Then you will find below screen

 

 

Step 2:-

Upload your .csv file. Once you upload it will give you successful message as shown below.

 

 

Step 3:-

Once we click on Go button Mail will be triggered to the concerned person. Person needs to be approved

 

 

Step 4: Once this is approved records will be turned into golden records.

 

 

 

Integrating Boomi flow with boomi atmosphere and MDM

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top