Process Apps → About Process Apps → Process Apps → Global Process App and Global Application
Every SBM database includes the Global Process App, which is a special process app that contains only the Global Application.
The Global Application initially includes system auxiliary tables—Companies, Contacts, Problems, Resolutions, and others—and their associated default icons. In a system upgrade from TeamTrack, the Global Application initially also contains any other existing auxiliary tables and scripts that are not associated with a single specific application and any existing triggers that are used in transition actions.
To access the Global Application, you first "get" the Global Process App in into the repository (as described in the Application Repository documentation. Then, you can create a reference to the Global Application in an existing process app. (See About References for details.) You can also check out the Global Process App, modify its contents, check it in, and publish and deploy it like any other process app.
When you open the Global Process App, the repository could list several Global Process Apps, identifiable by the names of the environment sets from which they were gotten, as in Global Process App (environment-set-name). For example, an environment set might include Development, Testing, and Production environments for a single SBM system; your company might have multiple environment sets.
The name of the Global Application initially includes the environment set name in parentheses. This helps you remember from which environment set the Global Process App that contained it was obtained. If you decide to rename the Global Application for some reason, you may want to consider leaving the environment set name unchanged in the new name for the Global Application. This helps you avoid the potential problems associated with deploying the Global Application to a different environment set.
For example, if the Global Process App from one environment set is deployed to an environment in a different environment set, and that second Global Process App is gotten into the repository, SBM Composer could display two triggers with the same name, and you have no way to tell which of the Global Process Apps they came from.
You can also create roles and assign role privileges for auxiliary tables that are defined in the Global Process App. The role privileges are granted to users and groups that you assign to the roles on the base project in Application Administrator.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.