Map iLogic rule folder to Vault in project file

[mfoster9TD82]

It would be nice to map an iLogic folder to Vault in the project file similar to how you can with Templates and Design Data.
We currently store ours in a network folder but it seems like that is discouraged.

[MattH_Work]

Adding to this, why not just allow 'any' arbitrary folder to be mapped and therefore downloaded automatically on log in

     Content Center Files

     Templates

     Design Data

     iLogic

     Macros

     Standard Parts

     .....

     ..... .....

[aimanGYFPS]

Hello

[gregory_nickol]

Our iLogic rules are inside our Design Data folder, which is directly next to the location where iLogic forms seem to go by default "UI". The problem we ran into though is when we migrated versions of Inventor, we created a new Design Data 2026 folder, and everyone had to manually re-map their iLogic configuration settings in Inventor to point at the new 2026 directory or they wouldn't see any new rules or any with updates for compatability with the new version.

[WCrihfield]

I like the general idea here.  However, this will not work as intended until they fix the other related functionality, which we have wanted for a long time...the ability for it to 'find' all of our external iLogic rule files within 'all' sub-folders of the one folder listed in that type of specification.  As it stands right now, if we have hundreds+ of external rules (like I do), we simply have to create a bunch of sub-folders to separate them into groups (such as by what type of documents they work on, or what types of tasks they do, or what products they are for, etc.).  And when we use sub-folders, we currently have to include each sub-folder within the top portion of the 'iLogic Configuration' settings dialog...otherwise it can cause all sorts of issues, and require including 'partial' relative paths with the name of the external rule when calling it to run from another rule.  Then sometimes we need to add another sub-folder, or rename one, which would cause all sorts of problems again, which require more tweaking in the iLogic Configuration settings.  If they just fixed it so that we could list one folder, then have it automatically find all rules in all of its sub-folders, without including any portion of the path when calling them to run, then something like this might work OK.  And I would definitely like it that way.  But we generally just use one main Project for everything all the time though (due to decades of pre-existing design files from many authors), instead of a new project for each design, so it is not a big deal for us.