website logo
⌘K
Explore our documentation
Contact APIANT support
What is APIANT?
Automation Editor
Key Concepts
Account Management
Managing Automations
App Connections
Building Automations
Alert Mappings
Troubleshooting
CRMConnect: Mindbody → HubSpot
CRMConnect: DonorPerfect → HubSpot
CRMConnect: DonorPerfect → ActiveCampaign
MailConnect: DonorPerfect → Mailchimp
ShopConnect
ShopConnect Settings
Sync Products
Manually sync Mindbody services/pricing options to Shopify
How to tag products in Shopify to prevent sync during sales sent to Mindbody
Retrying orders from Shopify → Mindbody
Manually pushing Mindbody orders to Shopify
Mindbody Pricing Discontinuation: Integration with Shopify
Guide to manually syncing Mindbody Packages with Shopify Products
Features that are not supported in ShopConnect
Automation Alert Reports
Linked Accounts
ZoomConnect
New features in version 4
Settings
General
Email & SMS
BOTs
MINDBODY
Zoom
ZoomConnect Mindbody Appointments - Setup and requirements
Troubleshooting
Assembly Editor
Key Concepts
Account Management
API Key Management
Managing Content
Building Assemblies
API Integrations
Other Assembly Types
Keyvalue Storage
Assembly development cycle
APIANT for Integrators
Help Forum
Automation Templates
Development Server
Module IDE
Shared App Connections
Tenants and Linked Accounts
APIANT Inline
Supported functionality
Embed Inline
Sandbox
Docs powered by
Archbee
Automation Editor
...
Gear Menu
Processing menu

Disabling data storage

3min

An automation can be configured so the system will not on its own store any data that the automation processes.

An example of when this may be desirable is for US patient privacy HIPAA law.

To disable automation data storage, select this menu option:

Document image


The menu option will then appear like this:

Document image


Data storage can be re-enabled by selecting the menu option again.

When data storage is disabled, all automation logging is turned off and the automation's data processing history pages will not show any processed data. It will not be possible to search transaction history for any data b/c there is no retained data to be searched.

It will not be possible to retry failed transactions b/c the system will not store information needed to perform retries.

The automation is still able to write information into the system's database via Lookup Table actions. The information the automation may write into the system's database is dependent on the automation's implementation.



Updated 03 Mar 2023
Did this page help you?
PREVIOUS
Concurrency
NEXT
Disabling logging
Docs powered by
Archbee
Docs powered by
Archbee