Cell Specification

« Loop Specifications | Import Specifications »

This manual is in pilot operation.

Cell specifications complement the Column and Row Specifications, allowing for the specification of different data sources, formulas, and number formats within the same row (or column) on a per-column (or row) basis. These specifications can be directly described in the cell specifications, but it is also possible to describe rules for arbitrating conflicts between row and column specifications.

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.

Table of Contents

Cell Specification

Cell Value Display and Editing Rules

Item Setting

Item	Setting
Data Source	The default value for the cell’s "Data Source". If no ledger or member is specified in the cell specification, the data source for each combination of column and row definitions is determined by Arbitration.
Formula	A Text Expression for calculating the value displayed in the cell. The result of the formula can be a string, not just a number.
Reflect Calculation Results to Ledger	Specifies whether to write the value calculated by the formula to the ledger^[1]. If writing is enabled, each target cell must have a fully specified data source (ledger and dimension member). For ledger cells of type Boolean or Enumeration, the following rules apply for writing calculation results: 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 spaces, `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 spaces. If no such item exists, a blank value is written. 1. When calculating values to be reflected in the ledger, the language is always set to English (even if another language is selected on the client side, it will be recalculated in English on the server side). This prevents 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.
Number Format	Specifies the Number Format to be applied to the cell. If no number format is specified in the cell specification, the number format to be applied to the cell is determined by Arbitration.
Format Text Values with Markup (fusion_place >= 10.0)	If this item is checked, for ledger cells of type string value, the formatted string with markup will be interpreted and displayed in both [Browser] and [Contributor]. For cells without a cell specification, if either column or row specification is checked, the markup formatting will be interpreted. For cells with a cell specification, the specification in the cell specification takes precedence over the same item in the column or row specification. That is, even if the same item is checked in the column or row specification, if it is not checked in the cell specification, the latter’s specification is prioritized. For more details on markup, please refer to Supported Markup Formats.
Sign Type	Specifies the method of displaying signs for amounts and numbers. Follow account attribute Treat debit as `+` Treat credit as `+` If no sign type is specified in the cell specification, the actual sign type applied will be determined for each combination of column and row specifications by Arbitration.
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, whether input is allowed is determined according to the input capability of the associated ledger cell. For cells without a cell specification, if either column or row specification is checked, the cell is protected. For cells with a cell specification, the specification in the cell specification takes precedence over the same item in the column or row specification. That is, even if the same item is checked in the column or row specification, if it is not checked in the cell specification, the latter’s specification 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 from the time of data retrieval to saving, the save operation will not revert that value. Changes made by other users are prioritized.

Data Source

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

Formula

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

Reflect Calculation Results to Ledger

Specifies whether to write the value calculated by the formula to the ledger^[1].
If writing is enabled, each target cell must have a fully specified data source (ledger and dimension member).

For ledger cells of type Boolean or Enumeration, the following rules apply for writing calculation results:

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 spaces, 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 spaces. If no such item exists, a blank value is written.

1. When calculating values to be reflected in the ledger, the language is always set to English (even if another language is selected on the client side, it will be recalculated in English on the server side). This prevents 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.

Number Format

Specifies the Number Format to be applied to the cell. If no number format is specified in the cell specification, the number format to be applied to the cell is determined by Arbitration.

Format Text Values with Markup
(fusion_place >= 10.0)

If this item is checked, for ledger cells of type string value, the formatted string with markup will be interpreted and displayed in both [Browser] and [Contributor].

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

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

Sign Type

Specifies the method of displaying signs for amounts and numbers.

Follow account attribute
Treat debit as +
Treat credit as +

If no sign type is specified in the cell specification, the actual sign type applied will be determined for each combination of column and row specifications by Arbitration.

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, whether input is allowed is determined according to the input capability of the associated ledger cell.

For cells without a cell specification, if either column or row specification is checked, the cell is protected.
For cells with a cell specification, the specification in the cell specification takes precedence over the same item in the column or row specification. That is, even if the same item is checked in the column or row specification, if it is not checked in the cell specification, the latter’s specification 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 from the time of data retrieval to saving, the save operation will not revert that value. Changes made by other users are prioritized.

Arbitration Rules

By default, if there is a conflict in descriptions between row and column specifications, the row specification is prioritized. To change this, use arbitration rules. For more details, please refer to Arbitration.

Item	Setting
Ledger Arbitration Rule	Specifies whether to prioritize row or column specification for the ledger specification of the data source.
Number Format Arbitration Rule	Specifies whether to prioritize row or column specification for the number format.
Formula Arbitration Rule	Specifies whether to prioritize row or column specification for the formula.
Sign Type Arbitration Rule	Specifies whether to prioritize row or column specification for the sign type.
Member Specification Arbitration Rule	For the member specification of the data source, specifies whether to prioritize row or column specification for each dimension.

Item

Setting

Ledger Arbitration Rule

Specifies whether to prioritize row or column specification for the ledger specification of the data source.

Number Format Arbitration Rule

Specifies whether to prioritize row or column specification for the number format.

Formula Arbitration Rule

Specifies whether to prioritize row or column specification for the formula.

Sign Type Arbitration Rule

Specifies whether to prioritize row or column specification for the sign type.

Member Specification Arbitration Rule

For the member specification of the data source, specifies whether to prioritize row or column specification for each dimension.

Validation Rules

Validation rules can be registered in the cell specification. Validation rules are rules for data checking, used when saving data in [Browser] and [Contributor], and when submitting packages in the business process management function. Each validation rule includes the following items:

Item Setting

Item	Setting
Name Required	Specifies the name of the validation rule.
Validation Level Required	Specifies the level (strictness) of validation, either "Warning" or "Error". Warning If a rule with this validation level is violated, you will receive a warning, but you can still submit the data. Error If a rule with this validation level is violated, you cannot submit the data.
Apply on Save	Check this if you want to apply the validation rule when saving data in [Browser] and [Contributor]. If checked, and the validation level is `Warning`, a message will be 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 Requester and [Web-API].
Validation Rule (Text Expression) Required	Describes the condition for validation using a Text Expression. The expression described here is evaluated for each cell in the cell range. If the result is `True`, it complies with the validation condition; if `False`, it is considered a violation. During submission in the workflow, English is applied for evaluating validation rules (even if another language is selected on the client side, it will be recalculated in English on the server side). This prevents the judgment result from changing depending on the language selected on the client side. Generally, form designs that allow the validation judgment result to be affected by the language are not desirable.
Message for Rule Violation (Text Expression) Required	Specifies the message to be displayed in case of violation of the above validation condition using a Text Expression. Text expressions can be specified for each language.

Name Required

Specifies the name of the validation rule.

Validation Level Required

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

Warning: If a rule with this validation level is violated, you will receive a warning, but you can still submit the data.
Error: If a rule with this validation level is violated, you cannot submit the data.

Apply on Save

Check this if you want to apply the validation rule when saving data in [Browser] and [Contributor]. If checked, and the validation level is Warning, a message will be 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 Requester and [Web-API].

Validation Rule (Text Expression) Required

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

During submission in the workflow, English is applied for evaluating validation rules (even if another language is selected on the client side, it will be recalculated in English on the server side). This prevents the judgment result from changing depending on the language selected on the client side. Generally, form designs that allow the validation judgment result to be affected by the language are not desirable.

Message for Rule Violation (Text Expression) Required

Specifies the message to be displayed in case of violation of the above validation condition using a Text Expression. Text expressions can be specified for each language.

Drill-down

Drill-down refers to transitioning to another form by clicking on a cell that meets certain conditions. Drill-down specifications consist of pairs of drill-down executable conditions and target forms, and multiple registrations are possible. Multiple registered drill-down specifications are checked from the first one for each cell, and the first drill-down specification that meets the executable condition is applied. Each drill-down specification includes the following items:

Item Setting

Item	Setting
Name Required	Specifies the name of the drill-down case.
Target Application ( fusion_place >= 12.1 )	Specifies the target application for drill-down. If not specified, this application itself is used as the drill-down target. For specific usage and constraints of multi-application drill-down, please refer to Q&A: Multi-Application Drill-down Feature Sample.
Target Form	Specifies the target form for drill-down. If not specified, this form itself is used as the drill-down target.
Drill-down Executable Condition	Describes the condition for determining drill-down eligibility using a text expression. If a text expression is specified here, drill-down is allowed only for cells where the text expression evaluates to `True` (i.e., the cell value becomes clickable). If no text expression is specified, drill-down is always possible.

Name Required

Specifies the name of the drill-down case.

Target Application
( fusion_place >= 12.1 )

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

Target Form

Specifies the target form for drill-down. If not specified, this form itself is used as the drill-down target.

Drill-down Executable Condition

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