Organizing Processes in Applications
Applications are used to group objects in a hierarchy; they can be nested inside one another.
Applications have their own section in the navigation bar.
When an application is selected in the navigation bar, the objects in that application are shown in the main pane ordered by the type of object. This allows you to quickly and easily locate an object or a group of objects.
Applications can contain other applications. This means that you cannot delete an application which has child applications or contains objects. You must first remove the contained objects from the application. This can be done by deleting contained objects, moving them to another application (by changing the value in each object's Application field), or setting their application to null.
Additionally, applications can be exported to a CAR archive file, using process definition System_ExportApplication or manually. These archives can then be imported with the System_Import_Archive process definition into other Repositories. This allows for easy migration from a DEV or QA environment into a PROD environment.
Business Keys
There are two types of business keys for applications. The first was defined as <Item>.<Item1>.<Item2>...<ItemN>, where <Item> would be a Partition and <ItemN> an Application or Partition. So the first item is always a partition, and the second always an application. The rule for subsequent items is that if the partitions stayed the same it would not be written out as an item. This potentially caused issues.
Type 2 business keys were introduced to avoid issues and are defined as follows: item 0 and all even items are always partitions, and item 1 and all odd numbered items are always applications. $2 is appended to version 2 business keys.
Example:
Tree of three applications all in the same partition:
MyPart.MyApp
MyPart.MySecondApp
MyPart.MyThirdApp
Type 1 Business Key
MyPart.MyApp.MySecondApp.MyThirdApp
Type 2 Business Key
MyPart.MyApp.MyPart.MySecondApp.MyPart.MyThirdApp.$2
Context-Menu
Applications support the following context-menu actions:
| Action | Description |
|---|---|
| Edit Security | Edit the security of the application |
| Duplicate | Make a copy of the application to create a similar one |
| Delete | Delete the application |
| Monitor related Processes | Go to the processes monitor, enable a temporary filter showing all processes related to the application |
| Export tree | Export the application and all its children into a CAR file |
| Edit | Edit the application |
| Show permalinks | Show links that can be used from third party applications to link to the object |
| Add to navigation bar | Add the current object to the navigation bar |
| Expand All | Expand all objects in the application |
| New application | Create a new application |
Deleting Applications
You can only delete libraries when no other objects relate to them. For example, if there are process definitions that use the application, the application cannot be deleted until all process definitions that use it have been modified. You can see all process definitions that relate to the application in Related Objects in the lower detail pane and on the show page.
The table in related objects contains three columns:
- Type - the type of object with a link to it
- Related Object - the name of the object with a link to it
- Used As - objects can sometimes be used in different roles
Security
| Privilege | Description |
|---|---|
| Application.Create | Create applications |
| Application.View | view applications |
| Application.CreateChildren | Create child-applications |
| Application.Edit | Edit applications |
| Application.Delete | Delete applications |
You can grant privileges on two levels, Access and Admin; a privilege granted on Admin level allows the grantee to grant the privilege to other users. These privileges can be granted per partition or system-wide.
The Security tab allows you to specify which users can access, edit, create children of, and delete the application.