To define the attributes of an embedded script element

Parent Previous Next

A CRM script need not exist in isolation, but rather can be seen as a component of a much larger script. Maintaining modular scripts in this way ensures that routine processes, potentially triggered from several customer interaction scenarios, need only be created once and embedded at the right point within multiple master scripts. Not only is this approach more efficient at the point of initial creation; it also ensures that any required changes are applied once and immediately rippled through to all related processes.


The procedure to define the attributes of an embedded script element is as follows:

  1. Prerequisite procedural steps are covered separately in the topic To add a node element to a CRM script definition. Refer to these before proceeding to step 2.
  2. Using the Element Type drop-down field, select the option Embedded script.
  3. Using the Embedded Script drop-down field, select an existing script definition to be launched from within the main script 1.
  4. Click on Save.


Note

1 Existing script definitions are denoted by their description; hence it is important to employ descriptions that are meaningful and unambiguous to the end user.


See related topics...

CRM script maintenance overview

To add a node element to a CRM script definition