Skip to main content

Advanced Settings

Configuring advanced settings on a Data Element

Updated this week

Data normalization ensures your data is structured, consistent, and optimized for use across applications. These advanced settings provide fine-grained control over how your data attributes are processed and presented.

Advanced Configuration Options

The following advanced configurations control how data attributes are normalized and processed within your system.

1. Enable Fallback Expression

Configure default values for missing data elements using SPEL (Spring Expression Language) expressions. When enabled, an expression editor allows you to define fallback logic.

Available Variables:

  • attribute - The current attribute

  • document - The document containing the data

  • metadata - Associated document metadata

  • family - The document family

Example Expressions:

Set a static default:

"Default Value"

Use metadata with fallback:

metadata['author'] ?: 'Unknown Author'

Reference document family:

family.name ?: 'General'

2. Enable Serialization Expression

Define custom formatting rules for data serialization to JSON, XML, or CSV formats. The expression receives the data attribute as root object with the value available as #value.

Example Expressions:

Convert to uppercase:

#value.toUpperCase()

Format numeric values:

T(String).format('%.2f', #value)

Append suffix:

#value + "_normalized"

3. Multivalue Attribute

Enable storage of multiple values for a single field.

  • When to use: Fields requiring lists or collections (e.g., multiple email addresses, tags)

  • Configuration: Enable the "Multivalue" option

4. User Editable

Control whether users can modify attribute values through forms.

  • When to use: Fields requiring manual user input or correction

  • Configuration: Enable the "User Editable" checkbox

5. Not User Labeled

Hide attributes from user-customizable labels.

  • When to use: System fields or internal attributes not relevant to end users

  • Configuration: Enable the "Not User Labeled" option

Advanced Normalization Best Practices

  1. Establish Format Standards: Define consistent formats for dates, numbers, and naming conventions before applying expressions

  2. Optimize Multivalue Usage: Enable only when truly needed to maintain performance

  3. Implement Robust Fallbacks: Design fallback expressions to handle edge cases gracefully

  4. Validate Serialization Logic: Test expressions thoroughly in a sandbox environment

  5. Audit User Permissions: Regularly review which fields are user-editable based on security requirements

Performance Considerations

When using these advanced settings:

  • Expression Complexity: Keep SPEL expressions simple for better performance

  • Multivalue Impact: Each multivalue field increases storage and processing overhead

  • Serialization Load: Complex serialization expressions may impact export performance

Benefits of Advanced Normalization

  • Data Integrity: Enforce consistency at the system level

  • Automated Cleanup: Reduce manual data correction efforts

  • Integration Ready: Ensure data meets external system requirements

  • Audit Compliance: Maintain data standards for regulatory needs

Did this answer your question?