2017 June Release

app.ducx Organizational Structure LanguagePermanent link for this heading

With app.ducx organizational structure language abstract organizational elements and access elements can be modelled.

Fabasoft Folio allows you to represent an organizational structure using abstract and concrete structure elements. These organizational structure elements can be used for assigning access rights and for defining actors in a workflow.

The following abstract elements are defined using the app.ducx organizational structure language and can be used to model an organizational hierarchy independently of users and groups:

  • organizational units define abstract areas of an organization (e.g. "manufacturing", "sales", "department")
  • positions are used to split up organizational units into functional tasks and areas of responsibility (e.g. "production manager" in organizational unit "manufacturing", "customer representative" in organizational unit "sales").

The benefit of the abstract elements is that you can model the organizational structure without taking into account actual users and groups. The concrete elements of the organizational structure – users and groups – can be linked to the abstract elements when your software component is deployed to the customer.

In a customer installation, groups can be linked to abstract organizational units, and users can be assigned to groups. A user can be member of one or more groups. Moreover, roles can be assigned to each user. A role is defined as the position that a user can occupy within a given group.

For instance, assume that Jane Bauer is the manager of the Sales business unit. This can be modeled in Fabasoft Folio by assigning a role to user Jane Bauer that is comprised of position “Manager” and group “Sales”. Furthermore, the “Sales” group must be assigned to organizational unit “Business Unit”.

Note: Users and groups are always created in the customers’ Fabasoft Folio Domains whereas the abstract elements, positions and organizational units, are defined using the app.ducx organizational structure language, and shipped with your software component.

An organizational structure model block consists of import declarations and organizational structure elements. The orgmodel keyword denotes an organizational structure model block. It must be followed by the reference of your software component and curly braces.

Organizational structure model blocks can only be contained in files with a .ducx-os extension.

Cloud profile note: Organizational structure models are not supported.

Syntax

orgmodel softwarecomponent
{
  // Import declarations
  import softwarecomponent;

  // Organizational structure model elements (positions, organizational
  // units)

  ...
}