Hello everyone,
According to Regular Update Package 8.3.1 for Creatio Products | Creatio there have been changes made to the Creatio Architecture with Version 8.3.1:
Schemas like personalized "Environment dashboards" (great feature!!!) will be now saved by default in "Environment Schemas" of the Configuration Section. 
Unfortunately, for the O.G. "Custom" - Package there is contradicting information in the Academy and I wasn't able to find any more information in the Release Notes (8.3.1 Twin release notes | Creatio Academy) or the Change Log (8.3.1 Twin changelog | Creatio Academy).
Did anyone use the "Custom" Package in Creatio 8.3.1 for smaller Customizations yet extensively ?
Is it truly behaving like a regular user-made package, or did you encounter any issues or restrictions with e.g. transporting changes, moving functionality between packages, or similar?
Regards,
David
Like
Hello David,
Thank you for the clarification.
In the current 8.3.1 build, the Custom package indeed still displays dependencies on all platform packages. This behaviour remains unchanged at the moment, and what you see in the trial environment is expected for the current release.
The updated logic - where the Custom package depends only on CrtCore and no longer automatically inherits dependencies from other packages - is planned for upcoming releases. This architectural improvement has been announced, but it has not yet been fully applied across all builds of 8.3.1.
Hello David,
In version 8.3.1, Creatio introduced architectural changes related to the Custom package, but it is important to clarify how these changes work in practice. The new behaviour applies only to newly created environments. This means that in all existing environments upgraded to 8.3.1, the Custom package keeps its original structure and dependencies to ensure backward compatibility and avoid breaking existing logic.
In new 8.3.1 environments, the Custom package is now treated as a regular package and depends only on the CrtCore package. It no longer automatically depends on newly created packages, and the outdated “Custom Package Id” system setting has been deprecated, with all related functionality now using the “Current package” system setting instead. This updated behaviour eliminates the typical cyclic dependency risks that existed in earlier versions.
Hello Andrii Kendzor,
Thank you for your reply!
This was also my understanding of the architecturial change.
My confusion stems from the most up-to-date Academy Article referring to a different behavior (Regular package | Creatio Academy) and from a brief look in the most current Trial Environment (Version 8.3.1.4481).
There, the dependencies of the Custom Package seem to include every package that is part of the OOTB platform, even though most of these packages are several levels lower in the package hierarchy than the "CrtCore" Package.
My understanding of dependencies might be wrong here, but it seems like the Custom Package by default depends on more than just the CrtCore Package (and its dependencies)?
Kind regards,
David
Hello David,
Thank you for the clarification.
In the current 8.3.1 build, the Custom package indeed still displays dependencies on all platform packages. This behaviour remains unchanged at the moment, and what you see in the trial environment is expected for the current release.
The updated logic - where the Custom package depends only on CrtCore and no longer automatically inherits dependencies from other packages - is planned for upcoming releases. This architectural improvement has been announced, but it has not yet been fully applied across all builds of 8.3.1.