Numeric and Currency
Numeric and Currency attributes capture measurable values in a structured format. They support consistent data entry, validation, calculations, reporting, and rule-based process decisions.
Numeric Attribute
A Numeric attribute is used for quantities, counts, measurements, durations, percentages, scores, or any other value that must be stored as a number rather than free text. It can be configured to suit whole-number or decimal-based input requirements.
Numeric values can be used in rules, calculations, filters, reports, and dashboards. This makes the attribute suitable for operational information that must be measured, compared, aggregated, or validated.
Use case: Inspection and quality measurement
A quality-inspection process may require users to record the measured thickness, temperature, quantity inspected, quantity rejected, or test score for a product or batch.
For example, a Numeric attribute named “Measured Thickness” can capture a decimal value, while “Quantity Inspected” and “Rejected Quantity” can capture whole numbers. Configured validation can ensure that users enter a valid numeric value.
The captured values can then be used to:
- Compare actual measurements with acceptable limits.
- Identify records that require review.
- Calculate rejection percentage or quality score.
- Display trends in dashboards and reports.
- Trigger process actions when a measurement is outside the accepted range.
Example: If the allowed thickness is between 4.5 mm and 5.0 mm, a rule can identify a recorded value of 4.2 mm as outside the permitted range and route the record for quality review.
Currency Attribute
A Currency attribute is designed to capture monetary values in a clear and consistent business format. It is useful for estimated costs, approved budgets, quotation values, invoice amounts, penalties, and other financial information associated with a record.
Currency values can be displayed using an appropriate monetary presentation and used in reports, dashboards, calculations, and approval-related logic.
Use case: Project cost approval
A project-change request may need to capture the estimated financial impact before it is approved. A Currency attribute named “Estimated Change Cost” can record the proposed amount.
The value can be used to determine the approval path. For example, a lower-value change may be approved by a project manager, while a higher-value change requires finance or leadership approval.