SBM
includes a Global Process App, a special process app that contains only the
Global Application. For on-premise systems, the Global Application initially
includes the system auxiliary tables—Companies, Contacts, Problems,
Resolutions, and others—and their associated default icons. In an on-demand
environment, the Global Application contains only the system Contacts table.
For details on using the Global Process App in
SBM
on-demand, refer to the
SBM Application Administrator
Guide.
The Global Application is referred to by all process apps that use its
contents. Deploying the Global Process App (or any process app that contains
the Global Application) affects all process apps that contain or refer to the
contents of the Global Application.
On-premise only — Note the following important information about
the Global Process App:
- When you create an environment, you see the Global Process App listed
on the
Deployments sub-tab as
Global Process App (environment–set–name).
For the Global Process App to be available to designers using
SBM Composer,
you must
Get the process app from the
SBM Application Engine server. This
puts the process app in the
repository, and
displays it on the
Process Apps tab in
Application
Repository.
- The Global Process App or any process app containing the Global
Application should be deployed and promoted
only to an environment in the same
environment set as the environment from which the Global Process
App was originally loaded. If you deploy or promote the Global Process App or
any process app containing the Global Application to a different environment
set, the Global Process App in the destination environment will contain
everything in the deployed Global Process App, and some system-provided
elements in the destination Global Process App will be overwritten.
- When you deploy or promote the Global Process App or any process app
containing the Global Application, set the
Stop Deploy or
Stop Promotion option to
on any warning. In this way if you inadvertently
deploy the wrong Global Process App or Global Application, the deployment or
promotion will stop and give you an opportunity to confirm you are deploying
the process app to the correct environment.
Promoting the Global Application (On-Premise Only)
To replicate users and groups (and other global configuration
entities) from one environment to another, you must promote the Global Process
App or any process app that contains the Global Application.
When the Global Application is part of a
promoted process app (for example, when you promote the Global Process App),
the following design and runtime data elements associated with the Global
Application are promoted:
Design
|
Runtime
|
- Auxiliary tables not directly associated with an
application. This includes system auxiliary tables (Companies, Contacts,
Problems, Resolutions, Languages, String Identifiers, Strings) and any
customer-added auxiliary tables that do not belong to a particular application
and could be used across applications (for example, a Parts table).
- Design data associated with the auxiliary tables (for
example, Fields, Dependencies, Labels, Custom Forms, and Icons); however, you
can select an option to exclude auxiliary table design data if you do not want
to update the field definition for tables in the destination environment.
- Scripts associated with the Global Application.
- Resources (such as images, style sheets, and JavaScript
files) associated with the Global Application.
- Custom strings associated with the Global Application.
- Triggers.
- Web services not associated with a particular
application.
|
- Users
- Groups
- Folders
- User field selections for global auxiliary tables
- Notifications associated with global auxiliary tables
- Reports associated with global auxiliary tables
- E-mail templates associated with global auxiliary tables
- User settings
- Custom themes
|
Copyright © 2007–2019 Micro Focus or one of its affiliates. All rights reserved.