Incorrect refusal to move condition

Get help. Get answers. Let others lend you a hand.

Moderator: Mr_Noodle

Incorrect refusal to move condition Fri Apr 12, 2019 8:46 pm • by dolfs
I start with the condition shown here:

Now the last "Contents contain match" contains the condition 0<1><1><1><1><1><1><1><1><1> (match a 10 digit number starting with 0). I next pickup that condition and drag it to the right to try and place it inside the "if all" above, and above the already existing condition there. I then get this:

To show where I was trying to move it:

  • The message seems incorrect.
  • There are no custom attributes (I assume this to mean tokens) in the condition.
  • Even if the <1> count as custom attributes I cannot see any reason why this move should not be allowed.
Posts: 11
Joined: Mon Dec 10, 2018 9:31 pm

Re: Incorrect refusal to move condition Mon Apr 15, 2019 10:41 am • by Mr_Noodle
That does seem like a bug. Can you export the rule and send it in to support? Click the "Contact Support" button in the "Info" section and attach it there.
Site Admin
Posts: 7760
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City

Return to Support