Actions75
- Compliance Report Actions
- Consent And Preference Actions
- Data Manager Actions
- Add Preference Into Your Configuration Tree
- Add Purpose Into Your Configuration Tree
- Create Preference
- Create Purpose
- Delete Preference
- Delete Purpose
- Delete Selected Preference
- Delete Selected Purpose
- Get Available Regulations and Related Information
- Get Configuration Tree
- Get Preference
- Get Purpose
- Get Vendor
- List Preferences
- List Purposes
- List User Rights
- List Vendors
- Update Preference
- Update Purpose
- Privacy Request Actions
- Widget Actions
- Create Authentication Provider
- Create Consent Notice
- Create Widget
- Delete Widget
- Get Archived Widget
- Get Current Draft Configuration For Notice
- Get Custom Theme
- Get Deployment
- Get Entity
- Get Widget
- List Archived Widget
- List Custom Themes
- List Deployments
- List Entities
- List Widgets
- Publish Current Draft Configuration For Notice
- Publish Widget
- Set Default Authentication Provider
- Update Component
- Update Current Draft Configuration For Notice
- Update Custom Theme
- Update Entity
- Update Multiple Components
- Update Multiple Entities
- Update Widget
Widget → Publish Current Draft Configuration For Notice
AI-generatedOverview
This node operation publishes the current draft configuration for a notice in the Didomi widget system. It is useful for scenarios where you have made changes to a widget's draft configuration and want to make those changes live by publishing them. For example, after customizing consent notices or preference center configurations, you can use this operation to deploy the updated configuration to end users.
Use Case Examples
- Publishing the latest draft configuration of a consent notice widget to make it active on a website.
- Deploying updated widget settings after editing the draft configuration for compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional parameters to customize the API request, such as filtering or pagination options. |
Output
JSON
statusCode- HTTP status code of the API responsebody- Response body containing the result of the publish operation
Dependencies
- Didomi API key and secret credentials for authentication
Troubleshooting
- Ensure that the API key and secret credentials are correctly set and valid, as missing or invalid credentials will cause authentication failures.
- Verify that the 'Request Body' JSON is correctly formatted if used, as malformed JSON can cause request errors.
- Check that required parameters such as notice IDs or configuration IDs are provided when necessary, otherwise the node will throw errors indicating missing parameters.
- If the API returns an error, review the error message and stack trace provided by the node to diagnose issues such as permission problems or invalid resource IDs.
Links
- Didomi API Documentation - Publish Current Draft Configuration For Notice - Official API documentation for the operation to publish the current draft configuration for a notice in Didomi widgets.