Date and Time — Reference
Expose a periodically updated date/time from the client’s clock.
Expose a periodically updated date/time from the client’s clock.
Before you begin
Section titled “Before you begin”- An App Connect page. Use a small known data set when verifying data binding or repetition.
Date and Time
Section titled “Date and Time”Expose a periodically updated date/time from the client’s clock.
Properties, data and actions
Section titled “Properties, data and actions”| Part | Meaning |
|---|---|
| ID | The component name, for example clock. |
| Interval | Seconds, Minutes, Hours or Days. It controls update frequency and output precision; for example Hours zeroes the smaller time fields rather than returning full seconds. |
| UTC Time | Uses UTC clock fields and appends Z when enabled. When off, the output uses local clock fields without a timezone suffix. |
| datetime data | Read clock.datetime. The output is a date/time string for display or further formatting, not a trusted server timestamp. |
Worked example
Section titled “Worked example”Add Date and Time named clock with Interval Seconds. Bind a text label to clock.datetime and watch it change. Enable UTC Time and inspect the Z-suffixed value. Switch to Minutes and confirm the seconds field is zeroed.
Behavior and limits
Section titled “Behavior and limits”The timer is scheduled relative to component initialization and can be delayed by browser scheduling. It is not guaranteed to tick exactly on clock boundaries. Use server time for trusted expiry, auditing or authorization decisions.
Build the surrounding page flow
Section titled “Build the surrounding page flow”Use a practical App Connect guide when you need the surrounding page, input or server-data workflow.
Check your result
Section titled “Check your result”You can use the component’s actual data path, configure its controls and verify the example’s reactive behavior.