Validation step not yielding the right output

Good morning,

I'm building a simple validation for a numerical field, where I'm using the "contains match" function. The output shows the right result (true) when looking in the grid view, however the output in the validation step is showing as a failure. (see screenshots below)

Is there any issue on this configuration causing the mismatch?

Best regards,

Marco

Best Answers

  • Josh Boxer
    Josh Boxer Administrator
    edited July 23 Answer ✓

    If you swap 'Exact' to 'Regular expression' it seems to resolve your particular case of basic integer lookup. I dont think you should need to, so we will continue to investigate. If you want to raise a support ticket to track you could include an export of the Workflow

  • Josh Boxer
    Josh Boxer Administrator
    edited August 13 Answer ✓

    Issue has been identified and confirmed it is isolated to the Contains match function only when used in the Validate step. 'Exact' requires the datatypes to match, but the step incorrectly treats lookup values as alphanumeric instead of the original numeric value type, since 123 != "123" it fails the validation. There will be a fix in the next release, thanks for reporting the issue.

Answers

  • Josh Boxer
    Josh Boxer Administrator

    Hi Marco

    Have you previously Published anything (Function, Rule Group etc.)? Just checking changes to the function are being 'seen' by the Workflow. Can you go into the Validate step > Edit script to firstly check it looks to be setup as you have set the Function. Assuming nothing obvious can you copy and share the script. Also comment which Aperture version you are using.

    -Josh

  • @Josh Boxer At the moment all the objects are in draft. Aperture version 2.14.2.2.

    Script -

    Lot Number Checks {{1da585ef-4b46-4754-abe7-1b30c4d9fa87}}
    Lot Number is Correct {{c54afb9f-416e-4817-a4a8-628204e597d9}}
    ContainsMatch([s:LotStaticDataMaintenance], 'Exact', 'Whole value', [sc:LotNumber], [c:Lot No.])