Boomi Lesson Learned

Posted on June 11, 2014 at 4.30 PM - Kuala Lumpur, Malaysia

After doing Boomi for few months in the project, following are lessons learned which I have picked up:

1. For complex interface, it's better to have test mode parameters rather than to change the process steps or steps properties all the time which is prone to error. This is especially true when the same parameters could be used by support team to debug the process in the future after deployment to production.

2. It's better to create sub process for steps which may be shared or reusable by other interfaces rather than copying the steps over to other process. By doing that, the maintenance effort can be put to minimum.

3. It's always good to provide visibility of the parameters set in the environment setting or dynamically in the process steps and scripting through the use of Notify step. This is very helpful for support team to understand as to why certain run might have been behave differently.

4. Even though the Notify step has the message level 'ERROR', unfortunately when it's used it does not create an exception, thus the interface still being shown as run successfully. To improve the visibility, all the exceptions in the process has to be flagged with Exception step.

Life is beautiful! Let's make it meaningful and colorful!