Is it possible to send in different context request classes to the same BPL?
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
Comments
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:
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.
if you are using Ens.Request as request class, you can redirect you message acording the name of the class using "Switch"
.png)
On each switch connector, you must evaluate the class name, as follows:
$classname(request)="MyApp.Msg.Test1".png)
I hope this is the answer that you are looking for
Best regads