Condition Editor -- PI7.1

[Former Member]

Hello XI'ers,

I am working with PI7.1 and getting mad with the condition Editor from the new System:

my Payload will look like:

<?xml version="1.0" encoding="UTF-8" ?> 
<Receive_MT>
 <entityList>
    <entity>
         <attribute name="version" system="AE6" value="0" /> 
         <error>Error Happened</error>
     </entity>     
 </entityList>
</Receive_MT>

once I have this payload in my process, I am doing a switch based on a condition "if error node exist then cancel the process else not"

Condition look like: (respronse/Receive_MT/entityList/entity/error EX)

If I look in the monitoring, my payload has no "error node" it means process should continue but process is canceled saying "error node" exist in the payload.

It look likes, my condition is wrong. can somebody able to correct my condition?

Thanks & regrads,

Satish.

[Former Member]

Hi Satish,

Are you using the BPM process. can you explain more on the scenario?

Thanks,

Raj

[Former Member]

Hi Satish,

the use of context objects and the value help for xpath is available for XI3.0 interfaces in PI 7.10 only. The functionality for "new" interfaces has been implemented in 7.11 only.

you have to use xpath w/o value help.

I have created a context object in one of our 7.10 test systems, and indeed I was unable to use it in a receiver determination unless the service interface pattern is "Stateles (XI 3.0 compatible)". If you were to change the service interface to that pattern, you have to change the operation name unless it is already identical to the interface name. So that may not be an option for you.

It was possible to use the context object in a receiver rule but then I could not activate the receiver determination because the software component version was supposedly unknown. I will check with my PI contacts - please let me know if the change to "XI 3.0" interface would be a possible workaround for you.

Try the steps which I am giving below, although it's a workaround and don't know the exact reason why it is failing.

1. Open your Outbound Message Interface (which you are using in your Receiver Determination) in IR, edit it and change the Interface pattern (which is there just below the category "Outbound") to "Stateless (XI30 - Compatible)" , save it activate it.

2. Follow the same step for your Inbound Message Interface. Change the Interface Pattern from "Sateless" to "Stateless (XI30 - Compatible)" .

3. Go to ID. Remove your Outbound and Inbound Message Interface from their respective Business Service/Comp and add it again.

4. Create your your receiver determination again using the Outbound and Inbound MI you have changed.

5. Open condition editor of your receiver determination.You should be able to see your Message Interface and can choose the XPath.

Thanks,

Raj

[Former Member]

Hi,

Seems a cache issue. In ID from menu Environment --> Clear SLD Data Cache and then try it again.

Regards,

Sarvesh