The Promote feature in Neo allows you to push an approved or live dataflow from one organization to another within the same cluster. Unlike the copy-paste feature in Aira Coder, Promote is designed for governance-controlled propagation of finalized dataflows — it enforces org type hierarchy, validates permissions in both the source and target organizations, and transfers the complete dataflow configuration.

Use Promote when you want to move an approved, production-ready dataflow to one or more target organizations so that teams in those organizations can use or build on it.

📘

Note:

Cross-cluster promotion and application-level promotion (promoting a group of dataflows together) are planned for future releases. The current release supports single dataflow promotion within the same cluster.

Promote vs. Copy-Paste

Both Promote and Copy-Paste (via Aira Coder) allow you to move dataflow logic across organizations. The table below describes how they differ.

Key Concepts

Org Type

Every organization that participates in the Promote workflow must be registered with Neo and assigned an org type. The org type defines the organization's role in the deployment pipeline.

Org Type Hierarchy

The org type hierarchy controls which org types can promote to which target org types. This prevents untested dataflows from being pushed directly to production.

Note: Downward promotion (for example, Prod to UAT) is not permitted.

Org Mapping

An org mapping defines a directional relationship between a source organization and one or more target organizations. You must set up org mappings before you can use the Promote feature.

Relationship Types

When you add an org mapping, you select a relationship type that describes how the source and target organizations are related.

Note: All org mappings are unidirectional in the UI — you define the relationship from the source org's perspective. Internally, Neo uses bidirectional mapping for routing.

Prerequisites

Before you use the Promote feature, complete the following:

1. Neo must be enabled on both the source and target organizations.
2. The source organization must be registered on the Org Mappings page with an assigned org type.
3. The target organization must also be registered on its own Org Mappings page.
4. An org mapping must exist from the source org to the target org.
5. A custom application must exist in the target organization. You cannot promote to the Default or Middleware application.
6. The user must have the Neo Promote permission set assigned in both the source and the target organization.

Registering Your Organization and Adding Org Mappings

Step 1: Navigate to the Org Mappings page

1. Open the Neo extension portal: {host url}/extensions/neo/ui.
2. Select your organization.
3. Navigate to the Org Mappings page.

Step 2: Register your organization

1. On the Org Mappings page, select Add Organization.
2. From the Organization Type dropdown, select the org type that applies to your organization (Dev, SIT, UAT, Automation, Demo, or Prod).
3. Select Save.

The organization is registered with Neo and assigned the selected org type.

Note: An organization with Neo enabled must still be explicitly registered on this page. Until it is registered, Neo does not recognize the org for promotion, and you see an error when you attempt to add a mapping that includes it.

Step 3: Add a related organization mapping

1. On the Org Mappings page, select Add Relation.

2. In the Target Org field, search for and select the target organization.

   If the target organization is not yet registered with Neo or does not have Neo enabled, an error appears. Register the target org first before adding the mapping.

3. Select the Relationship Type — Parent-Child, Sibling, or Default.

4. Select Save.

The mapping is added. Repeat this step for each additional organization you want to promote to.

---

Promoting a Dataflow

Prerequisites

• The dataflow version is in Approved or Live status.
• The source and target organizations are mapped.
• A custom application exists in the target organization.
• The user has the Neo Promote permission in both organizations.

Steps

1. Navigate to the dataflow version page.

2. Open an Approved or Live version of the dataflow.

3. Select Promote.

   The Promote Dataflow dialog opens.

4. From the Target Org dropdown, select the target organization.

   Only organizations that are mapped to the current org and are of a promotable org type appear in the list.

5. From the Target Application dropdown, select the custom application in the target org where the dataflow is to be promoted.

   If no custom applications exist in the target org, this field is empty and an informational message appears. Create a custom application in the target org before retrying.

6. Select Promote.

Neo validates the promotion request before proceeding. Validations include:

• The target org is registered and Neo-enabled.
• The org type hierarchy permits the promotion.
• The target org has access to the required module.
• The user has the Neo Promote permission in both orgs.

If all validations pass, the dataflow is promoted. If any validation fails, an error message is displayed describing the issue.

What Happens After Promotion

• An Approved version of the dataflow is created in the target organization, under the selected custom application.
• A Draft version is also created automatically, so the team in the target org can make further modifications.
• The promoted dataflow retains the same trigger URL, HTTP method, block structure, block configurations, and headers from the source.
• The promotion is recorded in the dataflow history, showing the source org, target org, and whether the promotion succeeded or failed.
• The dataflow icon on the dataflow list updates to indicate that the dataflow has been promoted.

Promotion Uniqueness Rules

Neo uses the combination of trigger URL and HTTP method to determine how a promoted dataflow maps to an existing dataflow in the target org.

• If the target org already contains a dataflow with the same trigger URL and HTTP method, Neo automatically routes the promotion to the application that already contains that dataflow. You cannot select a different application in this case.
• If the trigger URL and method combination is new to the target org, you can select any custom application as the destination.
• You cannot promote the same version to the same target org more than once. If a new version is approved, you can promote it again.
• If the trigger URL changes between versions, Neo treats the promoted dataflow as a new dataflow and creates it separately. Promotion history is not tracked across such URL changes.

Promoting Multiple Times

• A single approved version can be promoted to multiple target orgs, one at a time.
• The same version cannot be promoted to the same org twice.
• After a new version is approved, it can be promoted to any org — including orgs that received a previous version.

What is Transferred During Promotion

Best practice: Avoid hardcoding org-specific values such as org IDs or credentials directly in the dataflow. Use the DAO function getValueByKey to retrieve values from the Configuration Manager. This ensures the promoted dataflow works correctly in the target org using its own configuration.

Eligible Dataflows for Promotion

Supported Targets

FAQs

1. Can I promote from Prod to UAT?

   No. The hierarchy only allows upward promotion (Dev → SIT → UAT → Prod). Downward promotion is not permitted.

2. What happens if the target org has no custom applications?

   The promotion does not proceed. You must create a custom application in the target org before retrying.

3. Can I promote to the Default application?

   No. Neo requires that you promote to a custom application. This is enforced to encourage organized grouping of dataflows within applications.

4. Is the Promote feature the same as copy-paste in Aira Coder?

   No. See Promote vs. Copy-Paste for a detailed comparison.

5. Can two orgs of the same type promote to each other?

   Yes. For example, two UAT orgs or two Prod orgs can promote dataflows to each other using a Sibling relationship.

6. Does a promoted dataflow go live automatically?

   No. An approved version and a draft version are created in the target org. The team in the target org must review and make the dataflow live manually.

7. What permissions does a user need to promote a dataflow?

   The user must have the Neo Promote permission set assigned in both the source and the target organization.

8. Can I promote global dataflows?

   Yes, global dataflows are eligible for promotion provided Neo is enabled and the org is registered.