Summary

This article will explain how to implement the locking permissions and optional properties in your existing studies.

Table of Contents



Freezing DataLocking Data
  • Freezing questions and forms will prevent changes to data
  • ‘Partially Frozen’ will be visible when some, but not all data is frozen
  • Locking questions and forms will prevent changes to data and metadata (managing queries and alerts, performing SDV, etc.)
  • ‘Partially Locked’ will be used when some, but not all data is locked

Concepts Covered

This tutorial covers the following topics:

  • Updating the Roles worksheet
  • Adding optional properties

Step 1: Define Roles worksheet in the DataArchitect file

Define the roles that shall have locked and freeze status:

metadata – lock data – Actions Required (lock, updateMetaData)
metadata – freeze data – Actions Required (freeze, updateMetaData)

By default, dynamic forms cannot be created when the parent form is frozen. There are two options for overriding this functionality:

  1. Add the property addDynamicWhenFrozen to the App Properties worksheet and set the value to true. This will allow any dynamic form to be created when the parent is frozen.
  2. To permit the creation of only certain forms by formType, add the property allowedDynamicTypesWhenFrozen. In the value column, enter a comma separated list of dynamic formTypes.

By default, no metadata actions (including eSignature) can be applied to locked data. To allow users to sign locked data, add the property signLocked to the App Properties worksheet and set the value to true.

In Conclusion

After completing this tutorial, you should be able to perform the following:

  • Define Roles with Freeze and Locking status actions
  • Adding optional properties


Need more help?

Please visit the Fountayn Contact Information page.