c# - How the Policy Execution works using FactRetriever? -


I am checking the document for the FactRetriever class by using the following link:

A fact hunter is a component used to record long-term facts in the policy during its execution. . You can apply the IFactRetriever interface and configure a policy version to use this implementation on runline to bring long-term factual examples.

If I'm trying , the invoke the updated facts method of authenticity on each execution cycle.

Business Rule Composer to use independently (not using orchestrations).

Question 1: When does a execution cycle occur? How is this getting started?

  • Is it based on a time interval? If so, is it configurable?
  • Is there a mechanism that executes a policy, if any fact has changed? If so, then what is the answer for then question 2.

Question 2: What is the performance cycle exactly? What is the algorithm?

  • Possible algorithm 1 implements the first policy , during its execution, it will UpdateFacts
  • potential algorithm 2 before UpdateFacts in any way, if some related facts are changed and some policies related to these facts, then they will be executed on converting facts. Will trigger for.
  • A1: You can read that fact every time the policy is executed , The update functions of your implementation method if IFactRetriever is called before any other real rule processing. There is no timer and there really is nothing to configure. Every time this is what it means.

    There is no way to update a long-term fact beyond the policy execution, and there is no reason. Sure, one fact can change, but if the policy is not executed, then this update was a garbage. This is your job, as the implementation of IFactRetriever, to keep track of changes in your facts and to provide the most current facts through update fax. To update a fact, there is no way for the engine or policy to simply 'know'. Technically, the policy is not taken into account that the fact has changed. It will always evaluate the rules based on facts.

    A2: This is just an execution cycle, a single call to the policy, such as by policy. Exam (), by any caller You can see an example here:

    The algorithm is as simple as possible. For our purposes, suppose that updatefax is the first thing that rules engine after doing the rule execute call, if there is a fixed retier course configured. This happens every time the update items are not immediately called at any other point immediately after execution, it is per execution.

    However, it is also worth pointing out that the engine can create many instances of the policy in memory so that they can call multiple callers in the same process (technically, it may be that AppDomain, check Never bothered to do so) Therefore, the updated facts are called for every execution on any instance of the policy.


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -