Page Comparison

This is pretty esoteric, but when you make certain changes, you can avoid having to automatically generate equivalent files in the Services layer. By not having to generate these files, you can potentially save up to 1-2 minutes for each change you make.

When making changes to Application layer files, you'll also need to automatically generate equivalent files in the Services layer in the vast majority of cases:

IF

• The default configuration file whose settings you wish to change or supplement contains a generate-services-schema="true" attribute value; e.g.:

  Code Block
  <record id="acquisition" in-findedit="yes" type="record,procedure" cms-type="default" generate-services-schema="true">

AND

• If your changes affect global behavior of a record in any way
  OR
• If you have:
  • Fundamentally changed the behavior of any field; for instance, by changing its data type, or altering whether it should appear in search and list results.
  • Added a field.
  • Removed a field.

If you've made only very minor changes that don't fundamentally change the behavior of a record or field, you might not always need to generate equivalent files in the Services layer. One example of such a minor change is if you modify the choices of data options that a user can make within a field, such as the set of options they can choose from a dropdown menu, or the set of vocabularies associated with an autocomplete field, that provide term matching suggestions as a user types into that field.

As a bottom line: if you don't know for certain whether you need to generate these Services layer files, it can't hurt to do it anyway.