View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

Projects/Absolute DateTime Reference/Functional Specs

Contents

Absolute DateTime Reference - Functional Specifications

Overview

This project intends to deliver two new references:

to be able to operate absolute time/datetime data within the application.

Purpose

Working with already existing "Time" and "DateTime" functions, the stored value is loaded from the backend (with the backend/server timezone) and displayed in the client/browser with the own client timezone. This behavior fits, for example, in the "created" or "updated" columns, where you need to save current client datetime value, but stored with the server timezone. With this, if a record has been modified, for example, 5 minutes ago, a user always will see in his screen this timestamp set as 5 minuted before its current date and time.

There is another scenario where the displayed datetime or time in the client/browser needs to be exactly the same that is stored in the server. Here it is when these new *absolute* references are needed to be used. Let's imagine a situation where the user wants to review the departure times of an airport. The user needs that this information be displayed exactly with the same timestamp, independently of his timezone. Needless to say, that in the case of adding data the same logic applies, and what the user sees on his screen is what should be persisted in the server.

Scope

Design Considerations

Constraints

Retrieved from "http://wiki.openbravo.com/wiki/Projects/Absolute_DateTime_Reference/Functional_Specs"

This page has been accessed 487 times. This page was last modified on 19 February 2014, at 20:14. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.