Optional apiOptional reactivateWhen true, any active dependent scripts will be re-activated. If false (default) only the specified script will be
activated and if the script is re-used in other scripts these will not be updated.
This is only required when you previously deactivated a script with through the UI and want dependent scripts that embed the to be activated script(s) to be reactivated as well. Generally this is not required when you do not deactivate scripts through the UI -or- when you run a full deployment/activation as this will automatically re-activate all dependent scripts in the correct order. Setting this to true for a full deployment will slow down the activation process as scripts are re-activated multiple times.
Optional remoteWhen true, the script will be activated using the standard Vlocity APEX activation function exposed by the
Vlocity Business Process Controller that runs as anonymous Apex.
When false (default) the script will be activated by locally generating the script activation records. This is faster compared to
the remote activation and avoids issues with governor limits that occur when activating a large scripts.
Optional skipSkip deployment of LWC components even when the script is LWC enabled.
By default activation will rebuild and deploy the LWC component of the script; setting this option to true will skip this step.
Optional toolingWhen true, the LWC components will be updated an deployed using the tooling API instead of the metadata API.
The benefit of this is that the LWC components will be deployed to the org without the need to deploy the entire package.
Optional toolingTimeout in milliseconds for the tooling API deployment. Default is 120 seconds.
120000
Optional useWhen set to true, the compiler will use the standard runtime for the generated LWC components
API version to use when deploying the LWC components