[jira] Created: (OFBIZ-2813) ProductStore did not allow the default timezone to be set

[Nicolas Malin (Jira)]

ProductStore did not allow the default timezone to be set
---------------------------------------------------------

                 Key: OFBIZ-2813
                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
             Project: OFBiz
          Issue Type: Improvement
          Components: product
    Affects Versions: SVN trunk
            Reporter: Bob Morley
            Priority: Minor


The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).

The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.

I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Morley updated OFBIZ-2813:
------------------------------

    Attachment: OFBIZ-2813.patch

OFBIZ-2813 contains the improvements.  In brief, the entity has the new attribute, the form was updated to put it in the proper group (add/edit), various utility methods that get timezone were enhanced to try to get it from the product store (instead of going right to the system default)

> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
>                 Key: OFBIZ-2813
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Priority: Minor
>         Attachments: OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740776#action_12740776 ]

Adrian Crum commented on OFBIZ-2813:
------------------------------------

Bob,

There is a setting available to set the default time zone - look for start.properties. If you need a single OFBiz instance to pretend to be in different time zones based on the product store, then your proposal might be worth looking into.

> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
>                 Key: OFBIZ-2813
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Priority: Minor
>         Attachments: OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740796#action_12740796 ]

Bob Morley commented on OFBIZ-2813:
-----------------------------------

Adrian,

Thank you very much for your quick comment -- I appreciate it!  In this JIRA I am trying to expand the functionality in Ofbiz which is driven from our system requirements -- specifically, we have implemented multi-tenancy so we absolutely have multiple customers using the same application server (and definition in different timezones).  Now interestingly enough, our requirement would actually be more at the "Company" level -- but in doing some research I noticed what I thought was a shortcoming in the ProductStore setup.  To be honest I did not know about this setting, but did know it was installation based.

So, I think in a multi-tenant situation you would definitely want to expose this value somewhere on an entity that was not the userLogin.  But even before that, I think it is reasonable to suggest that you may have a Company that has multiple stores and spans more than one timezone where you would want this type of configuration.  Would you buy that?  :)  In this fix I have tried to follow the #1 premise (do no harm) so I have elected not to seed this attribute and allow it to pass through as it does now (userLogin -> productStore -> System Default).

Thoughts?

> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
>                 Key: OFBIZ-2813
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Priority: Minor
>         Attachments: OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740804#action_12740804 ]

David E. Jones commented on OFBIZ-2813:
---------------------------------------

As a side bonus, it is also much more consistent with the other settings...

> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
>                 Key: OFBIZ-2813
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Priority: Minor
>         Attachments: OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884193#action_12884193 ]

Jacques Le Roux commented on OFBIZ-2813:
----------------------------------------

Is this issue still relevant with the OOTB multi-tenancy?

> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
>                 Key: OFBIZ-2813
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Priority: Minor
>         Attachments: OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888001#action_12888001 ]

Bob Morley commented on OFBIZ-2813:
-----------------------------------

Yes, I believe it is more relevant because in a multi-tenant deployment you are more likely to have product stores (across your tenants) that have different time zones.

> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
>                 Key: OFBIZ-2813
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2813
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Priority: Minor
>         Attachments: OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString.  What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this improvement.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.