rdpscript

RDPScript follows a well defined pattern and boils down to a if-then-end statement

Syntax

SegPos = if (Condition|CodeCondition|Calc) then Usage|LocalCode|Error end

SegPos = if (Condition|CodeCondition|Calc) then Usage|LocalCode|Error else Usage|LocalCode|Error end

SegPos = if (Condition|CodeCondition|Calc) then Usage|LocalCode|Error elseif (Condition) then Usage|LocalCode|Error end

Definitions

SegPos

The segment position we want to modify.  Ordinal values are used.  For example SegPos[1] is the ISA segment.  SegPos[1:2] will be the second element of segment ISA.  SegPos[1:2:1] would be ISA02 composite element 1

Condition

A condition that must evaluate to true before the statement in the then clause can execute.

+SegPos[27] = if (SegPos[26:2] == "18") then Usage[Optional] else Usage[NotUsed] end

In this scenario we want to change the usage of Segment Position 27 to Optional if Segment 26 Element 2 is equal to 18 otherwise mark it as Not Used

Calc

Calcs allow arithmetic calculations to be performed on element data to make sure they are correct

+SegPos[3:1] = if ( Calc{# (SegPos[3:1] - SegPos[2:2])* 10 #} == 2.23  ) then Error[ElementHasWrongValue,"Doesn't total up!"] end

Calcs currently supports the basic +,–,*, and / operators that can be combined in an infinite amount to ways to make sure EDI data is correct.

Calcs can be used on both the left hand and right side positions

Example

+SegPos[3:1] = if ( Calc{# (SegPos[3:1] - SegPos[2:2]) * 10 #} == Calc{# (SegPos[3:1] - SegPos[2:4])* 10 #} ) then Error[ElementHasWrongValue,"Doesn't total up!"] end

Example

+SegPos[3:1] = if ( Calc{# ((SegPos[3:1] - SegPos[2:2]) * (SegPos[3:1] - SegPos[2:2])) * ((SegPos[3:1] - SegPos[2:2]) - (SegPos[3:1] - SegPos[2:2])) #} == SegPos[2:7] ) then Error[ElementHasWrongValue,"Doesn't total up!"] end

The usual arithmetic operators can be used to compare the results of the Calcs.  For example, ==, !=, <, >, <=, >=

Complex Conditions

+SegPos[146] = if ((SegPos[140:1] == "R") or (SegPos[140:1] == "S")) then Usage[Required] else Usage[Optional] end

Boolean Operations

Examples

+SegPos[27] = if (SegPos[26:2] == "18") then Usage[Optional] else Usage[NotUsed] end

+SegPos[31] = if (SegPos[26:2] == "18") then Usage[Required] else Usage[Optional] end

+SegPos[40] = if (SegPos[26:2] == "18") then Usage[Required] else Usage[NotUsed] end

+SegPos[146] = if ((SegPos[140:1] == "R") or (SegPos[140:1] == "S")) then Usage[Required] else Usage[Optional] end

LocalCode

A keyword used to modify the accepted values of elements

+SegPos[3:1] = if ( SegPos[3:1] ==  "837" ) then LocalCode["we","w9"] end 

+SegPos[3:1] = if ( SegPos[3:1] ==  "837" ) then LocalCode["we","w9"] else LocalCode["837"] end

In this scenario we are changing the accepted values of SegPos[3:1] to ‘we’ and ‘w9’ if it’s value is ‘837’

Error

A keyword used to create custom errors.  EDIValidator will generate an error if the condition evaluates to true

+SegPos[135:5] = if (SegPos[135:5] == SegPos[40:5:1]) then Error[ElementHasWrongValue,"SV105 must be different from 2300 CLM05-01"] end

+SegPos[104:9] = if ((SegPos[26:9] != "") and (SegPos[104:9] != "")) then Error[ElementHasWrongValue,"SBR09 is used It should not be used after National PlanID is mandated"] end

+SegPos[275:2] = if ( SegPos[275:2] !=  SegPos[3:2] ) then Error[ElementHasWrongValue,"ST02 must be equal to SE02"] end elseif ( SegPos[275:2] !=  SegPos[3:3] ) then Error[ElementHasWrongValue,"ST02 must be equal to SE03"] end elseif ( SegPos[275:2] !=  SegPos[3:4] ) thenError[ElementHasWrongValue,"ST02 must be equal to SE04"] end else Error[ElementHasWrongValue,"ST02 must be equal to SE05"] end

Custom error messages that can be used are listed below

ElementHasWrongValue, ElementNotUsed, ElementRecommended, ElementNotRecommended, ElementMissing, CompositeElementHasWrongValue, CompositeElementNotUsed, CompositeElementRecommended, CompositeElementNotRecommended, CompositeElementMissing, SegmentNotUsed, SegmentMissing, SegmentRecommended, SegmentNotRecommended

Checking for null

+SegPos[135:5] = if (SegPos[135:5] == null) then Error[ElementRecommended,"This element is recommended"] end

+SegPos[135:5] = if (SegPos[135:5] != null) then Error[ElementNotUsed,"This element is not used"] end

String Operations

+SegPos[11:3] = if ( (SegPos[11:3] >l  "13") and (SegPos[11:3] then Error[ElementHasWrongValue,"length"]  end

+SegPos[11:3] = if (SegPos[11:3] =c  "Provider") then Error[ElementHasWrongValue,"Cannot contain text Provider"]  end

+SegPos[11:3] = if (SegPos[11:3] =s  "P") then Error[ElementHasWrongValue,"Cannot start with P"]  end

+SegPos[11:3] = if (SegPos[11:3] =e  "xxx") then Error[ElementHasWrongValue,"Cannot end with xxx"]  end

Operators

Code Conditions – Custom Validating with .Net

+SegPos[277:2] = if ( CodeCondition["shouldStartWithZeros"] ) then Error[ElementHasWrongValue,"Value should start with zeros"]  end

Register for the appropriate event on the EDIValidator

ediValidator.OnCodeCondition += new EDIValidator.CodeConditionEvent(ediValidator_CustomCondition);

Write a custom validation check using .Net

private void ediValidator_CustomCondition(object sender, CodeConditionEventArgs e){
  if (e.CodeCondition.Id == "shouldStartWithZeros"){
     if (e.CurrentSegment.Elements[1].DataValue.StartsWith("0000")){
      e.ConditionValid = true;
     }
  }
}

When Are Rules Are Executed

A Trigger SegPos is the segment that a rule belongs to.  Rules are executed when the Trigger SegPos is encountered while validation occurs.

+SegPos[31] = if (SegPos[26:2] == "18") then Usage[Required] else Usage[Optional] end

The above rule is executed when segment 31 is encountered.

+SegPos[3:1] = if ( SegPos[3:1] ==  "837" ) then LocalCode["we","w9"] end 

The above the rule is executed when segment 3 element 1 is encountered