This is a quick follow up to a comment posted on the original thread – I had a discussion with some people about the post, and was asked the following (hence the new post): “Can we use wma.name = ‘RESULT’ instead of wma.subtype=’RESPOND’ as each message that requires a RESPONSE action will have RESULT attribute?”. Here’s my response:
Not every message that requires a response will have a RESULT attribute, though. The RESULT attribute only applies to notifications which have conditional branching based on a result applied to them.
If you have no result type, but have respond attributes, then the notification still requires a response but does not have a result.
Have a look at this test flow for an example. Launching the flow and then selecting from the WF_NOTIFICATION_ATTRIBUTES table returns one row for the attribute IA1 – there is no RESULT attribute since the notification does not have a result.
Here’s the output:
**** Notifications NID Context Status ----- --------------- -------- 40899 NEW_TYP4:1:1692 OPEN SELECT notification_id, NAME FROM wf_notification_attributes WHERE notification_id = 40899 / NOTIFICATION_ID NAME --------------- ---- 40899 IA1
So, although the notification requires a response, there is no RESULT attribute, and it’s certainly not uncommon to have notifications and messages defined in this way – if the requirement is to capture a response, but not to branch conditionally depending on the result, this is the way to build the Workflow.