Skip to main content
Solved

Application configuration package (ACP) repository

  • October 10, 2023
  • 1 reply
  • 421 views

Forum|alt.badge.img+3
  • Sidekick (Partner)
  • 6 replies

Hi all 👋

As I'm new to the IFS delivery process, I've been trying to document myself to the best of my ability.

 

The problem I'm facing is as follows:

When configuring IFS (via the native cloud webpage) you can export ACPs. These ACPs should reside in <component>/server/appconfig or <component>/nobuild/appconfig as per the documentation here: https://docs.ifs.com/techdocs/23r1/020_lifecycle/035_configuration_management/#overview

 

ACP location according to documentation

 

However, what if the APC contains more than one custom entity belonging to 2 or more different modules?

Let's say I have an ACP that adds a custom field in the CustomerInfo entity (enterp module) and another custom field in the FooterField entity (accrul module).

How should I store the ACP in the git repository? Do I need to split the custom fields into 2 different ACPs?

 

Thanks in advance for any answers!

Best answer by Kasun Alahakoon

Hi @Colin, 

Although there is no technical limitation, it is best practice to separate configurations based on component/module. For example, if you have two custom fields resides in different components, you should ideally have two separate configuration files.

1 reply

Forum|alt.badge.img+9
  • Hero (Employee)
  • 48 replies
  • Answer
  • October 10, 2023

Hi @Colin, 

Although there is no technical limitation, it is best practice to separate configurations based on component/module. For example, if you have two custom fields resides in different components, you should ideally have two separate configuration files.