It is possible to extend FS Cloud in various ways. In this section of the guide, we will cover the details of extending on the inside. But you must never customize anything belongs to a framework component as this could impair the appropriate function of IFS Cloud. In 22R1 and onwards LAA or Extend on the inside is restricted for Framework components. Please refer to Restrict LAA/Extend on the inside for more details.
This concept, covers all types of modification of source code either by modeling or code changes. These changes are highly invasive but will give you the most control over the business logic. Here typically Developer Studio and other developer facing tools are used. The result must be version controlled and maintained.
Note that a customization should only be used as very last resort as it causes implications when upgrading and taking patches. Read more about the tailoring domain to know more about when to do customizations and before using Utility Packages to do customizations, we recommend you to read the customization best practices.
Customization is mostly covered within the development guide. Until we are finished with a more comprehensive guide you can follow the following links to find out more.
Customizing Server using the layered architecture
Setting up a customization project in Developer Studio
How to analyze customization impacts when upgrading