Configuring virtual environment replacements

Introduction

Having created a virtual environment draft version, you can configure a set of replacement rules for components used in any process flows that run in the associated environment. For example:

  • If a process flow running in this environment includes NetSuite Instance - MASTER, then replace it with NetSuite Instance - LIVE.

  • If a script running in this environment includes a script named Script for Currency Conversion - MASTER, then replace it with Script for Currency Conversion - LIVE.

What replacements can I configure for a virtual environment?

You can define overrides/replacements for the following process flow components for any virtual environment:

Item
Related shape/area

Connector instances

Connector

Data pools

De-dupe

Cross-reference lookups

Map shape (transform function)

Scripts

Script shape

Map shape (transform function)

Company caches

Add to cache shape Load from cache shape Map shape (transform function)

Flow variables

Process flow settings

Flow priority

Process flow settings

Creating replacement rules

To configure replacements that must be made when process flows are running in a virtual environment, you define replacement rules. Typically, a rule requires you to select an existing component in a master process flow, followed by a replacement component. These steps are summarised below.

Before starting, ensure that all required replacement components have been created.

1

Access the draft version for your virtual environment

If you're not there already, access the draft version in the relevant virtual environment.

A virtual environment will only ever have one draft version. If you've just created a virtual environment, you'll see that a draft version has been generated automatically.

2

Choose the first component to configure

All process flow components that can be replaced are listed - click the first one that you want to update, for example:

Did you see the notes option at the top of this page, beneath the title? You can use this to add internal notes about this version - for example:

Any notes added here are displayed above the notes option, and stay with this version throughout its lifecycle)

3

Create a new replacement rule

Click the create button to add a new replacement rule:

If you don't see a create button, it's likely that you didn't access a draft version at the start (replacements must be configured in a draft version and then deployed).

4

Configure the replacement rule

Except for variables and flow priorities, replacement details are defined by selecting an existing component in your master process flow (on the left) and the item to be used instead (on the right). Click the create button to confirm.

For specific guidance on configuring different components, please see: Replacement instances | Replacement caches | Replacement cross-reference lookups | Replacement scripts | Replacement data pools | Replacement variables | Replacement flow priorities.

5

Add more replacement rules for this component

Repeat steps 3 and 4 if you need additional replacement rules for the selected component.

Keep in mind that you might deploy a single process flow to a given virtual environment or multiple process flows. Any replacements that you define here should cover ALL process flows that are deployed to this virtual environment. Don't worry if you're unsure which flows will be deployed - start with whatever you do know and come back to update the configuration later, if necessary.

6

Add replacement rules for other components

Repeat steps 3, 4, and 5 to add replacement rules for all required components.

7

Deploy the draft version

When you're satisfied that all required replacements are configured, you can go on to deploy the draft version.

PreviousUnderstanding virtual environment versionsNextReplacement instances

Last updated