Hi,

When am testing transaction, I see for some in TN , “User Status” is UNMATCHED/IGNORED. Those transactions invoked the “Default Rule”.

Any reason for this?

Rgds,
Sam.

That means this document doesn’t match any of the existing processing rules.
If you want to invoke service or some other action, create a rule for this doc.

Also do make sure your custom rule is above the Default rule to get it triggered and recognized:

HTH,
RMG

i have similar thing in our environments…

in default processing rule we set that ‘User Status’ as IGNORED. But we are getting UNMATCHED in one of our environment and IGNORED in one of the other environment, but both env uses the same set of rules & document types etc.,

Why is it?

Thanks

You shouldn’t be using or changing any Default rule status’s and do you have any custom rule set in env’s?

HTH,
RMG

Hi,

Actually when we used the sample data in QA severs it’s showing it as UNMATCHED but not in performance server(getting it as IGNORED. Which is as expected).

Yes in Default Rule, we set the “Change User Status” as IGNORED. Verified the profile, doc type, Rule, no luck…

Any idea on this?

Rgds,
Sam

Hi,

Verified all the stuff, missed to check the Default rule Active/In-Active state. Once we enabled this. Issue resolved (as expected IGNORED has been updated in USERSTATUS).

thanks,
sam.

Here you go…good deal: