Breadcrumbs

6. Implement Customizations as New Dashboards

If an accelerator has been customized, a new dashboard must be created based on the latest version of the accelerator, with the customizations applied on top.

This process can be time-consuming. It should only be initiated after the customer has tested the solution and signed the contract. Confirm with your Project Manager before proceeding. Continue this task only after formal approval.

All customized objects must be stored in their corresponding component folders:

  • agents-custom

  • customer-insights-custom

  • dashboard-library-custom

  • shared-library-custom

  • sales-insights-custom

Steps

  1. Create Customization Branch.

    1. Create a branch customization, based on your commit Standard Sales Insight Accelerator x.y.z.
      info Corresponding version you have previously identified.

  2. Fetch the latest Sales Insights Accelerator Source Code.

    1. Use the PfxComponents to fetch the most recent version of the Sales Insights Accelerator Source Code.

  3. Commit the Standard Version.

    1. Commit to branch with commit message such as:
      PFAGENTS-123 installation of standard Sales Insights Accelerator 1.14.3
      info Replace the ticket number and version as appropriate.

  4. Apply Customizations from your Previous Commit.

    1. Apply the changes from your commit PFAGENTS-123 moving accelerators to component folders.
      info For more information see 3. Ensure Accelerator Objects Are Backed Up or Already Stored in Git.

    2. Reapply the Changes from the Commit.

      1. If the merge completes successfully, continue. If conflicts occur, apply the changes manually and selectively.

  5. Rename Customized Objects.

    1. Rename all customized objects and their internal references by adding a _Custom suffix. For example:

    2. Configurator_Outliers → Configurator_Outliers_Custom

    3. Dashboard_Margin_Breakdown -> Dashboard_Margin_Breakdown_Custom
      info Renaming folders alone is insufficient. Object names are also defined within their respective JSON files. Rename each object in the Pricefx Studio using the General tab of the corresponding editor form.

  6. Rename the Component Folder.

    1. Update the folder name by replacing:
      • Search: -accelerator
      • Replace: -custom

  7. Commit Custom Components.

    1. Commit each custom component folder individually to Git. Use a separate commit for each folder to maintain clear version control history.

  8. Merge Customization Branch.

    1. Merge branch customization into the main pfxagents.