Low-code Development
We have visual process editor, enhanced with C# code.
Frends uses BPMN 2.0 notation to define APIs, integrate systems, and automate processes. Frends provides enhancements to the notation with Handlebars-enabled C# programming, making it possible to create most anything that is visually pleasing, easy for non-programmers to read and understand, and requiring only minimal programming by the developer.
Process Editor
At the core of Frends is our prized Process Editor, which utilises BPMN 2.0 notation to create the integration flows or Processes. With the drag and drop editor, it is easy to both visualize what is happening and in what order, as well as create the logic to do exactly what you want and need to do. No coding expertise required to understand the Processes.

When you save a Process, it is validated and compiled to C# — meaning syntax errors and type mismatches are caught immediately, alongside BPMN flow errors. Expressions, Handlebars, and dynamic types are only evaluated at runtime, so errors such as a null value or an unexpected data shape will surface during execution rather than on save.
Coding features
While most of the logic can be done with only the graphical elements, including the powerful Tasks to perform pre-defined actions, Frends is specifically a low-code platform for integrations. Thus, if you need and want to, you can include C# code in the Processes to fine tune more complex logic.

Code can be included as separate shapes to perform actions in task-like manner.
Use an Assign Variable shape to compute a single value and reuse it across the Process, or a Code Task when you need multi-line C# logic.
For shorter needs, you can include small pieces of code into any text, JSON, or XML field using Handlebars syntax to inject values inline. If a field needs to return a specific type rather than plain text, switch it to Expression mode instead.
If advanced programming or external libraries are needed, or the action could be useful to others beyond the current Process, consider building a Custom Task.

And finally, Reference values allow you to access data from across the Process using a simple hashtag notation. #trigger gives you data from the event that started the Process, #var holds variables you have defined or computed during the flow, and #env provides Environment Variables that are centrally managed and can differ between Environments like development and production. These are available Process-wide and work just like variables in standard C# code.
Last updated
Was this helpful?

