Private Readonly activatorPrivate Readonly containerPrivate Readonly embeddedPrivate Readonly loggerPrivate Readonly lwcPrivate Readonly preprocessorStatic ParallelNumber of parallel activations to perform.
Static ParallelNumber of parallel tooling deployments to perform.
Private activateActivate the OmniScripts in Parallel using the activator without deploying the LWC components
Private addPrivate addAdd a warning message to a record from the preprocessing stage; stores the messages and adds them to the records in the afterRecordConversion stage.
All pre-processor messages are warnings, if the pre-processor encounters an error it should throw an exception.
Source key of the future record to add the warning to
Message to add
Private addShould be called in the afterRecordConversion stage to add the preprocessor messages to the records
Records to add the preprocessor messages to
This hook is called after all records of a datapack are deployed and will only be called once for every datapack in the deployment.
Use this hook to execute datapack activation logic. It is comparable to post-step in Vlocity tools
and should also execute any activation logic if required.
Use the getDeployedRecords function to get a list of deployed records for a specific SObject type. This excludes any records that didn't get deployed.
The type argument passed to getRecords should not be prefixed with a namespace even if the object
you try to access has a namespace; see also __type.
event object
This hook is almost identical to the __type hook except that executes after a datapack is converted into 1 or more Salesforce records.
The list of records past into this hook contains all the records generated for a single datapack; it is not possible to remove/drop any record but individual records can be manipulated,
Note At this point dependencies are not yet resolved
Private deployDeploy OmniScript LWC components to the target org
This function executes before a datapack is converted into a set of DatapackDeploymentRecord's and allow changing the datapack data, correct faulty field values that would otherwise cause errors during record conversion or remove certain fields that should not be deployed.
This hook can also be used to override certain fields with autogenerated values; i.e. setting the element order and level field of OmniScript elements
Datapack object
Private updateUpdate the order and level of the elements in the OmniScript or IntegrationProcedure.
A deployment spec contains Datapack specific logic and allows hooking into the deployment process to manipulate what get's deployed and execute post-deployment activation logic.
Implementers can implement any of the specified functions in this interface, all functions are optional and only the implemented functions are executed.
For many standard datapacks spec logic is implemented under the ./deploymentSpecs folder.