In terms of the build folders structure ...
Do people hold separate dev / test / prod folders ?
Is this a best practice ?
The short answer is no.
Our folder structure is build like this:
The root folder (not shown here) contains all reusable components, which can be used in several different processes.
Below that we have main folders i.e. "A35_NWF_NewStoreFood" as the subject for all processes in that folder.
Occasionally we build something, just for the fun (yes, I know it sounds strange) or experimental purposes i.e. small processes to answer questions here in the community. Those are kept in a Sandbox folder.
Hope it helps.
No change in folder structure for test/ dev/ production.
The folder structure show in screenshot. It depends on our requirement and how we would like to organize our folder structures.
You can create three sub folder in one main folder for one interface and rename sub folders as Test, Dev, Production .
It depends on our use case and how we would like to organize our folder structures. This way we could easily track what are the processes that are for Development OR Under development. What are all in Production OR what are all planned for production. What are all for testing purposes.
I saw this kind of structure and people are using this as far as I know.
Adam Arrowsmith, Could you correct me If I went wrong and also please help us here?
Happy Exploring Boomi.
We don't have any folders that would indicate that processes/components are staged/targeted for an environment. (we have just Test and Prod environments)
However, we do have a folder named '#Sandbox and POC' (POC = Proof of Concept), where we keep sub folders of processes and components for items that are NEVER meant to be in Production. (those components/processes are also not part of any upcoming project)
It's pretty common to have prod and non-prod folders as a means to distinguish things that are in-development vs. running in prod (or on their way to). What I would strongly discourage is COPYING between these folders as a means of version control. The creation of net-new components (including IDs and references) will be difficult to sort out and preclude any ability to use common/shared components (not to mention the high likelihood of deploying duplicate connections and consuming more licenses than you need to).
Retrieving data ...