Use of Message Shape During Boomi Process Testing 

After the Boomi integration process is developed, while testing multiple sub-process calls if any changes are required or if testing is required only for a particular sub-component, Message Shape can meet the requirements. There is no need for testing end-to-end flow if changes need to be tested and verified for a particular process or sub-flows to validate the changes. With the use of Message shape, the following can be achieved 

1. Required data can be passed to the next shape
2. Modified data can be supplied on the fly
3. Testing from Source connector data might take more time than can be saved
4. Ability to test multiple flows using different test data supplied to each message shape in the flow

To test the process flow or changes in the Boomi platform, the content will be added in the message field of the Message Shape and it will be connected to the next shape. Below are different scenarios with different message types to test with Message Shape 1. JSON Message:  For testing with JSON messages, use single quotes. Ex: ‘{ “FirstName” : “Russell”, “LastName” : “Crowe” }’ 2. XML Message:  Use original XML message that contains &, < and > with double quotes (“) in the top line of XML directly in the Message shape. The Message shape will not take single quotes in XML. Ex: <?xml version=”1.0″ encoding=”UTF-8″?> <root> <row> <userId>1</userId> <parentid>1</parentid> <title>delectus aut autem</title> <status>false</status> </row> </root> 3. EDI or Flat file Message:  Copy actual EDI or Flat file message without any modifications into Message shape. If EDI data contains single quotes, use an extra single quote to escape it. Ex: (a) X12 message (truncated) ISA*00*0000000000*00*0000000000*08*4532345856 *12*8038025150 *020624*1158*U*00401*000000009*0*P*>~ GS*PO*4532345856*8038025150*20020624*1158*2*X*004010~   (b)EDIFACT message (truncated) UNB+UNOA:1+US::US+50138::THEM+140531:0305+001934++ORDERS UNH+1+ORDERS:91:2:UN BGM+220+A761902+4:20140530:102+9′ ’ 4. Database Message:  When testing with DB message, component ID (after DBSTART and DBEND) needs to be replaced with new DB profile component ID need to be replaced if the profiles are copied during testing. Eg: DBSTART|828ac9d7-8334-44e0-8739-4139cf86f2e5|2|@|BEGIN|2|@|OUT_START|3|@|1259|^|20201209 182925.764|^|Alex Jr|^|1111111|#||#|OUT_END|3|@|END|2|@|DBEND|828ac9d7-8334-44e0-8739-4139cf86f2e5|2|@| In the above example, the bold text needs to be replaced with the component ID of the new DB profile