Core Database Elements

The Base Project serves as a root for your system's project hierarchy. The Base Project cannot be deleted, but it can be renamed to suit your company's needs. You can also set numbering properties for the Base Project. These numbering properties can be inherited by new projects created in the hierarchy.

The Base Workflow serves as a root for your system's workflow hierarchy. The Base Workflow cannot be edited, deleted, or used by any project.

Two types of root folders are provided for you to add to as needed:

• Public Folders – Public folders contain links to items that can be accessed by all SBM users. Users with appropriate privileges can view items in, add items to, and remove items from public folders.

• Knowledge Base – Knowledge Base folders contain links to items in the SBM Knowledge Base. Problems and resolutions can be published to Knowledge Base folders for internal and external viewing.

The Global Application is a container for system auxiliary tables and other assets that are generally 'global' across multiple process apps. The Event, Scripts, Triggers, Web Services, and Workflow nodes are not available in the Global Application because these design element types are generally not used 'globally' across process apps.

When designers add or edit items in the Global Application, these changes will be reflected in all process apps that reference the Global Application.

The following system auxiliary tables are contained in the Global Application and are provided for storing auxiliary information related to your workflows:

• Companies table – This table can be used to store information about the companies with which you interact. The Database Wizard provides two system required fields for this table (Company Name and Company Number), but you can also add custom fields, such as Address, City, State, Phone Number, and more. The fields can be modified at a later time, and all but the system required fields can be deleted.

• Contacts table – This table can be used to store information about individuals with which your company interacts. The Database Wizard provides five system required fields for this table (First Name, Middle Name, Last Name, User Name, E-mail, and Company), but you can also add custom fields that describe your contacts (such as Department or Job Title). The fields can be modified at a later time, and all but the system required fields can be deleted.

• Problems table – This table stores problem records that can be associated with a primary item, published to the Knowledge Base for either public or internal viewing, or both. The Database Wizard provides several fields for this table that can be modified at a later time. Additionally, all but two system required fields (Title and Visibility) can be deleted at a later time.

• Resolutions table – This table stores resolution records that can be associated with a problem contained in the Problems table and published to the Knowledge Base for either public or internal viewing, associated with a primary item, or both. The Database Wizard provides several fields for this table that can be modified at a later time. Additionally, all but three system required fields (Title, Problem, and Visibility) can be deleted at a later time.

The following system auxiliary tables are provided for translating SBM into one or more languages or for modifying provided labels in the end-user interface:

• Languages table – This tables stores language records that enable you to associate strings with a specific language, which is associated with a locale. This table is used in conjunction with the Strings and String IDs tables to enable users to view labels and error messages in the language associated with the locale specified in their user profile, if such strings exist.
• Strings table – This table stores string records that can be used to modify or translate elements, such as labels, button names, and error messages, into one or more languages.
• String IDs table – String identifiers contain the root string information and should not be modified.
  CAUTION:
  For best results, limit privileges to the Languages, Strings, and String IDs tables to users who will translate your SBM system into another language or are responsible for modifying existing strings. For example, you might grant privileges to these tables to a translator from a globalization vendor or to an SBM managed administrator who is authorized to modify string names. Before granting privileges to the Languages, Strings, and String IDs tables, refer to the SBM System Administrator Guide.

Refer to the Integration Guide for SharePoint for more information.