> For the complete documentation index, see [llms.txt](https://docs.justransform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.justransform.com/development/business-processes/components-of-business-process.md). # Components of Business Process **Justransform Business Process (BP)** is complete encapsulation of a all message processing and business rules that needs to get applied over a set of messages received by a connection. The Business Process Editor allows users to implement these rules by utilizing different components of the **BP.** Once you get familiar with the editor and the components you can virtually implement any simple to complex logic to for any message processing rules. The following components are available Map/MapChain/JTScript (Custom Function) JTUtils EditSyncResponse Conditional Fork IF Condition (CBR) Content Based Routing EDI to XML Transformation XML to EDI Transformation Insert Business Process Import Business Process Set File Name Set Business IDs Set Source Target Data Type HL7EDI to XML Transformation 997 Response Generation CSV to XML Transformation XML to CSV Transformation IDOC to XML Transformation PDF to XML Transformation --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.justransform.com/development/business-processes/components-of-business-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.