In our RODOD implementation using OSM 7.0.3, we are using the concept of "extensible attributes" intensively.
The concept is great: lots of data coming from Siebel or gathered during the fulfillment process is stored in my order lines' "extensible attributes", almost OOTB, without no need for further customization.
The problem comes when we want to use these extensible attributes in conditions for data jeopardies, change notifications, process branching, etc. All these conditions are configured as "Order Rules", which are based on simple dictionary elements, and which cannot refer to my "extensible attributes" using complex XPath like the following one:
My question is: Is there any way to use complex XPath in "Order Rules" so I can refer directly my "extensible attributes"?
Right now, we are using lots of workarounds to copy the "extensible attributes" in simple order elements, so they can be referred directly from the "order rules". This approach works in a sunny day scenario, but it will bring problems with revisions that are changing the "extensible attributes" but not the simple order elements.
Right now we'll try to use a workaround that doesn't go through low level customization.
The point is that we can do this because our rule is associated to a Jeopardy event. Basically, we'll let the Jeopardy be always triggered and leave the complexity of checking the extensible attributes to the jeopardy's automation.
Unfortunately, this solution only works for rules associated to events triggering any automation. In other cases, your solution should be considered, even if it's not configurable from the design studio.