Question
Sun Life Financial
CA
Last activity: 10 Sep 2024 12:35 EDT
Project with multiple project assets, referencing the same utility in v22.1
In v19.1, our project structure would generally consist of a startup project and a few child projects, each referencing a 'utility project' that contains functions we use accross the board (custom logging, message translation, etc.).
We're now converting to v22.1 and it seems like this architecture poses a problem. Our initial thought was to convert the child projects to project assets, and then import those into our main project. But the fact that they all reference the same 'utility project' (now converted to a utility asset) seems to make Studio behave weirdly. More specifically, it looks like it breaks the debugger. Nothing happens when testing an automation or doing a 'Run All'.
Are we missing a step to make this work or is this architecure just not supported anymore? If it's the latter, how do you suggest we change our approach?
Thanks