routing Flashcards
a rule set is made up of
a constraint
a condition
and actions
What do constraints do?
check attributes of messages coming in
What do conditions do?
look inside the message and route based on content
when are routing actions performed?
if conditions and constraints are true
If there is a return at the end of a rule
if conditions and constraints are true, the routing engine will stop processing and will not attempt to evaluate more rules
source is
the business service that sent the message to the routing engine
HL7 schema is controlled by what constraint?
docCategory
message type is controlled by what constraint?
docName
the target field
indicates where a message is sent if constraints and conditions are met
transform
applies a data transformation (dtl) before sending to the target
how would you navigate to the rule editor
ensemble
build
business rules
or
select a business process in a production
click on the magnifying glass next to business rule name on the settings tab
To match on a non-repeating HL7 message field in the expression editor, start typing
HL7.{
how do you open the expression editor?
double click the condition field in a rule
what icon lets you choose functions to use in your expression?
fx
what icon lets you choose operators to use in your expression?
op
to route a message if constraints and conditions are met
click on when plus sign send specify the target(s) save
how would you test a routing rule
Ensemble Test Business Hosts choose target type (business process or business operation) choose target name from dropdown test add test message invoke testing service
To match on a repeating HL7 message field in the expression editor, start typing
HL7.(
how would you make a condition case insensitive using the expression editor?
click on the condition field that references the HL7 segment
click the function dropdown
choose ToLower
make sure the value being checked is lowercase
if you want to check all rules,
do not provide a return action within any of the rule clauses.
You may then provide a value in a return action at the end of the rule set for the case where no rule clauses evaluate to true.
The business rule log
is a persistent record of business rules that have been executed, their respective results, and reasons for the result.
Ensemble > View > Business Rule Log
assign
Assigns values to properties in the business process execution context. For details see the entry in the Ensemble Business Process Language Reference.
return
Returns to the business process without further execution of the rule set. For general rules it also returns the indicated value to the result location.
trace
Adds the information you enter into the Event Log when this specific part of the rule is executed. For details see the entry in the Ensemble Business Process Language Reference.
debug
Adds the expression text and value to the Rule Log when this specific part of the rule is executed. The debug action is executed only if the router business process RuleLogging property specifies the d flag, For details on the RuleLogging property, see “Rule Logging ” in Ensemble Virtual Documents.
send
Sends the message to a particular target after optionally transforming it. See “Selecting the Transformation and Target of a Send Action” for details.
delete
Deletes the current message.
delegate
Delegates the message to a different rule.
an HL7 Sequence Manager
is a business process that accepts incoming HL7 messages (possibly from multiple sources), then forwards the messages to a target configuration item in the order specified by the MSH:13 SequenceNumbers field in the messages.
d in validation
examines the DocType property of the document to see if it has a value.
m in validation
verifies that the document segment structure is well formed, and that it can be parsed using the schema identified in the DocType property of the document.
1 in validation
same as dm, examines doctype and segment structure
