Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Requirements

  • The ability to select templates (like the email address verification email) by criteria such as the user's language, or the version of the app;
  • The ability to clearly specify the template that should be used if the criteria filtering is ambiguous (unlike app configurations where we just take the first one);
  • The ability to audit changes to templates (like study consents, which create immutable revisions... just record who created the revision);
  • The possibility of creating custom templates that can be used with scheduling or notifications (right now, you have to manage these outside the system and can't schedule anything);
  • The ability to add additional documents easily (the privacy document has long been considered, because it's required to submit an app to the App Store);
  • Should definitely replace the templates on the study object; could conceivably replace the study consent documents;

Not Requirements

  • Document inclusions or attachments (e.g. images for HTML documents... unless we really want this)
  • Variable resolution (that's part of using the template);
  • Publishing documents (e.g. the publicly available versions of the consents). However we'd need something like this for the privacy document

Document Model

You can now add any number of templates for a specific type of template, differentiated by their guids, and selectable using Criteria.


  • No labels