3. Ensure Accelerator Objects Are Backed Up or Already Stored in Git

This page outlines the process for ensuring all accelerator objects are backed up and properly stored in Git, either by organizing them into dedicated component folders or verifying existing structures.

Accelerator objects must be maintained in a Git repository, similar to other configuration assets. Moving forward, each accelerator’s objects should be stored in a dedicated component folder. The structure of each component folder should mirror that of the root folder. All objects must reside in their respective entity folders (such as CalculationLogic, Dashboard, etc.).

Goal is to:

• Create a backup for every installed accelerator, containing all objects that may be overwritten by a newer version during an upgrade.

• Ensure all objects are moved into their corresponding component folders.

No Accelerator within Scope Was Installed

If none of the accelerators listed are installed in the partition, this section can be skipped. Proceed to the next topic.

Accelerator in Scope was Already Installed

a) Code is in Git, but not in Component Folders

I. Prepare a Commit with the Standard Accelerator Version

This step helps identify any customizations made to the standard accelerator version. If no customizations exist, you may skip this part.

1. Create and check out the pfxagents Git branch based on the branch matching the partition (usually master branch).

2. Launch the IntelliJ IDEA with the Pricefx Studio plugin.

3. Go to Tool Window.

4. Click PfxComponents.

5. Search for each installed accelerator from the below scope by typing accelerator.

   

6. Click Import.
   This action will download the latest source code.

7. Delete the Preference folder in each component folder.

8. Commit each folder in Git with the following commit message such as:
   PFAGENTS-123 standard accelerators to component folders
   Replace the ticket number as appropriate.
   Do not push this commit to origin yet! Since auto-deployment could deploy this standard accelerator and overwrite the customized one on the partition. This commit will be useful later on, when you do the comparison to look for the customizations.

II. Create Backup Commit

1. Update the source in the folders with the actual version. Ideally by moving them in Git (preferred, but only if git is matching the partition) or fetching the actual version from the partition.

2. The move-in-git way – For each component folder, for each object:

   1. Remember the object name and delete it.

   2. Find the object in the root folder and if it exists, move it to the component folder.

3. The download-from-partition way – In the Fetch tool window, for each downloaded component folder:

   1. Click the button Select objects that exist in the local directory.
      Feature is only available within the Pricefx Studio version 15.1.7 or higher. This action will tick a checkbox for all entities and all objects that exist on partition and on disk. If there are no objects present on the partition that means the given accelerator is not installed, so you should not commit this folder and you can continue with the 4. Upgrade or Install Accelerators.

   2. Delete all objects from the component folder.

   3. Click PfxFetch.
      This action will download the code from the partition.

   4. Delete the objects in the root folder and if any exists.

4. In each component folder and CalculationLogic or PricingParameter subfolders, rename all object folders that have validAfter suffix (e.g. +2020-01-01) and remove it.
   If you are using a multi-rename tool such as Total Commander or Double Commander, the regex string to replace is \+\d\d\d\d-\d\d-\d\d$.

5. For Sales Insights Accelerator – Fetch the following Advanced Configurations:
   • SIP_AdvancedConfiguration
   • waterfall-configuration

6. For Customer Insights Accelerator – Fetch the following Advanced Configuration:
   • customer-insights-accelerator

7. Commit the component folders in Git with the following commit message such as:
   PFAGENTS-123 moving accelerators to component folders
   Replace the ticket number as appropriate.

b) Code is in Git and Already in Component Folders

1. Verify that the Git repository code is up to date with the partition.

2. In each component folder (and within CalculationLogic or PricingParameter subfolders), rename all object folders that contain the validAfter suffix by removing it.

List of Required Accelerators

• Sales Insights Accelerator Source Code

• Customer Insights Accelerator Source Code

• Actionable Insights Accelerator Source Code

• Shared Library Accelerator Source Code

• Dashboard Library Accelerator Source Code