Private Readonly activatorPrivate Readonly containerPrivate Readonly loggerAdds card dependencies based on the child cards mentioned in the card states object. Ensures that child cards are deployed and activated before their parent is deployed and activated
Datapack deployment record to validate
Handles post-deployment activities for OmniUiCard datapacks.
This method activates deployed OmniUiCard records and, if configured to use Metadata API, collects and deploys the associated LWC components. The process can run in parallel based on the deployment configuration.
The deployment event containing information about the deployed datapacks
A Promise that resolves when all post-deployment activities are completed
Will propagate any errors that occur during the activation or deployment process
Hook that is called after records are converted from datapack format. This method adds card state dependencies and sets specific fields for upsert operations.
The converted datapack deployment records to process
Deactivates all OmniUiCards that are being updated before deployment. This method is called before deploying the records to ensure that active cards are deactivated first, preventing potential conflicts during deployment.
Array of datapack deployment records to be deployed
A Promise that resolves when all cards have been deactivated
Private collectPre-process template datapacks
Datapack
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.