Define the second-level element of your organization by creating a
division.
-
In the header of Dev Studio, click .
-
In the Organization Name field, specify the name of an existing
organization data instance, a key to an Organization instance.
-
In the Division Name field, enter the name of this division, for
example, Finance. Begin the name with a letter and use only letters, numbers, the
ampersand character, and hyphens. Division identifiers are limited to 32 characters.
As a best practice, limit the division name to no more than eight characters in
length. When you use App Studio, the division name becomes one segment of
several class names.
-
Click Create and open.
- Optional:
Identify an access group to be available to users in this organization. As a user or
other requestor belonging to this division signs on, the system adds the RuleSets and
versions in the application rules of that access group to the user's RuleSet list.
-
In the Defined by list, select
an Application-based
Access Group
.
The selection an Explicit RuleSet list
remains available for
Division data instances created in Version 4 systems. However, this approach is
deprecated for new development.
-
In the Access Group Name field, identify one or more access
groups that contains one or more access roles. Mark one access group as the initial
default by selecting a radio button. In specific, unusual situations, this access
group is used at sign-on, for Operator IDs where no access group is present on the
Access tab. (This can occur only for operators created in version 6.1SP1 or
earlier.)
- Optional:
Determine to whom an assignment is routed or an email is addressed.
-
In the Cost Center field, enter the cost center for the
division. This field is not referenced by any standard rules but appears in the
organization chart.
-
In the Cost Center Manager field, enter the Operator ID of a
user of the application who can receive assignments or email. This field is not
referenced by standard rules but appears in the organization chart.
-
Click Save.
What to do next: If the Associated RuleSet is [none]
, the
associated RuleSet is set to the RuleSet from the current application of the logged-in user.
This association assists with application packaging. You can update the associated
RuleSet by using the field in the top left of the form.