Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Omitting history snapshots for data types

Updated on April 6, 2022

To improve performance and manage your resources efficiently, you can choose not to take history snapshots when you develop data types. Every time a value in a data type changes, before you implement the change, the system takes a snapshot of the previous instance in case you need to restore the data type to the previous state. With multiple changes, omitting the snapshot can save you time and resources.

For example, you can choose not to take the snapshot of a data type in the following scenarios:
  • A data type is only an additive and remains unchanged throughout your entire business process.
  • The frequency of updates to a data type is large, which makes snapshots less useful.
  • Because every snapshot is a BLOB write, high numbers of snapshots might affect performance.
  • You implement your custom history-saving policy.

The system stores snapshots in the History- class of a respective data type.

Note: You can omit snapshots only for data types. When you develop rules, the system takes snapshots and stores them in a related History- class.

  1. In the navigation pane of Dev Studio, click Data types.
  2. Hover over a data type, and then click MoreView definition.
  3. On the data type rule form, click the Advanced tab.
  4. In the Bypass History on Save section, select True.
  5. Click Save.
Result: When a value in a data type changes, the system does not take the snapshot of the initial value.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us