|
Home > Archive > BizTalk Server General > January 2006 > Rule fires sometimes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Rule fires sometimes
|
|
|
| I have a rule that test for existence of one node and not existence of a 2nd
node. If the condition is true, then the action is to add a
"processingStatus" node and then a "status" child of that (via a .NET
assembly). So far so good. If I test the rule, it works fine and the xml
instance document now has a processingStatus node with a status child.
The problem occurs if I try to assign a value to the status node. If I add
a third action to set the status, the agenda does't get updated and the rule
doesn't fire UNLESS the processingStatus and status nodes already exist in
the input XML instance.
I've tried asserting and updating after adding the nodes but can't get the
rule to fire. Can someone tell me what I'm missing here?
Thanks
Tom
| |
| Leonid Ganeline 2006-01-30, 5:53 pm |
| Do you "assert" the new node?
| |
|
| Yes, I tried assert as well as update. Still can't get the rule to fire even
though the conditions evaluate to true.
I also tried adding 2 new rules with a higher priority that add the parent
and child nodes respectively and tried asserting and updating there but still
have the same problem where trying to populate the node prevent the rule from
firing.
"Leonid Ganeline" wrote:
> Do you "assert" the new node?
>
|
|
|
|
|