Re: Build failed

[Mohammad Kathawala]

Hello All,

We are again getting this build failure issue suddenly from yesterday in
our project. It was working fine before that. We are using release 17.12.
Do we have any permanent fix for this?
As per the patch on this ticket
https://issues.apache.org/jira/browse/OFBIZ-10590 if I update every
*noNamespaceSchemaLocation* with *https *then it works fine.
My question is if we have changed the redirect rule condition in the past,
why is this issue suddenly occurring again? Is there a change in the
resource location recently?

Any help would be appreciated.

Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com


On Tue, Oct 2, 2018 at 1:48 AM Deepak Dixit  wrote:

> I am sure that this is due to the changes done in the ofbiz website, After
> updating the redirect rule condition it's fixed.
> http to https redirect affect all the older version as well, all the ofbiz
> versions usinging http://ofbiz.apache.org/dtds/* as a namespace.
>
> Thanks Benjamin Jugl and Pierre Smits for your suggestion :)
>
> Thanks & Regards
> --
> Deepak Dixit
>
>
> On Tue, Oct 2, 2018 at 12:56 AM, Taher Alkhateeb <
> slidingfilame...@gmail.com
> > wrote:
>
> > I have a feeling this has nothing to do with this commit, I have an
> > older working copy that is also crashing.
> >
> > This could mean that the problem is somewhere in the gradle
> > dependencies, something corrupted or wrong in JCenter perhaps?
> > On Mon, Oct 1, 2018 at 4:42 PM Deepak Dixit 
> > wrote:
> > >
> > > This should be fixed at r#1842499
> > >
> > > Here is the ticket for further work as mentioned by Michale.
> > > https://issues.apache.org/jira/browse/OFBIZ-10590
> > >
> > > Thanks & Regards
> > > --
> > > Deepak Dixit
> > >
> > >
> > > On Mon, Oct 1, 2018 at 5:59 PM, Pierre Smits 
> > wrote:
> > >
> > > > Upgrading the references in the code base to
> > > > https://ofbiz.apache.org/dtds/entity-config.xsd should do the trick,
> > > > correct?
> > > >
> > > > Best regards,
> > > >
> > > > Pierre Smits
> > > >
> > > > *Apache Trafodion <https://trafodion.apache.org>, Vice President*
> > > > *Apache Directory <https://directory.apache.org>, PMC Member*
> > > > Apache Incubator <https://incubator.apache.org>, committer
> > > > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without
> > privileges)
> > > > since 2008*
> > > > Apache Steve <https://steve.apache.org>, committer
> > > >
> > > >
> > > > On Mon, Oct 1, 2018 at 1:42 PM Deepak Dixit 
> > > > wrote:
> > > >
> > > > > I think its due to changes done at r#1842437
> > > > >
> > > > > While build using debug mode found following warning
> > > > > 
> > > > >
> > > > > 17:04:57.839 [DEBUG] [TestEventLogger] 2018-10-01 17:04:57,839
> > |Test
> > > > > worker  |UtilXml   |W|
> > > > > [UtilXml.LocalResolver.resolveEntity] could not find LOCAL
> > DTD/Schema
> > > > with
> > > > > publicId [null] and the file/resource is [entity-config.xsd]
> > > > > 
> > > > >
> > > > > UtilXml fails to read the entity-config.xsd file as
> entityengine.xml
> > > > using
> > > > > the following URL
> > > > >
> > > > > http://ofbiz.apache.org/dtds/entity-config.xsd
> > > > >
> > > > >
> > > > > I think we need to update the noNamespaceSchemaLocation or exclude
> > the
> > > > > dtds folder in redirect rule.
> > > > > Exclusion looks good to me in this case.
> > > > >
> > > > > any other opinion?
> > > > >
> > > > >
> > > > > Thanks & Regards
> > > > > --
> > > > > Deepak Dixit
> > > > >
> > > > >
> > > > > On Mon, Oct 1, 2018 at 4:56 PM, Pritam Kute <
> > > > pritam.k...@hotwaxsystems.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Same here. About to write an email. :)
> > > > > >
> > > > > > Thanks and Regards
> > > &g

Re: Welcome to Devanshu Vyas as new committer!

[Mohammad Kathawala]

Many Congratulations Devanshu 

On Wed, 19 Aug 2020 at 2:32 PM, Pawan Verma  wrote:

> The OFBiz PMC has invited Devanshu Vyas to become a new committer and we
>
> are happy to announce that he has accepted this role.
>
>
>
> Some of the reasons for inviting Devanshu Vyas include:
>
>
>
> - He is invested in the OFBiz project and has been a member for many years
>
> - He is taking an initiative towards improving the system
>
> - He has functional experience in various areas of the framework
>
> - He enjoys working with the community and collaborating with others
>
>
>
> Please join me in welcoming and congratulating Devanshu!
>
>
>
> Cheers
>
> Pawan Verma
>
> ofbiz.apache.org
>
> --
Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com

Re: Headless Commerce Plugin for OFBiz

[Mohammad Kathawala]

Hello Arpit,

+1 for the initiative.

Headless commerce is indeed the need of an hour. The e-commerce component
of OFBiz is tightly coupled with OFBiz design and technologies. It is
always difficult for a front-end developer to have a freedom of using
his/her preferred front end technologies and design desired UI/UX without
having to learn how to code in OFBiz.

Providing a set of REST APIs which will cover all the eCommerce features,
will make the life of front end developer much easier. This way they will
be able to get advantage of OFBiz’s backend capabilities along with their
own front end.

After having the recent REST API support in OFBiz, this definitely should
be the next step forward.

Thanks for the initiative Arpit. I will be happy to contribute in this
effort.

On Tue, 18 Aug 2020 at 8:52 PM, Arpit Mor 
wrote:

> Hi Devs,
>
>
>
> Hope everyone is safe and healthy amidst Covid-19 pandemic
>
>
>
> Most of you might have heard about “Headless Commerce” or API first
>
> commerce, but in case you haven’t, here is a brief summary of what headless
>
> commerce is and why it is the need of the hour.
>
>
>
> What is Headless Commerce?
>
> In its simplest form, headless commerce is the decoupling of the
>
> presentation layer (frontend) of an eCommerce from backend such that both
>
> are able to function independently. This decoupling is achieved by using
>
> APIs to expose core backend functionalities.
>
>
>
> Why Headless Commerce?
>
> Today, customers are consuming context from various channels and
>
> touch-points. Gone are the days when customers primarily needed to visit a
>
> website to buy online. With the rise of smartphones and the Internet of
>
> Things (IoT), customers can now shop from multiple channels like IoT
>
> devices, progressive web apps (PWAs), social media platforms, mobile apps,
>
> smart assistants, smart TV, kiosks, and many more.
>
> By decoupling frontend from backend - user interface, social commerce,
>
> mobile apps, IoT, and many more – can be changed or updated individually,
>
> without interfering with backend. Data is available to separate frontend
>
> applications via API calls and the backend runs invisibly in the
> background.
>
>
>
> Benefits of Headless Commerce
>
> Unlimited Channels and Touchpoints: With API first Headless Commerce,
>
> integration with the new channels and touchpoints becomes easy, economical,
>
> and quick.
>
>
>
> Innovation and Engaging User Experience: With traditional monolithic
>
> Commerce, making user-centric changes to your website requires both a front
>
> and backend transformation. But with headless commerce, all the
>
> frontend/app developers have to focus on is user experience,
>
> personalization, and consistency without having to worry about changes to
>
> the backend.
>
>
>
> Easy-to-Manage Integrations: Headless commerce not only includes providing
>
> API support to the frontend, but it also includes communication between
>
> various components (like ERP, WMS, OMS, CRM, POS, etc.) via APIs. This will
>
> reduce the complexity of the integration and its maintenance.
>
>
>
> Business Agility & less time to market: Companies must be able to respond
>
> quickly to new market opportunities by constantly releasing new features.
>
> In traditional commerce, each component is tightly coupled with another
>
> which makes changes a complex task. But with Headless commerce different
>
> components communicate via APIs, which make changes to one component easy
>
> without having to worry about changes to other components.
>
>
>
> I’d like to put forward a suggestion for developing a headless commerce
>
> plugin, to keep the competitive edge of OFBiz with the rapidly changing
>
> technological trends by exposing core backend functionalities via APIs (The
>
> REST capabilities are already added to OFBiz recently).
>
>
>
> Looking forward to suggestions and feedback.
>
>
>
> Thanks & Regards
>
> Arpit Mor
>
> --
Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com

Re: Welcome Arun Patidar as new PMC member

[Mohammad Kathawala]

Congratulations Arun!

Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com


On Mon, Jul 6, 2020 at 12:30 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> The OFBiz PMC has invited Arun Patidar to become member of the committee
> and we are glad to announce that he has accepted the nomination.
>
> On behalf of the OFBiz PMC, welcome on board Arun!
>
>

Re: Welcome Suraj Khurana as new PMC member

[Mohammad Kathawala]

Congratulations Suraj!

Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com


On Sat, Jul 4, 2020 at 5:22 PM Jacques Le Roux 
wrote:

> The OFBiz PMC has invited Suraj Khurana to become member of the committee
> and we are glad to announce that he has accepted the nomination.
>
> On behalf of the OFBiz PMC, welcome on board Suraj!
>
>

Re: Welcome Aditya Sharma as new PMC member

[Mohammad Kathawala]

Congratulations Aditya!
Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com


On Sun, Jul 5, 2020 at 10:24 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> The OFBiz PMC has invited Aditya Sharma to become member of the committee
> and we are glad to announce that he has accepted the nomination.
>
> On behalf of the OFBiz PMC, welcome on board Aditya!
>
>

Re: Welcome Swapnil M Mane as new PMC member

[Mohammad Kathawala]

Many Congratulations Swapnil!
Kind Regards,
Mohammad Kathawala
Senior Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7772858789
office: 0731-409-3684
http://www.hotwaxsystems.com


On Sat, Apr 25, 2020 at 7:19 PM Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> Swapnil M,
>
> Congratulations and welcome.
> Looking forward to a wonderful journey together.
>
> Best regards,
> Pranay Pandey
>
>
> On Thu, Apr 23, 2020 at 5:02 PM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > The OFBiz PMC has invited Swapnil M Mane to become member of the
> committee
> > and we are glad to announce that he has accepted the nomination.
> >
> > On behalf of the OFBiz PMC, welcome on board!
> >
> >
>

Re: Valid Item Status for partial shipment

[Mohammad Kathawala]

Hello Shikha,

The statuses mentioned by you in all the scenarios seem correct to me and
AFAIK it works in the same way in OFBiz. We can definitely improve it by
adding a 'Partially Complete/Partially Fulfilled' status to an order item
as mentioned by Pawan.

Thanks & Regards
Mohammad Kathawala

On Tue, Apr 14, 2020 at 6:03 PM Suraj Khurana 
wrote:

> Adding Dev ML.
>
> --
> Best Regards,
> Suraj Khurana
> Senior Technical Consultant
>
> On Tue, Apr 14, 2020 at 5:13 PM Shikha Jaiswal <
> shikha.jais...@hotwaxsystems.com> wrote:
>
> > Hello team,
> >
> > From the business point of view, please share what should be the exact
> > status of an item after approval, if it is being shipped partially.
> >
> > Suppose an order item is of 3 qty and all three are split down into
> > separate ship groups and shipped one by one, what should be the ideal
> > status on each following instances, as we maintain item status on
> OrderItem
> > level only, not specific to OISGA:
> >
> > - One item is shipped, two are pending.
> > -- IMO, it should be Approved as there are still pending items, please
> > confirm.
> >
> > - Two items are shipped, one is pending.
> > -- IMO, it should be Approved as there are still pending items, please
> > confirm.
> >
> > - Two items are shipped, one is canceled.
> > -- IMO, it should be Completed as it is shipped or canceled, please
> > confirm.
> >
> > OR
> >
> > - All three items are shipped
> > -- IMO, it should be Completed as all items are shipped.
> >
> > Please let me know your thoughts on this.
> >
> > --
> > Thanks & Regards,
> > Shikha Jaiswal
> > Senior Enterprise Software Engineer
> >
>

Re: Demo Trunk NPE

[Mohammad Kathawala]

Working for me.
Regards*,*
*Mohammad Kathawala* | Sr. Technical Consultant
*HotWax Commerce* by *HotWax Systems*
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Cell phone: 7772858789

HotWax Systems recently received 8 mentions in *The Gartner Digital
Commerce Vendor Guide, 2016 *by Gartner, Inc., the world's leading IT
research and advisory company. Learn more about our research here
<https://www.gartner.com/technology/media-products/newsletters/HotWax/1-2UVLP6M/index.html>
.


On Sat, Sep 22, 2018 at 2:19 PM Rishi Solanki 
wrote:

> Hello Team,
> Browse to Webtools >> Logging >> Service Log on demo trunk returns NPE.
>
> Quick Reference:
> https://demo-trunk.ofbiz.apache.org/webtools/control/ServiceLog
>
> Not able to replicate it on local setup, anyone face the same issue then
> please revert back. Will log Jira Ticket for that.
>
> Regards,
> --
> Rishi Solanki
> Sr Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
> www.hotwax.co
>

Issue: Additional shipping charge editable on shipment even after shipment is packed and invoice is generated

[Mohammad Kathawala]

Hello Devs,

I need to confirm if the following scenario is valid or not:
At the time of packing an order, an additional shipping charge can be added
from the packing screen which is stored in the shipment entity.
When package/s are completed, the shipment is marked as packed and an
invoice is generated for the order in ready for posting status. Also, an
invoice line item is created from the additional shipping charge added in
the shipment. Now, since the invoice is in ready for posting status, it
cannot be edited. But, the additional shipping charge on the shipment is
still editable. Is this a valid scenario?

My second concern is if someone has entered wrong shipping charge at the
time of packing then how can it be corrected since the invoice gets
generated as soon as shipment is packed.

Thanks.
Regards*,*
*Mohammad Kathawala* | Sr. Technical Consultant
*HotWax Commerce* by *HotWax Systems*
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Cell phone: 7772858789

HotWax Systems recently received 8 mentions in *The Gartner Digital
Commerce Vendor Guide, 2016 *by Gartner, Inc., the world's leading IT
research and advisory company. Learn more about our research here
<https://www.gartner.com/technology/media-products/newsletters/HotWax/1-2UVLP6M/index.html>
.

Re: Purchase Order Cancel status

[Mohammad Kathawala]

Hi,

IMO, if all the items of the order need to be canceled then the user
should/would directly cancel the order rather than canceling all the items
individually. This will automatically cancel all the items and the order at
header level. Despite this, still, if the user cancels all the items
individually then IMO the order should not get canceled automatically at
header level because after the order is canceled you cannot add new items
to it and it might be possible that user wants to add new items to the
order after canceling all the existing items. The order should be canceled
manually in this case.

Thanks.

Regards*,*
*Mohammad Kathawala* | Technical Consultant / Team Lead
*HotWax Commerce* by *HotWax Systems*
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Cell phone: 7772858789

HotWax Systems recently received 8 mentions in *The Gartner Digital
Commerce Vendor Guide, 2016 *by Gartner, Inc., the world's leading IT
research and advisory company. Learn more about our research here
<https://www.gartner.com/technology/media-products/newsletters/HotWax/1-2UVLP6M/index.html>
.

On Fri, Oct 6, 2017 at 7:14 PM, Ratnesh Upadhyay <upadhyay.ratn...@gmail.com
> wrote:

> Hi Renuka,
>
> I would also prefer to remove this condition as it's not making sense to
> keep order in created status when all the order items get canceled.
>
> Thanks!!
>
> Regards,
> Ratnesh Upadhyay
> HotWax Systems | www.hotwaxsystems.com
>
> On Fri, Oct 6, 2017 at 12:52 PM, Deepak Dixit <
> deepak.di...@hotwaxsystems.com> wrote:
>
> > Hi Renuka,
> >
> > I see no reason to keen this condition.  we can remove this.
> > As I know there is no business scenario around this. If all order item
> > cancelled than order should be cancel either its Sales or Purchase order.
> >
> >
> >
> > Thanks & Regards
> > --
> > Deepak Dixit
> > www.hotwaxsystems.com
> > www.hotwax.co
> >
> > On Thu, Oct 5, 2017 at 7:17 PM, Renuka Srishti <
> renuka.srisht...@gmail.com
> > >
> > wrote:
> >
> > > Hello Devs,
> > >
> > > This is reference to
> > > http://markmail.org/message/wggbvdumrndpkxrj
> > >
> > > In "applications/order/src/org/ofbiz/order/order/OrderServices.java",
> > > under
> > > "checkItemStatus" service, there is one check for all item cancelled:
> > >
> > > if (!"PURCHASE_ORDER".equals(orderTypeId)) {
> > > newStatus = "ORDER_CANCELLED";
> > > }
> > >
> > > I was trying to find out the reason behind it but did not get any.
> > >
> > > When we cancel all the items of an order, Order should cancel at the
> > header
> > > level too. Then why we have added this special check for purchase
> order?
> > >
> > > Becuase of this check, after canceling of all the items, purchase order
> > do
> > > not get canceled at the header level. Currently, we need to cancel the
> > > purchase order manually.
> > >
> > >
> > > Thanks
> > > Renuka Srishti
> > >
> >
>

Re: Welcome Akash Jain as a New Committer!

[Mohammad Kathawala]

Congratulations Akash!

Regards
On Wed, Aug 9, 2017 at 2:28 PM, Sharan Foga  wrote:

> The OFBiz PMC has invited Akash Jain to become a new committer and are
> happy to announce that he has accepted.
>
> Some of the key factors considered for inviting him were as follows:
>
> - He has been involved with the OFBiz project for quite a while which
> shows his dedication and commitment
> - He has a lot of good knowledge (both functional and technical) that he
> is happy to share which shows he is a good team player
> - He is very active, positive and respectful to others in the community
> - He has contributed patches and shows a willingness to learn which is
> really important as the project continues to go through changes
>
> Please join me in welcoming and congratulating Akash.
>
> Thanks
> Sharan
>

Re: Welcome Rishi Solanki as a New Committer!

[Mohammad Kathawala]

Congratulations Rishi!  :)

Regards
On Wed, Aug 9, 2017 at 2:46 PM, Padma Rawat 
wrote:

> Many Congratulations Rishi!
>
>
>
>
> *Thanks & Regards*
>
> *Padmavati Rawat*
>
> On Wed, Aug 9, 2017 at 2:44 PM, Arvind singh tomar <
> arvindtomar1...@gmail.com> wrote:
>
> > Many Congratulations Rishi!!!
> >
> > Kind Regards-
> > Arvind Singh Tomar
> >
> > On 9 August 2017 at 14:26, Sharan Foga  wrote:
> >
> > > The OFBiz PMC has invited Rishi Solanki to become a new committer and
> are
> > > happy to announce that he has accepted.
> > >
> > > Some of the key factors considered for inviting him were as follows:
> > >
> > > - He has been involved with the OFBiz project for quite a while which
> > > shows dedication and commitment
> > > - He has a lot of good knowledge that he is happy to share which shows
> he
> > > is a good team player
> > > - His work is consistent, has good code quality and he has provided a
> > > range of patches
> > > - He is friendly, respectful and keen to help out others in the
> community
> > >
> > > Please join me in welcoming and congratulating Rishi!
> > >
> > > Thanks
> > > Sharan
> > >
> >
>

Re: Welcome Deepak Dixit as a new PMC member

[Mohammad Kathawala]

Congratulations Deepak Dixit.
You deserved to be in PMC.

Regards,
Mohammad Kathawala
Technical Consultant / Team Lead,
Hotwax Systems,
mohammad.kathaw...@hotwaxsystems.com <mohammad.kathaw...@hotwaxmedia.com>

On Mon, Feb 27, 2017 at 10:21 AM, Rehan <rehan.k...@hotwaxsystems.com>
wrote:

> Congratulations Deepak !!
>
> Thanks & Regards,
> Rehan Khan
>
>
> On Friday 24 February 2017 06:38 PM, Jacques Le Roux wrote:
>
>> The OFBiz PMC has invited Deepak Dixit to become a new member of the
>> committee; and the committee members are happy to announce that he has
>> accepted.
>>
>> Deepak has been involved in OFBiz for a long time now, and is a respected
>> committer for 2 years.
>>
>> We are sure Deepak will help us to take good decisions in favour of a
>> bright future for OFBiz!
>>
>> Please join me in welcoming and congratulating Deepak.
>>
>> Thanks
>>
>> Jacques
>> PS: Deepak, I let you change your status on the wiki PMC page :)
>>
>>
>

[jira] [Assigned] (OFBIZ-7544) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Manufacturing' component

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7544:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Manufacturing' component
> ---
>
> Key: OFBIZ-7544
> URL: https://issues.apache.org/jira/browse/OFBIZ-7544
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Reporter: Swapnil Shah
>    Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7544.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7544) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Manufacturing' component

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364233#comment-15364233
 ] 

Mohammad Kathawala commented on OFBIZ-7544:
---

Hi [~soledad],

I just thought of usability. Checkbox is always easier to use instead of 
multiple select as we need to use CTRL key to select multiple options in 
multiple select box.

WDYT?

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Manufacturing' component
> ---
>
> Key: OFBIZ-7544
> URL: https://issues.apache.org/jira/browse/OFBIZ-7544
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7544.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7544) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Manufacturing' component

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7544:
--
Attachment: OFBIZ-7544.patch

Replaced status dropdown with checkboxes in Find Production Run form.
Now user will be able to search on the basis of multiple statuses.

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Manufacturing' component
> ---
>
> Key: OFBIZ-7544
> URL: https://issues.apache.org/jira/browse/OFBIZ-7544
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7544.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7543:
--
Attachment: OFBIZ-7543.patch

Added checkbox for status fields on 
- Find Orders
- Find Quotes
- Find Requirements
- Find Returns

On find orders, did changes in groovy in order to handle list of statuses.

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Order' component
> ---
>
> Key: OFBIZ-7543
> URL: https://issues.apache.org/jira/browse/OFBIZ-7543
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7543.patch
>
>
> Please refer the details provided on OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7543:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Order' component
> ---
>
> Key: OFBIZ-7543
> URL: https://issues.apache.org/jira/browse/OFBIZ-7543
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>
> Please refer the details provided on OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7553) On order list page, the 'All' checkbox for status field does not work properly

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7553:
--
Issue Type: Improvement  (was: Bug)

> On order list page, the 'All' checkbox for status field does not work properly
> --
>
> Key: OFBIZ-7553
> URL: https://issues.apache.org/jira/browse/OFBIZ-7553
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>Assignee: Divesh Dutta
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7553.patch, Screenshot.png
>
>
> Steps to generate:
> 1) Go to order list page.
> 2) For status field, check the 'All' checkbox. This will check all the other 
> status checkboxes.
> 3) Now uncheck any one or more checkbox other than 'All'.
> - Expected: This should uncheck the 'All' checkbox also.
> - Actual: 'All' checkbox remains checked.
> Please see the screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7553) On order list page, the 'All' checkbox for status field does not work properly

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363784#comment-15363784
 ] 

Mohammad Kathawala commented on OFBIZ-7553:
---

Thanks [~jacques.le.roux],

I think it is an improvement as the functionality was already working before 
the fix. Changing the type to Improvement.


> On order list page, the 'All' checkbox for status field does not work properly
> --
>
> Key: OFBIZ-7553
> URL: https://issues.apache.org/jira/browse/OFBIZ-7553
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>Assignee: Divesh Dutta
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7553.patch, Screenshot.png
>
>
> Steps to generate:
> 1) Go to order list page.
> 2) For status field, check the 'All' checkbox. This will check all the other 
> status checkboxes.
> 3) Now uncheck any one or more checkbox other than 'All'.
> - Expected: This should uncheck the 'All' checkbox also.
> - Actual: 'All' checkbox remains checked.
> Please see the screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7580) Order: Correct all the checkboxes and radio buttons in all the order FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7580:
--
Attachment: OFBIZ-7580.patch

Added label tags for all the checkboxes and radio buttons in all the FTLs of 
order application i.e. all the FTLs related to order in 
'applications/order/template'
Attached patch.

> Order: Correct all the checkboxes and radio buttons in all the order FTLs.
> --
>
> Key: OFBIZ-7580
> URL: https://issues.apache.org/jira/browse/OFBIZ-7580
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7580.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7669) SpecialPurpose/ebaystore: Correct all the checkboxes and radio buttons in all the ebaystore FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7669:
--
Attachment: OFBIZ-7669.patch

Added label tags for all the checkboxes and radio buttons in all the FTLs of 
ebaystore application i.e. all the FTLs related 
'specialpurpose/ebaystore/template'.
Attached patch.

> SpecialPurpose/ebaystore: Correct all the checkboxes and radio buttons in all 
> the ebaystore FTLs.
> -
>
> Key: OFBIZ-7669
> URL: https://issues.apache.org/jira/browse/OFBIZ-7669
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7669.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7581) Party: Correct all the checkboxes and radio buttons in all the party FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala closed OFBIZ-7581.
-
Resolution: Not A Problem

It seems that we do not have anything to change in FTLs of party component.
So closing the ticket

> Party: Correct all the checkboxes and radio buttons in all the party FTLs.
> --
>
> Key: OFBIZ-7581
> URL: https://issues.apache.org/jira/browse/OFBIZ-7581
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: party
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7579) Marketing: Correct all the checkboxes and radio buttons in all the marketing FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala closed OFBIZ-7579.
-
Resolution: Not A Problem

> Marketing: Correct all the checkboxes and radio buttons in all the marketing 
> FTLs.
> --
>
> Key: OFBIZ-7579
> URL: https://issues.apache.org/jira/browse/OFBIZ-7579
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: marketing
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7579) Marketing: Correct all the checkboxes and radio buttons in all the marketing FTLs.

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354586#comment-15354586
 ] 

Mohammad Kathawala commented on OFBIZ-7579:
---

It seems that we do not have anything to change in the FTLs of marketing 
component.
So closing the ticket.

> Marketing: Correct all the checkboxes and radio buttons in all the marketing 
> FTLs.
> --
>
> Key: OFBIZ-7579
> URL: https://issues.apache.org/jira/browse/OFBIZ-7579
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: marketing
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7671) SpecialPurpose/googlebase: Correct all the checkboxes and radio buttons in all the googlebase FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7671:
-

 Summary: SpecialPurpose/googlebase: Correct all the checkboxes and 
radio buttons in all the googlebase FTLs.
 Key: OFBIZ-7671
 URL: https://issues.apache.org/jira/browse/OFBIZ-7671
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: Upcoming Branch
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7670) SpecialPurpose/ecommerce: Correct all the checkboxes and radio buttons in all the ecommerce FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7670:
-

Assignee: Mohammad Kathawala

> SpecialPurpose/ecommerce: Correct all the checkboxes and radio buttons in all 
> the ecommerce FTLs.
> -
>
> Key: OFBIZ-7670
> URL: https://issues.apache.org/jira/browse/OFBIZ-7670
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7669) SpecialPurpose/ebaystore: Correct all the checkboxes and radio buttons in all the ebaystore FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7669:
-

Assignee: Mohammad Kathawala

> SpecialPurpose/ebaystore: Correct all the checkboxes and radio buttons in all 
> the ebaystore FTLs.
> -
>
> Key: OFBIZ-7669
> URL: https://issues.apache.org/jira/browse/OFBIZ-7669
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7670) SpecialPurpose/ecommerce: Correct all the checkboxes and radio buttons in all the ecommerce FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7670:
-

 Summary: SpecialPurpose/ecommerce: Correct all the checkboxes and 
radio buttons in all the ecommerce FTLs.
 Key: OFBIZ-7670
 URL: https://issues.apache.org/jira/browse/OFBIZ-7670
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: Upcoming Branch
Reporter: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7668) SpecialPurpose/ebay: Correct all the checkboxes and radio buttons in all the ebay FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7668:
-

 Summary: SpecialPurpose/ebay: Correct all the checkboxes and radio 
buttons in all the ebay FTLs.
 Key: OFBIZ-7668
 URL: https://issues.apache.org/jira/browse/OFBIZ-7668
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: Upcoming Branch
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7667) Webtools: Correct all the checkboxes and radio buttons in all the webtools FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7667:
-

 Summary: Webtools: Correct all the checkboxes and radio buttons in 
all the webtools FTLs.
 Key: OFBIZ-7667
 URL: https://issues.apache.org/jira/browse/OFBIZ-7667
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: Upcoming Branch
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7667) Framework/Webtools: Correct all the checkboxes and radio buttons in all the webtools FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7667:
--
Summary: Framework/Webtools: Correct all the checkboxes and radio buttons 
in all the webtools FTLs.  (was: Webtools: Correct all the checkboxes and radio 
buttons in all the webtools FTLs.)

> Framework/Webtools: Correct all the checkboxes and radio buttons in all the 
> webtools FTLs.
> --
>
> Key: OFBIZ-7667
> URL: https://issues.apache.org/jira/browse/OFBIZ-7667
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7585) Humanares: Correct all the checkboxes and radio buttons in all the humanares FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7585:
--
Attachment: OFBIZ-7585.patch

Added label tags for radio buttons in FindEmployee.ftl file.
Could not find any other use of checkbox/radio in ftl in humanres component.

> Humanares: Correct all the checkboxes and radio buttons in all the humanares 
> FTLs.
> --
>
> Key: OFBIZ-7585
> URL: https://issues.apache.org/jira/browse/OFBIZ-7585
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7585.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7578) Content: Correct all the checkboxes and radio buttons in all the content FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7578:
--
Attachment: OFBIZ-7578.patch

Added label tags for all the checkboxes and radio buttons in all the FTLs of 
content application i.e. all the FTLs related 'applications/content/template'
Attached patch.

> Content: Correct all the checkboxes and radio buttons in all the content FTLs.
> --
>
> Key: OFBIZ-7578
> URL: https://issues.apache.org/jira/browse/OFBIZ-7578
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7578.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7583) Facility: Correct all the checkboxes and radio buttons in all the facility FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7583:
--
Attachment: OFBIZ-7583.patch

Added label tags for all the checkboxes and radio buttons in all the FTLs of 
facility application i.e. all the FTLs related to facility in 
'applications/product/template'
Attached patch.

> Facility: Correct all the checkboxes and radio buttons in all the facility 
> FTLs.
> 
>
> Key: OFBIZ-7583
> URL: https://issues.apache.org/jira/browse/OFBIZ-7583
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7583.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7582) Catalog: Correct all the checkboxes and radio buttons in all the catalog FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7582:
--
Attachment: OFBIZ-7582.patch

Added label tags for all the checkboxes and radio buttons in all the FTLs of 
catalog application i.e. all the FTLs related to product catalog in 
'applications/product/template'

Attached patch.

> Catalog: Correct all the checkboxes and radio buttons in all the catalog FTLs.
> --
>
> Key: OFBIZ-7582
> URL: https://issues.apache.org/jira/browse/OFBIZ-7582
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7582.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7578) Content: Correct all the checkboxes and radio buttons in all the content FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7578:
--
Component/s: (was: ALL APPLICATIONS)
 content

> Content: Correct all the checkboxes and radio buttons in all the content FTLs.
> --
>
> Key: OFBIZ-7578
> URL: https://issues.apache.org/jira/browse/OFBIZ-7578
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7579) Marketing: Correct all the checkboxes and radio buttons in all the marketing FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7579:
--
Component/s: (was: ALL APPLICATIONS)
 marketing

> Marketing: Correct all the checkboxes and radio buttons in all the marketing 
> FTLs.
> --
>
> Key: OFBIZ-7579
> URL: https://issues.apache.org/jira/browse/OFBIZ-7579
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: marketing
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7585) Humanares: Correct all the checkboxes and radio buttons in all the humanares FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7585:
-

 Summary: Humanares: Correct all the checkboxes and radio buttons 
in all the humanares FTLs.
 Key: OFBIZ-7585
 URL: https://issues.apache.org/jira/browse/OFBIZ-7585
 Project: OFBiz
  Issue Type: Sub-task
  Components: humanres
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7577) Accounting: Correct all the checkboxes and radio buttons in all the accounting FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7577:
-

 Summary: Accounting: Correct all the checkboxes and radio buttons 
in all the accounting FTLs.
 Key: OFBIZ-7577
 URL: https://issues.apache.org/jira/browse/OFBIZ-7577
 Project: OFBiz
  Issue Type: Sub-task
  Components: accounting
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7582) Catalog: Correct all the checkboxes and radio buttons in all the catalog FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7582:
-

 Summary: Catalog: Correct all the checkboxes and radio buttons in 
all the catalog FTLs.
 Key: OFBIZ-7582
 URL: https://issues.apache.org/jira/browse/OFBIZ-7582
 Project: OFBiz
  Issue Type: Sub-task
  Components: product
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7584) Workeffort: Correct all the checkboxes and radio buttons in all the workeffort FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7584:
-

 Summary: Workeffort: Correct all the checkboxes and radio buttons 
in all the workeffort FTLs.
 Key: OFBIZ-7584
 URL: https://issues.apache.org/jira/browse/OFBIZ-7584
 Project: OFBiz
  Issue Type: Sub-task
  Components: workeffort
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7583) Facility: Correct all the checkboxes and radio buttons in all the facility FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7583:
-

 Summary: Facility: Correct all the checkboxes and radio buttons in 
all the facility FTLs.
 Key: OFBIZ-7583
 URL: https://issues.apache.org/jira/browse/OFBIZ-7583
 Project: OFBiz
  Issue Type: Sub-task
  Components: product
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7580) Order: Correct all the checkboxes and radio buttons in all the order FTLs.

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7580:
-

Assignee: Mohammad Kathawala

> Order: Correct all the checkboxes and radio buttons in all the order FTLs.
> --
>
> Key: OFBIZ-7580
> URL: https://issues.apache.org/jira/browse/OFBIZ-7580
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: order
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7581) Party: Correct all the checkboxes and radio buttons in all the party FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7581:
-

 Summary: Party: Correct all the checkboxes and radio buttons in 
all the party FTLs.
 Key: OFBIZ-7581
 URL: https://issues.apache.org/jira/browse/OFBIZ-7581
 Project: OFBiz
  Issue Type: Sub-task
  Components: party
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7579) Marketing: Correct all the checkboxes and radio buttons in all the marketing FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7579:
-

 Summary: Marketing: Correct all the checkboxes and radio buttons 
in all the marketing FTLs.
 Key: OFBIZ-7579
 URL: https://issues.apache.org/jira/browse/OFBIZ-7579
 Project: OFBiz
  Issue Type: Sub-task
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7580) Order: Correct all the checkboxes and radio buttons in all the order FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7580:
-

 Summary: Order: Correct all the checkboxes and radio buttons in 
all the order FTLs.
 Key: OFBIZ-7580
 URL: https://issues.apache.org/jira/browse/OFBIZ-7580
 Project: OFBiz
  Issue Type: Sub-task
  Components: order
Reporter: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7578) Content: Correct all the checkboxes and radio buttons in all the content FTLs.

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7578:
-

 Summary: Content: Correct all the checkboxes and radio buttons in 
all the content FTLs.
 Key: OFBIZ-7578
 URL: https://issues.apache.org/jira/browse/OFBIZ-7578
 Project: OFBiz
  Issue Type: Sub-task
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7553) On order list page, the 'All' checkbox for status field does not work properly

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7553:
--
Attachment: OFBIZ-7553.patch

Attached patch.
- Used replaced old js code with jQuery code.
- Added js function which will watch for statuses of all checkbox other than 
'All' and change the 'All' status checkbox accordingly.
- Added class on checkboxes other than 'All' checkbox in order to bind the 
change event in jQuery.
- Also added id on 'All' checkbox to bind its change event in jQuery.

> On order list page, the 'All' checkbox for status field does not work properly
> --
>
> Key: OFBIZ-7553
> URL: https://issues.apache.org/jira/browse/OFBIZ-7553
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: OFBIZ-7553.patch, Screenshot.png
>
>
> Steps to generate:
> 1) Go to order list page.
> 2) For status field, check the 'All' checkbox. This will check all the other 
> status checkboxes.
> 3) Now uncheck any one or more checkbox other than 'All'.
> - Expected: This should uncheck the 'All' checkbox also.
> - Actual: 'All' checkbox remains checked.
> Please see the screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7553) On order list page, the 'All' checkbox for status field does not work properly

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7553:
--
Attachment: Screenshot.png

> On order list page, the 'All' checkbox for status field does not work properly
> --
>
> Key: OFBIZ-7553
> URL: https://issues.apache.org/jira/browse/OFBIZ-7553
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Upcoming Branch
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Attachments: Screenshot.png
>
>
> Steps to generate:
> 1) Go to order list page.
> 2) For status field, check the 'All' checkbox. This will check all the other 
> status checkboxes.
> 3) Now uncheck any one or more checkbox other than 'All'.
> - Expected: This should uncheck the 'All' checkbox also.
> - Actual: 'All' checkbox remains checked.
> Please see the screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7553) On order list page, the 'All' checkbox for status field does not work properly

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7553:
-

 Summary: On order list page, the 'All' checkbox for status field 
does not work properly
 Key: OFBIZ-7553
 URL: https://issues.apache.org/jira/browse/OFBIZ-7553
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Upcoming Branch
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor
 Attachments: Screenshot.png

Steps to generate:

1) Go to order list page.
2) For status field, check the 'All' checkbox. This will check all the other 
status checkboxes.
3) Now uncheck any one or more checkbox other than 'All'.
- Expected: This should uncheck the 'All' checkbox also.
- Actual: 'All' checkbox remains checked.

Please see the screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7542) Convert search criteria on 'Status' into multi-select pattern on all search screens

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7542:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Convert search criteria on 'Status' into multi-select pattern on all search 
> screens
> ---
>
> Key: OFBIZ-7542
> URL: https://issues.apache.org/jira/browse/OFBIZ-7542
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
>
> There are many screens where search can be performed on on given status at a 
> time as its shown in form of dropdown and user can select only one value from 
> it.
> Like Order list screen, we can try using this multi-select as generic search 
> pattern starting with 'Status' and leveraging upon it for any other eligible 
> search criteria. It should behave as follows:
> # Selecting "All" (via checkbox) should auto-select all applicable statuses 
> # De-selecting "All" should remove selection from all selected statuses
> # After selecting "All" if any other status(es) are selected and "All" should 
> be de-selected automatically
> # Multiple statuses should be selectable simultaneously
> # The search result should honor the selected statuses



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7061) Autocompletion for Compound Widget

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15344123#comment-15344123
 ] 

Mohammad Kathawala edited comment on OFBIZ-7061 at 6/22/16 11:07 AM:
-

Getting following or similar errors on console while going through any 
application.

bq.Error message: cvc-complex-type.3.2.2: Attribute 'field' is not allowed to 
appear in element 'set'.



was (Author: mohammad k):
Getting following or similar errors on console while going through any 
application.


bq. [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml   
|E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 25. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 25. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 28. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'now-timestamp'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 28. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'now-timestamp'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 29. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'sequenced-id'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 29. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'sequenced-id'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 30. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 30. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 40. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 40. Error message: cvc-co
 

> Autocompletion for Compound Widget
> --
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: james yong
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7061.patch, OFBIZ-7061.patch, OFBIZ-7061.patch
>
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc; 
> targetNamespace="http://ofbiz.apache.org/sc;
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets 
> use only one consolidated schema. 
> 3. Update ExampleCompou

[jira] [Commented] (OFBIZ-7061) Autocompletion for Compound Widget

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15344123#comment-15344123
 ] 

Mohammad Kathawala commented on OFBIZ-7061:
---

Getting following or similar errors on console while going through any 
application.


bq. [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml   
|E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 25. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 25. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 28. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'now-timestamp'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 28. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'now-timestamp'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 29. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'sequenced-id'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 29. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'sequenced-id'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 30. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 30. Error message: cvc-complex-type.4: Attribute 'field' 
must appear on element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 40. Error message: cvc-complex-type.3.2.2: Attribute 
'field' is not allowed to appear in element 'set'.
 [java] 2016-06-22 16:30:10,128 |http-nio-8443-exec-7 |UtilXml  
 |E| XmlFileLoader: File 
file:/home/mohammad/ofbiz-trunk/applications/commonext/minilang/SystemInfoServices.xml
 process error. Line: 40. Error message: cvc-co
 

> Autocompletion for Compound Widget
> --
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: james yong
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7061.patch, OFBIZ-7061.patch, OFBIZ-7061.patch
>
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc; 
> targetNamespace="http://ofbiz.apache.org/sc;
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets 
> use only one consolidated schema. 
> 3. Update ExampleCompoundWidgets.xml to use the new compound-widgets.xsd. For 
> example
> {code}
> http://www.w3.org/2001/XMLSchema-instance; 
> xmlns:sc="http://ofbiz.apache.org/sc;
> xmlns:m="http://ofbiz.apache.org/m;
>

[jira] [Updated] (OFBIZ-7414) Purchase by Organization report fetching all parties in Internal Org role

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7414:
--
Sprint: Community Day 2 - 2016

> Purchase by Organization report fetching all parties in Internal Org role
> -
>
> Key: OFBIZ-7414
> URL: https://issues.apache.org/jira/browse/OFBIZ-7414
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Fix For: 14.12.01, 15.12.01
>
> Attachments: PObyOrg.png
>
>
> Under Purchase by Organization report it looks like 'To Party' dropdown is 
> currently seems to be fetching all parties in INTERNAL_ORGANIZATION role 
> which could multiple but not necessarily the ones where PO is going to be 
> billed or received eventually (i.e. as per PartyAcctgPreference). We can only 
> show in drop down those parties which are available at the time PO entry
> Please refer attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7403) Allow user to select multiple options in "Purchases by Payment Method" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7403:
--
Sprint: Community Day 2 - 2016

> Allow user to select multiple options in "Purchases by Payment Method" report 
> from basic search criterias while generating report
> -
>
> Key: OFBIZ-7403
> URL: https://issues.apache.org/jira/browse/OFBIZ-7403
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: Purchase_by_Payment_Method.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Payment Method' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Status
> 4) Let's convert Order type into radio button so it only work either for 
> Sales Order or for PO at one time/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7389) Allow user to select multiple options in "Purchases by Organization" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7389:
--
Sprint: Community Day 2 - 2016

> Allow user to select multiple options in "Purchases by Organization" report 
> from basic search criterias while generating report
> ---
>
> Key: OFBIZ-7389
> URL: https://issues.apache.org/jira/browse/OFBIZ-7389
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7389.patch, PurchasebyOrg.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Organization' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) To Party
> 2) Order Status



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7394) Allow user to select multiple options in "Purchases by Product" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7394:
--
Sprint: Community Day 2 - 2016

> Allow user to select multiple options in "Purchases by Product" report from 
> basic search criterias while generating report
> --
>
> Key: OFBIZ-7394
> URL: https://issues.apache.org/jira/browse/OFBIZ-7394
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Attachments: OFBIZ-7394+OFBIZ-7403.patch, 
> OFBIZ-7394+OFBIZ-7403.patch, PurchasebyProduct.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Product' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Let's remove Order type and make it only work for Purchase Order type as 
> for Sales we already have similar report called "Sales by Store"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7386) Allow user to select multiple options in "Open Order Items" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7386:
--
Sprint: Community Day 2 - 2016

> Allow user to select multiple options in "Open Order Items" report from basic 
> search criterias while generating report
> --
>
> Key: OFBIZ-7386
> URL: https://issues.apache.org/jira/browse/OFBIZ-7386
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7386.patch, OrderItemReport.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Open Order Items' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Type (could make it either or selection i.e. either SO or PO with 
> help of radio button)
> 2) Order Status (Here just allow to list only "Created"/"Approved"/"Hold" 
> order (as systemically only these status should have open item)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7385) Allow user to select multiple options in "Sales By Store" report from basic search criteria while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7385:
--
Sprint: Community Day 2 - 2016

> Allow user to select multiple options in "Sales By Store" report from basic 
> search criteria while generating report
> ---
>
> Key: OFBIZ-7385
> URL: https://issues.apache.org/jira/browse/OFBIZ-7385
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: OFBIZ-7385.patch, Salebystore.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence report is generated only based on any one given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Status
> and show the results based on all the selected values. Please refer attached 
> screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7484) The UI of payment section distorts when there is a billing account present for a customer while placing a sales order

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7484:
--
Attachment: OFBIZ-7484.patch

Attached patch.
Removed unnecessary two columns from the rows of the table and merged contents 
in single columns in each row.

> The UI of payment section distorts when there is a billing account present 
> for a customer while placing a sales order
> -
>
> Key: OFBIZ-7484
> URL: https://issues.apache.org/jira/browse/OFBIZ-7484
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Fix For: Trunk
>
> Attachments: OFBIZ-7484.patch, ScreenShot2.png, Screenshot1.png
>
>
> Steps to generate:
> 1) Go to order entry process and select a customer having a billing account
> 2) Add items and continue to payment screen through Finalize Order or Quick 
> Finalize Order
> 3) Due to the select box of billing account, the UI distorts
> Please see the attached screenshots for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7484) The UI of payment section distorts when there is a billing account present for a customer while placing a sales order

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7484:
--
Attachment: ScreenShot2.png
Screenshot1.png

> The UI of payment section distorts when there is a billing account present 
> for a customer while placing a sales order
> -
>
> Key: OFBIZ-7484
> URL: https://issues.apache.org/jira/browse/OFBIZ-7484
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>    Reporter: Mohammad Kathawala
>    Assignee: Mohammad Kathawala
>Priority: Minor
> Fix For: Trunk
>
> Attachments: ScreenShot2.png, Screenshot1.png
>
>
> Steps to generate:
> 1) Go to order entry process and select a customer having a billing account
> 2) Add items and continue to payment screen through Finalize Order or Quick 
> Finalize Order
> 3) Due to the select box of billing account, the UI distorts
> Please see the attached screenshots for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7484) The UI of payment section distorts when there is a billing account present for a customer while placing a sales order

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7484:
-

 Summary: The UI of payment section distorts when there is a 
billing account present for a customer while placing a sales order
 Key: OFBIZ-7484
 URL: https://issues.apache.org/jira/browse/OFBIZ-7484
 Project: OFBiz
  Issue Type: Improvement
  Components: order
Reporter: Mohammad Kathawala
Assignee: Mohammad Kathawala
Priority: Minor
 Fix For: Trunk


Steps to generate:

1) Go to order entry process and select a customer having a billing account
2) Add items and continue to payment screen through Finalize Order or Quick 
Finalize Order
3) Due to the select box of billing account, the UI distorts

Please see the attached screenshots for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7394) Allow user to select multiple options in "Purchases by Product" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7394:
--
Attachment: OFBIZ-7394+OFBIZ-7403.patch

Attached updated patch with correction of typo.

> Allow user to select multiple options in "Purchases by Product" report from 
> basic search criterias while generating report
> --
>
> Key: OFBIZ-7394
> URL: https://issues.apache.org/jira/browse/OFBIZ-7394
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7394+OFBIZ-7403.patch, 
> OFBIZ-7394+OFBIZ-7403.patch, PurchasebyProduct.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Product' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Let's remove Order type and make it only work for Purchase Order type as 
> for Sales we already have similar report called "Sales by Store"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7403) Allow user to select multiple options in "Purchases by Payment Method" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15338437#comment-15338437
 ] 

Mohammad Kathawala commented on OFBIZ-7403:
---

Changes included in the patch of 
[OFBIZ-7394|https://issues.apache.org/jira/browse/OFBIZ-7394].

> Allow user to select multiple options in "Purchases by Payment Method" report 
> from basic search criterias while generating report
> -
>
> Key: OFBIZ-7403
> URL: https://issues.apache.org/jira/browse/OFBIZ-7403
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: Purchase_by_Payment_Method.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Payment Method' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Status
> 4) Let's convert Order type into radio button so it only work either for 
> Sales Order or for PO at one time/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7394) Allow user to select multiple options in "Purchases by Product" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7394:
--
Attachment: OFBIZ-7394+OFBIZ-7403.patch

Attaching a combined patch for this task and for 
[OFBIZ-7403|https://issues.apache.org/jira/browse/OFBIZ-7403] as both the 
reports have a common form.

Did the following changes:
- Changed single select box to multiple select box for product store id in 
forms of both the reports.
- Changed single select box to multiple select box for origin facility id in 
forms of both the reports.
- Changed single select box to checkbox for status id in forms of both the 
reports.
- Removed order type field from Purchases by Product report as we only need to 
have Purchase Orders fetched. Handled this on fetching screen.
- Handled list of product ids, status ids and origin facility ids for both the 
reports on response screen.
- Additional: Changed every product store field in rest of the reports from 
checkbox to multiple select, to have better UI.

> Allow user to select multiple options in "Purchases by Product" report from 
> basic search criterias while generating report
> --
>
> Key: OFBIZ-7394
> URL: https://issues.apache.org/jira/browse/OFBIZ-7394
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7394+OFBIZ-7403.patch, PurchasebyProduct.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Product' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Let's remove Order type and make it only work for Purchase Order type as 
> for Sales we already have similar report called "Sales by Store"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7403) Allow user to select multiple options in "Purchases by Payment Method" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7403:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Allow user to select multiple options in "Purchases by Payment Method" report 
> from basic search criterias while generating report
> -
>
> Key: OFBIZ-7403
> URL: https://issues.apache.org/jira/browse/OFBIZ-7403
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: Purchase_by_Payment_Method.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Payment Method' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Status
> 4) Let's convert Order type into radio button so it only work either for 
> Sales Order or for PO at one time/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7394) Allow user to select multiple options in "Purchases by Product" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7394:
-

Assignee: Mohammad Kathawala  (was: Divesh Dutta)

> Allow user to select multiple options in "Purchases by Product" report from 
> basic search criterias while generating report
> --
>
> Key: OFBIZ-7394
> URL: https://issues.apache.org/jira/browse/OFBIZ-7394
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: PurchasebyProduct.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Product' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Origin Facility
> 3) Let's remove Order type and make it only work for Purchase Order type as 
> for Sales we already have similar report called "Sales by Store"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7414) Purchase by Organization report fetching all parties in Internal Org role

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337779#comment-15337779
 ] 

Mohammad Kathawala commented on OFBIZ-7414:
---

This issue should be fixed along with this 
[https://issues.apache.org/jira/browse/OFBIZ-7389]

> Purchase by Organization report fetching all parties in Internal Org role
> -
>
> Key: OFBIZ-7414
> URL: https://issues.apache.org/jira/browse/OFBIZ-7414
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>    Assignee: Mohammad Kathawala
> Attachments: PObyOrg.png
>
>
> Under Purchase by Organization report it looks like 'To Party' dropdown is 
> currently seems to be fetching all parties in INTERNAL_ORGANIZATION role 
> which could multiple but not necessarily the ones where PO is going to be 
> billed or received eventually (i.e. as per PartyAcctgPreference). We can only 
> show in drop down those parties which are available at the time PO entry
> Please refer attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7414) Purchase by Organization report fetching all parties in Internal Org role

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7414:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Purchase by Organization report fetching all parties in Internal Org role
> -
>
> Key: OFBIZ-7414
> URL: https://issues.apache.org/jira/browse/OFBIZ-7414
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>    Assignee: Mohammad Kathawala
> Attachments: PObyOrg.png
>
>
> Under Purchase by Organization report it looks like 'To Party' dropdown is 
> currently seems to be fetching all parties in INTERNAL_ORGANIZATION role 
> which could multiple but not necessarily the ones where PO is going to be 
> billed or received eventually (i.e. as per PartyAcctgPreference). We can only 
> show in drop down those parties which are available at the time PO entry
> Please refer attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7389) Allow user to select multiple options in "Purchases by Organization" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337772#comment-15337772
 ] 

Mohammad Kathawala edited comment on OFBIZ-7389 at 6/18/16 11:26 AM:
-

- Changed To Party dropdown to checkbox.
- Changed Order Status dropdown to checkbox.
- Handled the value of toPartyId and orderStatusId as list in response screen.
- Also fetch the To parties from 'PartyAcctgPrefAndGroup' entity as done on 
Create Purchase Order screen.


was (Author: mohammad k):
-Changed To Party dropdown to checkbox.
-Changed Order Status dropdown to checkbox.
-Handled the value of toPartyId and orderStatusId as list in response screen.
- Also fetch the To parties from 'PartyAcctgPrefAndGroup' entity as done on 
Create Purchase Order screen.

> Allow user to select multiple options in "Purchases by Organization" report 
> from basic search criterias while generating report
> ---
>
> Key: OFBIZ-7389
> URL: https://issues.apache.org/jira/browse/OFBIZ-7389
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7389.patch, PurchasebyOrg.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Organization' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) To Party
> 2) Order Status



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7389) Allow user to select multiple options in "Purchases by Organization" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7389:
--
Attachment: OFBIZ-7389.patch

-Changed To Party dropdown to checkbox.
-Changed Order Status dropdown to checkbox.
-Handled the value of toPartyId and orderStatusId as list in response screen.
- Also fetch the To parties from 'PartyAcctgPrefAndGroup' entity as done on 
Create Purchase Order screen.

> Allow user to select multiple options in "Purchases by Organization" report 
> from basic search criterias while generating report
> ---
>
> Key: OFBIZ-7389
> URL: https://issues.apache.org/jira/browse/OFBIZ-7389
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7389.patch, PurchasebyOrg.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Organization' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) To Party
> 2) Order Status



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7389) Allow user to select multiple options in "Purchases by Organization" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7389:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Allow user to select multiple options in "Purchases by Organization" report 
> from basic search criterias while generating report
> ---
>
> Key: OFBIZ-7389
> URL: https://issues.apache.org/jira/browse/OFBIZ-7389
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: PurchasebyOrg.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Purchases by Organization' report is generated only based on any one 
> given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) To Party
> 2) Order Status



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7386) Allow user to select multiple options in "Open Order Items" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7386:
--
Attachment: OFBIZ-7386.patch

Done the suggested changes.
Also handled list of product store id and status id at groovy level. Filtered 
statuses for Create/Approved/Held in search option.

> Allow user to select multiple options in "Open Order Items" report from basic 
> search criterias while generating report
> --
>
> Key: OFBIZ-7386
> URL: https://issues.apache.org/jira/browse/OFBIZ-7386
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7386.patch, OrderItemReport.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Open Order Items' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Type (could make it either or selection i.e. either SO or PO with 
> help of radio button)
> 2) Order Status (Here just allow to list only "Created"/"Approved"/"Hold" 
> order (as systemically only these status should have open item)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7386) Allow user to select multiple options in "Open Order Items" report from basic search criterias while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7386:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Allow user to select multiple options in "Open Order Items" report from basic 
> search criterias while generating report
> --
>
> Key: OFBIZ-7386
> URL: https://issues.apache.org/jira/browse/OFBIZ-7386
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OrderItemReport.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence 'Open Order Items' report is generated only based on any one given 
> selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Type
> 2) Order Status (Here just allow to list only "Created"/"Approved"/"Hold" 
> order (as systemically only these status should have open item)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7385) Allow user to select multiple options in "Sales By Store" report from basic search criteria while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7385:
--
Attachment: OFBIZ-7385.patch

Attached patch. Made the product store and status field as multi-select through 
checkboxes. Also did respective changes on screen to handle lists for 
productStoreId and orderStatusId.

Did minor changes in fo.ftl in respect to show list of selected product stores 
and order statuses.

> Allow user to select multiple options in "Sales By Store" report from basic 
> search criteria while generating report
> ---
>
> Key: OFBIZ-7385
> URL: https://issues.apache.org/jira/browse/OFBIZ-7385
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7385.patch, Salebystore.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence report is generated only based on any one given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Status
> and show the results based on all the selected values. Please refer attached 
> screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7385) Allow user to select multiple options in "Sales By Store" report from basic search criteria while generating report

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala reassigned OFBIZ-7385:
-

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

> Allow user to select multiple options in "Sales By Store" report from basic 
> search criteria while generating report
> ---
>
> Key: OFBIZ-7385
> URL: https://issues.apache.org/jira/browse/OFBIZ-7385
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk, 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: Salebystore.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence report is generated only based on any one given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Status
> and show the results based on all the selected values. Please refer attached 
> screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Use of utility method for checking null GenericValue

[Mohammad Kathawala]

 Makes sense to me. If we can simply do the null check, then we should not
use UtilValidate.isNotEmpty() and increase the overhead.

+1

On Sat, Jun 18, 2016 at 10:13 AM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> +1
>
> Best regards,
>
> Pranay Pandey
> HotWax Systems
> http://www.hotwaxsystems.com/
>
> On Fri, Jun 17, 2016 at 8:00 PM, Ratnesh Upadhyay <
> upadhyay.ratn...@gmail.com> wrote:
>
> > Hello community,
> >
> > There are lots of places in code where we have used
> > UtilValidate.isNotEmpty() or UtilValidate.isEmpty() for GenericValue
> object
> > . GenericValue is never empty. Its always null or not null. So should we
> > use directly null or not null check instead of UtilValidate.isNotEmpty()
> > and UtilValidate.isEmpty() for GenericValue objects ?
> >
> > Basically these validation methods should preferably be used on Strings
> or
> > Lists and normal Maps.
> >
> > Thanks!!
> >
> > Regards,
> > Ratnesh Upadhyay
> > HotWax Systems | www.hotwaxsystems.com
> >
>



-- 
Regards,
Mohammad Kathawala
Technical Consultant / Team Lead,
Hotwax Systems,
mohammad.kathaw...@hotwaxsystems.com <mohammad.kathaw...@hotwaxmedia.com>

[jira] [Updated] (OFBIZ-7255) Not able to cancel quantity of order item less than ordered quantity

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7255:
--
Issue Type: Improvement  (was: Bug)

> Not able to cancel quantity of order item less than ordered quantity
> 
>
> Key: OFBIZ-7255
> URL: https://issues.apache.org/jira/browse/OFBIZ-7255
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>    Reporter: Mohammad Kathawala
>Assignee: Divesh Dutta
> Attachments: Screenshot1.png, Screenshot2.png, Screenshot3.png
>
>
> Steps to generate:
> 1) Create a sales order with item quantity more than 1. Lets suppose 3.
> 2) Go to order overview page and click on 'Edit Items'.
> 3) Try to cancel the item with quantity less than 3. Lets suppose 2.
> Expected result:
> Item's 2 quantity should be cancelled.
> Actual result:
> All 3 quantity gets cancelled.
> See attached screenshots for more info.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7299) Partial shipped orders are getting cancelled using cancel option over order header

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325776#comment-15325776
 ] 

Mohammad Kathawala commented on OFBIZ-7299:
---

IMO, 'Cancel Order' option should not be there if the order is partially 
shipped.

> Partial shipped orders are getting cancelled using cancel option over order 
> header 
> ---
>
> Key: OFBIZ-7299
> URL: https://issues.apache.org/jira/browse/OFBIZ-7299
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Ankush Upadhyay
>
> Steps to reproduce:
> 1. Place sales order with quantities more than 1.
> 2. Ship few quantities from facility manager.
> 3. Now cancel the order.
> Actual Behaviour:
> - Order gets cancelled, status in OrderHeader change to ORDER_CANCELLED and 
> in OrderItem change to ITEM_CANCELLED.
> Expected result:
> - Order should mark to ORDER_COMPLETED and item should mark to 
> ITEM_COMPLETED, 
> - Remaining quantity (unshipped) should be set in OrderItem.cancelQuantity. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7255) Not able to cancel quantity of order item less than ordered quantity

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324395#comment-15324395
 ] 

Mohammad Kathawala commented on OFBIZ-7255:
---

I agree with [~diveshdut]. We should do this improvement for logging the cancel 
quantity for the order item.

> Not able to cancel quantity of order item less than ordered quantity
> 
>
> Key: OFBIZ-7255
> URL: https://issues.apache.org/jira/browse/OFBIZ-7255
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>    Reporter: Mohammad Kathawala
>Assignee: Divesh Dutta
> Attachments: Screenshot1.png, Screenshot2.png, Screenshot3.png
>
>
> Steps to generate:
> 1) Create a sales order with item quantity more than 1. Lets suppose 3.
> 2) Go to order overview page and click on 'Edit Items'.
> 3) Try to cancel the item with quantity less than 3. Lets suppose 2.
> Expected result:
> Item's 2 quantity should be cancelled.
> Actual result:
> All 3 quantity gets cancelled.
> See attached screenshots for more info.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7255) Not able to cancel quantity of order item less than ordered quantity

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324395#comment-15324395
 ] 

Mohammad Kathawala edited comment on OFBIZ-7255 at 6/10/16 12:49 PM:
-

I agree with [~diveshdut]. We should do this improvement for logging the 
cancelled quantity of the order item.


was (Author: mohammad k):
I agree with [~diveshdut]. We should do this improvement for logging the cancel 
quantity for the order item.

> Not able to cancel quantity of order item less than ordered quantity
> 
>
> Key: OFBIZ-7255
> URL: https://issues.apache.org/jira/browse/OFBIZ-7255
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>    Reporter: Mohammad Kathawala
>Assignee: Divesh Dutta
> Attachments: Screenshot1.png, Screenshot2.png, Screenshot3.png
>
>
> Steps to generate:
> 1) Create a sales order with item quantity more than 1. Lets suppose 3.
> 2) Go to order overview page and click on 'Edit Items'.
> 3) Try to cancel the item with quantity less than 3. Lets suppose 2.
> Expected result:
> Item's 2 quantity should be cancelled.
> Actual result:
> All 3 quantity gets cancelled.
> See attached screenshots for more info.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7248) Improve the layout of PDF documents

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323910#comment-15323910
 ] 

Mohammad Kathawala commented on OFBIZ-7248:
---

Hi [~pfm.smits],

I am just thinking of making the PDFs more readable. Giving some proper spacing 
between the cells, providing proper borders for the cells and rows etc. will 
make them a lot more readable than what they are now.

Thanks [~soledad] for your proposals. They seems good to me.
In this task we can definitely try going for no.1 i.e. Defining a generic 
decorator for xsl-fo page. I will go ahead and try to prepare a  decorator and 
share it here so that you guys can review it.

For proposal no.2 i.e. Configuring document for each party and using 
partyContent model to render PDFs, we can do this work in separate task as it 
will require much more analysis and efforts.

> Improve the layout of PDF documents
> ---
>
> Key: OFBIZ-7248
> URL: https://issues.apache.org/jira/browse/OFBIZ-7248
> Project: OFBiz
>  Issue Type: Improvement
>    Reporter: Mohammad Kathawala
> Fix For: Trunk
>
>
> The layout of all the PDF documents in OFBiz like Order, Invoice, Picklist, 
> Shipment etc. does not look very good and is not very readable for end users. 
> We need to have a properly structured PDF documents which is easy to read.
> I am going  to create sub-tasks of this parent task for all the different 
> objects.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7255) Not able to cancel quantity of order item less than ordered quantity

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7255:
--
Attachment: Screenshot3.png
Screenshot2.png
Screenshot1.png

> Not able to cancel quantity of order item less than ordered quantity
> 
>
> Key: OFBIZ-7255
> URL: https://issues.apache.org/jira/browse/OFBIZ-7255
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>    Reporter: Mohammad Kathawala
> Attachments: Screenshot1.png, Screenshot2.png, Screenshot3.png
>
>
> Steps to generate:
> 1) Create a sales order with item quantity more than 1. Lets suppose 3.
> 2) Go to order overview page and click on 'Edit Items'.
> 3) Try to cancel the item with quantity less than 3. Lets suppose 2.
> Expected result:
> Item's 2 quantity should be cancelled.
> Actual result:
> All 3 quantity gets cancelled.
> See attached screenshots for more info.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7255) Not able to cancel quantity of order item less than ordered quantity

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7255:
--
Description: 
Steps to generate:

1) Create a sales order with item quantity more than 1. Lets suppose 3.
2) Go to order overview page and click on 'Edit Items'.
3) Try to cancel the item with quantity less than 3. Lets suppose 2.

Expected result:
Item's 2 quantity should be cancelled.
Actual result:
All 3 quantity gets cancelled.

See attached screenshots for more info.

  was:
Steps to generate:

1) Create a sales order with item quantity more than 1. Lets suppose 3.
2) Go to order overview page and click on 'Edit Items'.
3) Try to cancel the item with quantity less than 3. Lets suppose 2.

Expected result:
Item's 2 quantity should be cancelled.
Actual result:
All 3 quantity gets cancelled.


> Not able to cancel quantity of order item less than ordered quantity
> 
>
> Key: OFBIZ-7255
> URL: https://issues.apache.org/jira/browse/OFBIZ-7255
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>    Reporter: Mohammad Kathawala
> Attachments: Screenshot1.png, Screenshot2.png, Screenshot3.png
>
>
> Steps to generate:
> 1) Create a sales order with item quantity more than 1. Lets suppose 3.
> 2) Go to order overview page and click on 'Edit Items'.
> 3) Try to cancel the item with quantity less than 3. Lets suppose 2.
> Expected result:
> Item's 2 quantity should be cancelled.
> Actual result:
> All 3 quantity gets cancelled.
> See attached screenshots for more info.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7255) Not able to cancel quantity of order item less than ordered quantity

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7255:
-

 Summary: Not able to cancel quantity of order item less than 
ordered quantity
 Key: OFBIZ-7255
 URL: https://issues.apache.org/jira/browse/OFBIZ-7255
 Project: OFBiz
  Issue Type: Bug
  Components: order
Reporter: Mohammad Kathawala


Steps to generate:

1) Create a sales order with item quantity more than 1. Lets suppose 3.
2) Go to order overview page and click on 'Edit Items'.
3) Try to cancel the item with quantity less than 3. Lets suppose 2.

Expected result:
Item's 2 quantity should be cancelled.
Actual result:
All 3 quantity gets cancelled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7187) Comment added while adding products to cart are not editable at cart item level

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7187:
--
Attachment: OFBIZ-7187.patch

Added patch for the improvement.

In patch, added text field for item comment in cart item. Added support in 
modifyCart to update the item comment. Comment will be updated on Recalculate 
Order for selected item.

> Comment added while adding products to cart are not editable at cart item 
> level
> ---
>
> Key: OFBIZ-7187
> URL: https://issues.apache.org/jira/browse/OFBIZ-7187
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Attachments: OFBIZ-7187.patch, PO_comment.png
>
>
> The comments added while adding any product to cart are not editable at cart 
> item level. We could try allowing user to update them and eventually transfer 
> them at order item level.
> Please refer to attached screenshot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7248) Improve the layout of PDF documents

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7248:
--
Description: 
The layout of all the PDF documents in OFBiz like Order, Invoice, Picklist, 
Shipment etc. does not look very good and is not very readable for end users. 
We need to have a properly structured PDF documents which is easy to read.

I am going  to create sub-tasks of this parent task for all the different 
objects.  

  was:
The structure of all the PDF documents of various objects in OFBiz like Order, 
Invoice, Picklist, Shipment etc. does not look very good and is not very 
readable. We need to have a properly structured PDF documents which is easy to 
read.

I am going to create sub-tasks of this parent task for all the different 
objects.  


> Improve the layout of PDF documents
> ---
>
> Key: OFBIZ-7248
> URL: https://issues.apache.org/jira/browse/OFBIZ-7248
> Project: OFBiz
>  Issue Type: Improvement
>    Reporter: Mohammad Kathawala
> Fix For: Trunk
>
>
> The layout of all the PDF documents in OFBiz like Order, Invoice, Picklist, 
> Shipment etc. does not look very good and is not very readable for end users. 
> We need to have a properly structured PDF documents which is easy to read.
> I am going  to create sub-tasks of this parent task for all the different 
> objects.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7248) Improve the layout of PDF documents

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7248:
--
Summary: Improve the layout of PDF documents  (was: Improve the structure 
of PDF documents)

> Improve the layout of PDF documents
> ---
>
> Key: OFBIZ-7248
> URL: https://issues.apache.org/jira/browse/OFBIZ-7248
> Project: OFBiz
>  Issue Type: Improvement
>    Reporter: Mohammad Kathawala
> Fix For: Trunk
>
>
> The structure of all the PDF documents of various objects in OFBiz like 
> Order, Invoice, Picklist, Shipment etc. does not look very good and is not 
> very readable. We need to have a properly structured PDF documents which is 
> easy to read.
> I am going to create sub-tasks of this parent task for all the different 
> objects.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7248) Improve the structure of PDF documents

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-7248:
-

 Summary: Improve the structure of PDF documents
 Key: OFBIZ-7248
 URL: https://issues.apache.org/jira/browse/OFBIZ-7248
 Project: OFBiz
  Issue Type: Improvement
Reporter: Mohammad Kathawala
 Fix For: Trunk


The structure of all the PDF documents of various objects in OFBiz like Order, 
Invoice, Picklist, Shipment etc. does not look very good and is not very 
readable. We need to have a properly structured PDF documents which is easy to 
read.

I am going to create sub-tasks of this parent task for all the different 
objects.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6952) After change password by admin, I got error (see description and screenshot)

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315478#comment-15315478
 ] 

Mohammad Kathawala edited comment on OFBIZ-6952 at 6/4/16 12:07 PM:


"updatePassword" service is used here. After updating the password, this 
service is not replacing the userLogin object in session with the newly updated 
userLogin object. This was creating the issue.

In the patch, we have used the simple method from LoginSimpleEvents.xml, which 
in turn calls the "updatePassword" service and set the newly updated userLogin 
object in the session. This fixes the issue.

Thanks [~rohit.koushal] for the research and help. 


was (Author: mohammad k):
"updatePassword" service is used here. After updating the password, this 
service is not replacing the userLogin object in session with the newly updated 
userLogin object. This was creating the issue.

In the patch, we have used the simple method from LoginSimpleEvents.xml, which 
in turn calls the "updatePassword" service and set the newly update userLogin 
object in the session. This fixes the issue.

Thanks [~rohit.koushal] for the research and help. 

> After change password by admin, I got error (see description and screenshot)
> 
>
> Key: OFBIZ-6952
> URL: https://issues.apache.org/jira/browse/OFBIZ-6952
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Supachai Chaima-ngua (Tor)
>  Labels: partymgr
> Fix For: Trunk
>
> Attachments: Image 086.png, OFBIZ-6952.patch, Screen Shot 2016-04-20 
> at 6.26.00 PM.png, screenshot-1.png
>
>
> The next page after save new password appear the message below. it should not 
> happen with admin.
> Message on screen:
> You do not have permission to view this page. ("PARTYMGR_VIEW" or 
> "PARTYMGR_ADMIN" needed)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6952) After change password by admin, I got error (see description and screenshot)

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-6952:
--
Attachment: OFBIZ-6952.patch

"updatePassword" service is used here. After updating the password, this 
service is not replacing the userLogin object in session with the newly updated 
userLogin object. This was creating the issue.

In the patch, we have used the simple method from LoginSimpleEvents.xml, which 
in turn calls the "updatePassword" service and set the newly update userLogin 
object in the session. This fixes the issue.

Thanks [~rohit.koushal] for the research and help. 

> After change password by admin, I got error (see description and screenshot)
> 
>
> Key: OFBIZ-6952
> URL: https://issues.apache.org/jira/browse/OFBIZ-6952
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Supachai Chaima-ngua (Tor)
>  Labels: partymgr
> Fix For: Trunk
>
> Attachments: Image 086.png, OFBIZ-6952.patch, Screen Shot 2016-04-20 
> at 6.26.00 PM.png, screenshot-1.png
>
>
> The next page after save new password appear the message below. it should not 
> happen with admin.
> Message on screen:
> You do not have permission to view this page. ("PARTYMGR_VIEW" or 
> "PARTYMGR_ADMIN" needed)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7102) Fix the Approve button label for newly added item to the existing PO

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7102:
--
Attachment: OFBIZ-7102-trunk.patch

Changed the Button Label to 'Approve Item'

> Fix the Approve button label for newly added item to the existing PO
> 
>
> Key: OFBIZ-7102
> URL: https://issues.apache.org/jira/browse/OFBIZ-7102
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Reporter: Ratnesh Upadhyay
>Priority: Minor
> Attachments: ApproveButtonLabel.png, OFBIZ-7102-trunk.patch
>
>
> Upon Adding new item to existing approved purchase order creates a new line 
> item to the existing order in CREATED state but it shows the button label as 
> 'APPROVE ORDER' instead of 'APPROVE ITEM'.
> Please refer to attached screenshot for more details



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7051) Add the support for specifying 'Lead Time' while placing the quote to purchase a product

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7051:
--
Attachment: OFBIZ-7051-trunk.patch

Extended 'QuoteItem' entity with a field 'leadTimeDays'.
Also shown the 'leadTimeDays' value on ViewQuote and ListQuoteItems screen.

> Add the support for specifying 'Lead Time' while placing the quote to 
> purchase a product
> 
>
> Key: OFBIZ-7051
> URL: https://issues.apache.org/jira/browse/OFBIZ-7051
> Project: OFBiz
>  Issue Type: New Feature
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
>Priority: Critical
> Attachments: OFBIZ-7051-trunk.patch
>
>
> Many a times the Offered/negotiated/Agreed price for an item for which quote 
> is accepted in the system from a supplier is dependent on the lead time taken 
> by supplier to ship the specified quantity. 
> We should have a way to specify the Lead Time (in Days to start with) against 
> each quote line item to allow purchasing manager to take more informed 
> decisions.
> Technically we can extend QuoteItem with "leadTimeDays" to support this 
> feature and show the same over QuoteItem and Quote Overview>>Quote Item 
> section.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7052) Comment added against any quote item is not getting reflected anywhere on Quote Item UI

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-7052:
--
Attachment: OFBIZ-7052.patch

> Comment added against any quote item is not getting reflected anywhere on 
> Quote Item UI
> ---
>
> Key: OFBIZ-7052
> URL: https://issues.apache.org/jira/browse/OFBIZ-7052
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Swapnil Shah
> Attachments: OFBIZ-7052.patch, QuoteItemComment_1.png, 
> QuoteItemComment_2.png, QuoteItemComment_3.png
>
>
> While any product is added as Quote Line Item with any comment then same need 
> to be reflected over Quote View >> Quote Item section and Quote Item screen 
> itself. 
> Please refer to attached screenshot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7052) Comment added against any quote item is not getting reflected anywhere on Quote Item UI

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15275091#comment-15275091
 ] 

Mohammad Kathawala commented on OFBIZ-7052:
---

Thanks Swapnil for reporting the issue.
I am working on it and will provide the patch soon.

> Comment added against any quote item is not getting reflected anywhere on 
> Quote Item UI
> ---
>
> Key: OFBIZ-7052
> URL: https://issues.apache.org/jira/browse/OFBIZ-7052
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Swapnil Shah
> Attachments: QuoteItemComment_1.png, QuoteItemComment_2.png, 
> QuoteItemComment_3.png
>
>
> While any product is added as Quote Line Item with any comment then same need 
> to be reflected over Quote View >> Quote Item section and Quote Item screen 
> itself. 
> Please refer to attached screenshot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6953) Can not go to "viewprofile" if you is on webtools (see description and screenshot)

[Mohammad Kathawala (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244048#comment-15244048
 ] 

Mohammad Kathawala commented on OFBIZ-6953:
---

I think the patch provided is correct.

I was able to reproduce the issue. In Tomahawk theme, the party profile link of 
the logged in user redirects to error page.
Steps to reproduce:
1) Change the visual theme to Tomahawk
2) Go to any application other than partymgr. For example, go to 
[https://localhost:8443/webtools/control/main]
3) From here, click on link to logged in user profile page on top right section

> Can not go to "viewprofile" if you is on webtools (see description and 
> screenshot)
> --
>
> Key: OFBIZ-6953
> URL: https://issues.apache.org/jira/browse/OFBIZ-6953
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Supachai Chaima-ngua (Tor)
> Attachments: TomahawkThemeCanNotGotoProfile.patch, screenshot-1.png
>
>
> :ERROR MESSAGE:
> org.ofbiz.webapp.control.RequestHandlerException: Unknown request 
> [viewprofile]; this request does not exist or cannot be called directly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6945) Worker class and worker methods for facility component

[Mohammad Kathawala (JIRA)]

Mohammad Kathawala created OFBIZ-6945:
-

 Summary: Worker class and worker methods for facility component
 Key: OFBIZ-6945
 URL: https://issues.apache.org/jira/browse/OFBIZ-6945
 Project: OFBiz
  Issue Type: Improvement
Reporter: Mohammad Kathawala
Priority: Minor


There isn't any worker class containing worker methods for facility component 
in OFBIZ.

 Various generic worker methods can be implemented like:
- 'differenceInShipCost' which will calculate the difference in estimated 
shipping cost (quoted during checkout process) and actual shipping cost 
(received when packing is complete and we have actual package weight) of any 
shipment.
- 'isPicklistPacked' which will determine whether any picklist is packed or not.
- 'getShipmentBoxTypes' for getting all the box types available for particular 
shipment method of a particular carrier party.

And there can be many more.

The worker class for facility will have all such kinds of worker methods.  

I propose to add this class and I can contribute some initial worker methods . 
I can also use these methods at applicable places. If community members agree 
then, I will start implementing these methods .  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5868) Have the ability to view the quote profit at all times

[Mohammad Kathawala (JIRA)]

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

Mohammad Kathawala updated OFBIZ-5868:
--
Attachment: OFBIZ-5868.patch

> Have the ability to view the quote profit at all times
> --
>
> Key: OFBIZ-5868
> URL: https://issues.apache.org/jira/browse/OFBIZ-5868
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: quote
> Attachments: OFBIZ-5868.patch
>
>
> Currently the View Profit overview is only visible when the quote has the 
> status 'QUO_CREATED'. It should be so that the user can see the profit 
> overview irrespect of the the status.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)