WF Rules worth noting: Reference judgment and endless Loops

• In the WF environment, it is easy to cause an endless loop, because according to the forward-channing reasoning principle, a rule can trigger itself, in which case it will cause an endless loop: IF this. disCount = 10 THEN this. disCount = 10 this statement can easily cause an endless loop. In addition, when there are two or more Rules, it is easy to cause an endless loop:
  R1: IF this. Name! = "Headchen" THEN this. disCount = 10
  R2: IF this. disCount = 10 THEN this. Name = "minnie"
• WF's judgment on Object attribute reference is limited to the attribute itself. When a set attribute, such as an array or dictionary, changes will be deemed as a holistic change, triggering relevant rules, ignore other call parameters. For example, a property of the Dictionary type, regardless of whether an Action triggers any of the items, WF considers that the entire Dictionary property has been changed and does not identify which item, the same applies to arrays.