FpML Issues Tracker

635: cd-32 wrong context, off one level

March 3, 2008

closed

Minor

Always

Validation Rules

Admin

mgratacos

Summary

cd-32 refers to elements that don't exist at that context.

Based on my experience I think the rule may be off one level on the context.

The rule today: " Context: PeriodicPayment (complex type) cd-32 (Mandatory) Preconditions: LongForm If fixedAmountCalculation exists, it must contain calculationAmount and dayCountFraction. "

IMHO what was probably meant was: " Context: //element(*, PeriodicPayment/fixedAmountCalculation) cd-32 (Mandatory) Preconditions: LongForm calculationAmount must exist and dayCountFraction must exist. "

The problem was calculationAmount and dayCountFraction are not at the context.

Notes:

  • mgratacos

    04/22/08 1:47 pm

    Suggested approach:

    Context: PeriodicPayment (complex type)
    cd-32 (Mandatory)
    Preconditions: LongForm
    If fixedAmountCalculation exists, it must contain fixedAmountCalculation/calculationAmount and fixedAmountCalculation/dayCountFraction.

  • andrew

    04/22/08 1:49 pm

    Or

    Context: PeriodicPayment (complex type)
    cd-32 (Mandatory)
    Preconditions: LongForm
    If fixedAmountCalculation exists then both fixedAmountCalculation/calculationAmount and fixedAmountCalculation/dayCountFraction must also exist.

  • matthewdr

    04/29/08 1:33 pm

    Context: PeriodicPayment (complex type)
    cd-32 (Mandatory)
    Preconditions: LongForm
    If fixedAmountCalculation/calculationAmount exists then fixedAmountCalculation/dayCountFraction must also exist.

  • mgratacos

    04/29/08 3:57 pm

    The suggested solution below has been implemented to the trunk and 5.0 branch.

    Context: PeriodicPayment (complex type)
    cd-32 (Mandatory)
    Preconditions: LongForm
    If fixedAmountCalculation/calculationAmount exists then fixedAmountCalculation/dayCountFraction must also exist.

  • Leave an update

    You must be logged in to post an update.