Process Property components.

What precisely are Dell Boomi's Process Property Components: Process properties are name/value pairs that can be used to store arbitrary information to assist with an integration project. You can set a property value in the beginning of the process and then retrieve it later in a different part of the process. According to the examples provided in the subject "Process Properties," process properties are a straightforward yet effective feature that may be utilized to simplify a variety of typical integration scenarios.

There are two types of process properties: Process Property components and dynamic process properties. Both types of process properties are used for the same purpose, but they are created differently.

• Process Property components are more powerful and are easier to work with. They are reusable components that can consist of a collection of properties.
• A dynamic process property is a single “on-the-fly” property that you create.

Process properties have an execution scope, which means that if a property is accessed or set, it is valid only for the length of the execution of the current process. As is typical in parent/child process designs, this also implies that the attributes are accessible across additional processes started using the Process Call or Process Route structure. A process property value, for instance, that was accessed or set in a parent process can be later retrieved in a child process. A process property value set or updated in a child process can, however, subsequently be retrieved in the parent process once the child execution is finished. Here are a few warnings:

• The same process attributes in memory are not shared by two separate processes operating at the same time. Process property values specified in one process that are scheduled to run concurrently with another process, for instance, are not accessible to the other process.
• If your process uses the Flow Control shape to introduce parallel processing, process property values set in one thread/process are not available in the other concurrent threads/processes.
• If your process uses a Process Route shape, the execution scope of process properties is maintained even though the parent process and child processes are deployed independently. Once a process property value is accessed or set, all default or extended values for that property in any process or subprocess are ignored. The only way to change that process property is to reset it explicitly, as described below.

Process properties can be retrieved from:

• the parameter value list for most process shapes.
• the Get-Process Property map function.
• a custom scripting step or custom scripting map function.

Process properties can be set in:

• the Set Properties shape.
• the Set Process Property map function.
• a custom scripting step or custom scripting map function.

You can also choose to persist a property value - that is, make the value available in subsequent process executions.?However, using persisted process properties in processes that allow simultaneous executions is not recommended.

Process properties can be defined as process extensions. This allows you to essentially parameterize different points in the process during configuration and defer specifying a value to deploy time. This is most often used in the context of environments to configure environment-specific settings or preferences (such as test versus production flags or other hard-coded values).

Reference: https://boomi.com/platform/

Signing Off

These are the main points I'd want to convey in this post. In the future, I'll aim to provide more articles like this on cloud integration, cloud integration tools, and related topics. If you found this post helpful in developing your cloud integration thoughts, please Like and share it with your friends.

Keep learning and diving deep!