Boomi process extensions allow developers to extend the process parameters based on the environment it is running on. It allows a process to connect to test systems when executing on a test environment and production systems on a prod environment. For this article, I am going to assume you have basic knowledge of process extensions. If you are new to this functionality, you can find more details at https://help.boomi.com/bundle/integration/page/c-atm-Process_extensions.html. While I believe the test/prod environment was the biggest reason for this feature, I would like to argue that it should be used across all processes, even in a single prod environment.
The process extensions allow changing process behavior without re-deployment. The benefits of this are endless. You can apply hotfixes or change the component behavior, such as connection credentials, cross-reference table, and many more. Imagine a system that must change credentials every two months. With this feature, you can write a few steps. A business user (non-Boomi developer) can follow them to update the credentials. Imagine a cross-reference table that is being managed by a business user. They can update the extended cross-reference table with a few steps.
Without the process extensions, the processes are static in terms of endpoints they connect to or the cross-reference table it is using. This functionality not only allows manual updates to extension values, but you can also use the AtomSphere API to automate the extensions management. Imagine a client using a password orchestration tool to manage and update API/Database credentials on a defined interval. The password orchestration tool can use AtomSphere API to auto-update the credentials on the extension objects.
Process extensions are a valuable part of Boomi. Developers should take advantage of it. I am excited to learn how you used environment extensions in your development. Please leave a comment and let me know what topic you would like me to cover next?
Comments
Post a Comment