Adds layout dependencies based on the child cards mentioned in the layout. Ensures that child cards are deployed and activated before the layout is activated
Datapack deployment record to validate
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 DatapackDeploymentEvent.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 DatapackDeploymentEvent.getRecords should not be prefixed with a namespace even if the object
you try to access has a namespace; see also beforeDeploy.
event object
This hook is almost identical to the DatapackDeploymentSpec.preprocess 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
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
./deploymentSpecsfolder.