Attributes

This page applies only if the new Decision Engine is enabled on your SD Elements instance. To check this is enabled, check the footer. Instances using the new Decision Engine display -te in the version string, for example: SD Elements v2026.6.1+2 -te © 2026 SD Elements Inc. All rights reserved.

Overview

Attributes are predefined Library objects that represent properties of a project in SD Elements. They are used as inputs in match conditions and rules to determine which content applies to a project.

An Attribute is added to a project when a user selects an Answer in the project Survey, or when a Component is present in the project.

When an Attribute is present for a project, it evaluates to True. When it is not present, it evaluates to False.

Attributes and Answers

Each Survey Answer can be mapped to one or more Attributes. When a user selects an Answer in the project Survey, the mapped Attributes are added to the project.

For example, a Survey might include the following question:

Does the application store, process, or transmit credit card data?

If the user selects Yes, that Answer may imply an Attribute such as:

In scope for PCI

Rules can then use the Attribute to determine whether PCI-related content applies to the project.

Attributes and Components

Each Component in the Library implies one or more Attributes.

For example, a project may include an authentication Component. That Component may imply an Attribute such as:

Handles authentication

Rules can then use the Handles authentication Attribute to determine whether authentication-related content applies to the project.

This allows SD Elements to identify applicable content based on both Survey responses and Components present in the project.

Attribute hierarchy and implication

Attributes have a hierarchy in the Library. When an Attribute is added to a project, all of its parent Attributes are also automatically added to the project.

For example, if an Attribute Uses PostgreSQL is a child of Uses relational database, adding Uses PostgreSQL to a project will also add Uses relational database. Rules that reference the parent Attribute will evaluate to True without requiring it to be explicitly mapped.

View Attributes

View the full list of Attributes available on your instance.

Prerequisites:

  • The user has the permission Global Roles → Customization → Customize content.

Steps:

  1. Navigate to Library → Attributes.

  2. Use the search and filter controls to locate a specific Attribute.

Add a custom Attribute

Add a new Attribute to the Library.

Prerequisites:

  • The user has the permission Global Roles → Customization → Customize content.

Steps:

  1. Navigate to Library → Attributes.

  2. Click + Attribute.

  3. Enter a Name for the Attribute. This field is required.

  4. Optionally, enter a Description.

  5. Optionally, select a Parent Attribute. When a parent is selected, the new Attribute becomes a child in the Attribute hierarchy. If the Attribute is added to a project, its parent Attributes are also added automatically.

  6. Click Create.

The new Attribute is available in the Library and can be used in match conditions and rules.

Edit an Attribute

Update an existing Attribute in the Library.

Prerequisites:

  • The user has the permission Global Roles → Customization → Customize content.

  • To edit a built-in Attribute, the Edit Built-in Attributes feature flag must be enabled on your instance.

Steps:

  1. Navigate to Library → Attributes.

  2. Hover over an Attribute and click the pencil icon to open the edit form.

  3. Update the fields as needed.

  4. Click Save.

Changes to a built-in Attribute are not overwritten by product updates.

results matching ""

    No results matching ""