Private ReadonlycontentPrivate ReadonlyloggerPrivate ReadonlysalesforceThis 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
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 beforeDeploy to run datapack activation processes.
PrivatecalculateCalculate the MD5 checksum of the VersionData of a ContentVersion record using the same logic as used
by Salesforce to calculate the value in the ContentVersion.Checksum field.
ContentVersion deployment record
MD5 checksum
PrivatecreateCreate ContentDocumentLink object for the just deployed ContentVersion's objects making
them available for the whole organization
PrivategetThis 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
PrivateupdateLink the ContentVersion objects to existing content document objects. If the content version is not changed skip deployment of a mew ContentVersion to save spaxce on the target org.
ContentVersion record
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.