Skip to main content

Project settings

Introduction​

Project settings are configurations that can be done within a project in the Solution Builder. They can be used to enable and disable capabilities that are available in the Solution Builder, allowing you to customize the project environment based on your specific needs and development approach.

By configuring project settings, you can:

  • Tailor the available modeling capabilities to your project requirements
  • Enable or disable specific design methodologies and patterns
  • Optimize the development environment for your team's workflow
  • Control which tools and features are accessible within the project

Profiles​

Profiles define the modeling vocabulary and design capabilities available in your project through the Open Modeling Language (OML). Each profile provides a set of model elements, relationship types, and properties that can be used on the modeling canvas. By enabling or disabling profiles, you control which modeling capabilities are available to your project.

The profiles section displays a table showing the current state (enabled/disabled), name, and description of each available profile. You can toggle profiles on or off based on your project's requirements.

the list of available profiles is defined by the baseline of the project.

Accessing Project Settings​

To access and configure project settings:

  1. Open your project in the Solution Builder
  2. Navigate to the project settings page
  3. Enable or disable the capabilities based on your project requirements
  4. Save your configuration changes
ℹ️note

Project settings are project-specific and do not affect other projects in your workspace.

💡tip

Consider enabling only the capabilities you need for your specific project type to maintain a clean and focused development environment.

Global Settings​

Global settings are branch agnostic settings that affect your whole project. You can change them on the project settings page.

Single feature branch​

If you turn this setting on, you restrict the project to only one additional branch besides your default branch. With this setting, the whole team can work on one single branch in order to avoid merge conflicts.