Using Publication For Capella Web Client

To create a new project, click on the '+' button in the Web Client Welcome Page. This displays the following form:

The name of a project must contain less than 1024 characters. If the name is not valid, a warning message is displayed and the 'Create Project' button is disabled.

To rename a project, open the project contextual menu in the Web Client Welcome Page and select 'Rename'.

Change the name and click on 'Rename' to rename the projects, or click on the background (or press 'Escape') to cancel the renaming.

To delete a project, open the project contextual menu in the Web Client Welcome Page and select 'Delete'.

Click on 'Delete' to confirm the deletion, or click on the background (or press 'Escape') to cancel the deletion.

The model explorer, in the left panel, can be used to navigate inside the structure of the model(s) available in the current project.

The top-level elements in the explorer correspond to the models themselves (1). Inside of it the user can find the actual model elements (2), which correspond to the content of the .capella model, and all the exported diagrams (3) organized by category (4).

Clicking on any element in the explorer will select it and display its corresponding information in the main panel, and details in the right panel. The information displayed in the main panel depends on the type of element selected. See Main Panel - Model Navigation for more details.

When navigating in the model elements, the explorer selections stays the same. To select the currently viewed element in the explorer, click on the target icon on top of the explorer.

Model Objects within a project can be searched in two ways:

The main panel displays useful information about a particular object, which can be a 'Model' or a 'Model Object', including a special kind of of model object that is a 'Diagram'.

The details display the selected object’s attributes, as defined by its meta-class.

The value of the properties cannot be edited. If the user attempts to edit them, an error message will be displayed.

There is exactly one history per project, which contains:

The history panel displays a list of the changes related to the current selection. Changes are displayed in a compact way but leaving the mouse over them displays a pop-up with detailed information.

Previews of model objects and remote artifacts linked through OSLC are available when hovering several elements:

The project settings visibility tab makes it possible to edit a project’s visibility (either private or public).

You can create a new organization using the 'Create Organization' button.

Clicking on an organization in the organizations list leads to the organization page.

In this organization page you can manage the projects inside the organization, people who have access to it and teams to bind people acces to projects.

You have to allow users to access your organization. To add a user to a organization, click on the 'People' tab of an organization page.

Then click on the 'Invite' button.

Enter his or her user name in the field and click on the 'Invite' button.

To remove a member from a organization, use the delete action next to the user in the organization page.

Members can be assigned a role within the organization:

To change the role of a member within the organization, click on its role and change the value in the drop down menu:

When migrating from a previous Publication For Capella version, the Default Organization will automatically be created (Refer to the installation guide, section 'Migrating to 2026.5.0' for more details) using the name specified by the perseus.default.org.name property. On any empty database, a default organization will be created the first time the server is launched with an available administrator account.

Only organization administrators can delete an organization. To delete an organization, click on the delete action next to the organization.

You can create a new team using the 'Create New Team' button.

You can then rename the team using the pen icon or delete it using the trash icon.

To add members and access rules to the team, click on the team name to access the team page.

To add a member to a team, use the 'Add member' button. Enter his or her user name in the field 'Member' and click on the 'Save' button.

To remove a member from a team, use the cross next to the user in the team page.

The team system allows to parameterize three access levels:

To create a project access rule in a team, use the 'New Project Access Rule' button.

Click on the 'Grant access' button.

Once granted, an access rule can be deleted using the trash icon or updated by creating a new access rule on the same project.

The model explorer view is filter according to the criteria defined in these settings. Each user can have its own settings, and they all inherit the server default settings if they don’t explicitly change these settings.

The server administrator can edit the server default settings and reload these default settings so that they become active for every user that has not explicitly configured their own settings.

The settings are based on two simple concepts:

To be displayed in the Model Explorer, an object must have a type (i.e. a meta-class) that complies with the following constraints:

For example, the default settings define two patterns:

The list of meta-classes to display in the explorer can be edited for each pattern. The editor offers completion features to facilitate the selection of the relevant type.

It is also possible to add or delete a pattern. The bottom text Field labeled 'New Pattern' can be used to enter the name of a new pattern to add. Then, the user must click on the 'Add' button.

A pattern and the associated list of meta-class names can be deleted from the settings by clicking on the delete icon of the corresponding panel.

Three buttons are available at the bottom of the page:

The Security tab provides users with means to understand and act on their security authorizations.

It lists all active authorizations, either:

Each of those authorizations can be revoked at any time using the delete action.

Administrators (and administrators only) can manage the registered or provisional consumers (friend servers) on a dedicated page. That page can be accessed via the administrator user menu, by clicking on the menu item Consumers:

When a third-party server has issued a friend request and it has not yet been validated by a server administrator, the request is 'provisional', which is materialized by the yellow question mark icon.

Clicking on a consumer leads to its dedicated consumer page:

Administrators can edit consumers as follows:

The first operation that needs to be performed to connect to a third-party repository is to emit a so-called 'Friend Request' to this repository.

Once the OSLC 'friendship' is established between the Publication For Capella server and a third-party repository, each Project Administrator can define 'OSLC Associations' between their Publication For Capella project and OSLC Service Providers of a friend server.

The association configuration page can be found in project settings, under the "Associations" tab:

Once a friend is selected, a service provider can be selected among available ones:

Clicking on "Create OSLC Association" will add the association to the list. This button is grayed if the association already exists:

An association can be deleted from the list, this will display a warning dialog.

An association can be parameterized by clicking on the pen icon next to it. A dialog makes it possible to change the following options:

Once at least one OSLC association has been configured on a Publication For Capella project, users that are allowed to edit the project can create links to artifacts hosted on the friend repositories.

See sections External Links, Add an OSLC Link, Delete an OSLC Link, or for more details.

The OSLC Linking Configuration makes it possible to configure, to some extent and depending on the third-party repositories capabilities, the kinds of links that can be created to third-party repository objects.

For example, it is possible to allow the creation of links 'satisfies' from Capella LogicalFunctions to third party Requirements, and of links 'refines' from Capella Logical Components to third-party Requirements.

Publication For Capella supports OAuth 1.0 to authenticate users with Friend servers (except CodeBeamer, which does not support OAuth 1.0 and with which authentication is made using HTTP Basic).

OAuth 1.0 is an authorization framework that makes it possible to have Publication For Capella communicate with third-party servers, on behalf of a user, without having to know the user’s login and password on the friend server.

This authentication can be triggered on different occasions, whenever a user action in the Publication For Capella web site requires authenticated communication with a friend server.

A pop-up frame will be displayed to the user. This frame embed a page from the Friend server that will ensure that the user is properly authenticated on the remote server and allows Publication For Capella to access the friend server on their behalf.

On the user has confirmed that he or she agrees on Publication For Capella accessing the friend server on their behalf, an access token is securely generated and will be used for further communication between the Publication For Capella server and the friend server. Depending on the friend server’s implementation, this access token might have a limited duration. As long a this token is valid, the user will be able to access the friend server from the Publication For Capella server. As soon as this token in invalidated, for whatever reason, the OAuth authentication process described above will be triggered again.

The following figures show how this authentication looks like when accessing a Polarion server from Publication For Capella.

To use Global Configuration, Publication For Capella must be associated with a friend server that provides Global Configurations. A project will then require an association to a Global Configuration service provider of this friend server.

On the friend side, Global Configuration must be activated and at least one configuration must exist.

In Publication For Capella, the use of Global Configuration is decided on a per-project basis. Deciding to use Global Configuration on a Publication For Capella Project is a final decision, it cannot be reverted afterwards.

To activate the use of Global Configuration on a project:

Once activated, the button is no longer available and a message indicates that Global Configuration has been activated for this project. A subtitle appears under the project name:

For the time being, each model should correspond to a single stream of work for this model.

Once the Global Configuration mode has been activated for a project, the models it contains can be assigned a Global Configuration as follows:

Once assigned, any OSLC link created on any of this model’s objects will use the configuration to retrieve the remote element data:

The project can be filtered to only display information related to a specific Global Configuration as follows:

Some operations can cause links to become technically invalid. That is the case if the remote server does not respond properly to a link change request, whatever the reason (the server could be in maintenance, or overloaded, or anything else).

This section describes the maintenance tools that can be used to act and hopefully repair such invalid links.