BpmFlow
  • BPM Flow Manual
  • Introduction
    • Road Map
  • Installation
    • GemStone/S
      • Login to GemStone/S
        • Login to GemStone/S with JADE
        • Login to GemStone/S with Topaz
    • BPM Flow
      • Run Web Server from Interactive Session
      • Run Web Server from Script
    • Highcharts
    • Orbeon
  • Application Setup
    • Scripts to run the Application
    • Listing OS Processes
    • Indexing
  • Application Manuals
    • Backoffice Manual
      • Main Menu
        • Applications
          • Manage Environments
          • Manage Applications
          • Manage Orbeon Forms
          • Manage Calendars
        • Processes
          • Processes Definitions
          • Define New Process
            • Performers and Roles
            • Gateways Conditions
            • Versioning
            • Remove BPM Process Definition
            • Define a Task to run a Script
            • Bizagi Extended Attributes
            • RACI roles
            • Import Errors Codes
              • Generic errors codes
              • Activities error codes
              • Gateways error codes
              • Subprocess error codes
              • Runtime evaluations error codes
              • Interprocess Comunication codes
              • Integration error codes
              • Unsupported elements error codes
              • Transitions errors codes
          • Monitor Processes
          • Browse Timers
          • Process Categories
          • Cancelled Processes
        • Users and Roles
          • Monitor Users
          • Manage Users
          • Manage Roles
          • Import Roles and Users
          • Export Roles and Users
        • Messages
          • Inbox
          • Outbox
        • Configuration
          • User Preferences
          • Server Setup
          • Login Mode
          • Change Password
          • Set Language
          • Internationalization
    • Frontoffice Manual
      • Main Menu
        • My Tasks
          • Current Tasks
            • View Process Status
          • Finished Tasks
          • Process Categories
        • Unassigned Tasks
          • View Unassgined Tasks
        • New Process
          • Available Processes
          • Granted Tasks
        • Messages
          • Inbox
          • Outbox
        • Configuration
          • Change Password
          • Display References
          • Set Language
      • Main Menu
    • BI Manual
      • Main Menu
        • Dashboards
          • Current Dashboards
          • Old Dashboard
          • Historical Dashboard
        • User Charts
          • My Charts
        • System Charts
          • Global Charts
          • Applications Charts
          • Untitled
          • Processes Charts
            • Creation Day
            • Field Values
            • Field Evolution
            • Processes Average Time
            • Processes Instances
            • Tasks HeatMap
          • Roles Charts
            • Number of Tasks
            • Number of Users
            • Unassigned Tasks
            • Users in Time
          • Users Charts
            • Current Tasks by Type
            • Possible Tasks
            • Finished Tasks by Type
            • Tasks Average Time
        • Compare Fields
          • Field Comparison
        • Chart Repository
  • Functional and Technical Information
    • Anonymous Process Creation
    • Scalable Vector Graphics Support
    • Timers
      • Event Monitor Timespan
      • Process Creation Timer
      • Task Timers
      • Timers and Caledars
    • States
      • Process States
    • Tasks Assignation Policy
    • Partial Execution Framework
      • Technical Information
      • Functional Information
    • Roles and Performers
    • Debugging Process Execution
      • Manually inspect a BPM Process Instance
      • Automatically Generate a Test Case
  • Engineering Models
    • 4+1 Architecture Models
      • Logical View
        • BPM Components Architecture
        • BPM Environments or Tenants
        • Users & Roles - Processes & Forms
        • BPM Model
        • Orbeon Form Model
        • Seaside Component Model
        • Task Creation Clockwork
        • XPDL Process Generator
        • User Messages
          • User Inbox
          • User Outbox
        • Searching Field values in Bpm Processes
      • Development View
      • Process View
        • Seaside Orbeon Integration
          • GemStone to Orbeon
          • Orbeon to GemStone
      • Physical View
      • Scenarios
    • Architecture for Atop Applications
      • Atop Model Integration with BPM Flow
        • User Methods
          • asBpmUser
          • canDelete
          • finalizeAssignment
          • getAllAvailableTaskAssignmentsIn
          • getAllTaskAssignmentsWithId
          • getApplicationsIn
          • getBackofficeApplicationsIn
          • getBpmEnvironments
          • getCurrentAssignmentsIn
          • getMyTaskAssignmentsWithId
          • getProcessInstanceCategoriesFor
          • getProperty
          • getVisibleRolesIn
          • getVisibleUsersIn
          • isInAdminsEnvironment
          • languageName
          • lateralListPagingSize
          • regularListPagingSize
          • roleName
          • rolesIn
          • take
          • transitionDisplayModeIsExpanded
          • untake
          • username
          • userOptions
        • Role Methods
          • asBpmRole
          • bpmApplication
          • bpmEnvironment
          • getApplicationName
          • isBackofficeRole
          • isGranted
      • BPM Subclassification
        • Create subclass of Bpm Process Browser
        • Create subclass of Process Task List
        • Create subclass of Role Manager
        • Create subclass of User Manager
        • Create subclass of Unassigned Tasks Bag
  • Troubleshooting
    • Requests from Orbeon
  • Orbeon Integration
    • Orbeon Persistence Layer for GemStone/S
      • Install GemStone/S
      • Install Persistence Layer
      • Manage Persistence Layer
        • workwith script
        • List of Scripts
        • upgradeGemStone script
      • Manual Configuration
        • Restrictions when Saving Forms
        • Path for Attachments
        • Maintenance of OS Files and Attachments
        • Search Types
        • Indexing
        • Forms Audit
        • Deferred Processing
      • Service Diagrams
        • Form Runner Home
        • Publish or Unpublish Forms in Form Runner
        • Form Builder Summary
        • Orbeon Form Builder Toolbox
        • Forms Summary
        • Save Form Definition in Orbeon Builder
        • Publish Form Definition in Orbeon Builder
        • New Form with one draft
        • New Form with more than one draft
        • Edit
      • Service Http Methods
        • PUT
        • GET
        • POST
        • DELETE
        • LOCK & UNLOCK
      • Technical Information
        • 4+1 Architectual Model
          • Logical View
            • Objects relation Summary
          • Development View
          • Process view
          • Physical view
          • Scenarios
          • Troubleshooting
            • Request From Orbeon
      • Migration from Relational Database to GemStone/S
        • Migration from MySQL
    • Persistence Layer Backoffice
      • Orbeon Server Configuration
      • Orbeon Application Viewer
      • Create Charts with Highcharts
        • Chart Examples
      • Migrate from Relational Database
Powered by GitBook
On this page
  1. Engineering Models
  2. 4+1 Architecture Models
  3. Logical View

BPM Environments or Tenants

PreviousBPM Components ArchitectureNextUsers & Roles - Processes & Forms

Last updated 6 years ago

An Environment is a collection of Applications and Users. An Application has a collection of Bpm Processes Definitions, Roles and Forms. And a User has a collection of Roles.

BpmFlow can work in two different modes with Environments: 1- Users Multi Environment Users are enabled to be part of more than one environment and at login time the user has to select the environment to work with. This mode is used in Governments when each environment represent a Ministry and a user can work on more than one Ministry. It is also used when the same people run two different companies and each environment is a company. A user has to have access to all companies. The user must select an Environment at login time. Once the user is logged the Environment is stored in the user web session. In order to work with other Environment the user has to logout and login in a different Environment. As it is shown in the below figure a user can have access to more than one Environment. 2- Users Single Environment Users are only enabled to be a part of only one environment and at login time there is no need to select the environment. This mode is used in SaaS (software as a service) installations where each environment is a different company and companies do not have relations with each other (users only access to one company). In this case an administrator set the environment for each user and at login time is not necessary to select the environment. In this mode there is an exception where admin users can be part of more than one environment. These admin users do the configuration of the SasS installation. Once the user is logged the system detect its Environment and store it in the user web session.

This configuration has to be set immediately after the installation by a system administrator: BpmEnvironment areUsersMultiEnvironment: true. "for option one" BpmEnvironment areUsersMultiEnvironment: false. "for option two"

Application names are global to the whole System (including Environments). Two Applications even in different Environments can not have the same name.

To checkout all objects affected by Environments search implementors and senders of bpmEnvironment method.

User multi environment diagram