- Manage Project Schema

Manage Project Schema

When using the WOW Builder, all of the displayed applications, operations, connections, field descriptors, etc are stored in the same project schema. You can switch to a different project schema using the drop down at the top of the page. After switching the current project schema, the builder will display all of the applications, etc from the new project schema.

example: Changing the current project schema

Choosing “(Manage Schemas)” from the drop down will take you to the Project Schema page. This page displays all of the available project schemas. You can copy an existing project schema in order to create a new one. You also have the option to manage any of the project schemas in WOW.

Creating / Copying project schemas

Copying or creating a project schema from the Project Schema page will result in a new schema being created in the database. This is one way to create a backup of the project metadata. You can then apply updates or experiment with the new copy of the project metadata without affecting the original metadata.

Project schema settings

• • Name - The name of the project schema. This is the database schema which contains all of the project metadata

  • Description - Text describing the project schema

  • Status - If the schema has a compatibility problem, a summary of the problem is displayed in the status field (see below for more information about schema compatibility.) Otherwise, you can set the status to one of these values:

    • Enabled - The schema is enabled and can be used

    • Disabled - Applications in the schema cannot be run, and the schema cannot be set as the current project schema in the Builder

    • Builder Only - Applications in the schema cannot be run, however the schema may be set as the current schema in the Builder

  • Hidden - When true, the schema does not appear in the drop down list of available schemas (this does not prevent the schema from being used - all it does it remove it from the drop down)

  • Auto Update - Whenever updates are available for the schema WOW should immediately apply those updates. See below for more information on the advantages and disadvantages of using automatic updates

  • Only Show on Server - For deployments where there are multiple WOW instances running on different servers, this field can be used to prevent the project schema from showing up in the schema drop down, unless WOW is running on the specified server

  • Restrict to Environment - Use this setting when the project schema should only be accessible when WOW is running with a particular environment mode. For example, if this field was set to “Production” then WOW would prevent the project schema from being accessed if the WOW Environment Mode was set to “Test”

  • Updates - A list of the updates which have or have not been applied to the project schema