[jira] [Commented] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265939#comment-16265939 ] Jacques Le Roux commented on OFBIZ-10012: - Hi Pierre, what is great exactly :D ? > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. > 6. For reference screenshot is attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9501) Move all data in applications to the datamodel component
[ https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265927#comment-16265927 ] Rishi Solanki commented on OFBIZ-9501: -- Taher, Thank you for your input, I also think on that data on the similar points. But while checking the dependencies I see the data is on seed reader and code will also have checks on those data to run the component. For the manufacturing help data is only uses the locale demonstration of manufacturing component only. For other components help data is only in US English, so I moved that data as well. In my previous commits I moved the similar data for other components, so if we decide to keep such configuration data to the component specific location then I'll make changes in those files as well. I agree on the point that configuration data should be with component only. But code base uses that data in several conditions and seed reader direct me to move that data as well. On the whole, we can rethink on this and keep the seed reader (for now) at component location. Then we can think on seed reader is appropriate for configuration data or not. Alternatively if we think seed reader is fine for configuration data then we can decide where to keep seed data. Like are we fine to have seed data of one component in data model as well as in some specific component (Party, Manufacturing etc.). Putting all this to maintain consistency and developers ease, because for me when I search for some data in files I usually expect that data to some location. Please suggest how should we proceed, thanks again for your help on this. It really help to better understand the things you want to achieve from this ticket. Due to the same reason I first add the patch on the ticket and after feedback commit the changes. > Move all data in applications to the datamodel component > > > Key: OFBIZ-9501 > URL: https://issues.apache.org/jira/browse/OFBIZ-9501 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Assignee: Rishi Solanki >Priority: Minor > Labels: application, data > Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, > OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, > OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, > OFBIZ-9501_Consolidated.patch > > > As per a community [discussion > thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E] > we decided to move all data (seed, seed-initial, demo) to the datamodel > component. and to also reduce and cleanup this data to ease debugging and > maintenance. > After moving all the data, the directory and file structure would be similar > to the below: > data/ > ├── demo > │ ├── AccountingDemoData.xml > │ ├── CommonDemoData.xml > │ ├── ContentDemoData.xml > │ ├── HumanresDemo.xml > │ ├── ManufacturingDemoData.xml > │ ├── MarketingDemoData.xml > │ ├── OrderDemoData.xml > │ ├── PartyDemoData.xml > │ ├── ProductDemoData.xml > │ ├── ShipmentDemoData.xml > │ └── WorkEffortDemoData.xml > ├── seed > │ ├── AccountingSeedData.xml > │ ├── CommonSeedData.xml > │ ├── ContentSeedData.xml > │ ├── HumanresSeedData.xml > │ ├── ManufacturingSeedData.xml > │ ├── MarketingSeedData.xml > │ ├── OrderSeedData.xml > │ ├── PartySeedData.xml > │ ├── ProductSeedData.xml > │ ├── ShipmentSeedData.xml > │ └── WorkEffortSeedData.xml > └── seed-initial > ├── AccountingSeedInitialData.xml > ├── CommonSeedInitialData.xml > ├── ContentSeedInitialData.xml > ├── HumanresSeedInitialData.xml > ├── ManufacturingSeedInitialData.xml > ├── MarketingSeedInitialData.xml > ├── OrderSeedInitialData.xml > ├── PartySeedInitialData.xml > ├── ProductSeedInitialData.xml > ├── ShipmentSeedInitialData.xml > └── WorkEffortSeedInitialData.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265808#comment-16265808 ] Pierre Smits commented on OFBIZ-10012: -- Great! > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. > 6. For reference screenshot is attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9653) Issue while creating new person in the party component
[ https://issues.apache.org/jira/browse/OFBIZ-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265805#comment-16265805 ] Jacques Le Roux commented on OFBIZ-9653: I updated the XSD at r1816167 > Issue while creating new person in the party component > -- > > Key: OFBIZ-9653 > URL: https://issues.apache.org/jira/browse/OFBIZ-9653 > Project: OFBiz > Issue Type: Bug >Reporter: Rubia Elza Joshep >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9653.patch, screenshot-1.png > > > Steps to regenerate: > 1) Open link [https://demo-trunk.ofbiz.apache.org/webtools/control/main] > 2) Go to party component. > 2) Click on Create new person. > 3) Fill in the mandatory fields and click on save button. > Actual: Redirects to the view profile page > https://demo-trunk.ofbiz.apache.org/partymgr/control/viewprofile with > following description "party found with the partyId of:" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9840) Mime Type not supported Error while generating a Composite Pdf
[
https://issues.apache.org/jira/browse/OFBIZ-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265797#comment-16265797
]
Jacques Le Roux commented on OFBIZ-9840:
Hi Aman,
Funny this long bug in ASF Jira where using my committer id renders Jan Le Roux
:) Actually there is no cure for that :/
Sorry I have no ideas about that, it's pre Apache era:
http://svn.apache.org/viewvc?view=revision&revision=418498
http://svn.apache.org/viewvc/incubator/ofbiz/trunk/applications/content/data/CompDocData.xml?limit_changes=0&view=log&pathrev=418498
According that this is 11+ years old at least I wonder if we should keep these
data, if it can help...
> Mime Type not supported Error while generating a Composite Pdf
> --
>
> Key: OFBIZ-9840
> URL: https://issues.apache.org/jira/browse/OFBIZ-9840
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Julian Leichert
>Assignee: Aman Mishra
>
> When generating a Composite Pdf in the Content Manager an Error occurs :
> Mime Type not Supported
> Steps to recreate the Error Message:
> Content Manager-> CompDoc ->T ree-> View Instances-> Tree -> Generate
> Composite Pdf
> Error log:
> {code:java}
> java.lang.Exception: Error in Service [renderCompDocPdf]: Mime Type not
> supported
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:361)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:302)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:537)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:229)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:88)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.content.compdoc.CompDocEvents.genCompDocPdf(CompDocEvents.java:171)
> [ofbiz.jar:?]
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OFBIZ-9996) Implement Groovy test in testtools
[
https://issues.apache.org/jira/browse/OFBIZ-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-9996.
Resolution: Implemented
Fix Version/s: Upcoming Release
I commit the first step on trunk at revision 1816335
> Implement Groovy test in testtools
> --
>
> Key: OFBIZ-9996
> URL: https://issues.apache.org/jira/browse/OFBIZ-9996
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9996.patch
>
>
> With the minilang deprecation and the migration to groovy, I tried to
> implement on the ofbiz testtools the possibility to use groovy for
> integration test.
> My idea is to define a new element on test-suite.xsd like this
> {code}
> location="component://base/groovyScript/test/SimpleTests.groovy"/>
> {code}
> After some research and unfortunately result I found a first solution present
> with the linked patch.
> To test it just apply the patch and run :
> {code}
> $ ./gradlew 'ofbiz --test component=base --test suitename=basetests '
> {code}
> This execute the basetest suite with the new groovy test suite present in
> base/groovyScript/test/SimpleTests.groovy
> I'm sure this code may be improve if you want how don't hesitate !
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9501) Move all data in applications to the datamodel component
[ https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265789#comment-16265789 ] Taher Alkhateeb commented on OFBIZ-9501: Hi Rishi, As usual thank you for this great work. I might be wrong as I did not do deep investigation like you probably did, but I find some data moved from strange files. For example: - applications/accounting/data/AccountingHelpData.xml - applications/accounting/data/AccountingSecurityPermissionSeedData.xml - applications/manufacturing/data/ManufacturingHelpData_EN.xml - applications/manufacturing/data/ManufacturingHelpData_NL.xml - applications/manufacturing/data/ManufacturingSecurityPermissionSeedData.xml The above files are for help and security permissions. I also saw some files for portlets. Wouldn't it make more sense to move "domain data" instead of "configuration data" to the datamodel component? Again I could be wrong in my analysis so please forgive my short-sighted input > Move all data in applications to the datamodel component > > > Key: OFBIZ-9501 > URL: https://issues.apache.org/jira/browse/OFBIZ-9501 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Assignee: Rishi Solanki >Priority: Minor > Labels: application, data > Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, > OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, > OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, > OFBIZ-9501_Consolidated.patch > > > As per a community [discussion > thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E] > we decided to move all data (seed, seed-initial, demo) to the datamodel > component. and to also reduce and cleanup this data to ease debugging and > maintenance. > After moving all the data, the directory and file structure would be similar > to the below: > data/ > ├── demo > │ ├── AccountingDemoData.xml > │ ├── CommonDemoData.xml > │ ├── ContentDemoData.xml > │ ├── HumanresDemo.xml > │ ├── ManufacturingDemoData.xml > │ ├── MarketingDemoData.xml > │ ├── OrderDemoData.xml > │ ├── PartyDemoData.xml > │ ├── ProductDemoData.xml > │ ├── ShipmentDemoData.xml > │ └── WorkEffortDemoData.xml > ├── seed > │ ├── AccountingSeedData.xml > │ ├── CommonSeedData.xml > │ ├── ContentSeedData.xml > │ ├── HumanresSeedData.xml > │ ├── ManufacturingSeedData.xml > │ ├── MarketingSeedData.xml > │ ├── OrderSeedData.xml > │ ├── PartySeedData.xml > │ ├── ProductSeedData.xml > │ ├── ShipmentSeedData.xml > │ └── WorkEffortSeedData.xml > └── seed-initial > ├── AccountingSeedInitialData.xml > ├── CommonSeedInitialData.xml > ├── ContentSeedInitialData.xml > ├── HumanresSeedInitialData.xml > ├── ManufacturingSeedInitialData.xml > ├── MarketingSeedInitialData.xml > ├── OrderSeedInitialData.xml > ├── PartySeedInitialData.xml > ├── ProductSeedInitialData.xml > ├── ShipmentSeedInitialData.xml > └── WorkEffortSeedInitialData.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9896) Incorrect success message after creating prospect
[ https://issues.apache.org/jira/browse/OFBIZ-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-9896. -- Resolution: Fixed Fix Version/s: 16.11.04 Thanks Sonal Patwari and Lalit Dashora, Your patch is in trunk r1816297 R16.11 r1816299 I simply removed the uppercase for Prospect in French :) I let others check their languages > Incorrect success message after creating prospect > - > > Key: OFBIZ-9896 > URL: https://issues.apache.org/jira/browse/OFBIZ-9896 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Jacques Le Roux > Fix For: 16.11.04 > > Attachments: OFBIZ-9896-Incorrect-Success-Message.patch > > > Navigate to > [NewProspect|https://demo-trunk.ofbiz.apache.org/partymgr/control/NewProspect], > after creating the prospect, success message 'ProductStoreRole is created > successfully'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9896) Incorrect success message after creating prospect
[ https://issues.apache.org/jira/browse/OFBIZ-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-9896: -- Assignee: Jacques Le Roux > Incorrect success message after creating prospect > - > > Key: OFBIZ-9896 > URL: https://issues.apache.org/jira/browse/OFBIZ-9896 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Jacques Le Roux > Attachments: OFBIZ-9896-Incorrect-Success-Message.patch > > > Navigate to > [NewProspect|https://demo-trunk.ofbiz.apache.org/partymgr/control/NewProspect], > after creating the prospect, success message 'ProductStoreRole is created > successfully'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265731#comment-16265731 ] Jacques Le Roux commented on OFBIZ-5959: I feel the need to put this link here: http://markmail.org/message/pqrmv5vpjgm6iigq see bottom of it > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: role, roles > Attachments: OFBIZ-5959-party-entitymodel.xml.patch > > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265730#comment-16265730 ] Jacques Le Roux commented on OFBIZ-3894: Thanks Pierre for the reminder on http://ofbiz.markmail.org/search/?q=lifespan%20field which remembers me my conclusion at bottom of http://markmail.org/message/pqrmv5vpjgm6iigq > Refactor Email handling > --- > > Key: OFBIZ-3894 > URL: https://issues.apache.org/jira/browse/OFBIZ-3894 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: BJ Freeman >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch, > OFBIZ-3894.patch > > Original Estimate: 1,344h > Remaining Estimate: 1,344h > > with the addition of the Website for each component > 1) create product store for Order entry, or use the B2C product store. > 2) move the email widgets from ecommerce to order compontent. > 3) modify the seed data so that Order entry has it own emails from order > component.this would be to add emails to > note: as I go through the different items this is turning out to be a bigger > project than I first anticipated. > so consider this so far just ideas. > Maybe break down in to small tasks as I have time to do something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9911) Add ability to record Return Communication
[ https://issues.apache.org/jira/browse/OFBIZ-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265728#comment-16265728 ] Ratnesh Upadhyay edited comment on OFBIZ-9911 at 11/25/17 2:31 PM: --- *Quick Update:* I am done with the feature implementation, now system started recording return related communications. Also user should be able to find and view communication by return from newly added screen. Attached patch and will share technical summary and verification details soon. was (Author: upadhyay.ratnesh): *Quick Update:* I am done with the feature implementation, now system started recording return related communications. Also user should be able to find and view communication by return from newly added screen. I'll share technical summary and verification details soon. > Add ability to record Return Communication > -- > > Key: OFBIZ-9911 > URL: https://issues.apache.org/jira/browse/OFBIZ-9911 > Project: OFBiz > Issue Type: New Feature > Components: order, party >Reporter: Ratnesh Upadhyay >Assignee: Rishi Solanki > Attachments: OFBIZ-9911.patch > > > In OOTB we are having the ability to record order specific communication in > CommunicationEventOrder and the user can retrieve/review them from party > > communications screen but we don't have such support for return > communications. So It would be great to have an ability to record return > specific communication in the system. > We have to implement following items to establish this feature : > *Data Model Details:* > - We will have to create new entity CommunicationEventReturn to record return > communication. It should have returnId and communicationEventId along with > other necessary fields. > - We have to implement following view CommunicationEventAndReturn to fetch > return communications over screens as needed. > *New Implementation Details:* > - We have to add CRUD services for the new entity. > *Existing Implementation Details:* > - We have to extend createCommunicationEvent service definition with retunId > field and extend the existing implementation to create the record in > CommunicationEventReturn based on supplied returnId parameter. > - Also, we have to extend return related email services to provide returnId > in service context. > *User Interface Details:* > - In the current system we have Party > Communications > Find Communication > By Order screen, in the same way, we can add another screen to find > communication by return. > - We can add return communication screenlet over Order Manager > Return > > Return History screen or we can add communication tab under Order > Return > screen, this is just a thought still thinking on it. > - We can also provide communication tab in order component as well. > Thanks to [~jacques.le.roux], [~rishisolankii] and [~deepakddixit] for > discussion and inputs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9911) Add ability to record Return Communication
[ https://issues.apache.org/jira/browse/OFBIZ-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki reassigned OFBIZ-9911: Assignee: Rishi Solanki (was: Ratnesh Upadhyay) > Add ability to record Return Communication > -- > > Key: OFBIZ-9911 > URL: https://issues.apache.org/jira/browse/OFBIZ-9911 > Project: OFBiz > Issue Type: New Feature > Components: order, party >Reporter: Ratnesh Upadhyay >Assignee: Rishi Solanki > Attachments: OFBIZ-9911.patch > > > In OOTB we are having the ability to record order specific communication in > CommunicationEventOrder and the user can retrieve/review them from party > > communications screen but we don't have such support for return > communications. So It would be great to have an ability to record return > specific communication in the system. > We have to implement following items to establish this feature : > *Data Model Details:* > - We will have to create new entity CommunicationEventReturn to record return > communication. It should have returnId and communicationEventId along with > other necessary fields. > - We have to implement following view CommunicationEventAndReturn to fetch > return communications over screens as needed. > *New Implementation Details:* > - We have to add CRUD services for the new entity. > *Existing Implementation Details:* > - We have to extend createCommunicationEvent service definition with retunId > field and extend the existing implementation to create the record in > CommunicationEventReturn based on supplied returnId parameter. > - Also, we have to extend return related email services to provide returnId > in service context. > *User Interface Details:* > - In the current system we have Party > Communications > Find Communication > By Order screen, in the same way, we can add another screen to find > communication by return. > - We can add return communication screenlet over Order Manager > Return > > Return History screen or we can add communication tab under Order > Return > screen, this is just a thought still thinking on it. > - We can also provide communication tab in order component as well. > Thanks to [~jacques.le.roux], [~rishisolankii] and [~deepakddixit] for > discussion and inputs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9911) Add ability to record Return Communication
[ https://issues.apache.org/jira/browse/OFBIZ-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-9911: Attachment: OFBIZ-9911.patch > Add ability to record Return Communication > -- > > Key: OFBIZ-9911 > URL: https://issues.apache.org/jira/browse/OFBIZ-9911 > Project: OFBiz > Issue Type: New Feature > Components: order, party >Reporter: Ratnesh Upadhyay >Assignee: Ratnesh Upadhyay > Attachments: OFBIZ-9911.patch > > > In OOTB we are having the ability to record order specific communication in > CommunicationEventOrder and the user can retrieve/review them from party > > communications screen but we don't have such support for return > communications. So It would be great to have an ability to record return > specific communication in the system. > We have to implement following items to establish this feature : > *Data Model Details:* > - We will have to create new entity CommunicationEventReturn to record return > communication. It should have returnId and communicationEventId along with > other necessary fields. > - We have to implement following view CommunicationEventAndReturn to fetch > return communications over screens as needed. > *New Implementation Details:* > - We have to add CRUD services for the new entity. > *Existing Implementation Details:* > - We have to extend createCommunicationEvent service definition with retunId > field and extend the existing implementation to create the record in > CommunicationEventReturn based on supplied returnId parameter. > - Also, we have to extend return related email services to provide returnId > in service context. > *User Interface Details:* > - In the current system we have Party > Communications > Find Communication > By Order screen, in the same way, we can add another screen to find > communication by return. > - We can add return communication screenlet over Order Manager > Return > > Return History screen or we can add communication tab under Order > Return > screen, this is just a thought still thinking on it. > - We can also provide communication tab in order component as well. > Thanks to [~jacques.le.roux], [~rishisolankii] and [~deepakddixit] for > discussion and inputs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9911) Add ability to record Return Communication
[ https://issues.apache.org/jira/browse/OFBIZ-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265728#comment-16265728 ] Ratnesh Upadhyay commented on OFBIZ-9911: - *Quick Update:* I am done with the feature implementation, now system started recording return related communications. Also user should be able to find and view communication by return from newly added screen. I'll share technical summary and verification details soon. > Add ability to record Return Communication > -- > > Key: OFBIZ-9911 > URL: https://issues.apache.org/jira/browse/OFBIZ-9911 > Project: OFBiz > Issue Type: New Feature > Components: order, party >Reporter: Ratnesh Upadhyay >Assignee: Ratnesh Upadhyay > Attachments: OFBIZ-9911.patch > > > In OOTB we are having the ability to record order specific communication in > CommunicationEventOrder and the user can retrieve/review them from party > > communications screen but we don't have such support for return > communications. So It would be great to have an ability to record return > specific communication in the system. > We have to implement following items to establish this feature : > *Data Model Details:* > - We will have to create new entity CommunicationEventReturn to record return > communication. It should have returnId and communicationEventId along with > other necessary fields. > - We have to implement following view CommunicationEventAndReturn to fetch > return communications over screens as needed. > *New Implementation Details:* > - We have to add CRUD services for the new entity. > *Existing Implementation Details:* > - We have to extend createCommunicationEvent service definition with retunId > field and extend the existing implementation to create the record in > CommunicationEventReturn based on supplied returnId parameter. > - Also, we have to extend return related email services to provide returnId > in service context. > *User Interface Details:* > - In the current system we have Party > Communications > Find Communication > By Order screen, in the same way, we can add another screen to find > communication by return. > - We can add return communication screenlet over Order Manager > Return > > Return History screen or we can add communication tab under Order > Return > screen, this is just a thought still thinking on it. > - We can also provide communication tab in order component as well. > Thanks to [~jacques.le.roux], [~rishisolankii] and [~deepakddixit] for > discussion and inputs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265729#comment-16265729 ] Jacques Le Roux commented on OFBIZ-9980: Suraj, I agree about committing this if before we create an issue to remember us to update the related screens, OK? > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10019) Replace ?default(value) by !value in Freemarker templates
[
https://issues.apache.org/jira/browse/OFBIZ-10019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10019:
Description:
I want to replace ?default(value) by !value in Freemarker templates, that's
1394 cases!
But before doing so I prefer to wait for a 2.4 Freemarker version because we
already experienced an issue at OFBIZ-4902, see
http://svn.apache.org/viewvc?view=revision&revision=r1624876
Actually I know now that it was not a bug of ours but [one of
Freemarker|https://freemarker.apache.org/docs/dgui_template_exp.html#dgui_template_exp_missing_default]:
bq. Warning! If you have a composite expression after the \!, like 1 + x,
always use parenthesses, like ${x!(1 + y)} or ${(x!1) + y)}, depending on which
interpretation you meant. That's needed because due to a programming mistake in
FreeMarker 2.3.x, the precedence of ! (when it's used as default value
operator) is very low at its right side. This means that, for example, ${x!1 +
y} is misinterpreted by FreeMarker as ${x!(1 + y)} while it should mean ${(x!1)
+ y}. This programming error will be fixed in FreeMarker 2.4, so you should not
utilize this wrong behavior, or else your templates will break with FreeMarker
2.4!
was:
I want to teplace ?default(value) by !value in Freemarker templates, that's
1394 cases!
But before doing so I prefer to wait for a 2.4 Freemarker version because we
already experienced an issue at OFBIZ-4902, see
http://svn.apache.org/viewvc?view=revision&revision=r1624876
Actually I know now that it was not a bug of ours but [one of
Freemarker|https://freemarker.apache.org/docs/dgui_template_exp.html#dgui_template_exp_missing_default]:
bq. Warning! If you have a composite expression after the \!, like 1 + x,
always use parenthesses, like ${x!(1 + y)} or ${(x!1) + y)}, depending on which
interpretation you meant. That's needed because due to a programming mistake in
FreeMarker 2.3.x, the precedence of ! (when it's used as default value
operator) is very low at its right side. This means that, for example, ${x!1 +
y} is misinterpreted by FreeMarker as ${x!(1 + y)} while it should mean ${(x!1)
+ y}. This programming error will be fixed in FreeMarker 2.4, so you should not
utilize this wrong behavior, or else your templates will break with FreeMarker
2.4!
> Replace ?default(value) by !value in Freemarker templates
> -
>
> Key: OFBIZ-10019
> URL: https://issues.apache.org/jira/browse/OFBIZ-10019
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Upcoming Release
>
>
> I want to replace ?default(value) by !value in Freemarker templates, that's
> 1394 cases!
> But before doing so I prefer to wait for a 2.4 Freemarker version because we
> already experienced an issue at OFBIZ-4902, see
> http://svn.apache.org/viewvc?view=revision&revision=r1624876
> Actually I know now that it was not a bug of ours but [one of
> Freemarker|https://freemarker.apache.org/docs/dgui_template_exp.html#dgui_template_exp_missing_default]:
> bq. Warning! If you have a composite expression after the \!, like 1 + x,
> always use parenthesses, like ${x!(1 + y)} or ${(x!1) + y)}, depending on
> which interpretation you meant. That's needed because due to a programming
> mistake in FreeMarker 2.3.x, the precedence of ! (when it's used as default
> value operator) is very low at its right side. This means that, for example,
> ${x!1 + y} is misinterpreted by FreeMarker as ${x!(1 + y)} while it should
> mean ${(x!1) + y}. This programming error will be fixed in FreeMarker 2.4, so
> you should not utilize this wrong behavior, or else your templates will break
> with FreeMarker 2.4!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OFBIZ-10019) Replace ?default(value) by !value in Freemarker templates
Jacques Le Roux created OFBIZ-10019:
---
Summary: Replace ?default(value) by !value in Freemarker templates
Key: OFBIZ-10019
URL: https://issues.apache.org/jira/browse/OFBIZ-10019
Project: OFBiz
Issue Type: Improvement
Components: ALL COMPONENTS
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Trivial
Fix For: Upcoming Release
I want to teplace ?default(value) by !value in Freemarker templates, that's
1394 cases!
But before doing so I prefer to wait for a 2.4 Freemarker version because we
already experienced an issue at OFBIZ-4902, see
http://svn.apache.org/viewvc?view=revision&revision=r1624876
Actually I know now that it was not a bug of ours but [one of
Freemarker|https://freemarker.apache.org/docs/dgui_template_exp.html#dgui_template_exp_missing_default]:
bq. Warning! If you have a composite expression after the \!, like 1 + x,
always use parenthesses, like ${x!(1 + y)} or ${(x!1) + y)}, depending on which
interpretation you meant. That's needed because due to a programming mistake in
FreeMarker 2.3.x, the precedence of ! (when it's used as default value
operator) is very low at its right side. This means that, for example, ${x!1 +
y} is misinterpreted by FreeMarker as ${x!(1 + y)} while it should mean ${(x!1)
+ y}. This programming error will be fixed in FreeMarker 2.4, so you should not
utilize this wrong behavior, or else your templates will break with FreeMarker
2.4!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OFBIZ-9675) Use ofbizCurrency macro and remove hardcoded ##0.00 string
[ https://issues.apache.org/jira/browse/OFBIZ-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-9675. -- Resolution: Fixed Fix Version/s: 16.11.04 Thanks Renuka Srishti and Ritesh Kumar, Ritesh, your patch is in trunk r1816291 R16.11 r1816296 > Use ofbizCurrency macro and remove hardcoded ##0.00 string > -- > > Key: OFBIZ-9675 > URL: https://issues.apache.org/jira/browse/OFBIZ-9675 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 16.11.04 > > Attachments: OFBIZ-9675 > > > ofbizAmount macro can be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9905) Issue with Agreement under Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265718#comment-16265718 ] sourabh jain commented on OFBIZ-9905: - Provided patch for Create Agreement screen. > Issue with Agreement under Accounting > - > > Key: OFBIZ-9905 > URL: https://issues.apache.org/jira/browse/OFBIZ-9905 > Project: OFBiz > Issue Type: Bug > Environment: > https://demo-trunk.ofbiz.apache.org/accounting/control/EditAgreement >Reporter: Aayush jain >Assignee: sourabh jain > Attachments: OFBIZ-9905.patch, UI_label .png > > > Following issues found: > 1. Create Agreement opens an edit agreement window > 2. Able to Create Agreement without any detail (empty Agreement) > Steps: > 1. Open URL > https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement > 2. Navigate to Agreement section > 3. Click on create Agreement > 4. Click submit button > Actual: Agreement id is generated for empty agreement and when create window > opens, it's redirection is wrong to edit window > Expected: Proper redirection should be there (create agreement) and if an > agreement is created without any details its of no use. > Note: Same Issue exist with following screens: > 1. Billing Account > 2. Tax Authority > 3. Agreement > 4. Fixed Asset > 5. Vendor > 6. WebSite > 7. Blog > 8. Employment > 9. Employee Position > 10.Performance Review > 11.Job Requisition > 12. Party Resume -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10010) No option to create the account contacts in SFA component
[ https://issues.apache.org/jira/browse/OFBIZ-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Choudhary updated OFBIZ-10010: -- Attachment: OFBIZ-10010.patch Added patch for the mentioned issue. Created new request-map and screen definition to redirect 'Create New' link on proper screen. So that user can add contacts to the Account. > No option to create the account contacts in SFA component > - > > Key: OFBIZ-10010 > URL: https://issues.apache.org/jira/browse/OFBIZ-10010 > Project: OFBiz > Issue Type: Bug >Reporter: Rubia Elza Joshep >Assignee: Pradeep Choudhary > Attachments: Accountcontacts.png, Accountscontact01.png, > OFBIZ-10010.patch > > > Steps to regenerate: > 1) Open URL [https://demo-trunk.ofbiz.apache.org/sfa/control/FindAccounts] > 2) Select an account from the list or create a new account. > 3) In the account profile page, click on "Create New" in the "List Related > Contacts" section. > Actual: No option to create the account contacts. > Expected: There should be an option to create account's contact. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9905) Issue with Agreement under Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sourabh jain updated OFBIZ-9905: Attachment: OFBIZ-9905.patch > Issue with Agreement under Accounting > - > > Key: OFBIZ-9905 > URL: https://issues.apache.org/jira/browse/OFBIZ-9905 > Project: OFBiz > Issue Type: Bug > Environment: > https://demo-trunk.ofbiz.apache.org/accounting/control/EditAgreement >Reporter: Aayush jain >Assignee: sourabh jain > Attachments: OFBIZ-9905.patch, UI_label .png > > > Following issues found: > 1. Create Agreement opens an edit agreement window > 2. Able to Create Agreement without any detail (empty Agreement) > Steps: > 1. Open URL > https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement > 2. Navigate to Agreement section > 3. Click on create Agreement > 4. Click submit button > Actual: Agreement id is generated for empty agreement and when create window > opens, it's redirection is wrong to edit window > Expected: Proper redirection should be there (create agreement) and if an > agreement is created without any details its of no use. > Note: Same Issue exist with following screens: > 1. Billing Account > 2. Tax Authority > 3. Agreement > 4. Fixed Asset > 5. Vendor > 6. WebSite > 7. Blog > 8. Employment > 9. Employee Position > 10.Performance Review > 11.Job Requisition > 12. Party Resume -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9978) Upgrade Jquery 1.11.0 to JQuery 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9978: - Attachment: OFBIZ-9978.patch OFBIZ-9978_plugins.patch Upgraded jQuery Timepicker Addon to 1.6.3 (https://github.com/trentrichardson/jQuery-Timepicker-Addon/). jQuery UI Slider Access comes with JQuery Timepicker addon package. Moved localization to i18n (as comes with package) & made changes accordingly Working well with even jQuery UI 1.10. Steps to verify: https://localhost:8443/ordermgr/control/ListQuoteRoles?quoteId=CQ0001 https://localhost:8443/example/control/FormWidgetExamples https://localhost:8443/catalog/control/EditProduct Interestingly it supports Millisecond, Microsecond and Time Zone too. > Upgrade Jquery 1.11.0 to JQuery 3.2.1 > - > > Key: OFBIZ-9978 > URL: https://issues.apache.org/jira/browse/OFBIZ-9978 > Project: OFBiz > Issue Type: Improvement >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Attachments: Image 001.png, Image 002.png, Image 003.png, > OFBIZ-9978.patch, OFBIZ-9978.patch, OFBIZ-9978.patch, > OFBIZ-9978_plugins.patch, OFBIZ-9978_plugins.patch, OFBIZ-9978_plugins.patch > > > Migration Steps: > 1. Upgrade JQuery 1.11.0 to 3.2.1 > * Remove JQuery 1.x & JQuery migrate 1.x > * Add JQuery 3.2.1 & JQuery migrate 3.0.0 > * Rectify any broken code and plugin > 2. Upgrade all the JQuery plugins to latest > 3. Remove JQuery migrate 3.0.0 & rectify any broken code -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10010) No option to create the account contacts in SFA component
[ https://issues.apache.org/jira/browse/OFBIZ-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Choudhary reassigned OFBIZ-10010: - Assignee: Pradeep Choudhary > No option to create the account contacts in SFA component > - > > Key: OFBIZ-10010 > URL: https://issues.apache.org/jira/browse/OFBIZ-10010 > Project: OFBiz > Issue Type: Bug >Reporter: Rubia Elza Joshep >Assignee: Pradeep Choudhary > Attachments: Accountcontacts.png, Accountscontact01.png > > > Steps to regenerate: > 1) Open URL [https://demo-trunk.ofbiz.apache.org/sfa/control/FindAccounts] > 2) Select an account from the list or create a new account. > 3) In the account profile page, click on "Create New" in the "List Related > Contacts" section. > Actual: No option to create the account contacts. > Expected: There should be an option to create account's contact. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9899) UI Issue with Account Limit at Find Billing Account(s)
[ https://issues.apache.org/jira/browse/OFBIZ-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankush Upadhyay updated OFBIZ-9899: --- Attachment: OFBIZ-9899.patch Actual issue in the code is, Billing Account rendering logic is using browser's locale(Due to Null BillingAccount object passed) to render currency symbol but the code should use BillingAcccount.accountCurrencyUomId that get's set by User on BillingAccount creation. Fixed the logic to use accountCurrencyUomId as currency to render currency symbol. Attached the patch for review. > UI Issue with Account Limit at Find Billing Account(s) > -- > > Key: OFBIZ-9899 > URL: https://issues.apache.org/jira/browse/OFBIZ-9899 > Project: OFBiz > Issue Type: Bug > Environment: demo-trunk.ofbiz.apache.org >Reporter: Aayush jain >Assignee: Ankush Upadhyay >Priority: Trivial > Attachments: Find_Billing_Account.png, OFBIZ-9899.patch > > > Steps: > 1. Open > https://demo-trunk.ofbiz.apache.org/accounting/control/FindBillingAccount > 2. Navigate to Find Billing account > 3. Check for Search Results > Actual: At Account Limit section, symbol is been displayed > Expected: Currency Symbols should be displayed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9840) Mime Type not supported Error while generating a Composite Pdf
[
https://issues.apache.org/jira/browse/OFBIZ-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265712#comment-16265712
]
Aman Mishra commented on OFBIZ-9840:
Issue is occurring because DataResource (ids are DR1105b and DR1105a) have mime
type as application/msword. Also the file associated with these DataResource is
'mswordtest2.doc' which is an msword file.
During generation of a Composite PDF from Content Manager, 'renderContentPdf'
service is invoked to render PDF file but there is not any support to render
msword file.
[~jleroux] Could you please provide some clarity about following data:
{code}
{code}
Thanks!
> Mime Type not supported Error while generating a Composite Pdf
> --
>
> Key: OFBIZ-9840
> URL: https://issues.apache.org/jira/browse/OFBIZ-9840
> Project: OFBiz
> Issue Type: Bug
> Components: content
>Affects Versions: Trunk
>Reporter: Julian Leichert
>Assignee: Aman Mishra
>
> When generating a Composite Pdf in the Content Manager an Error occurs :
> Mime Type not Supported
> Steps to recreate the Error Message:
> Content Manager-> CompDoc ->T ree-> View Instances-> Tree -> Generate
> Composite Pdf
> Error log:
> {code:java}
> java.lang.Exception: Error in Service [renderCompDocPdf]: Mime Type not
> supported
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:361)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:302)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:537)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:229)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:88)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.content.compdoc.CompDocEvents.genCompDocPdf(CompDocEvents.java:171)
> [ofbiz.jar:?]
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-9501) Move all data in applications to the datamodel component
[ https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki updated OFBIZ-9501: - Attachment: OFBIZ-9501_Consolidated-2.patch Here is another consolidated patch for product, manufacturing and accounting component. Patch covers both seed and seed initial data. Also I have skip only confusing data, on which we can discuss once we complete the effort. I would like to commit the changes once my tests pass. Thanks! > Move all data in applications to the datamodel component > > > Key: OFBIZ-9501 > URL: https://issues.apache.org/jira/browse/OFBIZ-9501 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Upcoming Release >Reporter: Taher Alkhateeb >Assignee: Rishi Solanki >Priority: Minor > Labels: application, data > Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, > OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, > OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, > OFBIZ-9501_Consolidated.patch > > > As per a community [discussion > thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E] > we decided to move all data (seed, seed-initial, demo) to the datamodel > component. and to also reduce and cleanup this data to ease debugging and > maintenance. > After moving all the data, the directory and file structure would be similar > to the below: > data/ > ├── demo > │ ├── AccountingDemoData.xml > │ ├── CommonDemoData.xml > │ ├── ContentDemoData.xml > │ ├── HumanresDemo.xml > │ ├── ManufacturingDemoData.xml > │ ├── MarketingDemoData.xml > │ ├── OrderDemoData.xml > │ ├── PartyDemoData.xml > │ ├── ProductDemoData.xml > │ ├── ShipmentDemoData.xml > │ └── WorkEffortDemoData.xml > ├── seed > │ ├── AccountingSeedData.xml > │ ├── CommonSeedData.xml > │ ├── ContentSeedData.xml > │ ├── HumanresSeedData.xml > │ ├── ManufacturingSeedData.xml > │ ├── MarketingSeedData.xml > │ ├── OrderSeedData.xml > │ ├── PartySeedData.xml > │ ├── ProductSeedData.xml > │ ├── ShipmentSeedData.xml > │ └── WorkEffortSeedData.xml > └── seed-initial > ├── AccountingSeedInitialData.xml > ├── CommonSeedInitialData.xml > ├── ContentSeedInitialData.xml > ├── HumanresSeedInitialData.xml > ├── ManufacturingSeedInitialData.xml > ├── MarketingSeedInitialData.xml > ├── OrderSeedInitialData.xml > ├── PartySeedInitialData.xml > ├── ProductSeedInitialData.xml > ├── ShipmentSeedInitialData.xml > └── WorkEffortSeedInitialData.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9996) Implement Groovy test in testtools
[
https://issues.apache.org/jira/browse/OFBIZ-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265710#comment-16265710
]
Nicolas Malin commented on OFBIZ-9996:
--
Thanks Jacques to look it.
I tries yesterdays to implement the groovy DSL but unfortunately to use it the
groovy script need to extends BaseScript class or the unit test extends
GroovyTestCase. So I didn't solve it at this time.
I will commit the first step without DSL
> Implement Groovy test in testtools
> --
>
> Key: OFBIZ-9996
> URL: https://issues.apache.org/jira/browse/OFBIZ-9996
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
> Attachments: OFBIZ-9996.patch
>
>
> With the minilang deprecation and the migration to groovy, I tried to
> implement on the ofbiz testtools the possibility to use groovy for
> integration test.
> My idea is to define a new element on test-suite.xsd like this
> {code}
> location="component://base/groovyScript/test/SimpleTests.groovy"/>
> {code}
> After some research and unfortunately result I found a first solution present
> with the linked patch.
> To test it just apply the patch and run :
> {code}
> $ ./gradlew 'ofbiz --test component=base --test suitename=basetests '
> {code}
> This execute the basetest suite with the new groovy test suite present in
> base/groovyScript/test/SimpleTests.groovy
> I'm sure this code may be improve if you want how don't hesitate !
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9890) Having condition is ignored on queryList() and queryFirst() calls in EntityQuery
[ https://issues.apache.org/jira/browse/OFBIZ-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265709#comment-16265709 ] Prakhar Kumar commented on OFBIZ-9890: -- While researching more on this issue I found that findList() method internally makes use of find() method which actually supports Having condition. But support for Having condition is not provided in findList() method itself. So there is a fair chance that this would have been done on purpose. As you have mentioned we can opt for queryIterator() for including Having condition, so we can easily get a list by using getCompleteList() method. So, is there any specific use case for which support for having is required in queryList() as well. Please share your thoughts on this :) > Having condition is ignored on queryList() and queryFirst() calls in > EntityQuery > > > Key: OFBIZ-9890 > URL: https://issues.apache.org/jira/browse/OFBIZ-9890 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Gareth Carter >Assignee: Prakhar Kumar >Priority: Minor > > queryList() and queryFirst() both call internal private query() method. This > method calls delegator.findList if a normal Entity/ViewEntity is used (not a > DVE). This has no option to include a having condition and so must opt to use > queryIterator(). Even queryCount() can use a having condition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-3894: - Assignee: Swapnil M Mane (was: Erwan de FERRIERES) > Refactor Email handling > --- > > Key: OFBIZ-3894 > URL: https://issues.apache.org/jira/browse/OFBIZ-3894 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: BJ Freeman >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch, > OFBIZ-3894.patch > > Original Estimate: 1,344h > Remaining Estimate: 1,344h > > with the addition of the Website for each component > 1) create product store for Order entry, or use the B2C product store. > 2) move the email widgets from ecommerce to order compontent. > 3) modify the seed data so that Order entry has it own emails from order > component.this would be to add emails to > note: as I go through the different items this is turning out to be a bigger > project than I first anticipated. > so consider this so far just ideas. > Maybe break down in to small tasks as I have time to do something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265707#comment-16265707 ] Swapnil M Mane commented on OFBIZ-3894: --- Thank you [~pfm.smits]! :-) > Refactor Email handling > --- > > Key: OFBIZ-3894 > URL: https://issues.apache.org/jira/browse/OFBIZ-3894 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: BJ Freeman >Assignee: Erwan de FERRIERES >Priority: Minor > Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch, > OFBIZ-3894.patch > > Original Estimate: 1,344h > Remaining Estimate: 1,344h > > with the addition of the Website for each component > 1) create product store for Order entry, or use the B2C product store. > 2) move the email widgets from ecommerce to order compontent. > 3) modify the seed data so that Order entry has it own emails from order > component.this would be to add emails to > note: as I go through the different items this is turning out to be a bigger > project than I first anticipated. > so consider this so far just ideas. > Maybe break down in to small tasks as I have time to do something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10018) Update markup of Register page according to standard markup given by Bootstrap v4.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitish Mishra reassigned OFBIZ-10018: - Assignee: Nitish Mishra > Update markup of Register page according to standard markup given by > Bootstrap v4.0.0 > - > > Key: OFBIZ-10018 > URL: https://issues.apache.org/jira/browse/OFBIZ-10018 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Affects Versions: Release Branch 16.11 >Reporter: Nitish Mishra >Assignee: Nitish Mishra > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10018) Update markup of Register page according to standard markup given by Bootstrap v4.0.0
Nitish Mishra created OFBIZ-10018: - Summary: Update markup of Register page according to standard markup given by Bootstrap v4.0.0 Key: OFBIZ-10018 URL: https://issues.apache.org/jira/browse/OFBIZ-10018 Project: OFBiz Issue Type: Sub-task Components: ecommerce Affects Versions: Release Branch 16.11 Reporter: Nitish Mishra -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9675) Use ofbizCurrency macro and remove hardcoded ##0.00 string
[ https://issues.apache.org/jira/browse/OFBIZ-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-9675: -- Assignee: Jacques Le Roux (was: Ritesh Kumar) > Use ofbizCurrency macro and remove hardcoded ##0.00 string > -- > > Key: OFBIZ-9675 > URL: https://issues.apache.org/jira/browse/OFBIZ-9675 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-9675 > > > ofbizAmount macro can be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10017) Alignment Issue on Variant product view page
[ https://issues.apache.org/jira/browse/OFBIZ-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana Asthana updated OFBIZ-10017: Attachment: AlignmentIssueInVariantProduct.jpg > Alignment Issue on Variant product view page > > > Key: OFBIZ-10017 > URL: https://issues.apache.org/jira/browse/OFBIZ-10017 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Archana Asthana > Attachments: AlignmentIssueInVariantProduct.jpg > > > Steps to Regenerate: > 1. Open https://demo-trunk.ofbiz.apache.org/ecommerce/control/main > 2. Go to Featured Products section > 3. Open any Product with Variants > Actual: > The Images are not aligned on the page > The Image is attached for reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10017) Alignment Issue on Variant product view page
Archana Asthana created OFBIZ-10017: --- Summary: Alignment Issue on Variant product view page Key: OFBIZ-10017 URL: https://issues.apache.org/jira/browse/OFBIZ-10017 Project: OFBiz Issue Type: Bug Components: ecommerce Reporter: Archana Asthana Steps to Regenerate: 1. Open https://demo-trunk.ofbiz.apache.org/ecommerce/control/main 2. Go to Featured Products section 3. Open any Product with Variants Actual: The Images are not aligned on the page The Image is attached for reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265699#comment-16265699 ] Suraj Khurana commented on OFBIZ-9980: -- Thanks, Jacques and Pierre for your comments. Yes, this is just the start of this implementation, we can start by having a support in services and further on need to have support to pass latitude and longitude from screens, forms by some API (Maybe Google Map API or something similar) Hope that also looks good to you as well. > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9896) Incorrect success message after creating prospect
[ https://issues.apache.org/jira/browse/OFBIZ-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lalit Dashora reassigned OFBIZ-9896: Assignee: (was: Lalit Dashora) > Incorrect success message after creating prospect > - > > Key: OFBIZ-9896 > URL: https://issues.apache.org/jira/browse/OFBIZ-9896 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: OFBIZ-9896-Incorrect-Success-Message.patch > > > Navigate to > [NewProspect|https://demo-trunk.ofbiz.apache.org/partymgr/control/NewProspect], > after creating the prospect, success message 'ProductStoreRole is created > successfully'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9896) Incorrect success message after creating prospect
[ https://issues.apache.org/jira/browse/OFBIZ-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265698#comment-16265698 ] Lalit Dashora commented on OFBIZ-9896: -- Hi [~sonal.patwari], I have fixed the reported issue. Please find the attached patch. Thanks! > Incorrect success message after creating prospect > - > > Key: OFBIZ-9896 > URL: https://issues.apache.org/jira/browse/OFBIZ-9896 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Lalit Dashora > Attachments: OFBIZ-9896-Incorrect-Success-Message.patch > > > Navigate to > [NewProspect|https://demo-trunk.ofbiz.apache.org/partymgr/control/NewProspect], > after creating the prospect, success message 'ProductStoreRole is created > successfully'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10016) Update markup of Login page according to standard markup given by Bootstrap v4.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parakh Maheshwari reassigned OFBIZ-10016: - Assignee: Parakh Maheshwari > Update markup of Login page according to standard markup given by Bootstrap > v4.0.0 > -- > > Key: OFBIZ-10016 > URL: https://issues.apache.org/jira/browse/OFBIZ-10016 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Reporter: Parakh Maheshwari >Assignee: Parakh Maheshwari > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9977) While creating return fin account used currency must be same
[ https://issues.apache.org/jira/browse/OFBIZ-9977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-9977: - Assignee: Akash Jain (was: Suraj Khurana) > While creating return fin account used currency must be same > > > Key: OFBIZ-9977 > URL: https://issues.apache.org/jira/browse/OFBIZ-9977 > Project: OFBiz > Issue Type: Bug >Reporter: Suraj Khurana >Assignee: Akash Jain > Attachments: OFBIZ-9977.patch > > > While creating a return, return currency must be similar to finAccount > currency used to credit return amount in processCreditReturn service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9971) Inventory transfer creates unnecessary record with 0
[ https://issues.apache.org/jira/browse/OFBIZ-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265697#comment-16265697 ] Pierre Smits commented on OFBIZ-9971: - An inventory transfer (between 2 locations) can be broken down into multiple transactions (physical and accounting - financial - related). The accounting transaction(s) should always have two records: # one for the location where it is transferred from, e.g.: 1221 Goods in transfer +1000 3001 Inventory Location X -1000 # one for the location where it is transferred into, e.g.: 3002 Inventory Location Y +1000 1221 Goods in transfer - 1000 > Inventory transfer creates unnecessary record with 0 > > > Key: OFBIZ-9971 > URL: https://issues.apache.org/jira/browse/OFBIZ-9971 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Suraj Khurana >Assignee: Akash Jain > Fix For: 16.11.04 > > Attachments: OFBIZ-9971.patch > > > While using inventory transfer for a product having multiple inventory items, > it creates an unnecessary record with 0 transfer quantity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9896) Incorrect success message after creating prospect
[ https://issues.apache.org/jira/browse/OFBIZ-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lalit Dashora updated OFBIZ-9896: - Attachment: OFBIZ-9896-Incorrect-Success-Message.patch > Incorrect success message after creating prospect > - > > Key: OFBIZ-9896 > URL: https://issues.apache.org/jira/browse/OFBIZ-9896 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Lalit Dashora > Attachments: OFBIZ-9896-Incorrect-Success-Message.patch > > > Navigate to > [NewProspect|https://demo-trunk.ofbiz.apache.org/partymgr/control/NewProspect], > after creating the prospect, success message 'ProductStoreRole is created > successfully'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10016) Update markup of Login page according to standard markup given by Bootstrap v4.0.0
Parakh Maheshwari created OFBIZ-10016: - Summary: Update markup of Login page according to standard markup given by Bootstrap v4.0.0 Key: OFBIZ-10016 URL: https://issues.apache.org/jira/browse/OFBIZ-10016 Project: OFBiz Issue Type: Sub-task Reporter: Parakh Maheshwari -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9971) Inventory transfer creates unnecessary record with 0
[ https://issues.apache.org/jira/browse/OFBIZ-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain closed OFBIZ-9971. - > Inventory transfer creates unnecessary record with 0 > > > Key: OFBIZ-9971 > URL: https://issues.apache.org/jira/browse/OFBIZ-9971 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Suraj Khurana >Assignee: Akash Jain > Fix For: 16.11.04 > > Attachments: OFBIZ-9971.patch > > > While using inventory transfer for a product having multiple inventory items, > it creates an unnecessary record with 0 transfer quantity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9971) Inventory transfer creates unnecessary record with 0
[ https://issues.apache.org/jira/browse/OFBIZ-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain updated OFBIZ-9971: -- Affects Version/s: Trunk Release Branch 16.11 > Inventory transfer creates unnecessary record with 0 > > > Key: OFBIZ-9971 > URL: https://issues.apache.org/jira/browse/OFBIZ-9971 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Suraj Khurana >Assignee: Akash Jain > Fix For: 16.11.04 > > Attachments: OFBIZ-9971.patch > > > While using inventory transfer for a product having multiple inventory items, > it creates an unnecessary record with 0 transfer quantity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9894) Dropdown dependent mechanism should be there while selecting any Sales Forecast detail
[ https://issues.apache.org/jira/browse/OFBIZ-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar reassigned OFBIZ-9894: --- Assignee: Ritesh Kumar > Dropdown dependent mechanism should be there while selecting any Sales > Forecast detail > -- > > Key: OFBIZ-9894 > URL: https://issues.apache.org/jira/browse/OFBIZ-9894 > Project: OFBiz > Issue Type: Bug >Reporter: Sonal Patwari >Assignee: Ritesh Kumar > > Navigate to SFA component and on Sales Forecast screen, after creating a > forecast when we add forecast details, it allows us to add any of the fields > separately without depending on the other fields. > Expected result: There should be a dependency while selecting forecast > details. > For example, While adding quantity, quantity UOM field should be dependent > and vice versa should also be possible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9998) Remove paymentId, orderId and orderItemSeqId from finAccountTrans entity
[ https://issues.apache.org/jira/browse/OFBIZ-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265693#comment-16265693 ] Jacques Le Roux commented on OFBIZ-9998: I agree, a small summary would be appreciated > Remove paymentId, orderId and orderItemSeqId from finAccountTrans entity > > > Key: OFBIZ-9998 > URL: https://issues.apache.org/jira/browse/OFBIZ-9998 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Vaibhav Jain >Assignee: Ayushi Rathod > > As per the discussion int respective mail thread > [http://ofbiz.markmail.org/message/i2wk2anzrhacbltq?q=%5BPROPOSAL%5D+Extend+returnId+and+shipmentId+in+FinAccountTrans+entity] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265691#comment-16265691 ] Pierre Smits commented on OFBIZ-9980: - Great to know that we *can* do this. But is it something that we *want* to have OOTB and as a default feature regarding the (physical/postal/etc. address) contact mechs? While reviewing the patch, I see only changes to services? I have the feeling that this is just 1 part of a greater set. I wonder what else is needed. > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9998) Remove paymentId, orderId and orderItemSeqId from finAccountTrans entity
[ https://issues.apache.org/jira/browse/OFBIZ-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265688#comment-16265688 ] Pierre Smits commented on OFBIZ-9998: - I feel it is a pity that the gist of the discussions is not captured in the description of this ticket. And that a reference to a thread seems to be sufficient. So, it is expected that # the developer will ## go through the discussion(s), ## extract the final actionable items (that have the consensus of the community), ## implement the changes; # any reviewer will ## go through the discussions(s), ## extract the final actionable items (that have the consensus of the community) ## review the implemented changes This will introduce a lot of of risk points leading failure. > Remove paymentId, orderId and orderItemSeqId from finAccountTrans entity > > > Key: OFBIZ-9998 > URL: https://issues.apache.org/jira/browse/OFBIZ-9998 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Vaibhav Jain >Assignee: Ayushi Rathod > > As per the discussion int respective mail thread > [http://ofbiz.markmail.org/message/i2wk2anzrhacbltq?q=%5BPROPOSAL%5D+Extend+returnId+and+shipmentId+in+FinAccountTrans+entity] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9675) Use ofbizCurrency macro and remove hardcoded ##0.00 string
[ https://issues.apache.org/jira/browse/OFBIZ-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265687#comment-16265687 ] Ritesh Kumar edited comment on OFBIZ-9675 at 11/25/17 12:17 PM: This patch is applicable to both trunk and 16.11. Replaced the hardcoded usages of ##0.00 with ofbizAmount macro. ##0.00 is used for default decimal format for currency. was (Author: ritesh.kumar): This patch is applicable to both trunk and 16.11. > Use ofbizCurrency macro and remove hardcoded ##0.00 string > -- > > Key: OFBIZ-9675 > URL: https://issues.apache.org/jira/browse/OFBIZ-9675 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-9675 > > > ofbizAmount macro can be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9675) Use ofbizCurrency macro and remove hardcoded ##0.00 string
[ https://issues.apache.org/jira/browse/OFBIZ-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar updated OFBIZ-9675: Attachment: OFBIZ-9675 This patch is applicable to both trunk and 16.11. > Use ofbizCurrency macro and remove hardcoded ##0.00 string > -- > > Key: OFBIZ-9675 > URL: https://issues.apache.org/jira/browse/OFBIZ-9675 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-9675 > > > ofbizAmount macro can be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10011) Update markup of Home page according to standard markup given by Bootstrap v4.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Dixit reassigned OFBIZ-10011: - Assignee: Saurabh Dixit > Update markup of Home page according to standard markup given by Bootstrap > v4.0.0 > - > > Key: OFBIZ-10011 > URL: https://issues.apache.org/jira/browse/OFBIZ-10011 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Reporter: Mayank Lambhate >Assignee: Saurabh Dixit > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[
https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265685#comment-16265685
]
Pierre Smits commented on OFBIZ-3894:
-
HI [~swapnilmmane], all,
All good suggestions.
{quote}I would suggest, we should go in baby steps for implementing this by
creating sub tickets. This will be helpful for reviewing and reduce the chances
of breaking anything.
We can follow proceed with these steps{quote}
Baby steps can be initiated, traced, and concluded through sub-tasks.
{quote}1.) Entity related changes
Update the existing entities by adding new required attributes.
(We will remove the unused fields in the 4rth step){quote}
Per entity a list of (intended) additions, and a list of (intended) removals
will help regarding communications about future release plans, releases,
impact, etc.
{quote}e.g. ProductStoreEmailSetting will have following more attributes
emailTemplateSettingId
fromDate
thruDate
{quote}
The discussion on adding lifespan fields (fromDate and thruDate) to various
entities was already started back in January /2015. It is good to see that it
is still alive. See:
* http://ofbiz.markmail.org/search/?q=lifespan%20field
* https://issues.apache.org/jira/issues/?jql=text%20~%20%22lifespan%22
{quote}4.) Will remove the unused fields from the entity. {quote}
See my comment regarding the quote #1
{quote}5.) Document the migration steps.{quote}
Great to see that this is an integral part of the total implementation. Would
love to see that in place, before mere entity and code changes are released to
adopters.
> Refactor Email handling
> ---
>
> Key: OFBIZ-3894
> URL: https://issues.apache.org/jira/browse/OFBIZ-3894
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: BJ Freeman
>Assignee: Erwan de FERRIERES
>Priority: Minor
> Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch,
> OFBIZ-3894.patch
>
> Original Estimate: 1,344h
> Remaining Estimate: 1,344h
>
> with the addition of the Website for each component
> 1) create product store for Order entry, or use the B2C product store.
> 2) move the email widgets from ecommerce to order compontent.
> 3) modify the seed data so that Order entry has it own emails from order
> component.this would be to add emails to
> note: as I go through the different items this is turning out to be a bigger
> project than I first anticipated.
> so consider this so far just ideas.
> Maybe break down in to small tasks as I have time to do something.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OFBIZ-6091) Supplier preferred currency not considered for drop-ship order
[ https://issues.apache.org/jira/browse/OFBIZ-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6091. -- Resolution: Invalid > Supplier preferred currency not considered for drop-ship order > -- > > Key: OFBIZ-6091 > URL: https://issues.apache.org/jira/browse/OFBIZ-6091 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 14.12, Trunk, 13.07.01 >Reporter: Akash Jain >Assignee: Mridul Pathak > Attachments: OFBIZ-6091.patch > > > Place sales order with a supplier for drop-ship then supplier preferred > currency not considered. To generate issue, follow these steps: > # Go to Order > Order Entry and initiate sales order. > # Select USD currency. > # Add product and quantity, then click the Add to Order button. > # Item will be added in the shopping cart, click the Finalize Order tab. > # Select supplier which have EUR preferred currency, and supply the product > (added in shopping cart) in EUR currency only. Make sure quantity of added > product in the shopping cart is equals / greater then to supplier minimum > order quantity of same product. > # Finally place the order. > Expected Result: > Drop-ship (PO) order should be generated for the sales order item. > Actual Result: > Drop-ship (PO) order not created and getting this error on console, > = > Error in Service [checkCreateDropShipPurchaseOrders]: The following error > occurred creating drop shipments for order WSCO10180: SupplierProduct not > found > = -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (OFBIZ-6091) Supplier preferred currency not considered for drop-ship order
[ https://issues.apache.org/jira/browse/OFBIZ-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-6091: > Supplier preferred currency not considered for drop-ship order > -- > > Key: OFBIZ-6091 > URL: https://issues.apache.org/jira/browse/OFBIZ-6091 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 14.12, Trunk, 13.07.01 >Reporter: Akash Jain >Assignee: Mridul Pathak > Fix For: 14.12.01, 12.04.06, 13.07.03, 16.11.01 > > Attachments: OFBIZ-6091.patch > > > Place sales order with a supplier for drop-ship then supplier preferred > currency not considered. To generate issue, follow these steps: > # Go to Order > Order Entry and initiate sales order. > # Select USD currency. > # Add product and quantity, then click the Add to Order button. > # Item will be added in the shopping cart, click the Finalize Order tab. > # Select supplier which have EUR preferred currency, and supply the product > (added in shopping cart) in EUR currency only. Make sure quantity of added > product in the shopping cart is equals / greater then to supplier minimum > order quantity of same product. > # Finally place the order. > Expected Result: > Drop-ship (PO) order should be generated for the sales order item. > Actual Result: > Drop-ship (PO) order not created and getting this error on console, > = > Error in Service [checkCreateDropShipPurchaseOrders]: The following error > occurred creating drop shipments for order WSCO10180: SupplierProduct not > found > = -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265669#comment-16265669 ] Michael Brohl commented on OFBIZ-3894: -- Hi folks, thanks for your work on this. For better review, can someone please lay out the complete new mechanism/changes? From the past discussions, I'm not sure what the final plan will be. Thanks and regards, Michael > Refactor Email handling > --- > > Key: OFBIZ-3894 > URL: https://issues.apache.org/jira/browse/OFBIZ-3894 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: BJ Freeman >Assignee: Erwan de FERRIERES >Priority: Minor > Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch, > OFBIZ-3894.patch > > Original Estimate: 1,344h > Remaining Estimate: 1,344h > > with the addition of the Website for each component > 1) create product store for Order entry, or use the B2C product store. > 2) move the email widgets from ecommerce to order compontent. > 3) modify the seed data so that Order entry has it own emails from order > component.this would be to add emails to > note: as I go through the different items this is turning out to be a bigger > project than I first anticipated. > so consider this so far just ideas. > Maybe break down in to small tasks as I have time to do something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265665#comment-16265665 ] Jacques Le Roux commented on OFBIZ-9980: Ah found also this good old one OFBIZ-5453 just for the fun :) > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10000) Remove occurrences of all deprecated delegator methods by EntityQuery methods
[ https://issues.apache.org/jira/browse/OFBIZ-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265664#comment-16265664 ] Jacques Le Roux commented on OFBIZ-1: - Hèè 1 !!! we did not celebrate :) > Remove occurrences of all deprecated delegator methods by EntityQuery methods > - > > Key: OFBIZ-1 > URL: https://issues.apache.org/jira/browse/OFBIZ-1 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Reporter: Suraj Khurana >Assignee: Suraj Khurana > > There are some console warnings as well regarding this. Replace all > occurrences of such methods by EntityQuery methods. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9990) The main logo in screen upper part shows distorted
[ https://issues.apache.org/jira/browse/OFBIZ-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-9990: --- Summary: The main logo in screen upper part shows distorted (was: The main logo in screen upper part shows distorted with Tomahawk theme) > The main logo in screen upper part shows distorted > -- > > Key: OFBIZ-9990 > URL: https://issues.apache.org/jira/browse/OFBIZ-9990 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: Image 004.png, Image 005.png > > > This is easily checked on trunk demo using > https://demo-trunk.ofbiz.apache.org/catalog/control/main?USERNAME=admin&PASSWORD=ofbiz&JavaScriptEnabled=Y > and Tomahawk theme -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9971) Inventory transfer creates unnecessary record with 0
[ https://issues.apache.org/jira/browse/OFBIZ-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-9971: - Assignee: Akash Jain (was: Suraj Khurana) > Inventory transfer creates unnecessary record with 0 > > > Key: OFBIZ-9971 > URL: https://issues.apache.org/jira/browse/OFBIZ-9971 > Project: OFBiz > Issue Type: Bug >Reporter: Suraj Khurana >Assignee: Akash Jain > Attachments: OFBIZ-9971.patch > > > While using inventory transfer for a product having multiple inventory items, > it creates an unnecessary record with 0 transfer quantity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9987) Enable drop ship PO if 'Drop-ship Only' property is set at Product Store level.
[ https://issues.apache.org/jira/browse/OFBIZ-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain reassigned OFBIZ-9987: - Assignee: Akash Jain > Enable drop ship PO if 'Drop-ship Only' property is set at Product Store > level. > --- > > Key: OFBIZ-9987 > URL: https://issues.apache.org/jira/browse/OFBIZ-9987 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Akash Jain > Fix For: Trunk > > Attachments: OFBIZ-9987.patch > > > Current: > For drop shipment process, cart method 'createDropShipGroups' only check > requirementMethodEnumId at Facility Level and Product level. Also, found the > unhandled case of not considering requirementMethodEnumId at Product Level if > this property found at Facility level. > Expected : > RequirementMethodEnumId should be decided in the order of property set at > ProductStore -> Facility -> Product. > Check and enable drop ship PO if 'Drop-ship Only' property is set at Store > level. Also, this property should be checked and override at Facility level > if exists to consider the case when Facility does not allow drop ship Order. > Finally, it should be checked at Product level to consider the case when > Store and Facility allow for drop ship but the product does not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-10005) Broken screen while performing find operation on 'MarketingCampaignAndVisit' entity from webtools
[ https://issues.apache.org/jira/browse/OFBIZ-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-10005. Resolution: Not A Problem Fix Version/s: (was: Trunk) > Broken screen while performing find operation on 'MarketingCampaignAndVisit' > entity from webtools > - > > Key: OFBIZ-10005 > URL: https://issues.apache.org/jira/browse/OFBIZ-10005 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Pradeep Choudhary >Assignee: Rohit Rai >Priority: Blocker > Attachments: EnityFindOperatioError.png > > > Steps to regenerate: > 1. Ope URL > [https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=MarketingCampaignAndVisit] > 2. Perform find operation on given entity with empty fields. > 3. Broken Screen appears. (Please find the attached screenshot) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265658#comment-16265658 ] Jacques Le Roux commented on OFBIZ-9760: Thanks Guys, looks really better :) > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderAfterBootstrapIntegration.png, HeaderBeforeBootstrapIntegration.png, > OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Footer.patch, > OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9990) The main logo in screen upper part shows distorted with Tomahawk theme
[ https://issues.apache.org/jira/browse/OFBIZ-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265657#comment-16265657 ] Jacques Le Roux commented on OFBIZ-9990: Actually the image used there and in many other places is !https://demo-trunk.ofbiz.apache.org/images/ofbiz_logo.gif! Note that it contains "Open For Business" project when we decided to ban this mention and alway rather use OFBiz. Should we continue to use this image? > The main logo in screen upper part shows distorted with Tomahawk theme > -- > > Key: OFBIZ-9990 > URL: https://issues.apache.org/jira/browse/OFBIZ-9990 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: Image 004.png, Image 005.png > > > This is easily checked on trunk demo using > https://demo-trunk.ofbiz.apache.org/catalog/control/main?USERNAME=admin&PASSWORD=ofbiz&JavaScriptEnabled=Y > and Tomahawk theme -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265653#comment-16265653 ] Swapnil M Mane commented on OFBIZ-3894: --- Thanks gentlemen for such a nice discussion and [~soledad] for the patch (very good work) I would suggest, we should go in baby steps for implementing this by creating sub tickets. This will be helpful for reviewing and reduce the chances of breaking anything. We can follow proceed with these steps 1.) Entity related changes Update the existing entities by adding new required attributes. (We will remove the unused fields in the 4rth step) e.g. ProductStoreEmailSetting will have following more attributes emailTemplateSettingId fromDate thruDate 2.) Create the new screens to manage the product store's mail setting as per our new model. 3.) Update the all the send mail services to honor our new model. 4.) Will remove the unused fields from the entity. 5.) Document the migration steps. The plan is first we will prepare all the things required for our implementation, which will not break anything. Then finally improve the send mail services code. Please let me know your thoughts this. Thanks! > Refactor Email handling > --- > > Key: OFBIZ-3894 > URL: https://issues.apache.org/jira/browse/OFBIZ-3894 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: BJ Freeman >Assignee: Erwan de FERRIERES >Priority: Minor > Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch, > OFBIZ-3894.patch > > Original Estimate: 1,344h > Remaining Estimate: 1,344h > > with the addition of the Website for each component > 1) create product store for Order entry, or use the B2C product store. > 2) move the email widgets from ecommerce to order compontent. > 3) modify the seed data so that Order entry has it own emails from order > component.this would be to add emails to > note: as I go through the different items this is turning out to be a bigger > project than I first anticipated. > so consider this so far just ideas. > Maybe break down in to small tasks as I have time to do something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10007) Party Classification Groups are not listing on FindParty screen.
[ https://issues.apache.org/jira/browse/OFBIZ-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10007: - Attachment: OFBIZ-10007.patch Fixed issue in which classification is not listed in the dropdown. First value is undefined in the list, this is because of asmSelect Jquery which will cover in another ticket. > Party Classification Groups are not listing on FindParty screen. > > > Key: OFBIZ-10007 > URL: https://issues.apache.org/jira/browse/OFBIZ-10007 > Project: OFBiz > Issue Type: Bug > Components: party >Reporter: Sonal Patwari >Assignee: Aman Agrawal > Attachments: FindPartyPageClassificationGroupsNotListing.png, > OFBIZ-10007.patch > > > - Navigate to [Find > Party|https://demo-trunk.ofbiz.apache.org/partymgr/control/findparty] Screen. > - Check Classification group dropdown > List is empty.. > - Refer attached screenshot for more clarity of the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-9980: -- Assignee: Suraj Khurana (was: Jacques Le Roux) > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265651#comment-16265651 ] Jacques Le Roux commented on OFBIZ-9980: Hi Suraj, After review, sounds good to me, but should we not also update screens for creation/update of postal addresses? > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Jacques Le Roux > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10015) Unable to create inventory item label
[ https://issues.apache.org/jira/browse/OFBIZ-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priya Sharma updated OFBIZ-10015: - Attachment: Screenshot from 2017-11-25 15-03-57.png Screenshot Attached > Unable to create inventory item label > - > > Key: OFBIZ-10015 > URL: https://issues.apache.org/jira/browse/OFBIZ-10015 > Project: OFBiz > Issue Type: Bug >Reporter: Priya Sharma > Fix For: Trunk > > Attachments: Screenshot from 2017-11-25 15-03-57.png > > > 1) Navigate to > [https://demo-trunk.ofbiz.apache.org/facility/control/createInventoryItemLabel] > 2) Try to create a new record. > 3) No value is shown in the drop-down for the inventory item label type field. > thus an exception is thrown by the service. > Info: There is no data in the InventoryItemLabelType entity, I believe that > is the cause of this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9905) Issue with Agreement under Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aayush jain updated OFBIZ-9905: --- Description: Following issues found: 1. Create Agreement opens an edit agreement window 2. Able to Create Agreement without any detail (empty Agreement) Steps: 1. Open URL https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement 2. Navigate to Agreement section 3. Click on create Agreement 4. Click submit button Actual: Agreement id is generated for empty agreement and when create window opens, it's redirection is wrong to edit window Expected: Proper redirection should be there (create agreement) and if an agreement is created without any details its of no use. Note: Same Issue exist with following screens: 1. Billing Account 2. Tax Authority 3. Agreement 4. Fixed Asset 5. Vendor 6. WebSite 7. Blog 8. Employment 9. Employee Position 10.Performance Review 11.Job Requisition 12. Party Resume was: Following issues found: 1. Create Agreement opens an edit agreement window 2. Able to Create Agreement without any detail (empty Agreement) Steps: 1. Open URL https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement 2. Navigate to Agreement section 3. Click on create Agreement 4. Click submit button Actual: Agreement id is generated for empty agreement and when create window opens, it's redirection is wrong to edit window Expected: Proper redirection should be there (create agreement) and if an agreement is created without any details its of no use. > Issue with Agreement under Accounting > - > > Key: OFBIZ-9905 > URL: https://issues.apache.org/jira/browse/OFBIZ-9905 > Project: OFBiz > Issue Type: Bug > Environment: > https://demo-trunk.ofbiz.apache.org/accounting/control/EditAgreement >Reporter: Aayush jain >Assignee: sourabh jain > Attachments: UI_label .png > > > Following issues found: > 1. Create Agreement opens an edit agreement window > 2. Able to Create Agreement without any detail (empty Agreement) > Steps: > 1. Open URL > https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement > 2. Navigate to Agreement section > 3. Click on create Agreement > 4. Click submit button > Actual: Agreement id is generated for empty agreement and when create window > opens, it's redirection is wrong to edit window > Expected: Proper redirection should be there (create agreement) and if an > agreement is created without any details its of no use. > Note: Same Issue exist with following screens: > 1. Billing Account > 2. Tax Authority > 3. Agreement > 4. Fixed Asset > 5. Vendor > 6. WebSite > 7. Blog > 8. Employment > 9. Employee Position > 10.Performance Review > 11.Job Requisition > 12. Party Resume -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10015) Unable to create inventory item label
Priya Sharma created OFBIZ-10015: Summary: Unable to create inventory item label Key: OFBIZ-10015 URL: https://issues.apache.org/jira/browse/OFBIZ-10015 Project: OFBiz Issue Type: Bug Reporter: Priya Sharma Fix For: Trunk 1) Navigate to [https://demo-trunk.ofbiz.apache.org/facility/control/createInventoryItemLabel] 2) Try to create a new record. 3) No value is shown in the drop-down for the inventory item label type field. thus an exception is thrown by the service. Info: There is no data in the InventoryItemLabelType entity, I believe that is the cause of this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10014) Error while adding the product to the order
[ https://issues.apache.org/jira/browse/OFBIZ-10014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garima jain updated OFBIZ-10014: Attachment: order.png > Error while adding the product to the order > > > Key: OFBIZ-10014 > URL: https://issues.apache.org/jira/browse/OFBIZ-10014 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Garima jain > Attachments: order.png > > > Steps to Generate the Issue. > 1. Navigate to[ > https://demo-trunk.ofbiz.apache.org/ordermgr/control/orderentry] > 2. Click on Quick LookUp button and select a product (cap,dvd) and click on > 'Add To Order' button. > Actual: Error occurred > Expected: The product should be added to the order. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10014) Error while adding the product to the order
Garima jain created OFBIZ-10014: --- Summary: Error while adding the product to the order Key: OFBIZ-10014 URL: https://issues.apache.org/jira/browse/OFBIZ-10014 Project: OFBiz Issue Type: Bug Components: order Reporter: Garima jain Steps to Generate the Issue. 1. Navigate to[ https://demo-trunk.ofbiz.apache.org/ordermgr/control/orderentry] 2. Click on Quick LookUp button and select a product (cap,dvd) and click on 'Add To Order' button. Actual: Error occurred Expected: The product should be added to the order. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10005) Broken screen while performing find operation on 'MarketingCampaignAndVisit' entity from webtools
[ https://issues.apache.org/jira/browse/OFBIZ-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265642#comment-16265642 ] Deepak Dixit commented on OFBIZ-10005: -- Hi Pradeep, When you use group by and function in sql you need to pass field to select while query for accurate result. But in case of webtools find view all field pass as field to select and it does not return correct result but it will working fine if you use this correctly in your code. I think we can close this as not a problem > Broken screen while performing find operation on 'MarketingCampaignAndVisit' > entity from webtools > - > > Key: OFBIZ-10005 > URL: https://issues.apache.org/jira/browse/OFBIZ-10005 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Pradeep Choudhary >Assignee: Rohit Rai >Priority: Blocker > Fix For: Trunk > > Attachments: EnityFindOperatioError.png > > > Steps to regenerate: > 1. Ope URL > [https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=MarketingCampaignAndVisit] > 2. Perform find operation on given entity with empty fields. > 3. Broken Screen appears. (Please find the attached screenshot) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9697) Create Related Account from Contact Profile redirect to empty profile screen.
[ https://issues.apache.org/jira/browse/OFBIZ-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain updated OFBIZ-9697: -- Affects Version/s: 16.11.04 > Create Related Account from Contact Profile redirect to empty profile screen. > - > > Key: OFBIZ-9697 > URL: https://issues.apache.org/jira/browse/OFBIZ-9697 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, 16.11.04 >Reporter: Ankit Joshi >Assignee: Akash Jain > Labels: sfa > Fix For: 16.11.04 > > Attachments: OFBIZ-9697.patch > > > Steps to Regenerate - > 1) Navigate to SFA and search for contacts. > 2) Move to Contact Profile detail screen. > 3) Click on Create New button to create Related Accounts for the Contact. > Actual: It redirects to the empty profile screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9697) Create Related Account from Contact Profile redirect to empty profile screen.
[ https://issues.apache.org/jira/browse/OFBIZ-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain closed OFBIZ-9697. - > Create Related Account from Contact Profile redirect to empty profile screen. > - > > Key: OFBIZ-9697 > URL: https://issues.apache.org/jira/browse/OFBIZ-9697 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, 16.11.04 >Reporter: Ankit Joshi >Assignee: Akash Jain > Labels: sfa > Fix For: 16.11.04 > > Attachments: OFBIZ-9697.patch > > > Steps to Regenerate - > 1) Navigate to SFA and search for contacts. > 2) Move to Contact Profile detail screen. > 3) Click on Create New button to create Related Accounts for the Contact. > Actual: It redirects to the empty profile screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265640#comment-16265640 ] Deepak Dixit commented on OFBIZ-9760: - Thanks Mayank, Parakh, Saurabh and Nitish for your contribution. OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Header.patch, and OFBIZ-9760-Footer.patch has been committed at ofbiz plugins trunk at r#1816274 and ofbiz_logo.png has been committed at r#1816275 > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderAfterBootstrapIntegration.png, HeaderBeforeBootstrapIntegration.png, > OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Footer.patch, > OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9849) Replace Inline js with External js in renderDropDownField macro
[ https://issues.apache.org/jira/browse/OFBIZ-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Wagela reassigned OFBIZ-9849: Assignee: Dhaval Wagela > Replace Inline js with External js in renderDropDownField macro > --- > > Key: OFBIZ-9849 > URL: https://issues.apache.org/jira/browse/OFBIZ-9849 > Project: OFBiz > Issue Type: Sub-task >Reporter: Aditya Sharma >Assignee: Dhaval Wagela >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10004) Error in Create Billing Account from Party Profile
[ https://issues.apache.org/jira/browse/OFBIZ-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265639#comment-16265639 ] Garima jain commented on OFBIZ-10004: - This Process is working as expected according to the given flow. If there is some other case in which billing account not created, then please mention. > Error in Create Billing Account from Party Profile > -- > > Key: OFBIZ-10004 > URL: https://issues.apache.org/jira/browse/OFBIZ-10004 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Release Branch 16.11 >Reporter: Mohammad Kathawala >Assignee: Garima jain > > Steps to generate: > 1) Go to Create Billing Account from Party Profile. > 2) Fill the form and click on save. It will give an error of request not > found. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10004) Error in Create Billing Account from Party Profile
[ https://issues.apache.org/jira/browse/OFBIZ-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garima jain reassigned OFBIZ-10004: --- Assignee: Garima jain > Error in Create Billing Account from Party Profile > -- > > Key: OFBIZ-10004 > URL: https://issues.apache.org/jira/browse/OFBIZ-10004 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Release Branch 16.11 >Reporter: Mohammad Kathawala >Assignee: Garima jain > > Steps to generate: > 1) Go to Create Billing Account from Party Profile. > 2) Fill the form and click on save. It will give an error of request not > found. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10013) Screen Rendering issue on Payment Overview screen
Pritam Kute created OFBIZ-10013: --- Summary: Screen Rendering issue on Payment Overview screen Key: OFBIZ-10013 URL: https://issues.apache.org/jira/browse/OFBIZ-10013 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Release Branch 16.11, Trunk Reporter: Pritam Kute Steps to regenerate are - 1. Go to https://demo-trunk.ofbiz.apache.org/accounting/control/main 2. Click on "show all payment" payments. 3. Select any payment of type "Customer Payment" and click on it to go to overview screen 4. On overview screen click on the button "Acctg Trans Entries PDF" Result: Actual: The broken screen Should be the PDF with account transaction entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Dixit updated OFBIZ-9760: - Attachment: (was: OFBIZ-9760-Bootstrap-Library.patch) > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderAfterBootstrapIntegration.png, HeaderBeforeBootstrapIntegration.png, > OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Footer.patch, > OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Dixit updated OFBIZ-9760: - Attachment: OFBIZ-9760-Bootstrap-Library.patch > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderAfterBootstrapIntegration.png, HeaderBeforeBootstrapIntegration.png, > OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Footer.patch, > OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-10012: -- Description: Steps to reproduce: 1. Go to [Content Component|https://demo-trunk.ofbiz.apache.org/content/control/main] 2. Click on Content from [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. 3. Click on the Advanced Search button [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. 4. Provide Content Id. 5. User should be able to see the alert message. 6. For reference screenshot is attached. was: Steps to reproduce: 1. Go to [Content Component|https://demo-trunk.ofbiz.apache.org/content/control/main] 2. Click on Content from [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. 3. Click on the Advanced Search button [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. 4. Provide Content Id. 5. User should be able to see the alert message. > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. > 6. For reference screenshot is attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonal Patwari updated OFBIZ-10012: -- Attachment: ContentSearchOptionsAlertShowing (1).png > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-9980: -- Assignee: Jacques Le Roux (was: Suraj Khurana) > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Jacques Le Roux > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9908) Quick Add button for shopping list on Orderentry screen is not working
[ https://issues.apache.org/jira/browse/OFBIZ-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265637#comment-16265637 ] Jacques Le Roux commented on OFBIZ-9908: Hi, This is an old bug also reproductible on old demo (that we now longer support, just to say), thanks! > Quick Add button for shopping list on Orderentry screen is not working > -- > > Key: OFBIZ-9908 > URL: https://issues.apache.org/jira/browse/OFBIZ-9908 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Garima jain >Assignee: Yogesh Naroliya >Priority: Minor > > steps to generate > 1. Navigate to https://demo-trunk.ofbiz.apache.org/ordermgr/control/orderentry > 2. Press continue on sales order screen. > 3. Add any finished good product to the sales order > 4. In 'Add Order Items to Shopping List' section, select 'new shopping list' > from the drop down and click on 'Add to shopping list' button > 5. you navigate to 'addBulkToShoppingList' screen, click on 'Quick Add' > button. > Issue: The quick add button is not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
Sonal Patwari created OFBIZ-10012: - Summary: Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup Key: OFBIZ-10012 URL: https://issues.apache.org/jira/browse/OFBIZ-10012 Project: OFBiz Issue Type: Bug Components: content Affects Versions: Trunk Reporter: Sonal Patwari Steps to reproduce: 1. Go to [Content Component|https://demo-trunk.ofbiz.apache.org/content/control/main] 2. Click on Content from [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. 3. Click on the Advanced Search button [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. 4. Provide Content Id. 5. User should be able to see the alert message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10005) Broken screen while performing find operation on 'MarketingCampaignAndVisit' entity from webtools
[ https://issues.apache.org/jira/browse/OFBIZ-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265636#comment-16265636 ] Rohit Rai commented on OFBIZ-10005: --- Hi, I found that a similar error is thrown on performing search on many other view entities as well. For example, CommunicationEventSum, MarketingCampaignAndOrderHeader, TrackingCodeAndOrderHeader and many more. A similar pattern is followed while creating these views, we have used group-by="true" for one of the columns of the view entity and group-by="false" for one other column. For instance, marketingCampaignId is used to group by the results while fromDate is not included in the group by. We can't have items in the select that are not in the group by unless we are going to use a summary function on them. If we group by id we are collapsing all rows with the same id into one row, if we want other columns to be presented we must perform an aggregate function on them or we can group by with more than one column. For the view definition, modifying the value of group-by="true" for the from date will fix the issue. But, I am not sure why we used group-by="false" with the date in the first place, I am looking into it. > Broken screen while performing find operation on 'MarketingCampaignAndVisit' > entity from webtools > - > > Key: OFBIZ-10005 > URL: https://issues.apache.org/jira/browse/OFBIZ-10005 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Pradeep Choudhary >Assignee: Rohit Rai >Priority: Blocker > Fix For: Trunk > > Attachments: EnityFindOperatioError.png > > > Steps to regenerate: > 1. Ope URL > [https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=MarketingCampaignAndVisit] > 2. Perform find operation on given entity with empty fields. > 3. Broken Screen appears. (Please find the attached screenshot) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Lambhate updated OFBIZ-9760: --- Attachment: HeaderAfterBootstrapIntegration.png Updated Header screenshot. > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderAfterBootstrapIntegration.png, HeaderBeforeBootstrapIntegration.png, > OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Footer.patch, > OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Lambhate updated OFBIZ-9760: --- Attachment: (was: HeaderAfterBootstrapIntegration.png) > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderBeforeBootstrapIntegration.png, OFBIZ-9760-Bootstrap-Library.patch, > OFBIZ-9760-Footer.patch, OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, > ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9844) Replace Inline js with External js in renderTextField macro
[ https://issues.apache.org/jira/browse/OFBIZ-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aishwary Shrivastava reassigned OFBIZ-9844: --- Assignee: Aishwary Shrivastava > Replace Inline js with External js in renderTextField macro > --- > > Key: OFBIZ-9844 > URL: https://issues.apache.org/jira/browse/OFBIZ-9844 > Project: OFBiz > Issue Type: Sub-task >Reporter: Aditya Sharma >Assignee: Aishwary Shrivastava >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9760) Using Bootstrap Framework for E-Commerce Website
[ https://issues.apache.org/jira/browse/OFBIZ-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265633#comment-16265633 ] Mayank Lambhate commented on OFBIZ-9760: Yes, these are still relevant, although we have just updated the heading markup, so will be adding the new screenshot soon. > Using Bootstrap Framework for E-Commerce Website > > > Key: OFBIZ-9760 > URL: https://issues.apache.org/jira/browse/OFBIZ-9760 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Saurabh Dixit >Assignee: Deepak Dixit > Attachments: FooterSectionAfterBootstrapIntgration.png, > FooterSectionBeforeBootstrapIntegration.png, > HeaderAfterBootstrapIntegration.png, HeaderBeforeBootstrapIntegration.png, > OFBIZ-9760-Bootstrap-Library.patch, OFBIZ-9760-Footer.patch, > OFBIZ-9760-Header.patch, OFBIZ-9760-Logo.patch, ofbiz_logo.png > > > Use of the bootstrap framework so that the UI of the e-commerce would be more > arranged and user-friendly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9987) Enable drop ship PO if 'Drop-ship Only' property is set at Product Store level.
[ https://issues.apache.org/jira/browse/OFBIZ-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Joshi reassigned OFBIZ-9987: -- Assignee: (was: Ankit Joshi) > Enable drop ship PO if 'Drop-ship Only' property is set at Product Store > level. > --- > > Key: OFBIZ-9987 > URL: https://issues.apache.org/jira/browse/OFBIZ-9987 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ankit Joshi > Fix For: Trunk > > Attachments: OFBIZ-9987.patch > > > Current: > For drop shipment process, cart method 'createDropShipGroups' only check > requirementMethodEnumId at Facility Level and Product level. Also, found the > unhandled case of not considering requirementMethodEnumId at Product Level if > this property found at Facility level. > Expected : > RequirementMethodEnumId should be decided in the order of property set at > ProductStore -> Facility -> Product. > Check and enable drop ship PO if 'Drop-ship Only' property is set at Store > level. Also, this property should be checked and override at Facility level > if exists to consider the case when Facility does not allow drop ship Order. > Finally, it should be checked at Product level to consider the case when > Store and Facility allow for drop ship but the product does not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9987) Enable drop ship PO if 'Drop-ship Only' property is set at Product Store level.
[ https://issues.apache.org/jira/browse/OFBIZ-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Joshi updated OFBIZ-9987: --- Attachment: OFBIZ-9987.patch Attached the patch with proper fix. > Enable drop ship PO if 'Drop-ship Only' property is set at Product Store > level. > --- > > Key: OFBIZ-9987 > URL: https://issues.apache.org/jira/browse/OFBIZ-9987 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Ankit Joshi > Fix For: Trunk > > Attachments: OFBIZ-9987.patch > > > Current: > For drop shipment process, cart method 'createDropShipGroups' only check > requirementMethodEnumId at Facility Level and Product level. Also, found the > unhandled case of not considering requirementMethodEnumId at Product Level if > this property found at Facility level. > Expected : > RequirementMethodEnumId should be decided in the order of property set at > ProductStore -> Facility -> Product. > Check and enable drop ship PO if 'Drop-ship Only' property is set at Store > level. Also, this property should be checked and override at Facility level > if exists to consider the case when Facility does not allow drop ship Order. > Finally, it should be checked at Product level to consider the case when > Store and Facility allow for drop ship but the product does not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9759) Fiscal Gl type is reflecting twice in drop-down of Cost Centers.
[ https://issues.apache.org/jira/browse/OFBIZ-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain closed OFBIZ-9759. - > Fiscal Gl type is reflecting twice in drop-down of Cost Centers. > > > Key: OFBIZ-9759 > URL: https://issues.apache.org/jira/browse/OFBIZ-9759 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk > Environment: > https://ofbiz-trunk.hotwaxsystems.com/accounting/control/GlAccountBalanceByCostCenter?organizationPartyId=Company >Reporter: Tejas Khanna >Assignee: Akash Jain >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9759.patch > > > Steps to reproduce: > 1. Select Accounting from Applications. > 2. Select Organization GL Settings from Accounting Manager. > 3. Click on accounting. > 4. Click on Reports > 5. Select Cost Centers > 6. Choose Fiscal Gl Type drop-down. > Actual result: on selecting Gl Type from drop-down, selected Gl Type is > reflecting twice. > Expected result: Selected value should come only once in drop-down after > report generation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9848) Replace Inline js with External js in renderDateTimeField macro
[ https://issues.apache.org/jira/browse/OFBIZ-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aishwary Shrivastava reassigned OFBIZ-9848: --- Assignee: Aishwary Shrivastava > Replace Inline js with External js in renderDateTimeField macro > --- > > Key: OFBIZ-9848 > URL: https://issues.apache.org/jira/browse/OFBIZ-9848 > Project: OFBiz > Issue Type: Sub-task >Reporter: Aditya Sharma >Assignee: Aishwary Shrivastava >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9759) Fiscal Gl type is reflecting twice in drop-down of Cost Centers.
[ https://issues.apache.org/jira/browse/OFBIZ-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Jain updated OFBIZ-9759: -- Affects Version/s: Trunk > Fiscal Gl type is reflecting twice in drop-down of Cost Centers. > > > Key: OFBIZ-9759 > URL: https://issues.apache.org/jira/browse/OFBIZ-9759 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk > Environment: > https://ofbiz-trunk.hotwaxsystems.com/accounting/control/GlAccountBalanceByCostCenter?organizationPartyId=Company >Reporter: Tejas Khanna >Assignee: Akash Jain >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9759.patch > > > Steps to reproduce: > 1. Select Accounting from Applications. > 2. Select Organization GL Settings from Accounting Manager. > 3. Click on accounting. > 4. Click on Reports > 5. Select Cost Centers > 6. Choose Fiscal Gl Type drop-down. > Actual result: on selecting Gl Type from drop-down, selected Gl Type is > reflecting twice. > Expected result: Selected value should come only once in drop-down after > report generation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10003) Lookup Not Working with All Screens
[ https://issues.apache.org/jira/browse/OFBIZ-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265630#comment-16265630 ] Jacques Le Roux commented on OFBIZ-10003: - Thanks Guys, Oops, I tried this but maybe forgot to restart. Now with common-theme you have to restart. Changing paths in commons and alike screens is not enough. I got misleaded more than once yesterday with my old habits :D > Lookup Not Working with All Screens > --- > > Key: OFBIZ-10003 > URL: https://issues.apache.org/jira/browse/OFBIZ-10003 > Project: OFBiz > Issue Type: Bug > Environment: https://demo-trunk.ofbiz.apache.org/partymgr/control/main >Reporter: Aayush jain >Assignee: Deepak Dixit >Priority: Critical > Fix For: Upcoming Release > > Attachments: Lookup_Screen.png > > > Steps: > 1. Open URL https://demo-trunk.ofbiz.apache.org/facility/control > 2. Navigate to any screen/page > 3. Click on lookup and check for find result > Actual: Lookup not working as expected, On click window opens but no results > been displayed > Expected: On Clicking, find button results should be displayed. > Kindly refer attachment for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
