---
schema_version: "1"
id: b699fd949379b599c886cc903b60447693b671c9d9a85c60d351b39c0c7ae05e
title: Installing Custom Order Management Extensions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_installing_custom_order_management_extensions_239103.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_installing_custom_order_management_extensions_239103.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 99fadc75ffafae167b3d44abd89fd23cc582eb5cef845efe94f444fd91db5f2a
description: "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."
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png)

Note Before you deploy any custom extensions, review this [important note on custom code security](https://help.salesforce.com/s/articleView?id=ind.iom_order_management_design_and_implementation_best_practices.htm&release=264.0.0&type=5 "When designing your Industries Order Management setup, or when troubleshooting a mature setup, consider the practices suggested on this page. These practices aren't strictly required, but are generally good ideas. If you already have a mature design that's working well, then you might not need these tips.").

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.

- **[Deploy Custom Extensions to the DEV Environment](https://help.salesforce.com/s/articleView?id=ind.comms_t_dev_environment_239114.htm&release=264.0.0&type=5)**  
    Deploy custom OM extensions to the DEV environment.