Skip to main content

Enable and Disable Event Actions on the Basis of Environments

Intro​

Enabling or disabling event actions based on different environments is essential for streamlined development and testing. This feature allows developers to control the execution of specific actions in distinct stages such as development, testing, and production.

Toggling the status of event actions ensures that functionalities are active during development and testing phases while preventing unintended consequences in live environments. This dynamic control enhances the application's robustness, facilitates debugging, and contributes to a smoother deployment process.

In this video tutorial you will learn how to Enable and Disable Event Actions on the basis of Environments in your web app.

1. Enable Event Actions​

To enable event action, create a new record and Submit it. This action creates a new record in your collection as well as the external API (Airtable, in this example).

On successful completion of this action it displays a relevant notification for the same.

DrapCode Builder Custom Page Redirect Event

2. Disable Event Actions​

Go to Events and choose the small black symbol on the right. Click it to Disable the event action.

This way when you create any record it will save in your collection but will not make a call in your external API.

DrapCode Builder Custom Page Redirect Event

3. Test Disable Event Actions​

To dsiable event action, create a new record and Submit it. This action will not create a new record in your external API (Airtable, in this example).

Conclusion​

One benefit of enabling/disabling event actions in a web app based on environments is enhanced risk mitigation. This feature allows developers to selectively activate or deactivate functionalities in different stages, reducing the risk of unintended consequences and ensuring a more stable deployment process.