routing

Question 1

a rule set is made up of

Answer 1

a constraint
a condition
and actions

Question 2

What do constraints do?

Answer 2

check attributes of messages coming in

Question 3

What do conditions do?

Answer 3

look inside the message and route based on content

Question 4

when are routing actions performed?

Answer 4

if conditions and constraints are true

Question 5

If there is a return at the end of a rule

Answer 5

if conditions and constraints are true, the routing engine will stop processing and will not attempt to evaluate more rules

Question 6

source is

Answer 6

the business service that sent the message to the routing engine

Question 7

HL7 schema is controlled by what constraint?

Answer 7

docCategory

Question 8

message type is controlled by what constraint?

Answer 8

docName

Question 9

the target field

Answer 9

indicates where a message is sent if constraints and conditions are met

Question 10

transform

Answer 10

applies a data transformation (dtl) before sending to the target

Question 11

how would you navigate to the rule editor

Answer 11

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

Question 12

To match on a non-repeating HL7 message field in the expression editor, start typing

Answer 12

HL7.{

Question 13

how do you open the expression editor?

Answer 13

double click the condition field in a rule

Question 14

what icon lets you choose functions to use in your expression?

Answer 14

fx

Question 15

what icon lets you choose operators to use in your expression?

Answer 15

op

Question 16

to route a message if constraints and conditions are met

Answer 16

click on when
plus sign
send
specify the target(s)
save

Question 17

how would you test a routing rule

Answer 17

Ensemble
Test
Business Hosts
choose target type (business process or business operation)
choose target name from dropdown
test
add test message
invoke testing service

Question 18

To match on a repeating HL7 message field in the expression editor, start typing

Answer 18

HL7.(

Question 19

how would you make a condition case insensitive using the expression editor?

Answer 19

click on the condition field that references the HL7 segment
click the function dropdown
choose ToLower
make sure the value being checked is lowercase

Question 20

if you want to check all rules,

Answer 20

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.

Question 21

The business rule log

Answer 21

is a persistent record of business rules that have been executed, their respective results, and reasons for the result.

Ensemble > View > Business Rule Log

Question 22

assign

Answer 22

Assigns values to properties in the business process execution context. For details see the entry in the Ensemble Business Process Language Reference.

Question 23

return

Answer 23

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.

Question 24

trace

Answer 24

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.

Question 25

debug

Answer 25

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.

Question 26

send

Answer 26

Sends the message to a particular target after optionally transforming it. See “Selecting the Transformation and Target of a Send Action” for details.

Question 27

delete

Answer 27

Deletes the current message.

Question 28

delegate

Answer 28

Delegates the message to a different rule.

Question 29

an HL7 Sequence Manager

Answer 29

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.

Question 30

d in validation

Answer 30

examines the DocType property of the document to see if it has a value.

Question 31

m in validation

Answer 31

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.

Question 32

1 in validation

Answer 32

same as dm, examines doctype and segment structure