Salesforce Docs Portal

Installing Custom Order Management Extensions

Project teams can develop custom integration adapters, auto tasks, and other code required by a customer, and then deploy this code to different environments: DEV, SIT, UAT, and others.

Note
Note Before you deploy any custom extensions, review this important note on custom code security.

Every project team needs to have three repositories to start development:

  • Custom Order Management code repository, owned by the project team.

  • Environment repository, provided by the engineering team. There is one repository for each environment.

  • vof_xom_deployment repository. A copy of this repository will be provided by the engineering team.

Non-Production Environments

All required modules should first be developed, deployed and tested in DEV.

To deploy custom OM extensions to non-production environments:

  1. Update env_repo/<Env name>/project-services.yaml.j2 to indicate the build number for different modules. Use the last successful build number from the Jenkins development pipeline

  2. Add any secrets to env_repo/config/secrets/.

  3. Commit and push your changes. Encrypt your secrets if you have changed them.

  4. Run the corresponding Jenkins pipeline to build and deploy. Indicate the following arguments:

    • buildVersion: Version of the Order Management product. Take this from env_repo/product-services.yaml.j2.

    • flywayVersion: The same custom code version as you used in env_repo/project-services.yaml.j2.