Configuring Naming Conventions in Teamsware Bauakte
Consistent naming of your project rooms and document storage locations is crucial for clarity and governance. In the Teamsware Bauakte, you can define individual naming conventions for each application.
Step 1: Accessing Naming Conventions
Navigate to the Administration area in your workspace. Under the Settings and Governance section, you will find the Naming Conventions menu item. Click this button to open the management of naming rules.
Step 2: Overview and Selection
You will now see a list of all naming conventions already stored. Each rule is assigned to a specific App (e.g., Teams, Planner, or SharePoint). To adjust an existing rule, select the corresponding entry and click Edit in the top action bar.
Step 3: Basic Rule Configuration
In edit mode, you define the fundamental properties of the convention:
- Name: The internal designation of the convention.
- App: The target application to which this rule applies.
- Rule (Preview): Here you can see the resulting pattern (e.g.,
PR_Number_<Team Name>). - Add App Name: If this toggle is set to Yes, the project title entered by the user is automatically added as the placeholder
<Team Name>at the end of the convention.
Step 4: Defining Components in Detail
In the lower area, you will find the table Naming Convention Components. Here you build the logic modularly. When adding or editing a component, a side menu opens with the following options:
- Arrangement: Choose between Prefix (before the name) or Suffix (after the name).
- Position: Define the numerical order (e.g., 10, 20, 30).
- Content Type: Determine the data source of the component:
- Custom: Static text (e.g., an underscore or a fixed abbreviation).
- Attribute: Linking with values from other existing conventions.
- Metadata: Dynamic selection from the metadata fields defined in the Bauakte (e.g., project number).
Step 5: Saving and Applying
After you have configured all components, click Save. The naming convention is now active and will be automatically applied whenever new projects or elements are requested via a template package that uses this convention.
Related Articles
Managing Metadata in the Teamsware Project File
In the Teamsware Project File, metadata plays a central role in organizing your project data. In this area, you can centrally manage all metadata, add new fields, and control their usage. Accessing Metadata Management To edit metadata, navigate to ...How to Update Project Templates in Teamsware
When changes are made to a project template in SharePoint—for example, to the templates themselves, permissions, or metadata—this information must be re-imported into Teamsware. This process is performed via a Project Update for Professional and ...Creating and Configuring "Clone Team" Templates in Teamsware
The goal of a "Clone Team" template is to copy an existing reference team in Microsoft Teams 1:1. Depending on your selection, channels, tabs, apps, members, and folder contents are duplicated. This function is ideal for Teamsware administrators to ...How to Integrate External Companies into the Teamsware Project File
With the Teamsware Project File (Bauakte), you can securely involve external companies in projects without the hassle of manually creating guest accounts for every individual. For full collaboration, we recommend the Professional version featuring ...Getting Started with the Teamsware Construction Files Dashboard and Navigation
This article explains the home page of the Teamsware Construction Files interface and its main navigation. You will learn how to find projects quickly, request or create new workspaces, and which functions are visible to administrators. Prerequisites ...