Groups multiple spec implementation together and executes them in sequence, specs can be added to the group and only for the exposed methods on the specs the group will expose implementations.

The order of execution of the specs is determine by the order in which they are added to the group.

Hierarchy

  • DatapackDeploymentSpecGroup

Implements

Constructors

Properties

specFns: Map<string, ((...args) => any)[]> = ...

Methods

  • 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.

    Parameters

    Returns any

  • Executes after a group of records is deployed, at this stage it is not possible to change any field value anymore. The hook point can be used to run post-deployment validations or post-deployment activation processes.

    Note: this runs on record level and use __type to run datapack activation processes.

    Parameters

    • event: readonly DatapackDeploymentRecord[]

      Array of records that got deployed; contains both the failed and success records.

    Returns any

  • This hook is called before deploying the first record in a datapack, and is only called once very datapack in the deployment.

    • Use this hook to execute and pre-deployment actions. This action is comparable with the pre-step job from the Vlocity tools library.
    • Use the getRecords function to get a list of records for a specific SObject type.

    The type argument passed to getRecords should not be prefixed with a namespace. I.e; to get a list of OmniScript__c records in the deployment use:

    DatapackDeploymentEvent.getRecords('OmniScript__c')
    

    instead of

    DatapackDeploymentEvent.getRecords('vlocity_cmt__OmniScript__c')
    

    The event object also exposes getDeployedRecords; in the __type this will always return an empty array.

    Parameters

    Returns any

  • Executed just before the records are being deployed; the event contains a readonly array of records. At this stage values for the records can still be manipulated. This hook point should only be used to run logic that depends on all dependencies on individual record level are resolved.

    Note: this runs on record level and use __type to run datapack activation processes.

    Parameters

    Returns any