IV 2021 iLogic: Illegal Characters in path

[corym]

We just moved to IV 2021 from IV 2020.

We have several rules that are triggered on a file open. In 2021, we are getting all sorts of iLogic errors about illegal characters in a path. These errors were not an issue in 2020.

For example, I just opened an .idw from the vault. It threw the error many times. Unfortunately, following the same procedure to reopen the .idw does not throw the same errors.

Rules that are triggered on open of an .idw:

1. Create and populate custom note picklist parameters (no path references in rule)

2. Create and populate custom tblock picklist parameters (no path references in rule)

3. Create custom properties (no path references in rule)

4. Sort plist by item number (no path references in rule)

5. Copy properties from .ipt/.iam to .idw.

I am not much of a programmer, so deciphering the iLogic error is a bit of a stretch for me.

Has anybody else seen this?

[Anonymous]

Hi Corym

Can you share the rule that is causing the problem with us?

It looks like you might have an event trigger set for an external rule that is no longer in the correct place (this might give the path error). Can you check to see if your external rule is still in the right place?

[corym]

They are all in the same place they have always been.

I do not know which rule is causing the issue. I have attached the 5 rules in a .zip that are triggered when I open an idw.

[Anonymous]

I've had a look through your rules, they don't appear to be reading or writing to any hard coded paths.

I think my initial suspicion about the external rules is correct. Open up the old version and got to "Tools", under the "Options" drop down (slightly hidden away), you will find "iLogic Configuration".

In the "advanced iLogic Configuration" setup window, there is an "External Rules Directories" area, make sure that this path is the same in both versions.

[corym]

Thanks Clint. That was the first thing I looked at. My 2021 Ilogic path is identical to my 2020 Ilogic path.

[Anonymous]

Hey Cory

If you edit the rule from 2021 (no need to make any changes), then close it (repeat for all 5), does it work?

[corym]

For whatever reason, I am not able to reproduce it today. When I get a chance, I will reboot and restart everything to see if the issue comes back. Monday moring, I saw it on 3 separate machines after the Monday morning boot up.