What is a Business Rules Engine?

The Business Rules Framework is a Microsoft .NET-compliant class library. It provides an efficient inference engine that can link highly readable, declarative, semantically rich rules to any business objects (.NET components), XML documents, or database tables.

Application developers can build business rules by constructing rules from small building blocks of business logic (small rule sets) that operate on information (facts) contained in .NET objects, database tables, and XML documents. This design pattern promotes code reuse, design simplicity, and molecularity of business logic.

A run-time inference engine that can link highly readable, declarative, semantically rich rules to any business objects (.NET components), XML documents, or database tables. It can evaluate rules against facts and initiate actions based on the results of that evaluation.

What is Fact Explorer of Rule composer containing?

  • A.      Vocabularies
  • B.      Schemas
  • C.      Databases
  • D.      .Net Assemblies

What is a Business Rule Language?

It is a rule markup language in XML format for declarative rule definitions.

How can I execute a Business Rule in my orchestration?

Using the Call Rules Shape. See more here   .

What is used to create new vocabulary definition?

 The Vocabulary Definition Wizard is used to create vocabulary definitions.

What is a Policy?

A policy is a logical grouping of rules. You compose a version of a policy, save it, test it by applying it to the facts, and, when you are satisfied with the results, publish it and deploy it to a production environment. See more here   .

Is it possible to change Business Rule policy after it was published?

No. After policies are published it can’t be edited. But if there is a need to have a change in policy then new version of policy is to be created.

Does rule composer have provision of adding ELSE logic?

No, there is no provision of adding ELSE but else logic can implemented with extra IF.

What is Long term fact and Short-Term fact?

The fact is the user data to which rule conditions are applied. At design time a fact is a reference to that data.
Facts have two categories – Short Term Facts and Long-Term Facts. Consider a loaning process of any Bank. We can think a “loan application” as short-term fact. Short team facts are business information which changes per occurrence. On the contrary, “interest rates” do not change very regularly. This business information is steady, and we can consider it a long-term fact. See more here   .

What is the difference between Publishing and Deploying the Rule?

Rule alone cannot be published or deployed, it must be wrapped under Policy and then published and deployed. When a policy is deployed it is ready to use and can’t be edited whereas when published, policy isn’t ready for use.

Can we call policies from .Net code?

Yes. Firstly, it needs to be declared (policy name which is to be called), passed in the fact instance and finally executed. 

Below links are available for other segment of Interview questions and Answers:

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s