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?
The presentation focused on the importance of thoughtful, timeless design, particularly as it applies to technology and data platforms. Using both humorous and serious real-world design examples, the speaker highlighted that great design must be simple, resilient, adaptable, and enable innovation. These principles are foundational to InterSystems IRIS, which was built to efficiently store and process any type of data, support powerful analytics and AI, and ensure interoperability and scalability without compromising performance.
Presenters: 🗣 @Scott Gnau, Head of Data Platforms, InterSystems 🗣 Peter Lesperance, Senior Director of Performance Engineering, Epic 🗣 @Tom Woodfin, Director of Development, Data Platforms, InterSystems 🗣 @Gokhan Uluderya, Head of Product Management, Data Platforms, InterSystems 🗣 @Jeff Fried, Director of Platform Strategy, InterSystems 🗣 @Daniel Franco, Senior Manager of Interoperability Product Management, InterSystems
Ready to join the conversation? Watch the video and subscribe for updates!
Open Exchange