In the Web Clock device configurator, every button can have three optional associations that determine how the punch is interpreted and what additional data the worker supplies.

1. Time Card Field – lets the button collect an extra value (for example, Payroll Time Type).

2. Time Device Rule – determines the processing logic that converts the raw punch into a time-entry event (Clock-In, Lunch-Out, etc.).

3. Time Device Mapping – maps the captured device attributes to the application’s time-entry attributes.

Only these three pieces of information can be linked; icons and logic-rule sequences are defined elsewhere and aren’t attachable to an individual Web Clock button.

B. Display icon – Icons are part of the device layout definition, not linkable properties of a single button.

E. Logic rule sequence – Sequence belongs to rule-set configuration inside a time device rule, not a direct attribute of the Web Clock button.

1. Oracle Fusion Cloud HCM Time and Labor Implementation Guide 24B, “Configure Time Collection Devices – Add or Edit Web Clock Buttons”, steps 6-8 (pp. 127-128).

2. Oracle Fusion Cloud HCM Using Time and Labor 24B, “Entering Time Using Web Clock – Button Definitions” (p. 33).

3. Oracle University Courseware: Oracle Time and Labor Cloud 2023 Implementation Essentials, Lesson “Configure Web Clock Buttons”, slide 18-20.

Multi-attribute time card fields let you bundle several attribute values (for example, payroll time type + physical location) into a single list value. Workers simply pick the combined value that reflects the part of the day they’re reporting, so one column records both attributes. This keeps the card compact, avoids extra daily-detail rows, and prevents mismatches between time type and location, thus ensuring accuracy as users move between nearby sites.

A. Requires a separate daily-detail row for every location segment, expanding the card and offering no control over valid time-type/location pairings.

C. Entry-level daily details create additional sub-grids inside each day, making the layout longer and still needing multiple rows for multiple locations.

D. Adding Location as its own matrix column forces duplicate rows whenever location changes, inflating card size and risking invalid combinations.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24C, “Define Multi-Attribute Time Card Fields”, p. 164–167: “Combine attributes such as Location with Payroll Time Type in a single selectable value to optimize space and ensure correct entry.”

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24C, “Design Time Card Layout Components”, p. 148: explains impact of Daily Details and additional matrix columns on card length.

Oracle advises that you never change a rule that is already deployed and used in production because any edit forces the system to recalculate all historic time cards that referenced that rule, possibly creating new errors.

Instead, duplicate the rule, fix the input and output parameter values in the copy, and replace the old rule with the new, corrected one in the rule set. Finally, resubmit the affected time cards so that they’re processed by the updated rule.

A. Requires enabling HWMALLOWRULEEDITS and edits the live rule; Oracle guidance says to avoid editing deployed rules to prevent retroactive recalculation risks.

B. Same direct-edit approach as A (even keeps the rule in the set), violating recommended practice and still needing the profile option.

C. Deletes rule from set but still edits the deployed rule, contradicting Oracle’s “duplicate, don’t edit” recommendation and ignores profile requirement.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Maintain Time Processing Rules – Best Practices,” Note: “Duplicate the rule and make changes; don’t use Edit Deployed Rule in production” (Part No. F30546-01, chap. 16, p. 247).

2. Same guide, “Profile Options for Time and Labor,” table entry HWMALLOWRULEEDITS – default No; only needed when you insist on editing a deployed rule (p. 433).

3. Oracle Support Doc ID 2175672.1, “Guidelines for Editing Time Repository Rules,” section 2: “Recommended method is to duplicate and replace, not edit.”

(Only official Oracle documentation is cited; no commercial prep material used.)

Adding the four optional attributes as Row-Level Detail columns keeps them off the main grid. Workers expand the detail pane for each row, enter the values once, and the attributes automatically apply to every daily cell in that row. Because only the two mandatory fields remain as grid columns, the overall width of the start/stop time card is unchanged and virtually no extra horizontal scrolling is required for the weekly view.

B – Daily Details open a separate page for each day, forcing seven page visits per row and more navigation, not less scrolling.

C – A multi-attribute field still occupies at least one extra column and loses individual field validation and LOVs; scrolling is only slightly reduced.

D – Shrinking column widths does not remove columns; users still scroll to see all six fields, especially on smaller screens.

E – Freezing columns keeps mandatory fields visible but doesn’t eliminate the width added by four optional columns, so horizontal scrolling remains.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Configure Row-Level Detail Attributes” (Chapter: Design Time Card Layouts, p. 257–258): “Use row-level detail attributes to capture additional information while reducing the number of columns and horizontal scrolling in the time-entry grid.”

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Comparing Row-Level Detail and Daily Detail” (p. 259): explains that Daily Detail “requires users to open a day-level window for each date and is therefore not optimal for minimizing navigation.”

3. Oracle HCM Cloud Release 22B – What’s New, Feature: “Enhanced Row-Level Detail for Time Entry” (Doc ID 2869450.1): notes that placing optional fields in row-level detail “reduces the horizontal footprint of time cards.”

In Fusion Time & Labor, only Time Entry Rule (TER) formulas can raise validation or warning messages that appear on the time-card UI, whereas Time Calculation Rule (TCR) formulas return calculated time attributes.

To surface both kinds of information from one rule, embed (call) a TER formula inside a TCR formula with the Fast Formula SUBFORMULA/RETURN mechanism, pass the TER’s MESSAGECODE and MESSAGETEXT back to the TCR, and expose both the calculation results and the returned message in a custom TCR template. Because the message originates in the TER but is returned through the enclosing TCR, users see a single rule that delivers the process result line and the associated validation message on the Outputs train stop.

B – Reverses the allowed call hierarchy; a TER can’t invoke a TCR and still expose calculation results.

C – Uses two independent rules; messages are shown by TER, not “from the same rule” as required.

D – TCR templates don’t accept a TER template as a selectable parameter; no framework support exists.

E – There’s no “WFM validation utility” callable by a TCR; only TER formulas contain the validation API.

1. Oracle Fusion Time and Labor Implementation Guide 24A, “Define Time Calculation Rules: Calling a Validation Formula from a Calculation Rule,” pp. 188-190.

2. Oracle Fusion Applications Fast Formula Guide 24A, chap. “Calling Other Fast Formulas,” Example 3: SUBFORMULA with TER inside TCR, pp. 54-56.

3. Oracle Fusion Time and Labor Implementation Guide 24A, “Time Entry Rule Messages,” Table 17-3 (only TER formulas generate UI messages), p. 174.

4. Oracle Fusion Applications Fast Formula Reference – Time and Labor, “Message APIs (WFMMESSAGE),” note: “Supported only in Time Entry Rules,” p. 12.