Re: Welcome to Daniel Watford as new PMC member
Many congratulations Daniel! On Thu, Feb 2, 2023 at 10:56 AM Deepak Dixit wrote: > Many manu Congratulations Daniel! > > Kind Regards, > Deepak Dixit > > > On Wed, Feb 1, 2023 at 6:28 PM Priya Sharma > wrote: > > > Many Congratulations Daniel! > > > > On Tue, 31 Jan 2023 at 15:05, Daniel Watford wrote: > > > > > Thanks all - I appreciate the invitation and am happy to be here :) > > > > > > On Mon, 30 Jan 2023 at 16:33, gil.portenseigne < > > > gil.portensei...@nereide.fr> > > > wrote: > > > > > > > Welcome Daniel, and Congrats ! > > > > > > > > Gil > > > > On 28/01/23 11:57, Jacopo Cappellato wrote: > > > > > The OFBiz PMC has invited Daniel Watford as a new PMC member and we > > > > > are glad to announce that Daniel has accepted the nomination. > > > > > > > > > > On behalf of the OFBiz PMC, welcome on board! > > > > > > > > > > > > > -- > > > Daniel Watford > > > > > > -- -- Thanks & Regards Chandan Khandelwal HotWax Systemshttp://www.hotwaxsystems.com
Re: public rest API
Hi Girish, I have gone through the implementation and tested it on API client with HTTP bearer token authentication and worked for me for both auth= true/false (bypass authorization). Kind Regards, Chandan Khandelwal On Sat, Sep 26, 2020 at 2:35 PM Girish Vasmatkar < girish.vasmat...@hotwaxsystems.com> wrote: > Hello Hans > > With the latest commi1361c3c > < > https://github.com/apache/ofbiz-plugins/commit/1361c3cdaf7d6756cc9abdc6c37450ef3d46f921 > > > on > trunk, the system now honours the "auth" attribute defined on service and > accordingly bypasses authorization for such services. > > Best, > Girish > > > On Thu, Sep 10, 2020 at 5:46 PM Hans Bakker > wrote: > > > Thank you Girish, > > > > look forward to your updates of this excellent and much needed addition > to > > OFBiz. > > > > Regars > > > > Hans > > www.antwebsystems.com > > On 9/10/20 3:27 PM, Girish Vasmatkar wrote: > > > > Thanks Hans, I will plan to include this change for the exportable > > services as well. > > > > There is also OFBIZ-11995, where more RESTFul resources can be declared > > (development is undergoing) and bound to services where I had planned to > > include declarative authentication. > > > > Best Regards, > > Girish Vasmatkar > > HotWax Systems > > > > > > > > > > On Thu, Sep 10, 2020 at 12:08 PM Hans Bakker > > > wrote: > > > >> Hi Girish, > >> > >> how about ecommerce? you want to show the products without logging in, > >> actually all information on the ecommerce frontend? > >> > >> so yes, really required. > >> > >> regards, > >> > >> Hans > >> > >> > >> On 9/10/20 12:37 PM, Girish Vasmatkar wrote: > >> > Every REST endpoint, as it is implemented now, is secured by default. > I > >> had > >> > not thought of a scenario where internal OFBiz services will need to > be > >> > invoked without authentication (externally) > >> > > >> > Yes, the services themselves can be specified to NOT require auth but > I > >> had > >> > always thought that was applicable within internal execution. I may be > >> > wrong here, so please correct me. > >> > > >> > auth and login-required are not taken into account yet, but can > >> certainly > >> > be, if some exportable services should be exposed as public APIs. > >> > > >> > Best Regards, > >> > Girish Vasmatkar > >> > HotWax Systems > >> > > >> > > >> > > >> > On Thu, Sep 10, 2020 at 5:55 AM Hans Bakker < > h.bak...@antwebsystems.com > >> > > >> > wrote: > >> > > >> >> Hi, Girish, > >> >> > >> >> thanks again for your last reply it defenity helped, however i have > >> >> another question. > >> >> > >> >> I need to access certain services publicly without a token. > >> >> > >> >> I have put auth="false" on the service definition and > >> >> login-required="false" on the simple-method implementation > >> >> > >> >> still i get a 401 response. > >> >> > >> >> any suggestions? > >> >> > >> >> Regards, > >> >> > >> >> Hans > >> >> > >> >> > >> > > >
Re: Headless Commerce Plugin for OFBiz
Thanks Arpit for this initiative and +1 for the separate headless commerce plugin. Kind Regards, Chandan Khandelwal On Thu, Aug 20, 2020 at 2:46 PM Mridul Pathak < mridul.pat...@hotwaxsystems.com> wrote: > +1. This is a great suggestion. > > OFBiz has been mainly adopted for its business applications, eCommere > being one of the top ones. Though its tightly coupled nature doesn’t make > it well suited for the modern day web or mobile application development. It > definitely needs to be revamped to make it more relevant in this ever > changing world of technology. > > Of course there will be some challenges that would need to be addressed to > be able to build a truly REST API but that opens up the path to the long > needed refactoring/reimplementation of some of these business processes and > objects, for example shopping cart. > > It is high time that we start taking steps to move from somewhat > monolithic implementation towards a more micro service based approach and > eCommerce would be a great start. Headless capabilities are must and > dedicated plugins could be a great way to expose existing business > functions as REST APIs in the form of micro services without needing to > change the core implementation much. The newly introduced REST plugin would > play a major role in this journey. > > Thanks. > Mridul Pathak > > > > On 20-Aug-2020, at 12:40 PM, Deepak Dixit wrote: > > > > Hi Arpit, > > > > Sounds like a plan, As now ofbiz supports rest, so we can think of > headless > > commerce. > > > > I think you need to work on the B2C ordering process, as per current > > implementation it's tightly coupled with ShoppingCart. > > All the e-commerce related processes are bound with ShoppingCart and > OFBiz > > use session to maintain shoppingCart. > > > > > > > > Thanks & Regards > > -- > > Deepak Dixit > > ofbiz.apache.org > > > > > > On Tue, Aug 18, 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 mus
Re: Welcome to Devanshu Vyas as new committer!
Many congratulations Devanshu! Kind Regards, Chandan Khandelwal On Fri, Aug 21, 2020 at 2:49 PM Ankit Joshi wrote: > Many Congratulations Devanshu > > Thanks & Regards, > Ankit Joshi > Sr. Technical Consultant > > *HotWax Systems* > *Enterprise open source experts* > cell: +91-8989267238 > office: 0731-409-3684 > http://www.hotwaxsystems.com > > > On Wed, Aug 19, 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 > > >
Re: Welcome Arun Patidar as new PMC member
Many Congratulations Arun! Kind Regards, Chandan Khandelwal On Mon, Jul 6, 2020 at 5:57 PM Devanshu Vyas wrote: > Many many Congratulations Arun! > > Thanks & Regards, > Devanshu Vyas. > > > 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 Aditya Sharma as new PMC member
Many Congratulations Aditya! Kind Regards, Chandan Khandelwal On Mon, Jul 6, 2020 at 5:19 PM Swapnil M Mane wrote: > Many congratulations Aditya, welcome aboard! > > - Best regards, > Swapnil M Mane, > ofbiz.apache.org > > > > 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 Suraj Khurana as new PMC member
Many Congratulations Suraj! Kind Regards, Chandan Khandelwal On Mon, Jul 6, 2020 at 5:20 PM Swapnil M Mane wrote: > Many congratulations Suraj, welcome aboard! > > - Best regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Sat, Jul 4, 2020 at 5:22 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> > 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: Use cache in Type Data lookup
Hi Pawan, +1 for using cache for type data. Kind Regards, Chandan Khandelwal On Tue, Jun 16, 2020 at 3:52 PM Pawan Verma wrote: > Hello Devs, > > Greetings for the day! > > Using cache while fetching data from Type entity is a good practice as Type > data is permanent in the system. We've already implemented this practice > proficiently in our code base but some lookups failed to do so. > > My proposal here is to use a cache for all the Type Data Lookups. If we are > unanimous for this improvement, I'll log a Jira for this. > > Please let me know your thoughts on this. Thanks! > > -- > Thanks & Regards > Pawan Verma > Technical Consultant > *HotWax Systems* > *Enterprise open source experts* > http://www.hotwaxsystems.com >
Re: EntityBatchIterator for large data set queries
Hello Pawan,
Approach looks good, my only suggestion is to use batch processing only
when we are dealing with large data set, as this method takes a longer time
compared to the normal method specially on a distributed environment, which
may negatively impact the performance.
Kind Regards,
Chandan Khandelwal
Senior Manager, Enterprise Software Development
*HotWax Systems*
*Enterprise open source experts*
cell: +91-98934-81076
office: 0731-409-3684
http://www.hotwaxsystems.com
On Fri, Jun 5, 2020 at 4:07 PM Pawan Verma
wrote:
> Thanks, Pritam and Scott for the discussion.
>
> I've created Jira OFBIZ-11789 for this improvement and also created a PR
> with the proposed changes.
>
> I request everyone to review the PR and suggest your thought on this.
> Thanks!
> --
> Thanks & Regards
> Pawan Verma
> Technical Consultant
> *HotWax Systems*
> *Enterprise open source experts*
> http://www.hotwaxsystems.com
>
>
> On Mon, Jun 1, 2020 at 12:36 PM Pritam Kute >
> wrote:
>
> > Thanks Scott for your detailed explanation.
> >
> > The solution looks good to me too. My confusion was with why we are going
> > to implement new method if we can achieve that using the current
> > EntityQuery methods.
> >
> > +1 for adding queryBatchIterator() to EntityQuery.
> >
> > Kind Regards,
> > --
> > Pritam Kute
> >
> >
> > On Thu, May 28, 2020 at 6:32 AM Scott Gray >
> > wrote:
> >
> > > Hi Pritam,
> > >
> > > I'm not sure about PostgreSQL or Derby but I know with MySQL that
> using a
> > > cursor doesn't really work. You have to set the result set to
> > > TYPE_FORWARD_ONLY and CONCUR_READ_ONLY and also set the fetch size to
> > > INTEGER.MIN_VALUE. Only then will the driver stream the results and
> even
> > > then, you may not execute any other SQL commands on the connection
> until
> > > you have fully read or closed the resultset.
> > >
> > > So if an EntityListIterator doesn't really conserve memory, then you
> need
> > > to take a paging query approach such as this:
> > > EntityQuery query =
> > EntityQuery.use(delegator).from("SomeTable").limit(100)
> > > List results = null
> > > while (!(results = query.queryList()).isEmpty()) {
> > > for (value : results) {
> > > // do something with each value
> > > }
> > > query.offset(query.getOffset() + query.getLimit())
> > > }
> > >
> > > Or with the proposed EntityBatchIterator:
> > > Iterator query =
> > >
> > >
> >
> EntityQuery.use(delegator).from("SomeTable").limit(100).queryBatchIterator()
> > > while (iterator.hasNext()) {
> > > result = iterator.next()
> > > // do something with each value
> > > }
> > >
> > > I guess an alternative approach would be to implement something similar
> > > within the EntityListIterator and perhaps a flag to turn it off or on
> > > depending on which database is being used and how well it supports
> > > iterating over results without loading the entire resultset into
> memory.
> > >
> > > Regards
> > > Scott
> > >
> > >
> > >
> > > On Sat, 23 May 2020 at 20:59, Pritam Kute <
> pritam.k...@hotwaxsystems.com
> > >
> > > wrote:
> > >
> > > > Hello Pawan,
> > > >
> > > > I just had a look into the EntityQuery.queryIterator() method and
> looks
> > > > like we can achieve that by using fetchSize(), fowardOnly(),
> > > > cursorScrollInsensitive(), cursorScrollSensitive() and offset()
> methods
> > > in
> > > > EntityQuery class. Let me know if I am missing anything.
> > > >
> > > > It will be good if you can post a pseudo code or something here so
> that
> > > we
> > > > could get an understanding of the exact design which you have in your
> > > mind.
> > > >
> > > > Kind Regards,
> > > > --
> > > > Pritam Kute
> > > >
> > > >
> > > > On Thu, May 21, 2020 at 7:41 PM Pawan Verma <
> > > pawan.ve...@hotwaxsystems.com
> > > > >
> > > > wrote:
> > > >
> > > > > Hello Devs,
> > > > >
> > > > > While working on the large database we have figured out that very
> > large
> > > > > queries consume all memory and crash ofbiz(because queryIterator()
> > > > doesn't
> > > > > really
Re: Welcome Swapnil M Mane as new PMC member
Congratulations Swapnil! Kind Regards, Chandan Khandelwal On Fri, Apr 24, 2020 at 1:17 PM Rishi Solanki wrote: > Congratulations Swapnil!! :-) > > Best Regards, > -- > Rishi Solanki > *CTO, Mindpath Technology* > Intelligent Solutions > cell: +91-98932-87847 > LinkedIn <https://www.linkedin.com/in/rishi-solanki-62271b7/> > > > On Fri, Apr 24, 2020 at 11:21 AM Michael Brohl > wrote: > > > Congratulations and welcome aboard, Swapnil! > > > > Michael > > > > > > Am 23.04.20 um 13:32 schrieb Jacques Le Roux: > > > 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: Welcome James Young as new PMC member
Congratulations James! Kind Regards, Chandan Khandelwal On Fri, Apr 24, 2020 at 1:20 PM Mridul Pathak wrote: > Congratulations James!! > > Thanks. > -- > Mridul Pathak > > > On Wed, Apr 22, 2020 at 2:08 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > The OFBiz PMC has invited James Young 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: Welcome Pranay Pandey as a new PMC member
Many Congratulations Pranay! Kind Regards, Chandan Khandelwal On Wed, Sep 25, 2019 at 10:56 AM Aditya Sharma wrote: > Felicitations Pranay !! > > Thanks and Regards, > Aditya Sharma > > On Wed, Sep 25, 2019 at 10:44 AM Suraj Khurana > wrote: > > > Many Congratulations Pranay !! > > > > -- > > Best Regards, > > Suraj Khurana > > Technical Consultant > > > > > > > > > > > > On Wed, Sep 25, 2019 at 10:14 AM Ashish Vijaywargiya < > > ashish.vijaywarg...@hotwaxsystems.com> wrote: > > > > > Many congratulations Pranay!! > > > > > > -- > > > Kind Regards, > > > Ashish Vijaywargiya > > > Vice President of Operations > > > *HotWax Systems* > > > *Enterprise open source experts* > > > cell: +91-9893479711 > > > http://www.hotwaxsystems.com > > > > > > > > > > > > On Tue, Sep 24, 2019 at 9:07 PM Jacques Le Roux < > > > jacques.le.r...@les7arts.com> wrote: > > > > > > > The OFBiz PMC has invited Pranay Pandey to become a new member of the > > > > committee and we are glad to announce that he has accepted the > > > nomination. > > > > > > > > Welcome on board Pranay! > > > > > > > > Jacques (on behalf of the OFBiz PMC) > > > > > > > > > > > > > >
Re: Welcome Paul Foxworthy as a new PMC member
Many Congratulations Paul! -- Chandan Khandelwal On Thu, Mar 22, 2018 at 5:15 AM, Paul Foxworthy <p...@cohsoft.com.au> wrote: > Thanks everyone! > > Cheers > > Paul Foxworthy > > On 22 March 2018 at 03:25, Michael Brohl <michael.br...@ecomify.de> wrote: > > > Good to have you on board, Paul. Congratulations! > > > > Regards, > > > > Michael > > > > > > > Am 21.03.2018 um 09:42 schrieb Jacopo Cappellato < > > jacopo.cappell...@gmail.com>: > > > > > > The OFBiz PMC has invited Paul Foxworthy to become a new member of the > > > committee and we are glad to announce that Paul has accepted the > > nomination. > > > > > > Welcome on board Paul! > > > > > > Jacopo Cappellato (on behalf of the OFBiz PMC) > > > > > > > -- > Coherent Software Australia Pty Ltd > PO Box 2773 > Cheltenham Vic 3192 > Australia > > Phone: +61 3 9585 6788 > Web: http://www.coherentsoftware.com.au/ > Email: i...@coherentsoftware.com.au >
Re: Make usage of EntitySyncRemove configurable
Here is the ticket for this improvement - https://issues.apache.org/jira/browse/OFBIZ-10008. -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Fri, Oct 6, 2017 at 11:25 AM, Chandan Khandelwal < chandan.khandel...@hotwaxsystems.com> wrote: > Thanks Jacques for your time on this. I will look into it more and provide > a patch for community review. > > > -- > Thanks & Regards, > Chandan Khandelwal > HotWax Systems > Direct: +91-9893481076 > http://www.hotwaxsystems.com/ > > On Tue, Oct 3, 2017 at 5:09 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > >> Hi Chandan, >> >> Then indeed a new mechanism should be introduced to prevent >> >> this.saveEntitySyncRemoveInfo(value.getPrimaryKey()); >> >> in GenericDelegator.removeValue() >> >> It seems to me that this should be set in entityengine.xml by delegator. >> Or maybe even simpler with a general property. >> >> Jacques >> >> >> >> Le 03/10/2017 à 13:07, Chandan Khandelwal a écrit : >> >>> Hi Jacques, >>> >>> cleanSyncRemoveInfo service will be used to clean/delete the >>> EntitySyncRemove records of specific time interval. >>> >>> When any records are removed the primary key will be saved in the >>> EntitySyncRemove entity's for syncing purpose, I am talking about to not >>> create EntitySyncRemove records (disable the usage of ENTITY_SYNC* >>> entities) if not needed. >>> >>> >>> >> > > >
Re: Make usage of EntitySyncRemove configurable
Thanks Jacques for your time on this. I will look into it more and provide a patch for community review. -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Tue, Oct 3, 2017 at 5:09 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Hi Chandan, > > Then indeed a new mechanism should be introduced to prevent > > this.saveEntitySyncRemoveInfo(value.getPrimaryKey()); > > in GenericDelegator.removeValue() > > It seems to me that this should be set in entityengine.xml by delegator. > Or maybe even simpler with a general property. > > Jacques > > > > Le 03/10/2017 à 13:07, Chandan Khandelwal a écrit : > >> Hi Jacques, >> >> cleanSyncRemoveInfo service will be used to clean/delete the >> EntitySyncRemove records of specific time interval. >> >> When any records are removed the primary key will be saved in the >> EntitySyncRemove entity's for syncing purpose, I am talking about to not >> create EntitySyncRemove records (disable the usage of ENTITY_SYNC* >> entities) if not needed. >> >> >> >
Re: Make usage of EntitySyncRemove configurable
Hi Jacques, cleanSyncRemoveInfo service will be used to clean/delete the EntitySyncRemove records of specific time interval. When any records are removed the primary key will be saved in the EntitySyncRemove entity's for syncing purpose, I am talking about to not create EntitySyncRemove records (disable the usage of ENTITY_SYNC* entities) if not needed. -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Tue, Oct 3, 2017 at 1:21 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Ah, actually EntitySyncRemove is automatically used by the "Clear > EntitySyncRemove Info" job which uses cleanSyncRemoveInfo > > Maybe you only need to deactivate this job? > > Jacques > > > > Le 01/10/2017 à 10:51, Jacques Le Roux a écrit : > >> Hi Chandan, >> >> Could you give us more information please? >> >> In my mind EntitySyncRemove is only used on demand, but I could be wrong. >> >> Did you find that EntitySyncRemove is automatically synced from somewhere? >> >> Thanks >> >> Jacques >> >> >> Le 23/09/2017 à 08:20, Chandan Khandelwal a écrit : >> >>> Hello All, >>> >>> I have reviewed the code and usage of EntitySyncRemove and found there >>> are >>> no configurations available to disable usage of EntitySyncRemove. >>> >>> It is creating problems when having a large database and frequent delete >>> operations. >>> >>> Please provide your inputs to make EntitySyncRemove configurable. >>> >>> >> >> >
Make usage of EntitySyncRemove configurable
Hello All, I have reviewed the code and usage of EntitySyncRemove and found there are no configurations available to disable usage of EntitySyncRemove. It is creating problems when having a large database and frequent delete operations. Please provide your inputs to make EntitySyncRemove configurable. -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/
Re: OrderHeader And WebSite Relationship
Hi All, I have created parent ticket to manage this effort throughout the application Ticket: https://issues.apache.org/jira/browse/OFBIZ-9671 -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Wed, Aug 30, 2017 at 9:20 PM, Ratnesh Upadhyay < upadhyay.ratn...@gmail.com> wrote: > Thanks everyone for your inputs. I'll add record for "OrderEntry" website > and relationship. > > @Jacques, I reviewed the usage of OrderTestData.xml and found that it's > using by test-suite "ordertests" and I think it will work as we have entry > for this suite in order/ofbiz-component.xml. > > Regards, > Ratnesh Upadhyay > HotWax Systems | www.hotwaxsystems.com > > On Sun, Aug 27, 2017 at 12:24 AM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > Hi Ratnesh, > > > > About 1 and 2, in such cases I always try to find the roots. > > > > 1. It's https://issues.apache.org/jira/browse/OFBIZ-290 look for > > webSiteId,OrderEntry > > 2. http://svn.apache.org/viewvc?view=revision=1128984 > > > > Unfortunately seems that this not add much. I also wonder if the data in > > OrderTestData.xml are ever used (else tests would fail, right?) > > > > Anyway, I agree with your conclusion. > > > > My 2cts > > > > Jacques > > > > > > > > Le 26/08/2017 à 14:48, Ratnesh Upadhyay a écrit : > > > >> Devs, > >> > >> I've noticed few things that needs to be discussed : > >> > >> 1. We have few order in DemoOrderTestData.xml and OrderTestData.xml > that > >> are having webSiteId="OrderEntry" but we don't have any record in > WebSite > >> entity for "OrderEntry" webSiteId. > >> 2. We have "setCustRequestStatus" and "setCustRequestStatus" ecas where > we > >> are having following condition : > >> > >> Although we don't have this webSite record in entity then these ecas are > >> no > >> more of use as system never meet this condition. > >> 3. There is no "webSiteId" is being set for orders placed from ordermgr > >> application, so IMO we should setup webSiteId parameter in > servletConetext > >> of ordermgr app to get it setup. I can see its usage to get the > >> information > >> of orders placed from store front as well as from backend application. > >> > >> To apply FK constraint either we have to add record in WebSite entity or > >> remove the references of "OrderEntry" webSiteId from order demo data. > Also > >> please let me know your thoughts to set webSiteId for backend apps. > >> > >> IMO, we should add record in WebSite entity for "OrderEntry". > >> > >> Thanks!! > >> > >> Regards, > >> Ratnesh Upadhyay > >> HotWax Systems | www.hotwaxsystems.com > >> > >> > >> > >> > >> > >> On Sat, Aug 26, 2017 at 1:08 PM, Ratnesh Upadhyay < > >> upadhyay.ratn...@gmail.com> wrote: > >> > >> Thanks everyone for your inputs. > >>> Here is the jira ticket : https://issues.apache.org/jira > >>> /browse/OFBIZ-9647 > >>> > >>> Regards, > >>> Ratnesh Upadhyay > >>> HotWax System | www.hotwaxsystems.com > >>> > >>> > >>> On Sat, Aug 26, 2017 at 11:54 AM, Arun Patidar < > >>> arun.pati...@hotwaxsystems.com> wrote: > >>> > >>> Nice catch Ratnesh, we can take this as an improvement. > >>>> > >>>> > >>>> > >>>> -- > >>>> Thanks & Regards > >>>> --- > >>>> Arun Patidar > >>>> Manager, Enterprise Software Development > >>>> > >>>> > >>>> HotWax Systems Pvt Ltd.www.hotwaxsystems.com > >>>> > >>>> > >>>> On Thu, Aug 24, 2017 at 7:50 PM, Ratnesh Upadhyay < > >>>> upadhyay.ratn...@gmail.com> wrote: > >>>> > >>>> Hello Devs, > >>>>> > >>>>> I just walked though from OrderHeader entity and noticed that we have > >>>>> webSiteId field there but we don't have any FK constraint for it from > >>>>> OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it > >>>>> > >>>> must be > >>>> > >>>>> there. > >>>>> > >>>>> So just curious to know why it was not there, was it intentional? > >>>>> Please > >>>>> let me know if anyone have any information on it else I would > provide a > >>>>> patch to get it fixed. > >>>>> > >>>>> Thanks!! > >>>>> > >>>>> Regards, > >>>>> Ratnesh Upadhyay > >>>>> HotWax Systems | www.hotwaxsystems.com > >>>>> > >>>>> > > >
Re: Help Needed to move our new website live
New site looks great. One thing I noticed here is security link in footer section is redirecting to download page ( http://ofbiz.apache.org/download.html). Created Jira issue for this: https://issues.apache.org/jira/browse/OFBIZ-9663 -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Tue, Aug 29, 2017 at 2:59 PM, gil portenseigne < gil.portensei...@nereide.fr> wrote: > Hi Jacopo, > > Yes I did, it seems to be an unsecure content protection see JIRA > OFBIZ-9662 : https://s.apache.org/vwwI > > Gil > > > > On 29/08/2017 10:40, Jacopo Cappellato wrote: > >> Hi Gil, >> >> did you try to refresh the pages? >> >> Jacopo >> >> On Tue, Aug 29, 2017 at 10:12 AM, gil portenseigne < >> gil.portensei...@nereide.fr> wrote: >> >> Congratulations and thanks to everyone who participated in this effort. >>> >>> I just detected some strange behavior on Getting >>> started/New/Documentation/Community links in the header, they are >>> pointing to the current page... >>> >>> Detected on Firefox and Chrome. >>> >>> Regards, >>> >>> Gil >>> >>> >>> >>> On 29/08/2017 09:58, Ashish Vijaywargiya wrote: >>> >>> Now let's make some noise about our brand new site :-) >>>> >>>>> +1 >>>>> >>>> The new Apache OFBiz website is looking super cool. >>>> Thanks everyone who was directly or indirectly involved in this effort. >>>> >>>> -- >>>> Kind Regards >>>> Ashish Vijaywargiya >>>> HotWax Systems - est. 1997 <http://www.hotwaxsystems.com/> >>>> >>>> >>>> On Tue, Aug 29, 2017 at 1:22 PM, Sharan Foga <sharan.f...@gmail.com> >>>> wrote: >>>> >>>> Thanks everyone for getting this live! Now let's make some noise about >>>> our >>>> >>>>> brand new site :-) >>>>> >>>>> Thanks >>>>> Sharan >>>>> >>>>> >>>>> On 29/08/17 09:48, Jacopo Cappellato wrote: >>>>> >>>>> Congratulations, the new site looks great! >>>>> >>>>>> Thank you Sharan, Kenneth and everyone who helped in this effort. >>>>>> >>>>>> Jacopo >>>>>> >>>>>> On Tue, Aug 29, 2017 at 8:51 AM, Deepak Dixit < >>>>>> deepak.di...@hotwaxsystems.com> wrote: >>>>>> >>>>>> Just to update you all, now its working fine >>>>>> >>>>>> Nice work Kenneth and Sharan. I found some enhancement. Will fix one >>>>>>> by >>>>>>> one >>>>>>> when I get a chance. >>>>>>> Thanks Ashish and Sandeep for your help. >>>>>>> >>>>>>> Special Thanks to infra team to fix the issue. >>>>>>> >>>>>>> Thanks & Regards >>>>>>> -- >>>>>>> Deepak Dixit >>>>>>> www.hotwaxsystems.com >>>>>>> www.hotwax.co >>>>>>> >>>>>>> On Tue, Aug 29, 2017 at 11:16 AM, Deepak Dixit < >>>>>>> deepak.di...@hotwaxsystems.com> wrote: >>>>>>> >>>>>>> Yes Pranay, need to debug what we are missing. >>>>>>> >>>>>>> Thanks & Regards >>>>>>>> -- >>>>>>>> Deepak Dixit >>>>>>>> www.hotwaxsystems.com >>>>>>>> www.hotwax.co >>>>>>>> >>>>>>>> On Tue, Aug 29, 2017 at 8:30 AM, Pranay Pandey < >>>>>>>> pranay.pan...@hotwaxsystems.com> wrote: >>>>>>>> >>>>>>>> Hi Deepak, >>>>>>>> >>>>>>>> Great job. Thanks for the effort. >>>>>>>>> I think still some configuration is missing. >>>>>>>>> >>>>>>>>> On 29-Aug-2017 1:20 AM, "Deepak Dixit" < >>>>>>>>> deepak.di...@hotwaxsystems.com >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> This h
Re: OrderHeader And WebSite Relationship
Hi Ratnesh, I have found missing FK constraint in multiple entity definitions (e.g. shoppingListId in OrderItem etc). So I think we need to verify and improve this throughout the application. -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Sat, Aug 26, 2017 at 1:08 PM, Ratnesh Upadhyay < upadhyay.ratn...@gmail.com> wrote: > Thanks everyone for your inputs. > Here is the jira ticket : https://issues.apache.org/jira/browse/OFBIZ-9647 > > Regards, > Ratnesh Upadhyay > HotWax System | www.hotwaxsystems.com > > On Sat, Aug 26, 2017 at 11:54 AM, Arun Patidar < > arun.pati...@hotwaxsystems.com> wrote: > > > Nice catch Ratnesh, we can take this as an improvement. > > > > > > > > -- > > Thanks & Regards > > --- > > Arun Patidar > > Manager, Enterprise Software Development > > > > > > HotWax Systems Pvt Ltd.www.hotwaxsystems.com > > > > > > On Thu, Aug 24, 2017 at 7:50 PM, Ratnesh Upadhyay < > > upadhyay.ratn...@gmail.com> wrote: > > > > > Hello Devs, > > > > > > I just walked though from OrderHeader entity and noticed that we have > > > webSiteId field there but we don't have any FK constraint for it from > > > OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it > must > > be > > > there. > > > > > > So just curious to know why it was not there, was it intentional? > Please > > > let me know if anyone have any information on it else I would provide a > > > patch to get it fixed. > > > > > > Thanks!! > > > > > > Regards, > > > Ratnesh Upadhyay > > > HotWax Systems | www.hotwaxsystems.com > > > > > >
Re: [PROPOSAL] Short Messaging Service(SMS) Gateway Integration
+1 Pritam. On Sat, Aug 26, 2017 at 5:49 PM, Rishi Solanki <rishisolan...@gmail.com> wrote: > +1 Pritam. > > Rishi Solanki > Sr Manager, Enterprise Software Development > HotWax Systems Pvt. Ltd. > Direct: +91-9893287847 > http://www.hotwaxsystems.com > www.hotwax.co > > On Sat, Aug 26, 2017 at 5:48 PM, Swapnil Mane < > swapnil.m...@hotwaxsystems.com> wrote: > > > Big +1 Pritam! > > > > > > - Best Regards, > > Swapnil M Mane > > > > On Sat, Aug 26, 2017 at 5:01 PM, Pritam Kute < > > pritam.k...@hotwaxsystems.com> > > wrote: > > > > > Hi Devs, > > > > > > Many e-commerce businesses (especially operating in Asian countries) > > > nowadays use short messaging service (SMS) in mobile phones to notify > and > > > update customers about order details, shipment statuses etc. > > > > > > I would like to propose an SMS Gateway Integration in Ofbiz. I will > share > > > proposed design details with you all soon. Till then, I would like to > > know > > > your thoughts on this idea. > > > > > > Thanks and Regards > > > -- > > > Pritam Kute > > > > > > -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/
Re: New ASF Members from OFBiz Community
Many Congratulations to all...! -- Thanks & Regards, Chandan Khandelwal HotWax Systems Direct: +91-9893481076 http://www.hotwaxsystems.com/ On Wed, Apr 5, 2017 at 5:53 PM, Rohit Rai <rohit@hotwaxsystems.com> wrote: > Many congratulations to Michael Brohl, Taher Alkhateeb, Anil Patel, Ashish > Vijaywargiya and Bilgin Ibryam !!! > > Best Regards, > Rohit Rai > Enterprise Software Engineer > Hotwax Systems Pvt Ltd > > On Wed, Apr 5, 2017 at 5:04 PM, Rehan <rehan.k...@hotwaxsystems.com> > wrote: > > > Congratulations to everyone !!! > > > > > > Thanks & Regards, > > Rehan Khan > > Sr. Enterprise Software Engineer > > HotWax Systems > > > > On Wednesday 05 April 2017 12:32 AM, Sharan Foga wrote: > > > >> Hi Everyone > >> > >> Wow – we have even more good news! Another three people from our > >> community have been invited to become members of the Apache Software > >> Foundation. They are Anil Patel, Ashish Vijaywargiya and Bilgin Ibryam > >> > >> Many congratulations Anil, Ashish and Bilgin !!! > >> > >> Thanks > >> Sharan > >> > >> On 2017-04-03 11:06 (+0200), "Sharan Foga"<sha...@apache.org> wrote: > >> > >>> Hi Everyone > >>> > >>> Please join me in congratulating Michael Brohl and Taher Alkhateeb as > >>> being invited to become members of the Apache Software Foundation. > >>> > >>> Congratulations Michael and Taher! > >>> > >>> Thanks > >>> Sharan > >>> > >>> > >>> > > >
Re: Welcome Swapnil Shah as a New Committer!
Many congratulations Swapnil...! -- Chandan Khandelwal On Wed, Feb 15, 2017 at 11:59 AM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > Many Congrats Swapnil... > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > > On Wed, Feb 15, 2017 at 10:41 AM, Akash Jain <akash.j...@hotwaxsystems.com > > > wrote: > > > Many congratulations Swapnil! > > > > Thanks and Regards > > -- > > Akash Jain > > > > On Tue, Feb 14, 2017 at 4:30 PM, Sharan Foga <sha...@apache.org> wrote: > > > > > The OFBiz PMC has invited Swapnil Shah to become a new committer and > are > > > happy to announce that he has accepted. > > > > > > Swapnil has been involved in OFBiz for a few years and has been active > on > > > both the development and user mailing lists responding to some quite > > > technical functional questions. > > > > > > Some of the key factors considered for inviting him were as follows: > > > > > > - He has very good functional knowledge about OFBiz and this is a > > valuable > > > skill that is useful to developers and users > > > - He is polite, positive, friendly and collaborative when dealing the > > > community discussions on the mailings lists or Jira > > > - He has raised Jiras, performed testing on patches and new other > > > functionality > > > - The PMC would like to see a wide range of people from the community > > > (developers and non-developers) recognised for their contributions to > the > > > project. > > > > > > Please join me in welcoming and congratulating Swapnil. > > > > > > Thanks > > > Sharan > > > > > >
[jira] [Commented] (OFBIZ-7875) Broken screen on adding billing account through any account
[ https://issues.apache.org/jira/browse/OFBIZ-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385581#comment-15385581 ] Chandan Khandelwal commented on OFBIZ-7875: --- Thanks Montalbano Florian for notifying, Updated the status to duplicate. > Broken screen on adding billing account through any account > > > Key: OFBIZ-7875 > URL: https://issues.apache.org/jira/browse/OFBIZ-7875 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Deepak Baghel >Assignee: Deepak Baghel > Attachments: AddingBillingAccountError.png > > > Step to regenerate this issue : > 1. Login to the SFA component. > 2. Go to the account section. > 3. Select any one of account and go to its overview page. > 4. Try to add new billing account from payment method information panel. > 5. Broken screen occurred. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-7875) Broken screen on adding billing account through any account
[ https://issues.apache.org/jira/browse/OFBIZ-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal resolved OFBIZ-7875. --- Resolution: Duplicate > Broken screen on adding billing account through any account > > > Key: OFBIZ-7875 > URL: https://issues.apache.org/jira/browse/OFBIZ-7875 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Deepak Baghel >Assignee: Deepak Baghel > Attachments: AddingBillingAccountError.png > > > Step to regenerate this issue : > 1. Login to the SFA component. > 2. Go to the account section. > 3. Select any one of account and go to its overview page. > 4. Try to add new billing account from payment method information panel. > 5. Broken screen occurred. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7858) Add paginate target on 'BillingAccountForms', 'CostForms' and 'AP/AR-InvoiceForms'
[ https://issues.apache.org/jira/browse/OFBIZ-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7858: -- Attachment: OFBIZ-7858.patch > Add paginate target on 'BillingAccountForms', 'CostForms' and > 'AP/AR-InvoiceForms' > --- > > Key: OFBIZ-7858 > URL: https://issues.apache.org/jira/browse/OFBIZ-7858 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey > Attachments: OFBIZ-7858.patch, OFBIZ-7858.patch > > > BillingAccountsForms.xml > # ListBillingAccountRoles > Steps : > # Create Billing Account > # Go To Billing Account Role Section > # Paginate target need to be added on result sections > Reference URL : > https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 > CostForms.xml > # ListCostComponentCalc > Steps : > # Go to accounting > globalGLSettings > # Go to Costs > # Paginate target need to be added on result sections > Reference URL : https://localhost:8443/accounting/control/EditCostCalcs > AR - InvoiceForms.xml > https://localhost:8443/ar/control/main > AP - InvoiceForms.xml > https://localhost:8443/ar/control/main -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7858) Add paginate target on 'BillingAccountForms', 'CostForms' and 'AP/AR-InvoiceForms'
[ https://issues.apache.org/jira/browse/OFBIZ-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7858: -- Description: BillingAccountsForms.xml # ListBillingAccountRoles Steps : # Create Billing Account # Go To Billing Account Role Section # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 CostForms.xml # ListCostComponentCalc Steps : # Go to accounting > globalGLSettings # Go to Costs # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditCostCalcs AR - InvoiceForms.xml https://localhost:8443/ar/control/main AP - InvoiceForms.xml https://localhost:8443/ar/control/main was: BillingAccountsForms.xml # ListBillingAccountRoles Steps : # Create Billing Account # Go To Billing Account Role Section # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 CostForms.xml # ListCostComponentCalc Steps : # Go to accounting > globalGLSettings # Go to Costs # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditCostCalcs > Add paginate target on 'BillingAccountForms', 'CostForms' and > 'AP/AR-InvoiceForms' > --- > > Key: OFBIZ-7858 > URL: https://issues.apache.org/jira/browse/OFBIZ-7858 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey > Attachments: OFBIZ-7858.patch > > > BillingAccountsForms.xml > # ListBillingAccountRoles > Steps : > # Create Billing Account > # Go To Billing Account Role Section > # Paginate target need to be added on result sections > Reference URL : > https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 > CostForms.xml > # ListCostComponentCalc > Steps : > # Go to accounting > globalGLSettings > # Go to Costs > # Paginate target need to be added on result sections > Reference URL : https://localhost:8443/accounting/control/EditCostCalcs > AR - InvoiceForms.xml > https://localhost:8443/ar/control/main > AP - InvoiceForms.xml > https://localhost:8443/ar/control/main -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7858) Add paginate target on 'BillingAccountForms', 'CostForms' and 'AP/AR-InvoiceForms'
[ https://issues.apache.org/jira/browse/OFBIZ-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7858: -- Summary: Add paginate target on 'BillingAccountForms', 'CostForms' and 'AP/AR-InvoiceForms' (was: Add paginate target on 'BillingAccountForms' and 'CostForms' ) > Add paginate target on 'BillingAccountForms', 'CostForms' and > 'AP/AR-InvoiceForms' > --- > > Key: OFBIZ-7858 > URL: https://issues.apache.org/jira/browse/OFBIZ-7858 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey > Attachments: OFBIZ-7858.patch > > > BillingAccountsForms.xml > # ListBillingAccountRoles > Steps : > # Create Billing Account > # Go To Billing Account Role Section > # Paginate target need to be added on result sections > Reference URL : > https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 > CostForms.xml > # ListCostComponentCalc > Steps : > # Go to accounting > globalGLSettings > # Go to Costs > # Paginate target need to be added on result sections > Reference URL : https://localhost:8443/accounting/control/EditCostCalcs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7858) Add paginate target on 'BillingAccountForms' and 'CostForms'
[ https://issues.apache.org/jira/browse/OFBIZ-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7858: -- Attachment: OFBIZ-7858.patch > Add paginate target on 'BillingAccountForms' and 'CostForms' > - > > Key: OFBIZ-7858 > URL: https://issues.apache.org/jira/browse/OFBIZ-7858 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Attachments: OFBIZ-7858.patch > > > BillingAccountsForms.xml > # ListBillingAccountRoles > Steps : > # Create Billing Account > # Go To Billing Account Role Section > # Paginate target need to be added on result sections > Reference URL : > https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 > CostForms.xml > # ListCostComponentCalc > Steps : > # Go to accounting > globalGLSettings > # Go to Costs > # Paginate target need to be added on result sections > Reference URL : https://localhost:8443/accounting/control/EditCostCalcs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7858) Add paginate target on 'BillingAccountForms' and 'CostForms'
[ https://issues.apache.org/jira/browse/OFBIZ-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7858: -- Description: BillingAccountsForms.xml # ListBillingAccountRoles Steps : # Create Billing Account # Go To Billing Account Role Section # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 CostForms.xml # ListCostComponentCalc Steps : # Go to accounting > globalGLSettings # Go to Costs # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditCostCalcs was: BillingAccountsForms.xml # ListBillingAccountRoles Steps : # Create Billing Account # Go To Billing Account Role Section # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 CostForms.xml # ListCostComponentCalc Steps : # Go to accounting > globalGLSettings # Go to Costs # Paginate target need to be added on result sections Referece URL : https://localhost:8443/accounting/control/EditCostCalcs > Add paginate target on 'BillingAccountForms' and 'CostForms' > - > > Key: OFBIZ-7858 > URL: https://issues.apache.org/jira/browse/OFBIZ-7858 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Chandan Khandelwal > Attachments: OFBIZ-7858.patch > > > BillingAccountsForms.xml > # ListBillingAccountRoles > Steps : > # Create Billing Account > # Go To Billing Account Role Section > # Paginate target need to be added on result sections > Reference URL : > https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 > CostForms.xml > # ListCostComponentCalc > Steps : > # Go to accounting > globalGLSettings > # Go to Costs > # Paginate target need to be added on result sections > Reference URL : https://localhost:8443/accounting/control/EditCostCalcs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7858) Add paginate target on 'BillingAccountForms' and 'CostForms'
Chandan Khandelwal created OFBIZ-7858: - Summary: Add paginate target on 'BillingAccountForms' and 'CostForms' Key: OFBIZ-7858 URL: https://issues.apache.org/jira/browse/OFBIZ-7858 Project: OFBiz Issue Type: Sub-task Components: accounting Affects Versions: Trunk Reporter: Chandan Khandelwal BillingAccountsForms.xml # ListBillingAccountRoles Steps : # Create Billing Account # Go To Billing Account Role Section # Paginate target need to be added on result sections Reference URL : https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=10021 CostForms.xml # ListCostComponentCalc Steps : # Go to accounting > globalGLSettings # Go to Costs # Paginate target need to be added on result sections Referece URL : https://localhost:8443/accounting/control/EditCostCalcs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Attachment: OFBIZ-7707.patch > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: Improved_PaymentMethodInformation_UI.png, > OFBIZ-7707.patch, OFBIZ-7707.patch, OFBIZ-7707.patch, screenshot-1.png > > > Improve payment method information UI on party profile screen for options of > creating new payment method. > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367598#comment-15367598 ] Chandan Khandelwal commented on OFBIZ-7707: --- Thanks Pranay for your feedback, will update the patch. > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: Improved_PaymentMethodInformation_UI.png, > OFBIZ-7707.patch, OFBIZ-7707.patch, OFBIZ-7707.patch, screenshot-1.png > > > Improve payment method information UI on party profile screen for options of > creating new payment method. > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367580#comment-15367580 ] Chandan Khandelwal commented on OFBIZ-7711: --- We can add EFT account from my profile and yes, it is similar as in accounting and profile. > Label not showing properly on 'Add EFT Account' screen of scrum > --- > > Key: OFBIZ-7711 > URL: https://issues.apache.org/jira/browse/OFBIZ-7711 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/scrum >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-7711.patch > > > Accounting Uilabel resource not added in scrum main decorator. > URL : > https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367580#comment-15367580 ] Chandan Khandelwal edited comment on OFBIZ-7711 at 7/8/16 12:00 PM: We can add EFT account from my profile and yes, it is similar as in accounting and party. was (Author: chandan.khandelwal): We can add EFT account from my profile and yes, it is similar as in accounting and profile. > Label not showing properly on 'Add EFT Account' screen of scrum > --- > > Key: OFBIZ-7711 > URL: https://issues.apache.org/jira/browse/OFBIZ-7711 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/scrum >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-7711.patch > > > Accounting Uilabel resource not added in scrum main decorator. > URL : > https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7752) 'parentCommEventId' is not passed in parameter from edit communication event
[ https://issues.apache.org/jira/browse/OFBIZ-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7752: -- Affects Version/s: Release Branch 13.07 Release Branch 14.12 Release Branch 15.12 > 'parentCommEventId' is not passed in parameter from edit communication event > > > Key: OFBIZ-7752 > URL: https://issues.apache.org/jira/browse/OFBIZ-7752 > Project: OFBiz > Issue Type: Bug > Components: marketing, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey > Attachments: OFBIZ-7752.patch > > > Steps : > # Create 'New Communication Event' with parentCommEventId > # Go To 'Edit Communication Event' > # Click on 'Go To Parent' button > No communicationEventId (parentCommEventId) passed with link. > Ref URL : https://localhost:8443/sfa/control/EditCommunicationEvent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7752) 'parentCommEventId' is not passed in parameter from edit communication event
[ https://issues.apache.org/jira/browse/OFBIZ-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7752: -- Attachment: OFBIZ-7752.patch > 'parentCommEventId' is not passed in parameter from edit communication event > > > Key: OFBIZ-7752 > URL: https://issues.apache.org/jira/browse/OFBIZ-7752 > Project: OFBiz > Issue Type: Bug > Components: marketing, party >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Attachments: OFBIZ-7752.patch > > > Steps : > # Create 'New Communication Event' with parentCommEventId > # Go To 'Edit Communication Event' > # Click on 'Go To Parent' button > No communicationEventId (parentCommEventId) passed with link. > Ref URL : https://localhost:8443/sfa/control/EditCommunicationEvent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7752) 'parentCommEventId' is not passed in parameter from edit communication event
[ https://issues.apache.org/jira/browse/OFBIZ-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7752: -- Affects Version/s: Trunk > 'parentCommEventId' is not passed in parameter from edit communication event > > > Key: OFBIZ-7752 > URL: https://issues.apache.org/jira/browse/OFBIZ-7752 > Project: OFBiz > Issue Type: Bug > Components: marketing, party >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Attachments: OFBIZ-7752.patch > > > Steps : > # Create 'New Communication Event' with parentCommEventId > # Go To 'Edit Communication Event' > # Click on 'Go To Parent' button > No communicationEventId (parentCommEventId) passed with link. > Ref URL : https://localhost:8443/sfa/control/EditCommunicationEvent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7752) 'parentCommEventId' is not passed in parameter from edit communication event
Chandan Khandelwal created OFBIZ-7752: - Summary: 'parentCommEventId' is not passed in parameter from edit communication event Key: OFBIZ-7752 URL: https://issues.apache.org/jira/browse/OFBIZ-7752 Project: OFBiz Issue Type: Bug Components: marketing, party Reporter: Chandan Khandelwal Attachments: OFBIZ-7752.patch Steps : # Create 'New Communication Event' with parentCommEventId # Go To 'Edit Communication Event' # Click on 'Go To Parent' button No communicationEventId (parentCommEventId) passed with link. Ref URL : https://localhost:8443/sfa/control/EditCommunicationEvent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7706) Error in Create Billing Account From SFA
[ https://issues.apache.org/jira/browse/OFBIZ-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7706: -- Attachment: OFBIZ-7706.patch > Error in Create Billing Account From SFA > > > Key: OFBIZ-7706 > URL: https://issues.apache.org/jira/browse/OFBIZ-7706 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Attachments: OFBIZ-7706.patch > > > # Go to profile page > (https://localhost:8443/sfa/control/viewprofile?roleTypeId=ACCOUNT=Company) > # Create new billing address > Error in Create Billing Account From SFA > URL : https://localhost:8443/sfa/control/EditBillingAccount?partyId=Company -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Attachment: OFBIZ-7707.patch > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: Improved_PaymentMethodInformation_UI.png, > OFBIZ-7707.patch, OFBIZ-7707.patch, screenshot-1.png > > > Improve payment method information UI on party profile screen for options of > creating new payment method. > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361140#comment-15361140 ] Chandan Khandelwal commented on OFBIZ-7707: --- Make sense to me,I will update the patch. > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: Improved_PaymentMethodInformation_UI.png, > OFBIZ-7707.patch, screenshot-1.png > > > Improve payment method information UI on party profile screen for options of > creating new payment method. > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Attachment: OFBIZ-7707.patch Improved_PaymentMethodInformation_UI.png > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: Improved_PaymentMethodInformation_UI.png, > OFBIZ-7707.patch, screenshot-1.png > > > Improve payment method information UI on party profile screen for options of > creating new payment method. > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7711: -- Attachment: OFBIZ-7711.patch > Label not showing properly on 'Add EFT Account' screen of scrum > --- > > Key: OFBIZ-7711 > URL: https://issues.apache.org/jira/browse/OFBIZ-7711 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/scrum >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7711.patch > > > Accounting Uilabel resource not added in scrum main decorator. > URL : > https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7711: -- Attachment: (was: OFBIZ-7707.patch) > Label not showing properly on 'Add EFT Account' screen of scrum > --- > > Key: OFBIZ-7711 > URL: https://issues.apache.org/jira/browse/OFBIZ-7711 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/scrum >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Trivial > > Accounting Uilabel resource not added in scrum main decorator. > URL : > https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7706) Error in Create Billing Account From SFA
[ https://issues.apache.org/jira/browse/OFBIZ-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7706: -- Description: # Go to profile page (https://localhost:8443/sfa/control/viewprofile?roleTypeId=ACCOUNT=Company) # Create new billing address Error in Create Billing Account From SFA URL : https://localhost:8443/sfa/control/EditBillingAccount?partyId=Company was: # Go to profile page https://localhost:8443/sfa/control/viewprofile?roleTypeId=ACCOUNT=Company # Create new billing address Error in Create Billing Account From SFA URL : https://localhost:8443/sfa/control/EditBillingAccount?partyId=Company > Error in Create Billing Account From SFA > > > Key: OFBIZ-7706 > URL: https://issues.apache.org/jira/browse/OFBIZ-7706 > Project: OFBiz > Issue Type: Bug > Components: marketing > Reporter: Chandan Khandelwal > > # Go to profile page > (https://localhost:8443/sfa/control/viewprofile?roleTypeId=ACCOUNT=Company) > # Create new billing address > Error in Create Billing Account From SFA > URL : https://localhost:8443/sfa/control/EditBillingAccount?partyId=Company -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7711: -- Attachment: OFBIZ-7707.patch > Label not showing properly on 'Add EFT Account' screen of scrum > --- > > Key: OFBIZ-7711 > URL: https://issues.apache.org/jira/browse/OFBIZ-7711 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/scrum >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7707.patch > > > Accounting Uilabel resource not added in scrum main decorator. > URL : > https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Attachment: (was: OFBIZ-7707.patch) > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal >Priority: Trivial > Attachments: screenshot-1.png > > > Improve payment method information UI on party profile screen > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Attachment: OFBIZ-7707.patch > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7707.patch, screenshot-1.png > > > Improve payment method information UI on party profile screen > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
Chandan Khandelwal created OFBIZ-7711: - Summary: Label not showing properly on 'Add EFT Account' screen of scrum Key: OFBIZ-7711 URL: https://issues.apache.org/jira/browse/OFBIZ-7711 Project: OFBiz Issue Type: Improvement Components: specialpurpose/scrum Affects Versions: Trunk Reporter: Chandan Khandelwal Priority: Trivial Accounting Uilabel resource not added in scrum main decorator. URL : https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Attachment: screenshot-1.png > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Trivial > Attachments: screenshot-1.png > > > Improve payment method information UI on party profile screen > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7707) Improve payment method information UI on party profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7707: -- Assignee: Chandan Khandelwal > Improve payment method information UI on party profile screen > - > > Key: OFBIZ-7707 > URL: https://issues.apache.org/jira/browse/OFBIZ-7707 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal >Priority: Trivial > Attachments: screenshot-1.png > > > Improve payment method information UI on party profile screen > https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7707) Improve payment method information UI on party profile screen
Chandan Khandelwal created OFBIZ-7707: - Summary: Improve payment method information UI on party profile screen Key: OFBIZ-7707 URL: https://issues.apache.org/jira/browse/OFBIZ-7707 Project: OFBiz Issue Type: Improvement Components: party Affects Versions: Trunk Reporter: Chandan Khandelwal Priority: Trivial Improve payment method information UI on party profile screen https://localhost:8443/partymgr/control/viewprofile?partyId=admin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7706) Error in Create Billing Account From SFA
Chandan Khandelwal created OFBIZ-7706: - Summary: Error in Create Billing Account From SFA Key: OFBIZ-7706 URL: https://issues.apache.org/jira/browse/OFBIZ-7706 Project: OFBiz Issue Type: Bug Components: marketing Reporter: Chandan Khandelwal # Go to profile page https://localhost:8443/sfa/control/viewprofile?roleTypeId=ACCOUNT=Company # Create new billing address Error in Create Billing Account From SFA URL : https://localhost:8443/sfa/control/EditBillingAccount?partyId=Company -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7647) Remove UI label dependencies between accounting and HR
[ https://issues.apache.org/jira/browse/OFBIZ-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7647: -- Attachment: OFBIZ-7647.patch > Remove UI label dependencies between accounting and HR > -- > > Key: OFBIZ-7647 > URL: https://issues.apache.org/jira/browse/OFBIZ-7647 > Project: OFBiz > Issue Type: Sub-task > Components: accounting, humanres > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7647.patch, OFBIZ-7647.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7647) Remove UI label dependencies between accounting and HR
[ https://issues.apache.org/jira/browse/OFBIZ-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352403#comment-15352403 ] Chandan Khandelwal commented on OFBIZ-7647: --- Reference Link : http://markmail.org/message/qus7otusx6yiqxzt > Remove UI label dependencies between accounting and HR > -- > > Key: OFBIZ-7647 > URL: https://issues.apache.org/jira/browse/OFBIZ-7647 > Project: OFBiz > Issue Type: Sub-task > Components: accounting, humanres > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7647.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7647) Remove UI label dependencies between accounting and HR
[ https://issues.apache.org/jira/browse/OFBIZ-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7647: -- Attachment: OFBIZ-7647.patch Added patch to remove dependencies of UI label, this is first attempt to remove dependencies between accounting and HR. I request community to review the patch and share feedback on this. > Remove UI label dependencies between accounting and HR > -- > > Key: OFBIZ-7647 > URL: https://issues.apache.org/jira/browse/OFBIZ-7647 > Project: OFBiz > Issue Type: Sub-task > Components: accounting, humanres > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7647.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7647) Remove UI label dependencies between accounting and HR
Chandan Khandelwal created OFBIZ-7647: - Summary: Remove UI label dependencies between accounting and HR Key: OFBIZ-7647 URL: https://issues.apache.org/jira/browse/OFBIZ-7647 Project: OFBiz Issue Type: Sub-task Components: accounting, humanres Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7208) Refactor XML shared dependencies between accounting and HR
[ https://issues.apache.org/jira/browse/OFBIZ-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7208: -- Description: Many shared dependencies exist bi-directionally between accounting and HR including screens, entities and other items. All such XML should propagate down to the commonext component. List of dependencies of HR on Accounting : # UI Label # Lookup # Screens # Requests # Forms was: Many shared dependencies exist bi-directionally between accounting and HR including screens, entities and other items. All such XML should propagate down to the commonext component. List of > Refactor XML shared dependencies between accounting and HR > -- > > Key: OFBIZ-7208 > URL: https://issues.apache.org/jira/browse/OFBIZ-7208 > Project: OFBiz > Issue Type: Improvement > Components: accounting, commonext/setup, humanres >Reporter: Pranay Pandey >Assignee: Pranay Pandey > > Many shared dependencies exist bi-directionally between accounting and HR > including screens, entities and other items. All such XML should propagate > down to the commonext component. > List of dependencies of HR on Accounting : > # UI Label > # Lookup > # Screens > # Requests > # Forms -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7208) Refactor XML shared dependencies between accounting and HR
[ https://issues.apache.org/jira/browse/OFBIZ-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7208: -- Description: Many shared dependencies exist bi-directionally between accounting and HR including screens, entities and other items. All such XML should propagate down to the commonext component. List of was:Many shared dependencies exist bi-directionally between accounting and HR including screens, entities and other items. All such XML should propagate down to the commonext component. > Refactor XML shared dependencies between accounting and HR > -- > > Key: OFBIZ-7208 > URL: https://issues.apache.org/jira/browse/OFBIZ-7208 > Project: OFBiz > Issue Type: Improvement > Components: accounting, commonext/setup, humanres >Reporter: Pranay Pandey >Assignee: Pranay Pandey > > Many shared dependencies exist bi-directionally between accounting and HR > including screens, entities and other items. All such XML should propagate > down to the commonext component. > List of -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7586) Error in Create Billing Account From HR
[ https://issues.apache.org/jira/browse/OFBIZ-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347735#comment-15347735 ] Chandan Khandelwal commented on OFBIZ-7586: --- Thanks Pranay for the feedback, makes sense to me. I am looking on other dependencies which we need to figure out and list the same on OFBIZ-7208. > Error in Create Billing Account From HR > --- > > Key: OFBIZ-7586 > URL: https://issues.apache.org/jira/browse/OFBIZ-7586 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey > > # Go To HR > # Select Comapny > # Create Billing Account > # Save > URL : > https://ofbiz-vm.apache.org:8443/humanres/control/EditBillingAccount?partyId=MARKETING > getting error "org.ofbiz.webapp.control.RequestHandlerException: Unknown > request [createBillingAccountAndRole]; this request does not exist or cannot > be called directly." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7586) Error in Create Billing Account From HR
Chandan Khandelwal created OFBIZ-7586: - Summary: Error in Create Billing Account From HR Key: OFBIZ-7586 URL: https://issues.apache.org/jira/browse/OFBIZ-7586 Project: OFBiz Issue Type: Bug Components: humanres Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12, Release Branch 13.07 Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal # Go To HR # Select Comapny # Create Billing Account # Save URL : https://ofbiz-vm.apache.org:8443/humanres/control/EditBillingAccount?partyId=MARKETING getting error "org.ofbiz.webapp.control.RequestHandlerException: Unknown request [createBillingAccountAndRole]; this request does not exist or cannot be called directly." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7523) Error in deleting AddressMatchMap for party
[ https://issues.apache.org/jira/browse/OFBIZ-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7523: -- Attachment: OFBIZ-7523.patch OFBIZ-7523_1412 .patch OFBIZ-7523_1512.patch OFBIZ-7523_1307.patch > Error in deleting AddressMatchMap for party > --- > > Key: OFBIZ-7523 > URL: https://issues.apache.org/jira/browse/OFBIZ-7523 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 > Reporter: Chandan Khandelwal >Assignee: Chandan Khandelwal > Attachments: OFBIZ-7523.patch, OFBIZ-7523_1307.patch, OFBIZ-7523_1412 > .patch, OFBIZ-7523_1512.patch > > > Go To Party -> AddressMatchMap > # Create New AddressMatchMap (or use an existing AddressMatchMap) > # Delete AddressMatchMap > # Try to delete the AddressMatchMap > URL : https://ofbiz-vm.apache.org:8443/partymgr/control/addressMatchMap > Here is the error message displayed in the screen: > The Following Errors Occurred: > Error calling event: org.ofbiz.webapp.event.EventHandlerException: Found URL > parameter [mapKey] passed to secure (https) request-map with uri > [removeAddressMatchMap] with an event that calls service > [removeAddressMatchMap]; this is not allowed for security reasons! The data > should be encrypted by making it part of the request body (a form field) > instead of the request URL. Moreover it would be kind if you could create a > Jira sub-task of https://issues.apache.org/jira/browse/OFBIZ-2330 (check > before if a sub-task for this error does not exist). If you are not sure how > to create a Jira issue please have a look before at > http://cwiki.apache.org/confluence/x/JIB2 Thank you in advance for your help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7523) Error in deleting AddressMatchMap for party
Chandan Khandelwal created OFBIZ-7523: - Summary: Error in deleting AddressMatchMap for party Key: OFBIZ-7523 URL: https://issues.apache.org/jira/browse/OFBIZ-7523 Project: OFBiz Issue Type: Sub-task Components: party Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12, Release Branch 13.07 Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal Go To Party -> AddressMatchMap # Create New AddressMatchMap (or use an existing AddressMatchMap) # Delete AddressMatchMap # Try to delete the AddressMatchMap URL : https://ofbiz-vm.apache.org:8443/partymgr/control/addressMatchMap Here is the error message displayed in the screen: The Following Errors Occurred: Error calling event: org.ofbiz.webapp.event.EventHandlerException: Found URL parameter [mapKey] passed to secure (https) request-map with uri [removeAddressMatchMap] with an event that calls service [removeAddressMatchMap]; this is not allowed for security reasons! The data should be encrypted by making it part of the request body (a form field) instead of the request URL. Moreover it would be kind if you could create a Jira sub-task of https://issues.apache.org/jira/browse/OFBIZ-2330 (check before if a sub-task for this error does not exist). If you are not sure how to create a Jira issue please have a look before at http://cwiki.apache.org/confluence/x/JIB2 Thank you in advance for your help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337797#comment-15337797 ] Chandan Khandelwal commented on OFBIZ-7404: --- Thanks Pierre for the reference. > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey > Attachments: OFBIZ-7404.patch, screenshot-1.png, screenshot-2.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7404: -- Attachment: OFBIZ-7404.patch > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7404.patch, screenshot-1.png, screenshot-2.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7404: -- Comment: was deleted (was: Hi Pierre, I did not understand the link you provided, can you please share more details.) > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: screenshot-1.png, screenshot-2.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337700#comment-15337700 ] Chandan Khandelwal commented on OFBIZ-7404: --- Hi Pierre, I did not understand the link you provided, can you please share more details. > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: screenshot-1.png, screenshot-2.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337701#comment-15337701 ] Chandan Khandelwal commented on OFBIZ-7404: --- Hi Pierre, I did not understand the link you provided, can you please share more details. > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: screenshot-1.png, screenshot-2.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7404: -- Attachment: screenshot-2.png > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: screenshot-1.png, screenshot-2.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
[ https://issues.apache.org/jira/browse/OFBIZ-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7404: -- Attachment: screenshot-1.png > Sales Quote can be created for canceled cust request item > - > > Key: OFBIZ-7404 > URL: https://issues.apache.org/jira/browse/OFBIZ-7404 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: screenshot-1.png > > > # Go to Order > # Create New Request > # Add Two Request Items > # Cancel One Request Item > # Create Quote from request > # View Quote > Quote Item should not be created for the request items which have cancelled > status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7404) Sales Quote can be created for canceled cust request item
Chandan Khandelwal created OFBIZ-7404: - Summary: Sales Quote can be created for canceled cust request item Key: OFBIZ-7404 URL: https://issues.apache.org/jira/browse/OFBIZ-7404 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal # Go to Order # Create New Request # Add Two Request Items # Cancel One Request Item # Create Quote from request # View Quote Quote Item should not be created for the request items which have cancelled status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7384) Remove status field from RequestRoles section on request overview page.
[ https://issues.apache.org/jira/browse/OFBIZ-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7384: -- Assignee: Chandan Khandelwal > Remove status field from RequestRoles section on request overview page. > --- > > Key: OFBIZ-7384 > URL: https://issues.apache.org/jira/browse/OFBIZ-7384 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7384.patch, screenshot-1.png > > > # Go to Order > # Create New Request > # Assign Request Roles > # Go to Request Overview Page (for reference : > https://localhost:8443/ordermgr/control/ViewRequest?custRequestId=9000) > Status ID field should be removed from Request Roles section as there is no > status associated with RequestRoles (CustRequestParty), and Status of Request > and RequestItem is already available in respective sections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7384) Remove status field from RequestRoles section on request overview page.
[ https://issues.apache.org/jira/browse/OFBIZ-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7384: -- Attachment: OFBIZ-7384.patch > Remove status field from RequestRoles section on request overview page. > --- > > Key: OFBIZ-7384 > URL: https://issues.apache.org/jira/browse/OFBIZ-7384 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7384.patch, screenshot-1.png > > > # Go to Order > # Create New Request > # Assign Request Roles > # Go to Request Overview Page (for reference : > https://localhost:8443/ordermgr/control/ViewRequest?custRequestId=9000) > Status ID field should be removed from Request Roles section as there is no > status associated with RequestRoles (CustRequestParty), and Status of Request > and RequestItem is already available in respective sections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7384) Remove status field from RequestRoles section on request overview page.
[ https://issues.apache.org/jira/browse/OFBIZ-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7384: -- Attachment: screenshot-1.png > Remove status field from RequestRoles section on request overview page. > --- > > Key: OFBIZ-7384 > URL: https://issues.apache.org/jira/browse/OFBIZ-7384 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Trivial > Attachments: screenshot-1.png > > > # Go to Order > # Create New Request > # Assign Request Roles > # Go to Request Overview Page (for reference : > https://localhost:8443/ordermgr/control/ViewRequest?custRequestId=9000) > Status ID field should be removed from Request Roles section as there is no > status associated with RequestRoles (CustRequestParty), and Status of Request > and RequestItem is already available in respective sections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7384) Remove status field from RequestRoles section on request overview page.
Chandan Khandelwal created OFBIZ-7384: - Summary: Remove status field from RequestRoles section on request overview page. Key: OFBIZ-7384 URL: https://issues.apache.org/jira/browse/OFBIZ-7384 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Chandan Khandelwal Priority: Trivial # Go to Order # Create New Request # Assign Request Roles # Go to Request Overview Page (for reference : https://localhost:8443/ordermgr/control/ViewRequest?custRequestId=9000) Status ID field should be removed from Request Roles section as there is no status associated with RequestRoles (CustRequestParty), and Status of Request and RequestItem is already available in respective sections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7381) Fix 'requestitems' target from order menu.
[ https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7381: -- Attachment: OFBIZ-7381.patch > Fix 'requestitems' target from order menu. > --- > > Key: OFBIZ-7381 > URL: https://issues.apache.org/jira/browse/OFBIZ-7381 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-7381.patch > > > Go To Order > Request > ViewRequest > RequestItems > Need to fix incorrect target for requestitems , It is showing multiple '/' in > URL > URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 > Code Snippet (OrderMenus.xml) : > > from-field="custRequest.custRequestId"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7381) Fix 'requestitems' target from order menu.
[ https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7381: -- Attachment: (was: OFBIZ-7381.patch) > Fix 'requestitems' target from order menu. > --- > > Key: OFBIZ-7381 > URL: https://issues.apache.org/jira/browse/OFBIZ-7381 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > > Go To Order > Request > ViewRequest > RequestItems > Need to fix incorrect target for requestitems , It is showing multiple '/' in > URL > URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 > Code Snippet (OrderMenus.xml) : > > from-field="custRequest.custRequestId"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7381) Fix 'requestitems' target from order menu.
[ https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7381: -- Component/s: order > Fix 'requestitems' target from order menu. > --- > > Key: OFBIZ-7381 > URL: https://issues.apache.org/jira/browse/OFBIZ-7381 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-7381.patch > > > Go To Order > Request > ViewRequest > RequestItems > Need to fix incorrect target for requestitems , It is showing multiple '/' in > URL > URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 > Code Snippet (OrderMenus.xml) : > > from-field="custRequest.custRequestId"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7381) Fix 'requestitems' target from order menu.
[ https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7381: -- Affects Version/s: Trunk > Fix 'requestitems' target from order menu. > --- > > Key: OFBIZ-7381 > URL: https://issues.apache.org/jira/browse/OFBIZ-7381 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-7381.patch > > > Go To Order > Request > ViewRequest > RequestItems > Need to fix incorrect target for requestitems , It is showing multiple (/) in > URL > URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 > Code Snippet (OrderMenus.xml) : > > from-field="custRequest.custRequestId"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7381) Fix 'requestitems' target from order menu.
[ https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7381: -- Description: Go To Order > Request > ViewRequest > RequestItems Need to fix incorrect target for requestitems , It is showing multiple '/' in URL URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 Code Snippet (OrderMenus.xml) : was: Go To Order > Request > ViewRequest > RequestItems Need to fix incorrect target for requestitems , It is showing multiple (/) in URL URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 Code Snippet (OrderMenus.xml) : > Fix 'requestitems' target from order menu. > --- > > Key: OFBIZ-7381 > URL: https://issues.apache.org/jira/browse/OFBIZ-7381 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-7381.patch > > > Go To Order > Request > ViewRequest > RequestItems > Need to fix incorrect target for requestitems , It is showing multiple '/' in > URL > URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 > Code Snippet (OrderMenus.xml) : > > from-field="custRequest.custRequestId"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7381) Fix 'requestitems' target from order menu.
[ https://issues.apache.org/jira/browse/OFBIZ-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7381: -- Attachment: OFBIZ-7381.patch > Fix 'requestitems' target from order menu. > --- > > Key: OFBIZ-7381 > URL: https://issues.apache.org/jira/browse/OFBIZ-7381 > Project: OFBiz > Issue Type: Improvement > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7381.patch > > > Go To Order > Request > ViewRequest > RequestItems > Need to fix incorrect target for requestitems , It is showing multiple (/) in > URL > URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 > Code Snippet (OrderMenus.xml) : > > from-field="custRequest.custRequestId"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7381) Fix 'requestitems' target from order menu.
Chandan Khandelwal created OFBIZ-7381: - Summary: Fix 'requestitems' target from order menu. Key: OFBIZ-7381 URL: https://issues.apache.org/jira/browse/OFBIZ-7381 Project: OFBiz Issue Type: Improvement Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal Priority: Trivial Go To Order > Request > ViewRequest > RequestItems Need to fix incorrect target for requestitems , It is showing multiple (/) in URL URL : https://localhost:8443/ordermgr/control//requestitems?custRequestId=9000 Code Snippet (OrderMenus.xml) : -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7360) Add functionality to remove CustRequestItem from ordermanager
[ https://issues.apache.org/jira/browse/OFBIZ-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7360: -- Attachment: QuoteItems.png Update_Request_Item.png > Add functionality to remove CustRequestItem from ordermanager > - > > Key: OFBIZ-7360 > URL: https://issues.apache.org/jira/browse/OFBIZ-7360 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7360.patch, QuoteItems.png, > Update_Request_Item.png, screenshot-1.png > > > # Go to Order > Requests > # Create New Request > # Add Request Item > There should be a remove link to delete the cust request item (e.g. > QuoteItems) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7360) Add functionality to remove CustRequestItem from ordermanager
[ https://issues.apache.org/jira/browse/OFBIZ-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335980#comment-15335980 ] Chandan Khandelwal commented on OFBIZ-7360: --- Thank you [~rishisolankii] for your feedback on this, as we have already option available to update request item and we can change the request status to cancel or any other from there (Attached screenshot). I have also checked the QuoteItem screen (Attached screenshot) which have option to delete QuoteItem. any thoughts ? > Add functionality to remove CustRequestItem from ordermanager > - > > Key: OFBIZ-7360 > URL: https://issues.apache.org/jira/browse/OFBIZ-7360 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7360.patch, screenshot-1.png > > > # Go to Order > Requests > # Create New Request > # Add Request Item > There should be a remove link to delete the cust request item (e.g. > QuoteItems) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7360) Add functionality to remove CustRequestItem from ordermanager
[ https://issues.apache.org/jira/browse/OFBIZ-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7360: -- Attachment: OFBIZ-7360.patch Patch to add remove functionality for CustRequestItem. > Add functionality to remove CustRequestItem from ordermanager > - > > Key: OFBIZ-7360 > URL: https://issues.apache.org/jira/browse/OFBIZ-7360 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: OFBIZ-7360.patch, screenshot-1.png > > > # Go to Order > Requests > # Create New Request > # Add Request Item > There should be a remove link to delete the cust request item (e.g. > QuoteItems) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7360) Add functionality to remove CustRequestItem from ordermanager
[ https://issues.apache.org/jira/browse/OFBIZ-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7360: -- Attachment: screenshot-1.png > Add functionality to remove CustRequestItem from ordermanager > - > > Key: OFBIZ-7360 > URL: https://issues.apache.org/jira/browse/OFBIZ-7360 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: screenshot-1.png > > > # Go to Order > Requests > # Create New Request > # Add Request Item > There should be a remove link to delete the cust request item (e.g. > QuoteItems) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7360) Add functionality to remove CustRequestItem from ordermanager
Chandan Khandelwal created OFBIZ-7360: - Summary: Add functionality to remove CustRequestItem from ordermanager Key: OFBIZ-7360 URL: https://issues.apache.org/jira/browse/OFBIZ-7360 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal # Go to Order > Requests # Create New Request # Add Request Item There should be a remove link to delete the cust request item (e.g. QuoteItems) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7132) cmssite Demo Data Upgrade to Demonstrate Usage of WebSitePathAlias
[ https://issues.apache.org/jira/browse/OFBIZ-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7132: -- Assignee: Chandan Khandelwal > cmssite Demo Data Upgrade to Demonstrate Usage of WebSitePathAlias > --- > > Key: OFBIZ-7132 > URL: https://issues.apache.org/jira/browse/OFBIZ-7132 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/cmssite >Reporter: Pranay Pandey > Assignee: Chandan Khandelwal >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-7132.patch > > > cmssite Demo Data to be Upgraded to Demonstrate Usage of WebSitePathAlias. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7132) cmssite Demo Data Upgrade to Demonstrate Usage of WebSitePathAlias
[ https://issues.apache.org/jira/browse/OFBIZ-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7132: -- Assignee: (was: Pranay Pandey) > cmssite Demo Data Upgrade to Demonstrate Usage of WebSitePathAlias > --- > > Key: OFBIZ-7132 > URL: https://issues.apache.org/jira/browse/OFBIZ-7132 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/cmssite >Reporter: Pranay Pandey >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-7132.patch > > > cmssite Demo Data to be Upgraded to Demonstrate Usage of WebSitePathAlias. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7132) cmssite Demo Data Upgrade to Demonstrate Usage of WebSitePathAlias
[ https://issues.apache.org/jira/browse/OFBIZ-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7132: -- Attachment: OFBIZ-7132.patch Added Patch for WebSitePathAlias demo data for the cmssite. > cmssite Demo Data Upgrade to Demonstrate Usage of WebSitePathAlias > --- > > Key: OFBIZ-7132 > URL: https://issues.apache.org/jira/browse/OFBIZ-7132 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/cmssite >Reporter: Pranay Pandey >Assignee: Pranay Pandey >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-7132.patch > > > cmssite Demo Data to be Upgraded to Demonstrate Usage of WebSitePathAlias. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7184) 'Data Source Id' should be editable/visible on error view screen of createDataSource
[ https://issues.apache.org/jira/browse/OFBIZ-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7184: -- Attachment: screenshot-1.png > 'Data Source Id' should be editable/visible on error view screen of > createDataSource > > > Key: OFBIZ-7184 > URL: https://issues.apache.org/jira/browse/OFBIZ-7184 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Chandan Khandelwal > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7184) 'Data Source Id' should be editable/visible on error view screen of createDataSource
Chandan Khandelwal created OFBIZ-7184: - Summary: 'Data Source Id' should be editable/visible on error view screen of createDataSource Key: OFBIZ-7184 URL: https://issues.apache.org/jira/browse/OFBIZ-7184 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Chandan Khandelwal Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7170) Improvements in 'Find Shipment' screen to make it consistent with other find screens
[ https://issues.apache.org/jira/browse/OFBIZ-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7170: -- Description: -- 'Find Shipment' button should be in screenlet-body -- On find action, if no search result or single record found then it is redirected to ViewShipment. -- Use Like operator for 'Shipment Id' search constraint. was: -- 'Find Shipment' button should be in screenlet-body -- On find action, if no search result or single records found then it is redirected to ViewShipment. -- Use Like operator for 'Shipment Id' search constraint. > Improvements in 'Find Shipment' screen to make it consistent with other find > screens > > > Key: OFBIZ-7170 > URL: https://issues.apache.org/jira/browse/OFBIZ-7170 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Minor > Attachments: screenshot-1.png > > > -- 'Find Shipment' button should be in screenlet-body > -- On find action, if no search result or single record found then it is > redirected to ViewShipment. > -- Use Like operator for 'Shipment Id' search constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7170) Improvements in 'Find Shipment' screen to make it consistent with other find screens
Chandan Khandelwal created OFBIZ-7170: - Summary: Improvements in 'Find Shipment' screen to make it consistent with other find screens Key: OFBIZ-7170 URL: https://issues.apache.org/jira/browse/OFBIZ-7170 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Trunk Reporter: Chandan Khandelwal Priority: Minor Attachments: screenshot-1.png -- 'Find Shipment' button should be in screenlet-body -- On find action, if no search result or single records found then it is redirected to ViewShipment. -- Use Like operator for 'Shipment Id' search constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7170) Improvements in 'Find Shipment' screen to make it consistent with other find screens
[ https://issues.apache.org/jira/browse/OFBIZ-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7170: -- Attachment: screenshot-1.png > Improvements in 'Find Shipment' screen to make it consistent with other find > screens > > > Key: OFBIZ-7170 > URL: https://issues.apache.org/jira/browse/OFBIZ-7170 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Reporter: Chandan Khandelwal >Priority: Minor > Attachments: screenshot-1.png > > > -- 'Find Shipment' button should be in screenlet-body > -- On find action, if no search result or single records found then it is > redirected to ViewShipment. > -- Use Like operator for 'Shipment Id' search constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7165) PO invoice is generated for the unit price for which order is created, it should be generated for the unit price on received inventory.
[ https://issues.apache.org/jira/browse/OFBIZ-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7165: -- Attachment: Receive_Inventory_With_Updated_Unit_Price.png Purchase_Invoice_1.pdf PO_With_Final_Unit_Price_1.pdf > PO invoice is generated for the unit price for which order is created, it > should be generated for the unit price on received inventory. > --- > > Key: OFBIZ-7165 > URL: https://issues.apache.org/jira/browse/OFBIZ-7165 > Project: OFBiz > Issue Type: Bug > Components: accounting, order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Chandan Khandelwal > Assignee: Chandan Khandelwal > Attachments: PO_With_Final_Unit_Price_1.pdf, > Purchase_Invoice_1.pdf, Receive_Inventory_With_Updated_Unit_Price.png > > > Steps : > 1. Create Purchase Order > 2. Approve Purchase Order > 3. Quick Receive Purchase Order > 4. Select Shipment and Receive Selected Shipment > 5. Update Per Unit Price > 6. Receive Selected Products > 7. View PO Invoice > Here, PO invoice is generated for the unit price for which order is created, > it should be generated for the unit price on received inventory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7165) PO invoice is generated for the unit price for which order is created, it should be generated for the unit price on received inventory.
Chandan Khandelwal created OFBIZ-7165: - Summary: PO invoice is generated for the unit price for which order is created, it should be generated for the unit price on received inventory. Key: OFBIZ-7165 URL: https://issues.apache.org/jira/browse/OFBIZ-7165 Project: OFBiz Issue Type: Bug Components: accounting, order Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12, Release Branch 13.07 Reporter: Chandan Khandelwal Assignee: Chandan Khandelwal Steps : 1. Create Purchase Order 2. Approve Purchase Order 3. Quick Receive Purchase Order 4. Select Shipment and Receive Selected Shipment 5. Update Per Unit Price 6. Receive Selected Products 7. View PO Invoice Here, PO invoice is generated for the unit price for which order is created, it should be generated for the unit price on received inventory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7133) ECommerce UI of 'Cart Summary' section is not consistent.
[ https://issues.apache.org/jira/browse/OFBIZ-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7133: -- Attachment: (was: Cart_Summary.png) > ECommerce UI of 'Cart Summary' section is not consistent. > - > > Key: OFBIZ-7133 > URL: https://issues.apache.org/jira/browse/OFBIZ-7133 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce > Reporter: Chandan Khandelwal >Assignee: Pranay Pandey >Priority: Trivial > Fix For: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 > > Attachments: screenshot-1.png > > > http://demo-stable-ofbiz.apache.org/ecommerce/control/main > UI of 'Cart Summary' section is not consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7133) ECommerce UI of 'Cart Summary' section is not consistent.
[ https://issues.apache.org/jira/browse/OFBIZ-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal updated OFBIZ-7133: -- Attachment: screenshot-1.png > ECommerce UI of 'Cart Summary' section is not consistent. > - > > Key: OFBIZ-7133 > URL: https://issues.apache.org/jira/browse/OFBIZ-7133 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce > Reporter: Chandan Khandelwal >Assignee: Arjun Kaushal >Priority: Trivial > Fix For: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 > > Attachments: Cart_Summary.png, screenshot-1.png > > > http://demo-stable-ofbiz.apache.org/ecommerce/control/main > UI of 'Cart Summary' section is not consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
