Is it possible to send in different context request classes to the same BPL?

Question

Question

The default request class, Ens.Request is fine for our initial workflow.

We want to define other workflows that will reuse the same BPL class. These workflows would send messages inbound to the BPL as different request classes.

Is this possible or is it required that we send in a request class matching the context request class in the context tab?

Thank you

Product version: IRIS 2022.1

$ZV: IRIS for Windows (x86-64) 2022.1 (Build 209_0_22239U) Wed Mar 1 2023 17:38:58 EST [Health:3.5.0]

Discussion (3)3

Log in or sign up to continue

Luis Angel Pére... · Sep 30

If the class of the message extends Ens.Request you can send whatever you want. To validate the class of the message you only need $CLASSNAME method.

1 0

Kurro Lopez · Sep 30

if you are using Ens.Request as request class, you can redirect you message acording the name of the class using "Switch"

On each switch connector, you must evaluate the class name, as follows:

$classname(request)="MyApp.Msg.Test1"

I hope this is the answer that you are looking for

Best regads

1 0

score 0 · Answer 1 · 2025-09-29T18:47:03-04:00

Yes, it is possible to send different request classes to the same BPL. You can define a BPL process and set its "Request Class" property in the "Context" tab of the BPL designer. This allows the BPL to handle incoming requests of different types as long as they adhere to the defined structure and logic within the process. You can also use context properties or logic within the BPL to handle variations based on the actual type of the request received [1][2].

Sources:

1.Editing a BPL Business Process | Developing BPL Processes | InterSystems IRIS Data Platform 2025.1

2.Introduction to BPL Processes | Developing BPL Processes | InterSystems IRIS Data Platform 2025.1