Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating a division

Updated on August 10, 2022

Define the second-level element of your organization by creating a division.

  1. In the header of Dev Studio, click Create OrganizationDivision.
  2. In the Organization Name field, specify the name of an existing organization data instance, a key to an Organization instance.
  3. 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.
  4. Click Create and open.
  5. 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.
    1. 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.
    2. 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.)
  6. Optional: Determine to whom an assignment is routed or an email is addressed.
    1. 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.
    2. 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.
  7. 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.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us