Properties

Request properties in Weissr Capex are structured data points that define and describe requests. These properties are used throughout request and expenditure workflows to maintain accurate, structured, and consistent information. Examples include Request Name, Requested Amount, Production Unit, Project Manager, and even supporting documentation like images.

Properties can be either built-in (system-defined) or dynamic (custom-defined by users). They help organizations tailor data entry to their internal processes, ensuring both flexibility and control.



Property categories

Static system properties

Predefined and core to Weissr’s functionality. These cannot be deleted or customized. Examples: Request Name, Requested Amount, Analysis Start Year, Production Unit.

For a full list and detailed descriptions of system properties, refer to: System Properties for Capex Management

Dynamic properties

Custom properties created by admins to meet specific organizational needs. Unlimited in number. Examples: Background, Risk Assessment, Cost Center, Profit Center.


Availability across request types

Global properties

Available across Capex, Expenditure, and Budget request types.
Used in investment forms, expenditure grids, and visible in all request views.
Example: Creation Date, Name

Capex properties

Specific to capital investment projects.
Used in investment forms and request list views, including capital budgets.
Example: Project Manager, Requested Amount, NPV (Pre-decision), Payback Period

Expenditure properties

Used in expenditure grids to track financial outlays.
Do not support model integration or expressions.
Example: Expense Type, Useful Life, Commitments


Required vs optional properties

Properties can be either mandatory or optional, depending on workflow requirements.

  • Required properties prevent request progression until completed.

    • Highlighted in red for capex request forms.

    • Mandatory input for new expenditure lines.

  • Optional properties provide added detail but do not block progression.


Visibility and access control

You can manage which user groups can see or edit each property.

  • Public properties: Visible to all users with access to the production unit.

  • Restricted properties: Controlled via user group permissions:

    • No Access

    • Read-Only

    • Full Edit

To restrict a property:

  • Go to Properties → List

  • Toggle Is Public OFF

  • Assign group-level access via User group permissions

Superusers have full access. Some system properties cannot be restricted.


Supported property types

Category

Property Types

Text and Input

Text (single/multi-line), Integer, Decimal, Boolean, Fiscal Year

Financial

Money, Currency

Date

Date

Lookup

Code (dropdowns), Country, Node

Organizational

User, Production Unit

Media

Image

Logic

Expression (read-only, calculated)

Advanced

Counter, Table

For more details, see: Property Type Descriptions



Property relations (dependencies)

Weissr supports dynamic behavior by letting one property’s options depend on others.

  • Single-property relation: One-to-one dependency
    E.g., Investment Category depends on Production Unit.

  • Multi-property relation: One-to-many or many-to-many
    E.g., Investment Form depends on Company, Investment Type, and Requested Amount.

If only one result is valid, it will be auto-selected.


Expressions and calculated properties

Properties can auto-calculate values using expressions:

  • Math operations: Total = A + B

  • Logic: IF(ProjectType = "Large"; Budget * 0.2; Budget * 0.1)

  • Aggregation: SUM(Expenditures)

These properties are always read-only and update automatically.
See: Using Property Expressions


Investment model integration

Properties and investment models can exchange data:

Retrieve values from model:

  • Pulls data from a specific row (first-year column).

  • Updates automatically when the model changes.

  • Example: Total Revenues property linked to Total Revenues row.

Use property values in model:

  • Injects values into the model for calculation or logic.

  • Example: A Risk Rating property influencing risk-weighted cash flows.


KPIs

Weissr supports built-in and custom KPIs to evaluate investment proposals:

Built-in KPIs

  • NPV – Net Present Value

  • DP – Discounted Payback

  • IRR – Internal Rate of Return

  • PI – Profitability Index

Custom KPIs

  • Create new properties to calculate or capture values

  • Combine them with expressions or model data as needed

See: Configuring KPIs in Weissr