1. Home
  2. FlexRule Runtime (SDK)
  3. Commands
  4. DRD commands
Searching...

DRD commands

Contents

◷ Reading Time: 2 minutes

DRD

DRD commands allow you model the Decision Requirements Diagram.

Summary

DRD node is the main node in the DRD mode. It contains Nodes element that models the relation between other nodes of the graph.

Parameters

  1. name
    1. Description: Name of the DRD model
    2. Mandatory: Yes
    3. Type: String

Sample

<DRD name="Premium DRD">
  <Nodes>
    <!-- list of other nodes -->
  </Nodes>
</DRD>

Decision

Decision node allows modeling decision logic relations and hierarchy. A decision node can reference any other logic document for execution.

Parameters

  1. name
    1. Description: Name of decision node
    2. Mandatory: Yes
    3. Type: String
  2. uri
    1. Description: Address of the logic document to be referenced to the decision node
    2. Mandatory: No
    3. Type: string (relative address to the logic file)
  3. type
    1. Description: Defines the type of the referenced logic document
    2. Mandatory: No
    3. Type: string of Tree, NaturalLanguage, Flow or DecisionTable. When left blank DecisionTable is by default.

Sample

<DRD name="Premium DRD">
  <Nodes>
    <Decision name="Premium" />
    <Decision name="Determine Rating">
      <Transition name="Transition8" to="Auto Premium" relationType="Information" />
    </Decision>
    <BusinessKnowledge name="Define Potential Theft Rating" uri="PotentialTheftRating.xml">
      <Transition name="Transition3" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <BusinessKnowledge name="Define Potential Occupant Injury Rating" uri="PotentialOccupantInjuryRating.xml">
      <Transition name="Transition4" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <KnowledgeSource name="KnowledgeSource1">
      <Transition name="Transition5" to="Premium" relationType="Authority" />
    </KnowledgeSource>
    <Decision name="Auto Premium" uri="Auto-no-style.xml">
      <Transition name="Transition7" to="Premium" relationType="Information" />
    </Decision>
    <Decision name="Base Premium" uri="Base.xml">
      <Transition name="Transition6" to="Premium" relationType="Information" />
    </Decision>
    <InputData name="car" isOutput="True">
      <Transition name="Transition9" to="Determine Rating" relationType="Information" />
      <Transition name="Transition11" to="Base Premium" relationType="Information" />
      <Transition name="Transition14" to="Decision5" relationType="Information" />
    </InputData>
    <InputData name="probList">
      <Transition name="Transition12" to="Determine Rating" relationType="Information" />
    </InputData>
    <Decision name="Decision5" uri="Auto-Tree.xml" type="Tree">
      <Transition name="Transition15" to="Auto Premium" relationType="Information" />
    </Decision>
  </Nodes>
</DRD>

BusinessKnowledge

BusinessKnowledge node allows modeling Business Knowledge logic relations and hierarchy. Similar to decision node it node can reference any other logic document for execution.

Parameters

  1. name
    1. Description: Name of BusinessKnowledge node
    2. Mandatory: Yes
    3. Type: String
  2. uri
    1. Description: Address of the logic document to be referenced to the decision node
    2. Mandatory: No
    3. Type: string (relative address to the logic file)
  3. type
    1. Description: Defines the type of the referenced logic document
    2. Mandatory: No
    3. Type: string of Tree, NaturalLanguage, Flow or DecisionTable. When left blank DecisionTable is by default.

Sample

<DRD name="Premium DRD">
  <Nodes>
    <Decision name="Premium" />
    <Decision name="Determine Rating">
      <Transition name="Transition8" to="Auto Premium" relationType="Information" />
    </Decision>
    <BusinessKnowledge name="Define Potential Theft Rating" uri="PotentialTheftRating.xml">
      <Transition name="Transition3" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <BusinessKnowledge name="Define Potential Occupant Injury Rating" uri="PotentialOccupantInjuryRating.xml" >
      <Transition name="Transition4" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <KnowledgeSource name="KnowledgeSource1">
      <Transition name="Transition5" to="Premium" relationType="Authority" />
    </KnowledgeSource>
    <Decision name="Auto Premium" uri="Auto-no-style.xml">
      <Transition name="Transition7" to="Premium" relationType="Information" />
    </Decision>
    <Decision name="Base Premium" uri="Base.xml">
      <Transition name="Transition6" to="Premium" relationType="Information" />
    </Decision>
    <InputData name="car" isOutput="True">
      <Transition name="Transition9" to="Determine Rating" relationType="Information" />
      <Transition name="Transition11" to="Base Premium" relationType="Information" />
      <Transition name="Transition14" to="Decision5" relationType="Information" />
    </InputData>
    <InputData name="probList">
      <Transition name="Transition12" to="Determine Rating" relationType="Information" />
    </InputData>
    <Decision name="Decision5" uri="Auto-Tree.xml" type="Tree">
      <Transition name="Transition15" to="Auto Premium" relationType="Information" />
    </Decision>
  </Nodes>
</DRD>

InputData

InputData node allows modeling the requirement for input data all through out the DRD.

Parameters

  1. name
    1. Description: Name of the InputData node. This simply can reference to a Parameter name.
    2. Mandatory: Yes
    3. Type: String
  2. uri
    1. Description: Address of the logic document to be referenced to the decision node
    2. Mandatory: No
    3. Type: string (relative address to the logic file)
  3. type
    1. Description: Defines the type of the referenced logic document
    2. Mandatory: No
    3. Type: string of Tree, NaturalLanguage, Flow or DecisionTable. When left blank DecisionTable is by default.

Sample

<DRD name="Premium DRD">
  <Nodes>
    <Decision name="Premium" />
    <Decision name="Determine Rating">
      <Transition name="Transition8" to="Auto Premium" relationType="Information" />
    </Decision>
    <BusinessKnowledge name="Define Potential Theft Rating" uri="PotentialTheftRating.xml">
      <Transition name="Transition3" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <BusinessKnowledge name="Define Potential Occupant Injury Rating" uri="PotentialOccupantInjuryRating.xml" >
      <Transition name="Transition4" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <KnowledgeSource name="KnowledgeSource1">
      <Transition name="Transition5" to="Premium" relationType="Authority" />
    </KnowledgeSource>
    <Decision name="Auto Premium" uri="Auto-no-style.xml">
      <Transition name="Transition7" to="Premium" relationType="Information" />
    </Decision>
    <Decision name="Base Premium" uri="Base.xml">
      <Transition name="Transition6" to="Premium" relationType="Information" />
    </Decision>
    <InputData name="car" isOutput="True">
      <Transition name="Transition9" to="Determine Rating" relationType="Information" />
      <Transition name="Transition11" to="Base Premium" relationType="Information" />
      <Transition name="Transition14" to="Decision5" relationType="Information" />
    </InputData>
    <InputData name="probList">
      <Transition name="Transition12" to="Determine Rating" relationType="Information" />
    </InputData>
    <Decision name="Decision5" uri="Auto-Tree.xml" type="Tree">
      <Transition name="Transition15" to="Auto Premium" relationType="Information" />
    </Decision>
  </Nodes>
</DRD>

Transition

Transition allows connecting different nodes with different type of dependencies:

  1. Information
  2. Knowledge
  3. Authority

Depends on type of the node origin and destination, different type of transition is required.

Parameters

  1. name
    1. Description: Name of the dependency (transition)
    2. Mandatory: Yes
    3. Type: String
  2. type
    1. Description: Type of dependencies
    2. Mandatory: Yes
    3. Type: Information, Knowledge or Authority

Sample

<DRD name="Premium DRD">
  <Nodes>
    <Decision name="Premium" />
    <Decision name="Determine Rating">
      <Transition name="Transition8" to="Auto Premium" relationType="Information" />
    </Decision>
    <BusinessKnowledge name="Define Potential Theft Rating" uri="PotentialTheftRating.xml">
      <Transition name="Transition3" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <BusinessKnowledge name="Define Potential Occupant Injury Rating" uri="PotentialOccupantInjuryRating.xml" >
      <Transition name="Transition4" to="Determine Rating" relationType="Knowledge" />
    </BusinessKnowledge>
    <KnowledgeSource name="KnowledgeSource1">
      <Transition name="Transition5" to="Premium" relationType="Authority" />
    </KnowledgeSource>
    <Decision name="Auto Premium" uri="Auto-no-style.xml">
      <Transition name="Transition7" to="Premium" relationType="Information" />
    </Decision>
    <Decision name="Base Premium" uri="Base.xml">
      <Transition name="Transition6" to="Premium" relationType="Information" />
    </Decision>
    <InputData name="car" isOutput="True">
      <Transition name="Transition9" to="Determine Rating" relationType="Information" />
      <Transition name="Transition11" to="Base Premium" relationType="Information" />
      <Transition name="Transition14" to="Decision5" relationType="Information" />
    </InputData>
    <InputData name="probList">
      <Transition name="Transition12" to="Determine Rating" relationType="Information" />
    </InputData>
    <Decision name="Decision5" uri="Auto-Tree.xml" type="Tree">
      <Transition name="Transition15" to="Auto Premium" relationType="Information" />
    </Decision>
  </Nodes>
</DRD>

Updated on July 31, 2019

Was this article helpful?

Yes No

Related Articles