Recording does not regenerate code after changing 'Match value'

Bug reports.
sux
Posts: 7
Joined: Fri Jan 07, 2022 1:14 pm

Recording does not regenerate code after changing 'Match value'

Post by sux » Wed Jun 01, 2022 2:06 pm

When changing the 'Match value' of a 'Wait for' action, the change does mark the recording as dirty and therefore does not regenerate the code when running the recording.
  1. Add recording step 'Wait for'
  2. Change it to AttributeEqual
  3. Set Match name to 'Enabled'
  4. Run the recording
  5. Change the Match value to either true or false (depending ont the associated repo item)
  6. Run the recording
The execution still fails with an error saying that value for 'Enabled' does not match expected value 'yourValue'.

I've seen this problem in 10.1.5 and 10.2.1.