<trial ChatGpt> Cell Specification

Designer
This manual is in pilot operation.

Cell specifications complement Column and Row Specifications, allowing for the specification of different data sources, formulas, and methods of displaying amounts and numbers for each column (row) within the same row (column). These details can be directly written into the cell specifications, but rules for arbitrating conflicts between row and column specifications can also be described.

A single cell specification can be registered for each combination of column and row specifications. It is not necessary to register cell specifications for all combinations of column and row specifications, only when needed.

Cell Value Display & Edit Rules

Item Setting

Data Source

The default value for the cell’s Data Source. If no ledger/member is specified in the cell specification’s data source, it is determined through Arbitration for each combination of column and row definitions.

Formula

A Text Expression used to calculate the value displayed in the cell. The result of the formula can be a string, not just a number.

Reflect Calculation Results in Ledger

Specifies whether to write the value calculated by the formula[1] into the ledger (if not specified, the calculated value is displayed but not written into the ledger).
If writing is desired, each target cell must have its data source (ledger and dimension member) fully specified.

When writing to a ledger cell whose data type is boolean or enumeration, the following rules apply:

Boolean

If the calculation result is an empty string, a blank value is written.
If the calculation result matches True, ignoring case and leading/trailing whitespace, True is written.
Otherwise, False is written.

Enumeration

If the calculation result is an empty string, a blank value is written.
Otherwise, the calculation result is considered a label, and the item (member of the value definition dimension of the enumeration account) with the same label in the value list is selected and written, ignoring case and leading/trailing whitespace. If no such item exists, a blank value is written.


1. For the calculation of values to be reflected in the ledger, English is always applied (even if another language is selected on the client side, it will be recalculated in English on the server side). This is to prevent the write value from changing depending on the language selected on the client side. Generally, form designs that allow the ledger write value to be affected by the language are not desirable.

Display/Input Method for Amounts and Numbers

Specifies the Display Method of Amounts and Numbers applied to the cell. If not specified in the cell specification, the display format for amounts and numbers applied to the cell is determined through Arbitration.

Format String Values with Markup
(fusion_place >= 10.0)

If checked, string values of ledger cell data types are interpreted and displayed using markup in both [Browser] and [Contributor].

For cells without cell specifications, if either column or row specifications are checked, markup formatting is interpreted.
For cells with cell specifications, the cell specification’s setting takes precedence over the same item in column or row specifications. That is, even if the item is checked in column or row specifications, if it is not checked in the cell specification, the latter’s setting is prioritized.

For more details on markup, please refer to Supported Markup Formats.

Sign Display Type

Specifies how to display the sign for amounts and numbers.

  • According to account attribute

  • Debit as +

  • Credit as +

If the sign display type is not specified in the cell specification, the actual sign display type applied is determined through Arbitration for each combination of column and row specifications.

Protect Cell (Disallow Input)

Specifies whether to protect the cell, i.e., disallow input. The default value is unchecked, meaning "Do not disallow."
Even if not protected, calculation cells are not inputtable, and for non-calculation cells, input capability is determined according to the input capability of the associated ledger cell.

For cells without cell specifications, if either column or row specifications are checked, the cell is protected.
For cells with cell specifications, the cell specification’s setting takes precedence over the same item in column or row specifications. That is, even if the item is checked in column or row specifications, if it is not checked in the cell specification, the latter’s setting is prioritized.

When saving data changed in the form, protected cells are excluded from being reflected in the ledger. For example, if the value of a protected cell has been changed by another user between data retrieval and saving, the save operation will not revert that value. Changes made by other users take precedence.

Arbitration Rules

If there are conflicts in descriptions between row and column specifications, by default, the row specification’s description is prioritized. To change this, arbitration rules are used. For more details, please refer to Arbitration.

Item Setting

Ledger Arbitration Rule

Specifies which to prioritize between row and column specifications for the ledger designation in the data source.

Display Method for Amounts and Numbers Arbitration Rule

Specifies which to prioritize between row and column specifications for the display method of amounts and numbers.

Formula Arbitration Rule

Specifies which to prioritize between row and column specifications for formulas.

Sign Display Type Arbitration Rule

Specifies which to prioritize between row and column specifications for the sign display type.

Member Specification Arbitration Rule

For the member specification in the data source, specifies which to prioritize between row and column specifications for each dimension.

Validation Rules

Cell specifications can include validation rules. Validation rules are rules for data checks that are used when saving data in the [Browser] or [Contributor], and when submitting packages in the business process management function. Each validation rule includes the following items:

Item Setting

Name Required

Specifies the name of the validation rule.

Validation Level Required

Specifies the level (severity) of validation, either "Warning" or "Error".

Warning

If this validation level is assigned to a rule that is violated, a warning is issued, but data can still be submitted.

Error

If this validation level is assigned to a rule that is violated, the data cannot be submitted.

Apply on Save

Check this if you want to apply the validation rule when saving data in the [Browser] or [Contributor]. If checked, and the validation level is Warning, a message is displayed for rule violations, but data can still be saved. If Error, saving is not possible.

Validation rules are not applied during data import via the Requester and [Web-API].

Validation Rule (Text Expression) Required

Describes the condition for validation using a Text Expression. The expression is evaluated for each cell within the cell range.
If the result is True, it complies with the validation condition; if False, it is considered a violation.

During submission in workflows, English is applied for evaluating validation rules (even if another language is selected on the client side, calculations are redone in English on the server side). This prevents the determination results from changing depending on the language selected on the client side. Generally, form designs that allow the validation determination results to be affected by language are not desirable.

Message for Rule Violation (Text Expression) Required

Specifies the message displayed when the above validation condition is violated, using a Text Expression. Text expressions can be specified for each language.

Drilldown

Drilldown refers to transitioning to another form when clicking on a cell that meets specific conditions. Drilldown specifications consist of pairs of drilldown executable conditions and destination forms, and multiple specifications can be registered. Multiple registered drilldown specifications are checked in order from the first for each cell, and the first drilldown specification whose conditions are met is applied. Each drilldown specification includes the following items:

Item Setting

Name Required

Specifies the name of the drilldown case.

Destination Application
( fusion_place >= 12.1 )

Specifies the destination application. If not specified, this application itself is used as the drilldown destination.
For specific usage and constraints of multi-application drilldown, please refer to Q&A: Multi-Application Drilldown Feature Sample.

Destination Form

Specifies the destination form. If not specified, this form itself is used as the drilldown destination.

Drilldown Executable Condition

Describes the condition for determining drilldown eligibility using a text expression. If a text expression is specified here, drilldown is only allowed for cells where the text expression evaluates to True (i.e., the cell value becomes clickable). If no text expression is specified, drilldown is always possible.