Pricefx Studio expects the project to have certain structure of folders and files. Also, one project can have more Modules (see details below), if you need to separate the configuration package into separate folders.
Generally the project contains:
partition configuration - set of folder and files as described in https://pricefx.atlassian.net/wiki/spaces/KB/pages/99200697/Configuration+Package#Structure
config.json file with connections to partitions
pom.xml file with links to Groovy and other libraries. This is needed only in some cases, not necessary for editing of logics.
Basic project structure sample:
Modules
IntelliJ has a concept of Modules (see https://www.jetbrains.com/help/idea/creating-and-managing-modules.html ), which allows you to have more Configuration Packages inside of one project. Studio supports this concept of modules.
Each module is inside of a subfolder in your project. You can imagine the project root folder also as a module - so, for example, the project structure can look like this:
Each module can contain the same what a project can contain, i.e. partition configuration, own config.json and own pom.xml. If a module does not have it’s own config.json file, it will use the one from project (from parent folder)
That’s why in some tools (like PfxFetch Toolbar and PfxDeploy Toolbar ) you have to first select the Module, before you can start selecting the environment and partition.