Reusable Content

Keeping yourself DRY makes things more simple.

In order to keep up with DRY principle (Don't Repeat Yourself), Frends includes Subprocesses and Environment Variables to allow defining functionality and values once and reusing them in your Processes.

Subprocesses

Subprocesses in Frends are like building blocks that help simplify complex integrations. They're reusable bits of Tasks and logic that you can run across different Processes. By breaking things down, Subprocesses make everything easier to manage, share, and update, allowing team members to independently tackle different parts of a project.

Subprocess calls can be used similarly to Tasks. They contain Process logic similar to the main Processes.

Basically the only differences between "Main Processes" and Subprocesses are that you can only define a single manual Trigger, which is used to provide parameters to the Subprocess to work on, and that Subprocesses can be called from Processes and other Subprocesses, while Processes cannot. Subprocesses can also be called on unhandled errors from Processes, making them the catch-block error handlers.

Error handler Subprocess can be used to process errors, that were not handled during Process execution.

Environment Variables

In case it is global values you need in multiple Processes, or values that are Environment specific, such as different credentials and connection points for testing and production, Environment Variables are there to take care of them.

Environment Variables are the global values for each Environment.

Environment Variables are defined centrally in the Environment Variables section of Frends Control Panel, and can hold groups of values for different purposes. Values can be grouped together by their purpose, such as per target system or for specifically global error handling, and the values themselves can be textual, numerical, lists or secrets.

As the key feature of Environment Variables, each Environment in your Frends Tenant can receive separate values for the same variable. This makes it easy to develop and test the integrations using test values and other test environments, and when the Process is ready, it can be deployed to production without any changes to the Process itself, because the Environment-specific values are defined separately and centrally in Environment Variables.

Using Environment Variables is recommended for example for connection parameters.