Back to Concepts and HOW TOs

Contents 1 Description 1.1 DesignGroups Status 1.1.1 DesignGroup Filtering 1.2 DesignGroups: Shared Areas 1.3 Depot 1.4 Production 1.5 Datasource 2 See Also 3 Tags

[edit] Description

DesignGroups let you collaborate with team members on a project (projects contain your Model code). The owner (SuperAdmin) of the DesignGroup invites members to join and can control who is active (can check objects in and out) in the DesignGroup.

• Each developer may create and/or join any number of DesignGroups (there is no policy limit for the number of DesignGroups a developer may belong to or create).
• Each developer has individual control of how public or private his/her work is. For example, by including other developers in a DesignGroup, applications developed within that DesignGroup are shared among its members via Bungee's check-in/check-out control capability.
• Members of a DesignGroup are not limited by geographical location. Members of a DesignGroup can include developers from anywhere there is Internet access.

Note Developers within the same DesignGroup share information and application projects. Care should be taken when choosing developers to invite to join a DesignGroup.

[edit] DesignGroups Status

Each member of a DesignGroup has a status within the group.

• SuperAdmin: the owner of the DesignGroup who has the right to invite others to join the group, suspend group members, or transfer the SuperAdmin status to another group member
• Active: the user is active in the DesignGroup and can participate in development, deployment, etc., within the DesignGroup
• Withdrawn: the user removed themselves voluntarily from the DesignGroup and can no longer participate in development within the DesignGroup. The SuperAdmin is the only one that can restore the user to the Active status.
• Suspended: the user was removed from the DesignGroup by the SuperAdmin and can no longer participate in development within the DesignGroup. The SuperAdmin is the only one that can restore the user to the Active status.
• Pending: the user is invited to join a DesignGroup and the user has not yet accepted the invitation.

[edit] DesignGroup Filtering

When a member of a DesignGroup has withdrawn or been suspended, the solutions within that DesignGroup will no longer be visible in their Open Solution dialog.

[edit] DesignGroups: Shared Areas

When you’re developing applications in Bungee Builder, you’re working in your own Workspace, even if you’re participating in someone else’s DesignGroup. However, members of a DesignGroup share a common Depot, production space (Production), and Datasource.

[edit] Depot

The Depot is where objects are checked in. Once an object is checked into the Depot, any member of a DesignGroup can check out the object, make changes, and check it back in (see Understanding Check In and Check Out).

[edit] Production

From the Staging tab in Bungee Builder, you post AppProjects from the Depot to Production. The same AppProject can be posted multiple times as different versions of the same application and you can control which version of an application is deployed to your users (see Managing a Deployed Application).

[edit] Datasource

Datasources can be used to persist user data with a defined scope, such as:
• User
• Application
• Deployment
• Posted application (cord)
• Global

[edit] See Also

Creating a DesignGroup
Understanding Check In and Check Out
Managing a Deployed Application
Datasources

[edit] Tags