Project based iLogic settings (iLogic Global Forms vs External Rules)

[PolemEngineering]

We are currently working on a project (trajectory) to change from Drawing Based to Model (and Item) Based working.

Because compatibility became an issue, we also created a new Vault database (with a matching Workspace) as part of this change. As part of the workspace we have a folder with shared settings (Design Data, like styles and such). When changes occur, I inform my users and ask them to 'Get' specific files or the entire Settings folder. This way , possibly abusive, we have a managed shared settings, locally available.

The 'problem' I am currently facing is that I can separate the iLogic Global Forms in terms of Project File, but the global Event Triggers (RulesOnEvents.xml) and the External Rule do not seem to be separable (they are, like Application Options, arranged application-wide).

I have now succeeded in terminating my iLogic rules directly after initiating them based on active Project File and database. What remains annoying is that we will continue to work with two systems for a long time, where users have to retrieve part of their settings from the old Vault and part from the new Vault.

Is this 'the way' or are there better methods?

Thanks,

René

In summary:

So in Projects I have an .ipj for both Vault databases (actually 4: 2x for engineering files and 2x for library files). In this, under Folder Options, the location for Design Data is defined. This allows me to keep the underlying iLogic folder separate.

In 'Advanced iLogic Configuration' I have defined two External Rule Directories (one for each database).

Unfortunately the global iLogic event triggers are stored in an xml in the first mentioned external rule directory.
Any changes will therefore require retrieving a file from a Vault that a user may not be actively using.

By the way, I'm using v2023.4.2