'Field Values Validation' test passes but is not validating correctly

[aansell]

I am having a problem with ATF, the Field Values Validation setting is passing successfully even though the value in the record is different to the filed being tested. Here is the validation test.

When I run my test it suceeds.

But this is not what was set on the record. Here' part of the screen shot that ATF records. You will see that the contact type is actually set to 'Direct Input'. See below.

Does anyone have any clue to what may be going on?

Thanks in advance,

Arthur

[aansell]

Version Info: We are running Kingston Patch 3a.

[Mark Stanger]

Thanks for the great screenshots.  That makes this much easier to follow.  I was able to set this up as a test in my personal dev instance (running on London) and everything works exactly as it should.  I'm not seeing the inconsistency you are seeing.  The only thing I can see from your screenshots that looks a bit odd is that you've got an extra 'Table' field on that form in steps 3-5.  I don't have that in my instance so I know that doesn't need to be on the form.  You might try removing that from the form and then re-creating in a new test and see if that makes a difference.  If it doesn't, then I'd say you've probably found a bug and will need to contact ServiceNow support.

[aansell]

Hi Mark,

Thanks for following that through. I had added the extra table field to see what table the 'Submit Record Producer' was working on. As you say it was not on the form - and it seems to have rippled through to the others. I will remove it as you suggest and re-try; but I suspect I shall be reporting this to Support. I will update this thread when I get have some further detail on the issue.

I appreciate you spending the time to review this,

best regards,

Arthur

[aansell · Accepted solution]

Hi Mark,

Further work (and help from a fresh pair of eyes from one of my colleagues!) revealed the solution and it was simple in the end. The problem was due to using 'Field Values Validation' rather than 'Record Validation'. Once the newly created record is opened, the requirement was to validate that new record hence the need for record validation rather than field validation.

The solution is as follows:

1. Set the 'Field Values Validation' step Active = False, or alternatively delete it completely, but I left it in for the screen shot.

2. Add extra step 'Record Validation' to the Test. 

  

With the above change made the validation works as expected.

Best regards,

Arthur