iLogic - Manage iLogic folder location from Project File

[cmcconnell]

When working with multiple clients, they each require different rules and triggers. It would be great if the iLogic folder location was managed by the project file.

Client specific project files make sense as each client has different styles, materials, and templates. iLogic control here makes sense too.

This would make it very simple to completely change the iLogic environment for each client.

[dan_szymanski]

Idea added to backlog for future consideration [32404]. Thanks!

[dusan.naus.trz]

It would be useful when changing the project so that the project keeps the correct paths to the External rule files.

I work with iLogic very often. I create various UIs for customers. I often switch between projects with other Design Data and I have to constantly change the path of External Rule Directories.

[dusan.naus.trz]

If the project holds the path to the UI, it should also hold the path to the External Rule. It might be interesting to be able to switch between different UI.

[dusan.naus.trz]

Context

https://www.youtube.com/watch?v=35cDV9uiXQE&list=PL8JAmheIZzlwqBP8Avqel2bppw7bllM_J&index=3

[dusan.naus.trz]

@corym

Thank you for the notice. You're right. Lots of ideas. I forgot about it. 🙂 Already to make it happen. 

[dusan.naus.trz]

@corym 

I have but nicer pictures. 🙂 🙂 🙂 

[jholland3XDLM]

This would also enable deploying iLogic rules to out Teams. I typically have to go to each workstation and do this for each user. This and the DLL library in the same screen.