[jira] [Closed] (OFBIZ-10296) Add Document Content: acc-financial-accounts.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga closed OFBIZ-10296. --- Thanks for the patch [~vaibhav.jain]! I did some very minor adjustments :) and committed it at r1844976. > Add Document Content: acc-financial-accounts.adoc > - > > Key: OFBIZ-10296 > URL: https://issues.apache.org/jira/browse/OFBIZ-10296 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Sharan Foga >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10296.patch > > > Add content for acc-financial-accounts.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OFBIZ-9900) Unable to create event in SFA component
[ https://issues.apache.org/jira/browse/OFBIZ-9900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reopened OFBIZ-9900: -- Assignee: Michael Brohl > Unable to create event in SFA component > --- > > Key: OFBIZ-9900 > URL: https://issues.apache.org/jira/browse/OFBIZ-9900 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Rubia Elza Joshep >Assignee: Michael Brohl >Priority: Major > Attachments: OFBIZ-9900-Trunk.patch > > > Steps- > 1) Open URL > https://demo-trunk.ofbiz.apache.org/sfa/control/createWorkEffortAndPartyAssign > 2) In SFA component, create an event by clicking on "Create new". > 3) Fill in the information with name and select "To party id" (except admin). > Expected: Event should be successfully created > Actual: Unable to create event -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-9900) Unable to create event in SFA component
[ https://issues.apache.org/jira/browse/OFBIZ-9900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-9900. Resolution: Duplicate Fix Version/s: (was: Trunk) > Unable to create event in SFA component > --- > > Key: OFBIZ-9900 > URL: https://issues.apache.org/jira/browse/OFBIZ-9900 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Rubia Elza Joshep >Assignee: Michael Brohl >Priority: Major > Attachments: OFBIZ-9900-Trunk.patch > > > Steps- > 1) Open URL > https://demo-trunk.ofbiz.apache.org/sfa/control/createWorkEffortAndPartyAssign > 2) In SFA component, create an event by clicking on "Create new". > 3) Fill in the information with name and select "To party id" (except admin). > Expected: Event should be successfully created > Actual: Unable to create event -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10296) Add Document Content: acc-financial-accounts.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1142#comment-1142 ] Sharan Foga commented on OFBIZ-10296: - Hi [~vaibhav.jain] thanks for the patch. I'll take a look. > Add Document Content: acc-financial-accounts.adoc > - > > Key: OFBIZ-10296 > URL: https://issues.apache.org/jira/browse/OFBIZ-10296 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Sharan Foga >Priority: Minor > Attachments: OFBIZ-10296.patch > > > Add content for acc-financial-accounts.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10296) Add Document Content: acc-financial-accounts.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga reassigned OFBIZ-10296: --- Assignee: Sharan Foga (was: Vaibhav Jain) > Add Document Content: acc-financial-accounts.adoc > - > > Key: OFBIZ-10296 > URL: https://issues.apache.org/jira/browse/OFBIZ-10296 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Sharan Foga >Priority: Minor > Attachments: OFBIZ-10296.patch > > > Add content for acc-financial-accounts.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10592) OutOfMemory and stucked JobPoller issue
[ https://issues.apache.org/jira/browse/OFBIZ-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1127#comment-1127 ] Taher Alkhateeb commented on OFBIZ-10592: - Hello guys, and sorry for jumping in a bit late. Okay I looked at everything and indeed I have a suspicion like Giulio that the problem might very well be in the job poller. The first question I have is: is this a very specific setup to your environment or can we repeat? Is it possible to repeat the infrastructure and setup and hit the same bug but on a clean stock OFBiz code base? > OutOfMemory and stucked JobPoller issue > --- > > Key: OFBIZ-10592 > URL: https://issues.apache.org/jira/browse/OFBIZ-10592 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Release Branch 13.07 > Environment: Two instances Ofbiz installation on two machines, > connected to an Apache HTTPD instance which acts as a proxy. > Request to ofbiz instances are handled and load balanced. > OFBiz version : 13.07.03 with Multitenant enabled > OS: Ubuntu Linux 16.04 LTS > RDBMS: MariaDB v10.1.24 >Reporter: Giulio Speri >Assignee: Giulio Speri >Priority: Critical > Attachments: alloc_tree_600k_12102018.png, > jvm_ofbiz1_profi_telem.png, jvm_prof_ofbiz1_telem2.png, > ofbiz1_jvm_profil_nojobpoller.png, recorder_object_600k_12102018.png, > telemetry_ovrl_600k_12102018.png > > > > This installation is composed by two instances of OFBiz (v13.07.03), served > via an Apache Tomcat webserver, along with a load balancer. > The database server is MariaDB. > > We had the first problems, about 3 weeks ago, when suddenly, the front1 > (ofbiz instance 1), stopped serving web requests; front2, instead, was still > working correctly. > > Obviously we checked the log files, and we saw that async services were > failing; the failure was accompanied by this error line: > > *_Thread "AsyncAppender-async" java.lang.OutOfMemoryError: GC overhead limit > exceeded_* > > We analyzed the situation with our system specialists, and they told us that > the application was highly stressing machine resources (cpu always at or near > 100%, RAM usage rapidly increasing), until the jvm run out of memory. > This "resource-high-consumption situation", occurred only when ofbiz1 > instance was started with the JobPoller enabled; if the JobPoller was not > enabled, ofbiz run with low resource usage. > > We then focused on the db, to check first of all the dimensions; the result > was disconcerting; 45GB, mainly divided on four tables: SERVER_HIT (about 18 > GB), VISIT (about 15 GB), ENTITY_SYNC_REMOVE (about 8 GB), VISITOR (about 2 > GB). > All the other tables had a size in the order of few MB each. > > The first thing we did, was to clear all those tables, reducing considerably > the db size. > After the cleaning, we tried to start ofbiz1 again, with the JobPoller > component enabled; this caused a lot of old scheduled/queued jobs, to execute. > Except than for the start-up time, the resource usage of the machine, > stabilized around normal to low values (cpu 1-10%). > Ofbiz seemed to work (web request was served), but we noticed taht the > JobPoller did not schedule or run jobs, anymore. > The number of job in "Pending" state in the JobSandbox entity was small > (about 20); no Queued, no Failed, no jobs in other states. > In addition to this, unfortunately, after few hours, jvm run out of memory > again. > > Our jvm has an heap maximum size of 20GB ( we have 32GB on the machine), so > it's not so small, I think. > The next step we're going to do is set-up locally the application over the > same production db to see what happens. > > Now that I explained the situation, I am going to ask if, in your > opinion/experience: > > Could the JobPoller component be the root (and only) cause of the OutOfMemory > of the jvm? > > Could this issue be related to OFBIZ-5710? > > Dumping and analyzing the heap of the jvm could help in some way to > understand what or who fills the memory or is this operation a waste of time? > > Is there something that we did not considered or missed during the whole > process of problem analysis? > > > I really thank you all for your attention and your help; any suggestion or > advice would really be greatly appreciated. > > Kind regards, > Giulio -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7670) OFBIZ-7517:SpecialPurpose/ecommerce: Correct all the checkboxes and radio buttons in all the ecommerce FTLs.
[ https://issues.apache.org/jira/browse/OFBIZ-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandrashekhar Dhakad updated OFBIZ-7670: - Attachment: OFBIZ-7670.patch > OFBIZ-7517:SpecialPurpose/ecommerce: Correct all the checkboxes and radio > buttons in all the ecommerce FTLs. > > > Key: OFBIZ-7670 > URL: https://issues.apache.org/jira/browse/OFBIZ-7670 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS >Affects Versions: 16.11.01 >Reporter: Mohammad Kathawala >Assignee: Chandrashekhar Dhakad >Priority: Minor > Attachments: OFBIZ-7670.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7670) OFBIZ-7517:SpecialPurpose/ecommerce: Correct all the checkboxes and radio buttons in all the ecommerce FTLs.
[ https://issues.apache.org/jira/browse/OFBIZ-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1109#comment-1109 ] Chandrashekhar Dhakad commented on OFBIZ-7670: -- Improved markup of all the radio buttons and checkboxes in all the FTL files of ecommerce as per the standard markup of the bootstrap 4. Attached patch for the same. > OFBIZ-7517:SpecialPurpose/ecommerce: Correct all the checkboxes and radio > buttons in all the ecommerce FTLs. > > > Key: OFBIZ-7670 > URL: https://issues.apache.org/jira/browse/OFBIZ-7670 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS >Affects Versions: 16.11.01 >Reporter: Mohammad Kathawala >Assignee: Chandrashekhar Dhakad >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10573) can‘t run job when user changed password
[ https://issues.apache.org/jira/browse/OFBIZ-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1099#comment-1099 ] Pierre Smits commented on OFBIZ-10573: -- My apologies, I accidentally (and unintentional) changed the assignee to me. Reverted. > can‘t run job when user changed password > > > Key: OFBIZ-10573 > URL: https://issues.apache.org/jira/browse/OFBIZ-10573 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 13.07, Release Branch 16.11 >Reporter: zhang.liang >Assignee: Rohit Koushal >Priority: Blocker > Attachments: image-2018-09-19-15-41-13-122.png, > image-2018-09-19-15-43-25-388.png > > > dispatcher.runAsync() create a job. if user changed password befor run job, > throw a exception > !image-2018-09-19-15-41-13-122.png! > ServiceDispatcher.chekAuth(); > !image-2018-09-19-15-43-25-388.png! > if check old password not equals new password auth failed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10573) can‘t run job when user changed password
[ https://issues.apache.org/jira/browse/OFBIZ-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1098#comment-1098 ] Rohit Koushal commented on OFBIZ-10573: --- In the OFBIZ-9557, I have added a support to run Job as system user. Now here I think we need to handle the case when user manually update the password and jobs gets fail due to the password change. So here I think we can handle the case like if password gets updated and mismatch occur then we can check it in the UserLoginPasswordHistory for the immediate old password in ServiceDispatcher and if found then we can use the new the updated user login(which having new password) to run job and save this userLogin in the RunTime data for further job execution(if it is recurring). Please review and let me know if you think this solution is acceptable. > can‘t run job when user changed password > > > Key: OFBIZ-10573 > URL: https://issues.apache.org/jira/browse/OFBIZ-10573 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 13.07, Release Branch 16.11 >Reporter: zhang.liang >Assignee: Pierre Smits >Priority: Blocker > Attachments: image-2018-09-19-15-41-13-122.png, > image-2018-09-19-15-43-25-388.png > > > dispatcher.runAsync() create a job. if user changed password befor run job, > throw a exception > !image-2018-09-19-15-41-13-122.png! > ServiceDispatcher.chekAuth(); > !image-2018-09-19-15-43-25-388.png! > if check old password not equals new password auth failed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10573) can‘t run job when user changed password
[ https://issues.apache.org/jira/browse/OFBIZ-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10573: Assignee: Rohit Koushal (was: Pierre Smits) > can‘t run job when user changed password > > > Key: OFBIZ-10573 > URL: https://issues.apache.org/jira/browse/OFBIZ-10573 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 13.07, Release Branch 16.11 >Reporter: zhang.liang >Assignee: Rohit Koushal >Priority: Blocker > Attachments: image-2018-09-19-15-41-13-122.png, > image-2018-09-19-15-43-25-388.png > > > dispatcher.runAsync() create a job. if user changed password befor run job, > throw a exception > !image-2018-09-19-15-41-13-122.png! > ServiceDispatcher.chekAuth(); > !image-2018-09-19-15-43-25-388.png! > if check old password not equals new password auth failed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10573) can‘t run job when user changed password
[ https://issues.apache.org/jira/browse/OFBIZ-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10573: Assignee: Pierre Smits (was: Rohit Koushal) > can‘t run job when user changed password > > > Key: OFBIZ-10573 > URL: https://issues.apache.org/jira/browse/OFBIZ-10573 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 13.07, Release Branch 16.11 >Reporter: zhang.liang >Assignee: Pierre Smits >Priority: Blocker > Attachments: image-2018-09-19-15-41-13-122.png, > image-2018-09-19-15-43-25-388.png > > > dispatcher.runAsync() create a job. if user changed password befor run job, > throw a exception > !image-2018-09-19-15-41-13-122.png! > ServiceDispatcher.chekAuth(); > !image-2018-09-19-15-43-25-388.png! > if check old password not equals new password auth failed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10631) remove deprecated and not used PhoneNumber functions
[ https://issues.apache.org/jira/browse/OFBIZ-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10631: - Description: Several phone number validation functions have been deprecated (and are not used in framework code). This concerns: * isUSPhoneNumber * isUSPhoneAreaCode * isUSPhoneMainNumber * isInternationalPhoneNumber was:Several phone number validation functions have been deprecated (and are not used in framework code). > remove deprecated and not used PhoneNumber functions > > > Key: OFBIZ-10631 > URL: https://issues.apache.org/jira/browse/OFBIZ-10631 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10631-UtilValidate.java.patch > > > Several phone number validation functions have been deprecated (and are not > used in framework code). > > This concerns: > * isUSPhoneNumber > * isUSPhoneAreaCode > * isUSPhoneMainNumber > * isInternationalPhoneNumber -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10631) remove deprecated and not used PhoneNumber functions
[ https://issues.apache.org/jira/browse/OFBIZ-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10631: - Attachment: OFBIZ-10631-UtilValidate.java.patch > remove deprecated and not used PhoneNumber functions > > > Key: OFBIZ-10631 > URL: https://issues.apache.org/jira/browse/OFBIZ-10631 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10631-UtilValidate.java.patch > > > Several phone number validation functions have been deprecated (and are not > used in framework code). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10631) remove deprecated and not used PhoneNumber functions
Pierre Smits created OFBIZ-10631: Summary: remove deprecated and not used PhoneNumber functions Key: OFBIZ-10631 URL: https://issues.apache.org/jira/browse/OFBIZ-10631 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Several phone number validation functions have been deprecated (and are not used in framework code). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10618) Update google libphonenumber to v8.9.16
[ https://issues.apache.org/jira/browse/OFBIZ-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1087#comment-1087 ] Pierre Smits commented on OFBIZ-10618: -- Have you? > Update google libphonenumber to v8.9.16 > - > > Key: OFBIZ-10618 > URL: https://issues.apache.org/jira/browse/OFBIZ-10618 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Major > Fix For: 17.12.01 > > > The new release contains mostly [metadata > changes|https://github.com/googlei18n/libphonenumber/blob/master/FAQ.md#metadata_definition]. > https://github.com/googlei18n/libphonenumber/blob/master/release_notes.txt > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10542) Instructions for Configurable PC don't work
[ https://issues.apache.org/jira/browse/OFBIZ-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1084#comment-1084 ] Priya Sharma edited comment on OFBIZ-10542 at 10/27/18 1:21 PM: Hi [~jacques.le.roux], * The method "showErrorAlert" populates the error section only when the message is not null and thus the button seems to be not working. * After a bit of exploration, I was able to figure out that if the instructions are null then this button should not be populated in the first place. But the check instructions?has_content failed and hence the button got populated. Thus adding an additional check for empty string would do. Please provide your views so that I can proceed further. Also, the inline js causes lots of errors on the browser console, should we add the meta tag in the header to allow inline-scripts !console-error.png! was (Author: priya.sharma.9362): Hi [~jacques.le.roux], * The method "showErrorAlert" populates the error section only when the message is not null and thus the button seems to be not working. * After a bit of exploration, I was able to figure out that if the instructions are null then this button should not be populated in the first place. But the check instructions?has_content failed and hence the button got populated. Thus adding an additional check for null value would do. Please provide your views so that I can proceed further. Also, the inline js causes lots of errors on the browser console, should we add the meta tag in the header to allow inline-scripts !console-error.png! > Instructions for Configurable PC don't work > --- > > Key: OFBIZ-10542 > URL: https://issues.apache.org/jira/browse/OFBIZ-10542 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, 16.11.04, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Priya Sharma >Priority: Minor > Attachments: console-error.png > > > This concerns only R16, R17 and the trunk. The "Instructions" button was not > present in R13. > This kind of message shows: > Trunk: > class="btn btn-outline-secondary btn-sm">Instructions > R16: > occurred","");"="" class="buttontext">Instructions > The same exists for all configurable products, notably Gold Pizza -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10542) Instructions for Configurable PC don't work
[ https://issues.apache.org/jira/browse/OFBIZ-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1084#comment-1084 ] Priya Sharma commented on OFBIZ-10542: -- Hi [~jacques.le.roux], * The method "showErrorAlert" populates the error section only when the message is not null and thus the button seems to be not working. * After a bit of exploration, I was able to figure out that if the instructions are null then this button should not be populated in the first place. But the check instructions?has_content failed and hence the button got populated. Thus adding an additional check for null value would do. Please provide your views so that I can proceed further. Also, the inline js causes lots of errors on the browser console, should we add the meta tag in the header to allow inline-scripts !console-error.png! > Instructions for Configurable PC don't work > --- > > Key: OFBIZ-10542 > URL: https://issues.apache.org/jira/browse/OFBIZ-10542 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, 16.11.04, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Priya Sharma >Priority: Minor > Attachments: console-error.png > > > This concerns only R16, R17 and the trunk. The "Instructions" button was not > present in R13. > This kind of message shows: > Trunk: > class="btn btn-outline-secondary btn-sm">Instructions > R16: > occurred","");"="" class="buttontext">Instructions > The same exists for all configurable products, notably Gold Pizza -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10542) Instructions for Configurable PC don't work
[ https://issues.apache.org/jira/browse/OFBIZ-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priya Sharma updated OFBIZ-10542: - Attachment: console-error.png > Instructions for Configurable PC don't work > --- > > Key: OFBIZ-10542 > URL: https://issues.apache.org/jira/browse/OFBIZ-10542 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, 16.11.04, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Priya Sharma >Priority: Minor > Attachments: console-error.png > > > This concerns only R16, R17 and the trunk. The "Instructions" button was not > present in R13. > This kind of message shows: > Trunk: > class="btn btn-outline-secondary btn-sm">Instructions > R16: > occurred","");"="" class="buttontext">Instructions > The same exists for all configurable products, notably Gold Pizza -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10598) Add an ofbizsetup to the data files names used by the ofbizsetup app
[ https://issues.apache.org/jira/browse/OFBIZ-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1081#comment-1081 ] Rishi Solanki commented on OFBIZ-10598: --- Added patch to show how changes would reflect and added back all the data in the renamed files. Please review and share your feedback. I will commit the changes in next week after testing data load. > Add an ofbizsetup to the data files names used by the ofbizsetup app > > > Key: OFBIZ-10598 > URL: https://issues.apache.org/jira/browse/OFBIZ-10598 > Project: OFBiz > Issue Type: Improvement > Components: commonext >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Rishi Solanki >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10598.patch > > > This follows the ["Shipping data > duplicated"|https://markmail.org/message/m3l7z3okir3u3gx2] discussion in dev > ML. > The idea is to add an ofbizsetup prefix to the data files names used by the > ofbizsetup app in order to not confuse them and their content with other same > data in demo files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10626) Add Document Content: acc-glossary.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1080#comment-1080 ] Vaibhav Jain commented on OFBIZ-10626: -- Hi team, Attached the patch for accounting glossary documentation. Please have a look into this. Thanks! > Add Document Content: acc-glossary.adoc > --- > > Key: OFBIZ-10626 > URL: https://issues.apache.org/jira/browse/OFBIZ-10626 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Reporter: Vaibhav Jain >Assignee: Vaibhav Jain >Priority: Major > Attachments: OFBIZ-10626.patch > > > Add content for acc-glossary.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10626) Add Document Content: acc-glossary.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Jain updated OFBIZ-10626: - Attachment: OFBIZ-10626.patch > Add Document Content: acc-glossary.adoc > --- > > Key: OFBIZ-10626 > URL: https://issues.apache.org/jira/browse/OFBIZ-10626 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Reporter: Vaibhav Jain >Assignee: Vaibhav Jain >Priority: Major > Attachments: OFBIZ-10626.patch > > > Add content for acc-glossary.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10626) Add Document Content: acc-glossary.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Jain reassigned OFBIZ-10626: Assignee: Vaibhav Jain > Add Document Content: acc-glossary.adoc > --- > > Key: OFBIZ-10626 > URL: https://issues.apache.org/jira/browse/OFBIZ-10626 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Reporter: Vaibhav Jain >Assignee: Vaibhav Jain >Priority: Major > > Add content for acc-glossary.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1079#comment-1079 ] Yashwant Dhakad commented on OFBIZ-9475: I have uploaded the new patch for serializing inventory and following changes did in this patch: * Removed the service which updated the serialize inventory ATP/QOH based on status. * Added support in the workflow where inventory item transactions happen and created the IID record. * InventoryItem ATP/QOH automatically updated by IID record. * I have tested the following scenarios: ** Receive inventory. ** Reserve, issue and return inventory from the sales order. ** Produce, Issue and return from the production run. ** Inventory transfer. Please have a look and provide your valuable feedback. > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement > Components: hhfacility >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, OFBIZ-9475.patch, OFBIZ-9475.patch, > OFBIZ-9475.patch, OFBIZ-9475.patch > > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialise and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > As we do a lot of discussion in the respective mail threads. > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > According to this email threads, I conclude that:- > There are 2 types of the inventory item in OFBiz. > 1. *Serialized* > 2. *Non serialized* > Majorly there are 3 entities to manage the various transaction of serialised > and non-serialized inventory items. > 1. _InventoryItem_ > 2. _InventoryItemDetail_ > 3. _InventoryItemStatus_ > Following changes need to be done in the workflow of inventory item records:- > 1) There is no need to manage a different workflow for serialised and non- > serialised inventory items. > 2) Transaction of serialised and non-serialised inventory item should be > managed in both InventoryItemStatus and InventoryItemDetail entity. > a) Transaction of serialised inventory items is managed by > inventoryItemstatus entity not managed in inventoryItemDetail entity. While > inventoryItemDetail and inventoryItemStatus should be managed for both > serialised and non-serialised inventory items. > b) As ATP/QOH/AQT are updated on the basis of ATPDIFF/QOHDIFF/AQTDIFF in > non-serialised inventory item. We should follow the same pattern for > serialised inventory item. > c) Change in ATP/QOH/AQT is tracked by inventoryItemDetail entity. > d)Status transaction of an inventory item is tracked in > InventoryItemStatus entity. > 3) No need to manage separate status for serialised and non-serialised > inventory item. They are already distinguished on the basis of inventory item > type. > 1. *Serialised*:- > In a serialised inventory item as of now ATP/QOH/AQT are managed on the > basis of inventory item status.While ATP/QOH/AQT should be the sum of > ATPDIFF/QOHDIFF/AQTDIFF of inventory item detail. > Ex: > 1. If we receive 2 inventory of serialised inventory item then 2 separate > inventory item records are created > InventoryItem:- > inventoryItemId="10001",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" > inventoryItemId="10002" statusId="AVAILABLE" > 2. If status of inventory item is changed from AVAILABLE -> PROMISED then > InventoryItem:- > inventoryItemId="10001",status="PROMISED", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10001", inventoryItemDetailSeqId="10002", ATPDIFF="-1", >
[jira] [Updated] (OFBIZ-10598) Add an ofbizsetup to the data files names used by the ofbizsetup app
[ https://issues.apache.org/jira/browse/OFBIZ-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki updated OFBIZ-10598: -- Attachment: OFBIZ-10598.patch > Add an ofbizsetup to the data files names used by the ofbizsetup app > > > Key: OFBIZ-10598 > URL: https://issues.apache.org/jira/browse/OFBIZ-10598 > Project: OFBiz > Issue Type: Improvement > Components: commonext >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Rishi Solanki >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10598.patch > > > This follows the ["Shipping data > duplicated"|https://markmail.org/message/m3l7z3okir3u3gx2] discussion in dev > ML. > The idea is to add an ofbizsetup prefix to the data files names used by the > ofbizsetup app in order to not confuse them and their content with other same > data in demo files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10402) Introduce ability to clear specific cache from cache maintenance
[ https://issues.apache.org/jira/browse/OFBIZ-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki reassigned OFBIZ-10402: - Assignee: Rishi Solanki > Introduce ability to clear specific cache from cache maintenance > > > Key: OFBIZ-10402 > URL: https://issues.apache.org/jira/browse/OFBIZ-10402 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Rishi Solanki >Priority: Minor > Attachments: OFBIZ-10402.jpg, OFBIZ-10402.patch, OFBIZ-10402.patch > > > Currently, either you can clear all caches or you can clear specific cache > records from clear button. > There should be checkbox pattern which enables user to select multiple caches > and some button on top like clear selected caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10402) Introduce ability to clear specific cache from cache maintenance
[ https://issues.apache.org/jira/browse/OFBIZ-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogesh Naroliya reassigned OFBIZ-10402: --- Assignee: (was: Yogesh Naroliya) > Introduce ability to clear specific cache from cache maintenance > > > Key: OFBIZ-10402 > URL: https://issues.apache.org/jira/browse/OFBIZ-10402 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Priority: Minor > Attachments: OFBIZ-10402.jpg, OFBIZ-10402.patch, OFBIZ-10402.patch > > > Currently, either you can clear all caches or you can clear specific cache > records from clear button. > There should be checkbox pattern which enables user to select multiple caches > and some button on top like clear selected caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10585) Production run not created for marketing package auto type product if component inventory is not available
[ https://issues.apache.org/jira/browse/OFBIZ-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankush Upadhyay updated OFBIZ-10585: Attachment: OFBIZ-10585.patch > Production run not created for marketing package auto type product if > component inventory is not available > -- > > Key: OFBIZ-10585 > URL: https://issues.apache.org/jira/browse/OFBIZ-10585 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 >Reporter: Yashwant Dhakad >Assignee: Ankush Upadhyay >Priority: Major > Attachments: OFBIZ-10585.patch > > > When we create an order for marketing package auto, the system checks the > component inventory and if found then it creates the production run job and > produce marketing package inventory, but if component quantity not available > then it does not create the job. So if we don't have an inventory item of > component then production run should be created with created status. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10598) Add an ofbizsetup to the data files names used by the ofbizsetup app
[ https://issues.apache.org/jira/browse/OFBIZ-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki reassigned OFBIZ-10598: - Assignee: Rishi Solanki > Add an ofbizsetup to the data files names used by the ofbizsetup app > > > Key: OFBIZ-10598 > URL: https://issues.apache.org/jira/browse/OFBIZ-10598 > Project: OFBiz > Issue Type: Improvement > Components: commonext >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Rishi Solanki >Priority: Minor > Fix For: Upcoming Branch > > > This follows the ["Shipping data > duplicated"|https://markmail.org/message/m3l7z3okir3u3gx2] discussion in dev > ML. > The idea is to add an ofbizsetup prefix to the data files names used by the > ofbizsetup app in order to not confuse them and their content with other same > data in demo files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10402) Introduce ability to clear specific cache from cache maintenance
[ https://issues.apache.org/jira/browse/OFBIZ-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogesh Naroliya updated OFBIZ-10402: Attachment: OFBIZ-10402.patch > Introduce ability to clear specific cache from cache maintenance > > > Key: OFBIZ-10402 > URL: https://issues.apache.org/jira/browse/OFBIZ-10402 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Yogesh Naroliya >Priority: Minor > Attachments: OFBIZ-10402.jpg, OFBIZ-10402.patch, OFBIZ-10402.patch > > > Currently, either you can clear all caches or you can clear specific cache > records from clear button. > There should be checkbox pattern which enables user to select multiple caches > and some button on top like clear selected caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10402) Introduce ability to clear specific cache from cache maintenance
[ https://issues.apache.org/jira/browse/OFBIZ-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogesh Naroliya updated OFBIZ-10402: Attachment: OFBIZ-10402.jpg > Introduce ability to clear specific cache from cache maintenance > > > Key: OFBIZ-10402 > URL: https://issues.apache.org/jira/browse/OFBIZ-10402 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Yogesh Naroliya >Priority: Minor > Attachments: OFBIZ-10402.jpg, OFBIZ-10402.patch, OFBIZ-10402.patch > > > Currently, either you can clear all caches or you can clear specific cache > records from clear button. > There should be checkbox pattern which enables user to select multiple caches > and some button on top like clear selected caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10402) Introduce ability to clear specific cache from cache maintenance
[ https://issues.apache.org/jira/browse/OFBIZ-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1078#comment-1078 ] Yogesh Naroliya commented on OFBIZ-10402: - I verified the changes and attached the patch and a screenshot for quick reference. > Introduce ability to clear specific cache from cache maintenance > > > Key: OFBIZ-10402 > URL: https://issues.apache.org/jira/browse/OFBIZ-10402 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Yogesh Naroliya >Priority: Minor > Attachments: OFBIZ-10402.jpg, OFBIZ-10402.patch, OFBIZ-10402.patch > > > Currently, either you can clear all caches or you can clear specific cache > records from clear button. > There should be checkbox pattern which enables user to select multiple caches > and some button on top like clear selected caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10627) Submit button should not display when there is no item present over Quote Prices Screen
[ https://issues.apache.org/jira/browse/OFBIZ-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1076#comment-1076 ] kumar Rahul commented on OFBIZ-10627: - Patch Provided For Submit button should not display when there is no item present over Quote Prices Screen > Submit button should not display when there is no item present over Quote > Prices Screen > --- > > Key: OFBIZ-10627 > URL: https://issues.apache.org/jira/browse/OFBIZ-10627 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: kumar Rahul >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10627.patch, QuotePrices.png > > > Currently system is showing submit button even though there is no rows to > process. Ideally it should not display is there is nothing to submit. > Steps to replicate the issue: > * Create Quote from OrderMgr>Quotes screen. > * Navigate over Quote Prices Screen. > * In Quote Prices screenlet, here system is showing submit button even > though there is no quote items to process. > Please refer attached screenshot for quick details. > !QuotePrices.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10314) Multiple rows are getting created on updating Party details
[ https://issues.apache.org/jira/browse/OFBIZ-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-10314. - > Multiple rows are getting created on updating Party details > --- > > Key: OFBIZ-10314 > URL: https://issues.apache.org/jira/browse/OFBIZ-10314 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > >Reporter: Archana Asthana >Assignee: Suraj Khurana >Priority: Major > Fix For: 17.12.01, 16.11.05 > > Attachments: 1034.png, EditPartydetails.png, > OFBIZ-10314-release16.11.patch, OFBIZ-10314-release17.12.patch, > OFBIZ-10314.patch, Working_fine.png > > > Steps to regenerate: > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Click Search Button to search Party > In the opened modal, check the box of any customer > Another model gets open to update the detail > Enter the required detail/s and click update > Multiple rows of the same customer are getting created in the Party search > Modal > Image is attached for reference. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10585) Production run not created for marketing package auto type product if component inventory is not available
[ https://issues.apache.org/jira/browse/OFBIZ-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1077#comment-1077 ] Ankush Upadhyay commented on OFBIZ-10585: - Following are the issues found: # System creates product run job for quantities by checking components inventory, so if user ordered 10 quantity order but system found inventory for only 5 quantity then it creates production run job for 5 quantity only and also produce marketing package inventory at the same time but never create any product run job for remaining unavailable quantities. # System does not create any production run job if not found inventory for components. # Order view page only shows one production run job at a time. Expectation: For #1, System should produce marketing package inventory based on available component inventory And create production run job for remaining unavailable ordered quantities with created status. For #2, System should create production run job for full ordered quantities in case of no found any inventory for components. For #3, Order view page should show all production run job associated with order. As per the expectation, I have made changes in service to handle above mentioned scenarios. > Production run not created for marketing package auto type product if > component inventory is not available > -- > > Key: OFBIZ-10585 > URL: https://issues.apache.org/jira/browse/OFBIZ-10585 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 >Reporter: Yashwant Dhakad >Assignee: Ankush Upadhyay >Priority: Major > > When we create an order for marketing package auto, the system checks the > component inventory and if found then it creates the production run job and > produce marketing package inventory, but if component quantity not available > then it does not create the job. So if we don't have an inventory item of > component then production run should be created with created status. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10314) Multiple rows are getting created on updating Party details
[ https://issues.apache.org/jira/browse/OFBIZ-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana updated OFBIZ-10314: -- Affects Version/s: Release Branch 17.12 Trunk Release Branch 16.11 > Multiple rows are getting created on updating Party details > --- > > Key: OFBIZ-10314 > URL: https://issues.apache.org/jira/browse/OFBIZ-10314 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > >Reporter: Archana Asthana >Assignee: Suraj Khurana >Priority: Major > Fix For: 17.12.01, 16.11.05 > > Attachments: 1034.png, EditPartydetails.png, > OFBIZ-10314-release16.11.patch, OFBIZ-10314-release17.12.patch, > OFBIZ-10314.patch, Working_fine.png > > > Steps to regenerate: > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Click Search Button to search Party > In the opened modal, check the box of any customer > Another model gets open to update the detail > Enter the required detail/s and click update > Multiple rows of the same customer are getting created in the Party search > Modal > Image is attached for reference. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10627) Submit button should not display when there is no item present over Quote Prices Screen
[ https://issues.apache.org/jira/browse/OFBIZ-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kumar Rahul updated OFBIZ-10627: Attachment: OFBIZ-10627.patch > Submit button should not display when there is no item present over Quote > Prices Screen > --- > > Key: OFBIZ-10627 > URL: https://issues.apache.org/jira/browse/OFBIZ-10627 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: kumar Rahul >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10627.patch, QuotePrices.png > > > Currently system is showing submit button even though there is no rows to > process. Ideally it should not display is there is nothing to submit. > Steps to replicate the issue: > * Create Quote from OrderMgr>Quotes screen. > * Navigate over Quote Prices Screen. > * In Quote Prices screenlet, here system is showing submit button even > though there is no quote items to process. > Please refer attached screenshot for quick details. > !QuotePrices.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10402) Introduce ability to clear specific cache from cache maintenance
[ https://issues.apache.org/jira/browse/OFBIZ-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yogesh Naroliya updated OFBIZ-10402: Attachment: OFBIZ-10402.patch > Introduce ability to clear specific cache from cache maintenance > > > Key: OFBIZ-10402 > URL: https://issues.apache.org/jira/browse/OFBIZ-10402 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Yogesh Naroliya >Priority: Minor > Attachments: OFBIZ-10402.patch > > > Currently, either you can clear all caches or you can clear specific cache > records from clear button. > There should be checkbox pattern which enables user to select multiple caches > and some button on top like clear selected caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10314) Multiple rows are getting created on updating Party details
[ https://issues.apache.org/jira/browse/OFBIZ-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-10314: - Assignee: Suraj Khurana (was: Shikha Jaiswal) > Multiple rows are getting created on updating Party details > --- > > Key: OFBIZ-10314 > URL: https://issues.apache.org/jira/browse/OFBIZ-10314 > Project: OFBiz > Issue Type: Bug > Components: webpos > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > >Reporter: Archana Asthana >Assignee: Suraj Khurana >Priority: Major > Attachments: 1034.png, EditPartydetails.png, > OFBIZ-10314-release16.11.patch, OFBIZ-10314-release17.12.patch, > OFBIZ-10314.patch, Working_fine.png > > > Steps to regenerate: > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Click Search Button to search Party > In the opened modal, check the box of any customer > Another model gets open to update the detail > Enter the required detail/s and click update > Multiple rows of the same customer are getting created in the Party search > Modal > Image is attached for reference. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9475: --- Attachment: OFBIZ-9475.patch > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement > Components: hhfacility >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, OFBIZ-9475.patch, OFBIZ-9475.patch, > OFBIZ-9475.patch, OFBIZ-9475.patch > > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialise and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > As we do a lot of discussion in the respective mail threads. > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > According to this email threads, I conclude that:- > There are 2 types of the inventory item in OFBiz. > 1. *Serialized* > 2. *Non serialized* > Majorly there are 3 entities to manage the various transaction of serialised > and non-serialized inventory items. > 1. _InventoryItem_ > 2. _InventoryItemDetail_ > 3. _InventoryItemStatus_ > Following changes need to be done in the workflow of inventory item records:- > 1) There is no need to manage a different workflow for serialised and non- > serialised inventory items. > 2) Transaction of serialised and non-serialised inventory item should be > managed in both InventoryItemStatus and InventoryItemDetail entity. > a) Transaction of serialised inventory items is managed by > inventoryItemstatus entity not managed in inventoryItemDetail entity. While > inventoryItemDetail and inventoryItemStatus should be managed for both > serialised and non-serialised inventory items. > b) As ATP/QOH/AQT are updated on the basis of ATPDIFF/QOHDIFF/AQTDIFF in > non-serialised inventory item. We should follow the same pattern for > serialised inventory item. > c) Change in ATP/QOH/AQT is tracked by inventoryItemDetail entity. > d)Status transaction of an inventory item is tracked in > InventoryItemStatus entity. > 3) No need to manage separate status for serialised and non-serialised > inventory item. They are already distinguished on the basis of inventory item > type. > 1. *Serialised*:- > In a serialised inventory item as of now ATP/QOH/AQT are managed on the > basis of inventory item status.While ATP/QOH/AQT should be the sum of > ATPDIFF/QOHDIFF/AQTDIFF of inventory item detail. > Ex: > 1. If we receive 2 inventory of serialised inventory item then 2 separate > inventory item records are created > InventoryItem:- > inventoryItemId="10001",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" > inventoryItemId="10002" statusId="AVAILABLE" > 2. If status of inventory item is changed from AVAILABLE -> PROMISED then > InventoryItem:- > inventoryItemId="10001",status="PROMISED", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10001", inventoryItemDetailSeqId="10002", ATPDIFF="-1", > QOHDIFF="0", AQTDIFF="0" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" statusEndDateTime="" > inventoryItemId="10002" statusId="PROMISED" > 2. *Non-serialised*:- > At the time of receive non-serialised inventory, Item should be received > in Available status. So that status of non-serialised inventory item can be > managed further. > Status of non-serialised inventory item should be managed at inventory > item level not on inventory item detail level i.e. there are limited >
[jira] [Updated] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9475: --- Attachment: (was: OFBIZ-9475.patch) > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement > Components: hhfacility >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, OFBIZ-9475.patch, OFBIZ-9475.patch, > OFBIZ-9475.patch, OFBIZ-9475.patch > > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialise and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > As we do a lot of discussion in the respective mail threads. > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > According to this email threads, I conclude that:- > There are 2 types of the inventory item in OFBiz. > 1. *Serialized* > 2. *Non serialized* > Majorly there are 3 entities to manage the various transaction of serialised > and non-serialized inventory items. > 1. _InventoryItem_ > 2. _InventoryItemDetail_ > 3. _InventoryItemStatus_ > Following changes need to be done in the workflow of inventory item records:- > 1) There is no need to manage a different workflow for serialised and non- > serialised inventory items. > 2) Transaction of serialised and non-serialised inventory item should be > managed in both InventoryItemStatus and InventoryItemDetail entity. > a) Transaction of serialised inventory items is managed by > inventoryItemstatus entity not managed in inventoryItemDetail entity. While > inventoryItemDetail and inventoryItemStatus should be managed for both > serialised and non-serialised inventory items. > b) As ATP/QOH/AQT are updated on the basis of ATPDIFF/QOHDIFF/AQTDIFF in > non-serialised inventory item. We should follow the same pattern for > serialised inventory item. > c) Change in ATP/QOH/AQT is tracked by inventoryItemDetail entity. > d)Status transaction of an inventory item is tracked in > InventoryItemStatus entity. > 3) No need to manage separate status for serialised and non-serialised > inventory item. They are already distinguished on the basis of inventory item > type. > 1. *Serialised*:- > In a serialised inventory item as of now ATP/QOH/AQT are managed on the > basis of inventory item status.While ATP/QOH/AQT should be the sum of > ATPDIFF/QOHDIFF/AQTDIFF of inventory item detail. > Ex: > 1. If we receive 2 inventory of serialised inventory item then 2 separate > inventory item records are created > InventoryItem:- > inventoryItemId="10001",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" > inventoryItemId="10002" statusId="AVAILABLE" > 2. If status of inventory item is changed from AVAILABLE -> PROMISED then > InventoryItem:- > inventoryItemId="10001",status="PROMISED", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10001", inventoryItemDetailSeqId="10002", ATPDIFF="-1", > QOHDIFF="0", AQTDIFF="0" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" statusEndDateTime="" > inventoryItemId="10002" statusId="PROMISED" > 2. *Non-serialised*:- > At the time of receive non-serialised inventory, Item should be received > in Available status. So that status of non-serialised inventory item can be > managed further. > Status of non-serialised inventory item should be managed at inventory > item level not on inventory item detail level i.e. there are
[jira] [Updated] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yashwant Dhakad updated OFBIZ-9475: --- Attachment: OFBIZ-9475.patch > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement > Components: hhfacility >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9475.patch, OFBIZ-9475.patch, OFBIZ-9475.patch, > OFBIZ-9475.patch, OFBIZ-9475.patch > > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialise and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > As we do a lot of discussion in the respective mail threads. > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 > According to this email threads, I conclude that:- > There are 2 types of the inventory item in OFBiz. > 1. *Serialized* > 2. *Non serialized* > Majorly there are 3 entities to manage the various transaction of serialised > and non-serialized inventory items. > 1. _InventoryItem_ > 2. _InventoryItemDetail_ > 3. _InventoryItemStatus_ > Following changes need to be done in the workflow of inventory item records:- > 1) There is no need to manage a different workflow for serialised and non- > serialised inventory items. > 2) Transaction of serialised and non-serialised inventory item should be > managed in both InventoryItemStatus and InventoryItemDetail entity. > a) Transaction of serialised inventory items is managed by > inventoryItemstatus entity not managed in inventoryItemDetail entity. While > inventoryItemDetail and inventoryItemStatus should be managed for both > serialised and non-serialised inventory items. > b) As ATP/QOH/AQT are updated on the basis of ATPDIFF/QOHDIFF/AQTDIFF in > non-serialised inventory item. We should follow the same pattern for > serialised inventory item. > c) Change in ATP/QOH/AQT is tracked by inventoryItemDetail entity. > d)Status transaction of an inventory item is tracked in > InventoryItemStatus entity. > 3) No need to manage separate status for serialised and non-serialised > inventory item. They are already distinguished on the basis of inventory item > type. > 1. *Serialised*:- > In a serialised inventory item as of now ATP/QOH/AQT are managed on the > basis of inventory item status.While ATP/QOH/AQT should be the sum of > ATPDIFF/QOHDIFF/AQTDIFF of inventory item detail. > Ex: > 1. If we receive 2 inventory of serialised inventory item then 2 separate > inventory item records are created > InventoryItem:- > inventoryItemId="10001",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" > inventoryItemId="10002" statusId="AVAILABLE" > 2. If status of inventory item is changed from AVAILABLE -> PROMISED then > InventoryItem:- > inventoryItemId="10001",status="PROMISED", ATP="1", QOH="1",AQT="1" > inventoryItemId="10002",status="AVAILABLE", ATP="1", QOH="1",AQT="1" > InventoryItemDetail:- > inventoryItemId="10001", inventoryItemDetailSeqId="10001", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > inventoryItemId="10001", inventoryItemDetailSeqId="10002", ATPDIFF="-1", > QOHDIFF="0", AQTDIFF="0" > inventoryItemId="10002", inventoryItemDetailSeqId="10002", ATPDIFF="1", > QOHDIFF="1", AQTDIFF="1" > InventoryItemStatus:- > inventoryItemId="10001" statusId="AVAILABLE" statusEndDateTime="" > inventoryItemId="10002" statusId="PROMISED" > 2. *Non-serialised*:- > At the time of receive non-serialised inventory, Item should be received > in Available status. So that status of non-serialised inventory item can be > managed further. > Status of non-serialised inventory item should be managed at inventory > item level not on inventory item detail level i.e. there are limited >
[jira] [Updated] (OFBIZ-10630) eCommerce - Return History Feature
[ https://issues.apache.org/jira/browse/OFBIZ-10630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-10630: - Description: While walk though the eCommerce application, noticed that we have Order History section there but we don't have Return History. So based upon community's approval we have to add support for "Return History" feature in eCommerce application. Items needs to be implemented under this ticket : - Add new navigation for return history. - Display list of returns submitted by the customer along with basic details. - Customer should be able to view return details by clicking upon view link OR returnID. Thanks to all the members for the discussion and approval. was: While walk though the eCommerce application, noticed that we have Order History section there but we don't have Return History. So based upon community's approval we have to add support for "Return History" feature in eCommerce application. Items needs to be implemented under this ticket : - Add new navigation for return history. - Display list of returns submitted by the customer along with basic details. - Customer should be able to view return details by clicking upon view link OR returnID. Thanks to all the members for the discussion and approval. > eCommerce - Return History Feature > -- > > Key: OFBIZ-10630 > URL: https://issues.apache.org/jira/browse/OFBIZ-10630 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: Ratnesh Upadhyay >Priority: Major > Fix For: Trunk > > > While walk though the eCommerce application, noticed that we have Order > History section there but we don't have Return History. So based upon > community's approval we have to add support for "Return History" feature in > eCommerce application. > Items needs to be implemented under this ticket : > - Add new navigation for return history. > - Display list of returns submitted by the customer along with basic details. > - Customer should be able to view return details by clicking upon view link > OR returnID. > > Thanks to all the members for the discussion and approval. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10630) eCommerce - Return History Feature
Ratnesh Upadhyay created OFBIZ-10630: Summary: eCommerce - Return History Feature Key: OFBIZ-10630 URL: https://issues.apache.org/jira/browse/OFBIZ-10630 Project: OFBiz Issue Type: New Feature Components: ecommerce Affects Versions: Trunk Reporter: Ratnesh Upadhyay Assignee: Ratnesh Upadhyay Fix For: Trunk While walk though the eCommerce application, noticed that we have Order History section there but we don't have Return History. So based upon community's approval we have to add support for "Return History" feature in eCommerce application. Items needs to be implemented under this ticket : - Add new navigation for return history. - Display list of returns submitted by the customer along with basic details. - Customer should be able to view return details by clicking upon view link OR returnID. Thanks to all the members for the discussion and approval. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10315) Update Contact Mech ID with Billing Account not working
[ https://issues.apache.org/jira/browse/OFBIZ-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-10315: - Assignee: Suraj Khurana (was: Shikha Jaiswal) > Update Contact Mech ID with Billing Account not working > > > Key: OFBIZ-10315 > URL: https://issues.apache.org/jira/browse/OFBIZ-10315 > Project: OFBiz > Issue Type: Bug > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Aayush jain >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10315.patch > > > Steps: > 1. Open URL > https://demo-trunk.ofbiz.apache.org/accounting/control/updateBillingAccount > 2. Edit/Update Contact Mech ID using dropdown > Actual Result: > Display a success message for update action, but when the page is refreshed > or again we navigate from Billing account. Updated contact mech id is not > displayed > Expected Result: > Contact Mech ID should be updated with new successfully. > Thanks in advance! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Joshi reassigned OFBIZ-10577: --- Assignee: Ankit Joshi (was: Yashwant Dhakad) > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Ankit Joshi >Priority: Major > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > *ProductCategoryFacilityLocation* > facilityId > locationSeqId > productCategoryId > fromDate > thruDate > isCountable > *Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > *ProductCategory* > isCountable > We will prevent following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving > Inventory receive > Issuance and return inventory in manufacturing Job > Kit breakup > Update Location > Physical Variance creation > The locked locations won’t have any bearing on the transactions that are > affecting the only ATP of parts i.e. Reserving component for
[jira] [Commented] (OFBIZ-10577) New Feature: Inventory Cycle Count
[ https://issues.apache.org/jira/browse/OFBIZ-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1072#comment-1072 ] Ankit Joshi commented on OFBIZ-10577: - Hi all, Started implementing the feature suggested and done following: -- Added required data modal entities. -- UX for Find session screen. Currently working on: -- UX to view the pending locations. -- Service to create a new session. Soon enough, I'll upload a patch for this feature. > New Feature: Inventory Cycle Count > -- > > Key: OFBIZ-10577 > URL: https://issues.apache.org/jira/browse/OFBIZ-10577 > Project: OFBiz > Issue Type: New Feature > Components: hhfacility >Affects Versions: Trunk >Reporter: Yashwant Dhakad >Assignee: Yashwant Dhakad >Priority: Major > > *Here are the design notes for cycle count workflow:* > *Find Session Screen:* In this screen, we will show all the sessions created > in the system with respect to the facility, locations, inventory count item, > current status, and created date. We have a search field to filter the > records on the basis of the facility, status. > *Find Pending Locations:* In this screen, we have a table listing all the > pending locations whose countings are pending and we can create a session for > them. All details regarding the pending locations are listed here with the > location, next count date, last count date and days extended for the count, > total inventory item and product for this location. We have facets for > filtering the records on the basis of the facility, not scanned since and > scheduled for next scan. Also, we have a global search at the top of the > screen. In Pending Locations screen, we have a Create Session button. To > create a session we can either select one or more records from the below list > or create a new session by yourself. > In Create Session screen, the basic overview is shown in the "Overview" > section and the items are listed in the "Items" section. We can create a new > line item by clicking on the 'Add' button and we can also update the item > quantity. After completing this, we can proceed with this session and mark it > with 'Pending for Review' status from the 'Status' button at the top of the > screen or we can simply 'Reject'. 'Reject' status button is available at the > top of the screen. > *Find Review Screen:* In this screen, we have a table listing all the > locations pending for the review. All the details regarding the review > sessions are listed with the facility, locations and counted inventory item. > We have facets for filtering records on the basis of the facility. By > clicking any session we can go to its detail screen, where basic details > regarding this session are listed in the 'Overview' section and items are > listed in the 'Items' section. We can select any number of rows and mark them > as 'Accept' or 'Reject'. When these items are marked as 'Accepted' then the > variance is created and these are added in the Count Progress report. Only > authorized persons can accept or reject the sessions and once the session is > accepted it is marked as 'Completed'. > *Count Progress Report:* In this screen, User can view the advanced counting > related analytics with respect to all the 'Completed' status session from > Reports Screen. We can filter the records on the basis of the facility and > within the date range. We can also see the percentage of the total locations, > inventory items counted and errors occurred during the process. Item variance > details are listed in the below section in tabular form. > Following changes to the existing data model to support end to end counting > process flow: > *New entities:* > *InventoryCount* > inventoryCountId > uploadedByUserLogin > facilityId > statusId > createdDatetime > *InventoryCountItem* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > itemStatusId > locationSeqId > productId > productIdentifier > quantity > *InventoryCountVariance* > inventoryCountId > inventoryCountItemSeqId > inventoryItemId > productId > productIdentifier > locationSeqId > systemQuantityOnHand > actualQuantityOnHand > varianceQuantityOnHand > totalCost > actualCost > costVariance > actualValue > totalValue > valueVariance > unitCost > *ProductCategoryFacilityLocation* > facilityId > locationSeqId > productCategoryId > fromDate > thruDate > isCountable > *Extended entity:* > *FacilityLocation* > locked > lastCountDate > nextCountDate > *ProductCategory* > isCountable > We will prevent following inbound and outbound transactions within the > application if the location is locked for counting: > Inventory Transfer > Issuance against Sales Order > Sales Return receiving >
[jira] [Commented] (OFBIZ-10629) View Request button should not display when there is no customer request data on Quote Items screen
[ https://issues.apache.org/jira/browse/OFBIZ-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1071#comment-1071 ] kumar Rahul commented on OFBIZ-10629: - Added patch to show button link for View Request column only when cust request id is there. > View Request button should not display when there is no customer request data > on Quote Items screen > --- > > Key: OFBIZ-10629 > URL: https://issues.apache.org/jira/browse/OFBIZ-10629 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ritesh Kumar >Assignee: kumar Rahul >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10629.patch > > > Currently on the Quote Items screen, in the view request column, a button > link is shown even though there is no customer request data. > Steps to regenerate: > * Create a quote from ordermgs> Quotes screen. > * On the Quote items screen, create Quote item. While creating, do not add > cust request value. > * when an item is added to quote, check the view request column, a button > link will be visible. This button link should not be visible if cust request > data is not there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10629) View Request button should not display when there is no customer request data on Quote Items screen
[ https://issues.apache.org/jira/browse/OFBIZ-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kumar Rahul updated OFBIZ-10629: Attachment: OFBIZ-10629.patch > View Request button should not display when there is no customer request data > on Quote Items screen > --- > > Key: OFBIZ-10629 > URL: https://issues.apache.org/jira/browse/OFBIZ-10629 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ritesh Kumar >Assignee: kumar Rahul >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10629.patch > > > Currently on the Quote Items screen, in the view request column, a button > link is shown even though there is no customer request data. > Steps to regenerate: > * Create a quote from ordermgs> Quotes screen. > * On the Quote items screen, create Quote item. While creating, do not add > cust request value. > * when an item is added to quote, check the view request column, a button > link will be visible. This button link should not be visible if cust request > data is not there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-6892) new action expire for service engine entity-auto
[
https://issues.apache.org/jira/browse/OFBIZ-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1070#comment-1070
]
Lalit Dashora commented on OFBIZ-6892:
--
Hi,
I faced an issue of status valid change if no transactions are found. The
system was throwing an error. The patch provided in this ticket shows commented
line for putting lookedUpValue in localcontext.
{code:java}
localContext.put("lookedUpValue", lookedUpValue);{code}
I have fixed this issue in the ticket TicketID: OFBIZ-10377. I have also
provided the patch for the same. If this looks good to you then we can proceed.
Thanks!
> new action expire for service engine entity-auto
>
>
> Key: OFBIZ-6892
> URL: https://issues.apache.org/jira/browse/OFBIZ-6892
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Fix For: 16.11.01
>
> Attachments: OFBIZ-6892.patch
>
>
> Relate to the thread
> http://ofbiz.135035.n4.nabble.com/entity-auto-and-cancel-operation-td4676929.html
> on the dev mailing list, I load the patch to manage the action expire.
> When you call *expire* on a entity :
> * if a date field is present on service attribute, OFBiz try to expire it
> with the given value or with now date
> * else try to expire thruDate field
> * else try to expire *ThruDate or thru*Date field
> The patch contains the new action, a code refactoring to separate each action
> on dedicate function and unit test associate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10377) Missing oldStatusId in error when no status valid change record found
[ https://issues.apache.org/jira/browse/OFBIZ-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lalit Dashora updated OFBIZ-10377: -- Attachment: StatusIssue.patch > Missing oldStatusId in error when no status valid change record found > - > > Key: OFBIZ-10377 > URL: https://issues.apache.org/jira/browse/OFBIZ-10377 > Project: OFBiz > Issue Type: Improvement >Reporter: Lalit Dashora >Assignee: Lalit Dashora >Priority: Major > Attachments: StatusIssue.patch > > > If no transaction for status valid change is found, OldStatusId is missing on > the console while showing error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10377) Missing oldStatusId in error when no status valid change record found
[ https://issues.apache.org/jira/browse/OFBIZ-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lalit Dashora updated OFBIZ-10377: -- Attachment: (was: OldStatusIdMissingPatch.patch) > Missing oldStatusId in error when no status valid change record found > - > > Key: OFBIZ-10377 > URL: https://issues.apache.org/jira/browse/OFBIZ-10377 > Project: OFBiz > Issue Type: Improvement >Reporter: Lalit Dashora >Assignee: Lalit Dashora >Priority: Major > Attachments: StatusIssue.patch > > > If no transaction for status valid change is found, OldStatusId is missing on > the console while showing error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10628) Quote list is not showing on ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammed Rehan Khan updated OFBIZ-10628: Attachment: OFBIZ-10628-Release-17.12.patch OFBIZ-10628-Trunk.patch > Quote list is not showing on ecommerce > -- > > Key: OFBIZ-10628 > URL: https://issues.apache.org/jira/browse/OFBIZ-10628 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, Release Branch 17.12 >Reporter: Mohammed Rehan Khan >Assignee: Mohammed Rehan Khan >Priority: Minor > Attachments: OFBIZ-10628-Release-17.12.patch, OFBIZ-10628-Trunk.patch > > > Steps to reproduce the issue: > # Visit: https://demo-trunk-ofbiz.apache.org/ecommerce/control/main > # Click on the ShoppingList button > # Create new shopping list if does not exits > # Click on create new quote link on shopping list detail section > # Now click on Quotes button (Right top) > Result: Quotes details are not showing > Expected Result: Quotes details should be displayed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10628) Quote list is not showing on ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1069#comment-1069 ] Mohammed Rehan Khan commented on OFBIZ-10628: - Here is patch to fix the issue > Quote list is not showing on ecommerce > -- > > Key: OFBIZ-10628 > URL: https://issues.apache.org/jira/browse/OFBIZ-10628 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk, Release Branch 17.12 >Reporter: Mohammed Rehan Khan >Assignee: Mohammed Rehan Khan >Priority: Minor > Attachments: OFBIZ-10628-Release-17.12.patch, OFBIZ-10628-Trunk.patch > > > Steps to reproduce the issue: > # Visit: https://demo-trunk-ofbiz.apache.org/ecommerce/control/main > # Click on the ShoppingList button > # Create new shopping list if does not exits > # Click on create new quote link on shopping list detail section > # Now click on Quotes button (Right top) > Result: Quotes details are not showing > Expected Result: Quotes details should be displayed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10629) View Request button should not display when there is no customer request data on Quote Items screen
Ritesh Kumar created OFBIZ-10629: Summary: View Request button should not display when there is no customer request data on Quote Items screen Key: OFBIZ-10629 URL: https://issues.apache.org/jira/browse/OFBIZ-10629 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Ritesh Kumar Assignee: kumar Rahul Fix For: Trunk Currently on the Quote Items screen, in the view request column, a button link is shown even though there is no customer request data. Steps to regenerate: * Create a quote from ordermgs> Quotes screen. * On the Quote items screen, create Quote item. While creating, do not add cust request value. * when an item is added to quote, check the view request column, a button link will be visible. This button link should not be visible if cust request data is not there. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9921) Payment transactions should use company currency
[ https://issues.apache.org/jira/browse/OFBIZ-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akshay Modak reassigned OFBIZ-9921: --- Assignee: Akshay Modak > Payment transactions should use company currency > > > Key: OFBIZ-9921 > URL: https://issues.apache.org/jira/browse/OFBIZ-9921 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Akash Jain >Assignee: Akshay Modak >Priority: Minor > > In case of multi-currency, payment transactions posted in company currency > for purchase order (PO) and customer currency for sales order (SO). For > consistency, payment transactions should be posted in company currency for > SO. For more detail, http://markmail.org/message/klrnzkpvcr2mk33l -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9358) Integrating google phone number library for validating telecom numbers
[ https://issues.apache.org/jira/browse/OFBIZ-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-9358: Description: As per discussion at https://lists.apache.org/thread.html/8279f19b83392f3b0f2956f64d3b55e95405b0dcc730d0979e290c91@%3Cdev.ofbiz.apache.org%3E Need to integrate Google telephone number to validate telephone numbers formats of various countries. was: As per discussion at https://lists.apache.org/list.html?d...@ofbiz.apache.org:lte=1M:Validating%20telecom%20numbers Need to integrate Google telephone number to validate telephone numbers formats of various countries. > Integrating google phone number library for validating telecom numbers > -- > > Key: OFBIZ-9358 > URL: https://issues.apache.org/jira/browse/OFBIZ-9358 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: 17.12.01 >Reporter: Suraj Khurana >Assignee: Arun Patidar >Priority: Major > Fix For: 17.12.01 > > Attachments: OFBIZ-9358.patch, OFBIZ-9358.patch, OFBIZ-9358.patch, > OFBIZ-9358.patch, OFBIZ-9358.patch > > > As per discussion at > > https://lists.apache.org/thread.html/8279f19b83392f3b0f2956f64d3b55e95405b0dcc730d0979e290c91@%3Cdev.ofbiz.apache.org%3E > Need to integrate Google telephone number to validate telephone numbers > formats of various countries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10628) Quote list is not showing on ecommerce
Mohammed Rehan Khan created OFBIZ-10628: --- Summary: Quote list is not showing on ecommerce Key: OFBIZ-10628 URL: https://issues.apache.org/jira/browse/OFBIZ-10628 Project: OFBiz Issue Type: Bug Components: ecommerce Affects Versions: Trunk, Release Branch 17.12 Reporter: Mohammed Rehan Khan Assignee: Mohammed Rehan Khan Steps to reproduce the issue: # Visit: https://demo-trunk-ofbiz.apache.org/ecommerce/control/main # Click on the ShoppingList button # Create new shopping list if does not exits # Click on create new quote link on shopping list detail section # Now click on Quotes button (Right top) Result: Quotes details are not showing Expected Result: Quotes details should be displayed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10618) Update google libphonenumber to v8.9.16
[ https://issues.apache.org/jira/browse/OFBIZ-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1066#comment-1066 ] Deepak Dixit commented on OFBIZ-10618: -- Hi [~pfm.smits] Have you checked in code? > Update google libphonenumber to v8.9.16 > - > > Key: OFBIZ-10618 > URL: https://issues.apache.org/jira/browse/OFBIZ-10618 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Major > Fix For: 17.12.01 > > > The new release contains mostly [metadata > changes|https://github.com/googlei18n/libphonenumber/blob/master/FAQ.md#metadata_definition]. > https://github.com/googlei18n/libphonenumber/blob/master/release_notes.txt > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10538) Promised Datetime & Current Promised Date values not getting updated in OISGIR Entity
[ https://issues.apache.org/jira/browse/OFBIZ-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1065#comment-1065 ] Ravi Lodhi commented on OFBIZ-10538: I was looking into this, here are my findings, In the create order process OrderItemShipGrpInvRes.promisedDateTime and OrderItemShipGrpInvRes.currentPromisedDate fields are set by reserverOrderItemInventory service which is called from reserveProductInventoryByFacility service. While updating "Ship Before Date" from order detail page, it just updates the OrderItemShipGroup.shipByDate by calling the service updateOrderItemShipGroup. OrderItem.shipBeforeDate, OrderItemShipGrpInvRes.promisedDateTime and OrderItemShipGrpInvRes.currentPromisedDate fields doesn't get updated. > Promised Datetime & Current Promised Date values not getting updated in > OISGIR Entity > - > > Key: OFBIZ-10538 > URL: https://issues.apache.org/jira/browse/OFBIZ-10538 > Project: OFBiz > Issue Type: Bug > Components: order, product >Affects Versions: Trunk >Reporter: Deepak Nigam >Priority: Major > > While creating the sales order from the backend, if we set the 'Ship Before > Date' it will be stored in OrderItemShipGroup.shipByDate field and same will > be propagated to OrderItemShipGrpInvRes.promisedDateTime and > OrderItemShipGrpInvRes.currentPromisedDate fields. > > On updating the 'Ship Before Date' from the order view page later, the > promisedDateTime and currentPromisedDate get updated in OrderItemShipGroup > entity but remains the same in OrderItemShipGroupInvRes entity. > > As OrderItemShipGrpInvRes.promisedDateTime & > OrderItemShipGrpInvRes.currentPromisedDate are being used in many services > like 'getOrderItemShipGroupEstimatedShipDate', 'getItemBackOrderedQuantity', > 'reserveProductInventory' etc., we should also update these on updating the > 'Ship Before Date' from the order overview page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10314) Multiple rows are getting created on updating Party details
[ https://issues.apache.org/jira/browse/OFBIZ-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1064#comment-1064 ] Shikha Jaiswal commented on OFBIZ-10314: Attached the patch for Release-17.12 and Release-16.11 (stable) > Multiple rows are getting created on updating Party details > --- > > Key: OFBIZ-10314 > URL: https://issues.apache.org/jira/browse/OFBIZ-10314 > Project: OFBiz > Issue Type: Bug > Components: webpos > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > >Reporter: Archana Asthana >Assignee: Shikha Jaiswal >Priority: Major > Attachments: 1034.png, EditPartydetails.png, > OFBIZ-10314-release16.11.patch, OFBIZ-10314-release17.12.patch, > OFBIZ-10314.patch, Working_fine.png > > > Steps to regenerate: > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Click Search Button to search Party > In the opened modal, check the box of any customer > Another model gets open to update the detail > Enter the required detail/s and click update > Multiple rows of the same customer are getting created in the Party search > Modal > Image is attached for reference. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9912) Force complete Purchase Order button throws error
[ https://issues.apache.org/jira/browse/OFBIZ-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1063#comment-1063 ] Amit Gadaley commented on OFBIZ-9912: - Provided patch. Thanks, [~mridul.pathak] for guidance. > Force complete Purchase Order button throws error > - > > Key: OFBIZ-9912 > URL: https://issues.apache.org/jira/browse/OFBIZ-9912 > Project: OFBiz > Issue Type: Bug > Environment: https://demo-trunk.ofbiz.apache.org/facility >Reporter: Priya Sharma >Assignee: Amit Gadaley >Priority: Major > Attachments: Force-receive-PO.png, OFBIZ-9912.patch > > > 1) Create a Purchase order. > 2) Create shipment for it. > 3) Click on receive against PO button > [https://demo-trunk.ofbiz.apache.org/facility/control/ReceiveInventoryAgainstPurchaseOrder?shipmentId=10024=10040] > 4) Click on the force complete PO button, error is thrown. > [https://demo-trunk.ofbiz.apache.org/facility/control/completePurchaseOrder?orderId=10040=WebStoreWarehouse=10024] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10013) Screen Rendering issue on Payment Overview screen
[ https://issues.apache.org/jira/browse/OFBIZ-10013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakhar Kumar reassigned OFBIZ-10013: - Assignee: Prakhar Kumar (was: Ankush Upadhyay) > 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: Trunk, Release Branch 16.11 >Reporter: Pritam Kute >Assignee: Prakhar Kumar >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10013) Screen Rendering issue on Payment Overview screen
[ https://issues.apache.org/jira/browse/OFBIZ-10013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1062#comment-1062 ] Prakhar Kumar commented on OFBIZ-10013: --- Able to regenerate the issue. Looking into it. > 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: Trunk, Release Branch 16.11 >Reporter: Pritam Kute >Assignee: Ankush Upadhyay >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9912) Force complete Purchase Order button throws error
[ https://issues.apache.org/jira/browse/OFBIZ-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Gadaley updated OFBIZ-9912: Attachment: OFBIZ-9912.patch > Force complete Purchase Order button throws error > - > > Key: OFBIZ-9912 > URL: https://issues.apache.org/jira/browse/OFBIZ-9912 > Project: OFBiz > Issue Type: Bug > Environment: https://demo-trunk.ofbiz.apache.org/facility >Reporter: Priya Sharma >Assignee: Amit Gadaley >Priority: Major > Attachments: Force-receive-PO.png, OFBIZ-9912.patch > > > 1) Create a Purchase order. > 2) Create shipment for it. > 3) Click on receive against PO button > [https://demo-trunk.ofbiz.apache.org/facility/control/ReceiveInventoryAgainstPurchaseOrder?shipmentId=10024=10040] > 4) Click on the force complete PO button, error is thrown. > [https://demo-trunk.ofbiz.apache.org/facility/control/completePurchaseOrder?orderId=10040=WebStoreWarehouse=10024] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (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 ] Suraj Khurana closed OFBIZ-10017. - Resolution: Won't Fix > 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 >Assignee: Ayushi Rathod >Priority: Major > 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 (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10017) Alignment Issue on Variant product view page
[ https://issues.apache.org/jira/browse/OFBIZ-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1061#comment-1061 ] Suraj Khurana commented on OFBIZ-10017: --- Thanks Ayushi for verifying this. As per comments, I am closing the ticket. > 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 >Assignee: Ayushi Rathod >Priority: Major > 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 (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9912) Force complete Purchase Order button throws error
[ https://issues.apache.org/jira/browse/OFBIZ-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Gadaley reassigned OFBIZ-9912: --- Assignee: Amit Gadaley > Force complete Purchase Order button throws error > - > > Key: OFBIZ-9912 > URL: https://issues.apache.org/jira/browse/OFBIZ-9912 > Project: OFBiz > Issue Type: Bug > Environment: https://demo-trunk.ofbiz.apache.org/facility >Reporter: Priya Sharma >Assignee: Amit Gadaley >Priority: Major > Attachments: Force-receive-PO.png > > > 1) Create a Purchase order. > 2) Create shipment for it. > 3) Click on receive against PO button > [https://demo-trunk.ofbiz.apache.org/facility/control/ReceiveInventoryAgainstPurchaseOrder?shipmentId=10024=10040] > 4) Click on the force complete PO button, error is thrown. > [https://demo-trunk.ofbiz.apache.org/facility/control/completePurchaseOrder?orderId=10040=WebStoreWarehouse=10024] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10583) Issue while creating any new event
[ https://issues.apache.org/jira/browse/OFBIZ-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-10583. - > Issue while creating any new event > -- > > Key: OFBIZ-10583 > URL: https://issues.apache.org/jira/browse/OFBIZ-10583 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: CreateEventIssue.jpg, OFBIZ-10583.patch > > > Steps to regenerate: > # Navigate to > [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. > # Try to create a new event. > # On clicking Add button an error occurs. > # Attached the screenshot of the error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10583) Issue while creating any new event
[ https://issues.apache.org/jira/browse/OFBIZ-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana updated OFBIZ-10583: -- Affects Version/s: (was: Release Branch 17.12) > Issue while creating any new event > -- > > Key: OFBIZ-10583 > URL: https://issues.apache.org/jira/browse/OFBIZ-10583 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: CreateEventIssue.jpg, OFBIZ-10583.patch > > > Steps to regenerate: > # Navigate to > [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. > # Try to create a new event. > # On clicking Add button an error occurs. > # Attached the screenshot of the error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10583) Issue while creating any new event
[ https://issues.apache.org/jira/browse/OFBIZ-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana updated OFBIZ-10583: -- Fix Version/s: Upcoming Branch > Issue while creating any new event > -- > > Key: OFBIZ-10583 > URL: https://issues.apache.org/jira/browse/OFBIZ-10583 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Sonal Patwari >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: CreateEventIssue.jpg, OFBIZ-10583.patch > > > Steps to regenerate: > # Navigate to > [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. > # Try to create a new event. > # On clicking Add button an error occurs. > # Attached the screenshot of the error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10627) Submit button should not display when there is no item present over Quote Prices Screen
[ https://issues.apache.org/jira/browse/OFBIZ-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay reassigned OFBIZ-10627: Assignee: kumar Rahul (was: Ratnesh Upadhyay) > Submit button should not display when there is no item present over Quote > Prices Screen > --- > > Key: OFBIZ-10627 > URL: https://issues.apache.org/jira/browse/OFBIZ-10627 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: kumar Rahul >Priority: Major > Fix For: Trunk > > Attachments: QuotePrices.png > > > Currently system is showing submit button even though there is no rows to > process. Ideally it should not display is there is nothing to submit. > Steps to replicate the issue: > * Create Quote from OrderMgr>Quotes screen. > * Navigate over Quote Prices Screen. > * In Quote Prices screenlet, here system is showing submit button even > though there is no quote items to process. > Please refer attached screenshot for quick details. > !QuotePrices.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10627) Submit button should not display when there is no item present over Quote Prices Screen
Ratnesh Upadhyay created OFBIZ-10627: Summary: Submit button should not display when there is no item present over Quote Prices Screen Key: OFBIZ-10627 URL: https://issues.apache.org/jira/browse/OFBIZ-10627 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Ratnesh Upadhyay Assignee: Ratnesh Upadhyay Fix For: Trunk Attachments: QuotePrices.png Currently system is showing submit button even though there is no rows to process. Ideally it should not display is there is nothing to submit. Steps to replicate the issue: * Create Quote from OrderMgr>Quotes screen. * Navigate over Quote Prices Screen. * In Quote Prices screenlet, here system is showing submit button even though there is no quote items to process. Please refer attached screenshot for quick details. !QuotePrices.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10583) Issue while creating any new event
[ https://issues.apache.org/jira/browse/OFBIZ-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1053#comment-1053 ] Praveen Sharma commented on OFBIZ-10583: The issue only persists for OFBiz trunk. Unable to regenerate issue on 16.12 and 17.12 instances. > Issue while creating any new event > -- > > Key: OFBIZ-10583 > URL: https://issues.apache.org/jira/browse/OFBIZ-10583 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 17.12 >Reporter: Sonal Patwari >Assignee: Suraj Khurana >Priority: Major > Attachments: CreateEventIssue.jpg, OFBIZ-10583.patch > > > Steps to regenerate: > # Navigate to > [Events|https://demo-trunk.ofbiz.apache.org/sfa/control/Events]. > # Try to create a new event. > # On clicking Add button an error occurs. > # Attached the screenshot of the error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10366) Proper User friendly message should visible at Create Inventory Transfer screen
[ https://issues.apache.org/jira/browse/OFBIZ-10366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1054#comment-1054 ] Ritesh Kumar commented on OFBIZ-10366: -- Added patch for showing a user-friendly message. The message will show the unavailable quantity and the total quantity to be transferred. I have also removed unrequired error messages. > Proper User friendly message should visible at Create Inventory Transfer > screen > --- > > Key: OFBIZ-10366 > URL: https://issues.apache.org/jira/browse/OFBIZ-10366 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-10366.patch, OFBIZ-10366.png > > > Steps to regenerate: > # Go to facility component. > # Select any facility. > # Click on Inventory Xfers. > # Now click on Inventory Transfer to create new Inventory Transfer. > # Now add any product id and submit > # At "Quantity To Transfer" field add quantity more than ATP. > # See the error message. PFA for error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: OFBiz-10620.patch > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: OFBiz-10620.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10366) Proper User friendly message should visible at Create Inventory Transfer screen
[ https://issues.apache.org/jira/browse/OFBIZ-10366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar updated OFBIZ-10366: - Attachment: OFBIZ-10366.patch > Proper User friendly message should visible at Create Inventory Transfer > screen > --- > > Key: OFBIZ-10366 > URL: https://issues.apache.org/jira/browse/OFBIZ-10366 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-10366.patch, OFBIZ-10366.png > > > Steps to regenerate: > # Go to facility component. > # Select any facility. > # Click on Inventory Xfers. > # Now click on Inventory Transfer to create new Inventory Transfer. > # Now add any product id and submit > # At "Quantity To Transfer" field add quantity more than ATP. > # See the error message. PFA for error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10314) Multiple rows are getting created on updating Party details
[ https://issues.apache.org/jira/browse/OFBIZ-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikha Jaiswal updated OFBIZ-10314: --- Attachment: OFBIZ-10314-release16.11.patch > Multiple rows are getting created on updating Party details > --- > > Key: OFBIZ-10314 > URL: https://issues.apache.org/jira/browse/OFBIZ-10314 > Project: OFBiz > Issue Type: Bug > Components: webpos > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > >Reporter: Archana Asthana >Assignee: Shikha Jaiswal >Priority: Major > Attachments: 1034.png, EditPartydetails.png, > OFBIZ-10314-release16.11.patch, OFBIZ-10314-release17.12.patch, > OFBIZ-10314.patch, Working_fine.png > > > Steps to regenerate: > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Click Search Button to search Party > In the opened modal, check the box of any customer > Another model gets open to update the detail > Enter the required detail/s and click update > Multiple rows of the same customer are getting created in the Party search > Modal > Image is attached for reference. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10314) Multiple rows are getting created on updating Party details
[ https://issues.apache.org/jira/browse/OFBIZ-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikha Jaiswal updated OFBIZ-10314: --- Attachment: OFBIZ-10314-release17.12.patch > Multiple rows are getting created on updating Party details > --- > > Key: OFBIZ-10314 > URL: https://issues.apache.org/jira/browse/OFBIZ-10314 > Project: OFBiz > Issue Type: Bug > Components: webpos > Environment: > [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > >Reporter: Archana Asthana >Assignee: Shikha Jaiswal >Priority: Major > Attachments: 1034.png, EditPartydetails.png, > OFBIZ-10314-release16.11.patch, OFBIZ-10314-release17.12.patch, > OFBIZ-10314.patch, Working_fine.png > > > Steps to regenerate: > Open [https://demo-trunk.ofbiz.apache.org/webpos/control/Login] > Click Search Button to search Party > In the opened modal, check the box of any customer > Another model gets open to update the detail > Enter the required detail/s and click update > Multiple rows of the same customer are getting created in the Party search > Modal > Image is attached for reference. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9557) Add the ability to schedule a job to run as a system/service user
[ https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Koushal reassigned OFBIZ-9557: Assignee: Jacques Le Roux (was: Rohit Koushal) > Add the ability to schedule a job to run as a system/service user > - > > Key: OFBIZ-9557 > URL: https://issues.apache.org/jira/browse/OFBIZ-9557 > Project: OFBiz > Issue Type: Improvement > Components: tools >Reporter: Matthew Mulligan >Assignee: Jacques Le Roux >Priority: Major > Attachments: OFBIZ-9557.patch > > > When scheduling a job it automatically schedules it to run as the user that > created the schedule. The issue comes up when that users password changes. > We use LDAP authentication and our passwords change every 90 days. Right now > every 90 days when my password changes I have to delete all previously > scheduled jobs and recreate them. > What would be nice is an option when scheduling the job to Run as System > account or Run as User and be able to put the users name in. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10626) Add Document Content: acc-glossary.adoc
Vaibhav Jain created OFBIZ-10626: Summary: Add Document Content: acc-glossary.adoc Key: OFBIZ-10626 URL: https://issues.apache.org/jira/browse/OFBIZ-10626 Project: OFBiz Issue Type: Sub-task Components: accounting Reporter: Vaibhav Jain Add content for acc-glossary.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9557) Add the ability to schedule a job to run as a system/service user
[
https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1052#comment-1052
]
Rohit Koushal commented on OFBIZ-9557:
--
Hi [~jacques.le.roux] ,
Attaching the patch for this improvement, which run Jobs as system user from
Schedule jobs screen.
For the permission thing I have created following data and assigning this
permission to the SUPER AND FULLADMIN group
{code}
{code}
Please review and test the changes and let me know if anything is missing.
> Add the ability to schedule a job to run as a system/service user
> -
>
> Key: OFBIZ-9557
> URL: https://issues.apache.org/jira/browse/OFBIZ-9557
> Project: OFBiz
> Issue Type: Improvement
> Components: tools
>Reporter: Matthew Mulligan
>Assignee: Rohit Koushal
>Priority: Major
> Attachments: OFBIZ-9557.patch
>
>
> When scheduling a job it automatically schedules it to run as the user that
> created the schedule. The issue comes up when that users password changes.
> We use LDAP authentication and our passwords change every 90 days. Right now
> every 90 days when my password changes I have to delete all previously
> scheduled jobs and recreate them.
> What would be nice is an option when scheduling the job to Run as System
> account or Run as User and be able to put the users name in.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10288) Move Accounting Guide into OFBiz Asciidoc Framework
[ https://issues.apache.org/jira/browse/OFBIZ-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Jain updated OFBIZ-10288: - Description: This is a general umbrella task for the creation and migration of all accounting related information and documentation into the OFBiz asciidoc documentation framework. Subtasks will be created for each area where documentation needs to be creaated. An initial list is as follows: # accounting.adoc (already created - may create an issue to track any additional work_ # acc-intro.adoc # acc-agreements.adoc # acc-tax-authorities.adoc # acc-invoices.adoc # acc-billing-accounts.adoc # acc-payments.adoc # acc-payment-gateway.adoc # acc-financial-accounts.adoc # acc-global-settings.adoc # acc-glossary.adoc was: This is a general umbrella task for the creation and migration of all accounting related information and documentation into the OFBiz asciidoc documentation framework. Subtasks will be created for each area where documentation needs to be creaated. An initial list is as follows: # accounting.adoc (already created - may create an issue to track any additional work_ # acc-intro.adoc # acc-agreements.adoc # acc-tax-authorities.adoc # acc-invoices.adoc # acc-billing-accounts.adoc # acc-payments.adoc # acc-payment-gateway.adoc # acc-financial-accounts.adoc # acc-global-settings.adoc > Move Accounting Guide into OFBiz Asciidoc Framework > --- > > Key: OFBIZ-10288 > URL: https://issues.apache.org/jira/browse/OFBIZ-10288 > Project: OFBiz > Issue Type: Task > Components: accounting >Reporter: Sharan Foga >Priority: Minor > Labels: accounting, asciidoc, documentation > Fix For: Upcoming Branch > > > This is a general umbrella task for the creation and migration of all > accounting related information and documentation into the OFBiz asciidoc > documentation framework. > Subtasks will be created for each area where documentation needs to be > creaated. An initial list is as follows: > # accounting.adoc (already created - may create an issue to track any > additional work_ > # acc-intro.adoc > # acc-agreements.adoc > # acc-tax-authorities.adoc > # acc-invoices.adoc > # acc-billing-accounts.adoc > # acc-payments.adoc > # acc-payment-gateway.adoc > # acc-financial-accounts.adoc > # acc-global-settings.adoc > # acc-glossary.adoc > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10625) Convert updateContent and removeContent service to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-10625: -- Summary: Convert updateContent and removeContent service to entity-auto (was: Convert updateContent and removeContent to entity-auto) > Convert updateContent and removeContent service to entity-auto > -- > > Key: OFBIZ-10625 > URL: https://issues.apache.org/jira/browse/OFBIZ-10625 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9557) Add the ability to schedule a job to run as a system/service user
[ https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Koushal updated OFBIZ-9557: - Attachment: OFBIZ-9557.patch > Add the ability to schedule a job to run as a system/service user > - > > Key: OFBIZ-9557 > URL: https://issues.apache.org/jira/browse/OFBIZ-9557 > Project: OFBiz > Issue Type: Improvement > Components: tools >Reporter: Matthew Mulligan >Assignee: Rohit Koushal >Priority: Major > Attachments: OFBIZ-9557.patch > > > When scheduling a job it automatically schedules it to run as the user that > created the schedule. The issue comes up when that users password changes. > We use LDAP authentication and our passwords change every 90 days. Right now > every 90 days when my password changes I have to delete all previously > scheduled jobs and recreate them. > What would be nice is an option when scheduling the job to Run as System > account or Run as User and be able to put the users name in. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10625) Convert updateContent and removeContent to entity-auto
Aditya Sharma created OFBIZ-10625: - Summary: Convert updateContent and removeContent to entity-auto Key: OFBIZ-10625 URL: https://issues.apache.org/jira/browse/OFBIZ-10625 Project: OFBiz Issue Type: Task Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Aditya Sharma Assignee: Aditya Sharma -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9743) updateContent service does not return an error/success message
[ https://issues.apache.org/jira/browse/OFBIZ-9743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1050#comment-1050 ] Aditya Sharma commented on OFBIZ-9743: -- Fixed for 17.12 at r1844954. It will be handled for trunk with OFBIZ-10625. > updateContent service does not return an error/success message > --- > > Key: OFBIZ-9743 > URL: https://issues.apache.org/jira/browse/OFBIZ-9743 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 >Reporter: Rohit Rai >Assignee: Aditya Sharma >Priority: Major > > 1. Go to Content, > 2. Click on Find in the search options to get a list of all the contents in > the system. > 3. Select a content from the list of content. > 4. Edit Content form should get opened. > 5. Click on update, the user is not presented with success or error message > on the screen. > Although, the service works and the content gets updated. > Here is a link to the issue, > https://demo-trunk.ofbiz.apache.org/content/control/editContent?contentId=TEMPLATE_MASTER -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10625) Convert updateContent and removeContent to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-10625: -- Issue Type: Sub-task (was: Task) Parent: OFBIZ-8408 > Convert updateContent and removeContent to entity-auto > -- > > Key: OFBIZ-10625 > URL: https://issues.apache.org/jira/browse/OFBIZ-10625 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10624) Dropdown/facet at Reports under 'Sale Orders By Channel' is not working fine.
[ https://issues.apache.org/jira/browse/OFBIZ-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dikpal Kanungo updated OFBIZ-10624: --- Summary: Dropdown/facet at Reports under 'Sale Orders By Channel' is not working fine. (was: Dropdown/facet at Reports under 'Sale Orders By Channel' are not working fine.) > Dropdown/facet at Reports under 'Sale Orders By Channel' is not working fine. > - > > Key: OFBIZ-10624 > URL: https://issues.apache.org/jira/browse/OFBIZ-10624 > Project: OFBiz > Issue Type: Bug >Reporter: Dikpal Kanungo >Priority: Trivial > Attachments: Facet.png > > > The facet should always display 'Select' or default option value (web > channel) in the list, right now it is blank. When a user clicks directly on > 'Run' without selecting any value from facet it generated the report > associated with the first element (web channel) in the list, though nothing > is selected from the list in the facet. !Facet.png! > Please have a look at the attached screenshot for quick reference. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10624) Dropdown/facet at Reports under 'Sale Orders By Channel' are not working fine.
Dikpal Kanungo created OFBIZ-10624: -- Summary: Dropdown/facet at Reports under 'Sale Orders By Channel' are not working fine. Key: OFBIZ-10624 URL: https://issues.apache.org/jira/browse/OFBIZ-10624 Project: OFBiz Issue Type: Bug Reporter: Dikpal Kanungo Attachments: Facet.png The facet should always display 'Select' or default option value (web channel) in the list, right now it is blank. When a user clicks directly on 'Run' without selecting any value from facet it generated the report associated with the first element (web channel) in the list, though nothing is selected from the list in the facet. !Facet.png! Please have a look at the attached screenshot for quick reference. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10296) Add Document Content: acc-financial-accounts.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1045#comment-1045 ] Vaibhav Jain commented on OFBIZ-10296: -- Hi team, Attached the patch for financial accounting documentation. Please have a look into this. Thanks! > Add Document Content: acc-financial-accounts.adoc > - > > Key: OFBIZ-10296 > URL: https://issues.apache.org/jira/browse/OFBIZ-10296 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Vaibhav Jain >Priority: Minor > Attachments: OFBIZ-10296.patch > > > Add content for acc-financial-accounts.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10623) Error message is displayed on ecommerce when user tries to use Split shipment functionality
Arpit Mor created OFBIZ-10623: - Summary: Error message is displayed on ecommerce when user tries to use Split shipment functionality Key: OFBIZ-10623 URL: https://issues.apache.org/jira/browse/OFBIZ-10623 Project: OFBiz Issue Type: Bug Components: ecommerce Affects Versions: Trunk Environment: https://demo-trunk.ofbiz.apache.org/ecommerce Reporter: Arpit Mor Attachments: 1-Checkout.png, 2-SplitShipment.png, 3-ErrorMessage.png Steps to regenerate: # Login to URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main] # Add multiple items to cart # Click on Check Out on cart summary (Please refer attachment: 1-Checkout) # Click on split shipment (Please refer attachment: 2-SplitShipment) Actual: Error message is displayed when user clicks on split shipment (Please refer attachment: 3-ErrorMessage) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10578) MIsc UI improvements in pages of ecommerce component
[ https://issues.apache.org/jira/browse/OFBIZ-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1040#comment-1040 ] Parakh Maheshwari commented on OFBIZ-10578: --- Attaching patch for UI improvement at Configurable Product detail page, Product Summary page, Forum page and message display page of e-commerce component. > MIsc UI improvements in pages of ecommerce component > > > Key: OFBIZ-10578 > URL: https://issues.apache.org/jira/browse/OFBIZ-10578 > Project: OFBiz > Issue Type: Sub-task >Reporter: Parakh Maheshwari >Assignee: Nitish Mishra >Priority: Major > Attachments: OFBIZ-10578-ConfigProduct.patch, > OFBIZ-10578-checkout.patch, OFBIZ-10578-promotions.patch, OFBIZ-10578.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10578) MIsc UI improvements in pages of ecommerce component
[ https://issues.apache.org/jira/browse/OFBIZ-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parakh Maheshwari updated OFBIZ-10578: -- Attachment: OFBIZ-10578-ConfigProduct.patch > MIsc UI improvements in pages of ecommerce component > > > Key: OFBIZ-10578 > URL: https://issues.apache.org/jira/browse/OFBIZ-10578 > Project: OFBiz > Issue Type: Sub-task >Reporter: Parakh Maheshwari >Assignee: Nitish Mishra >Priority: Major > Attachments: OFBIZ-10578-ConfigProduct.patch, > OFBIZ-10578-checkout.patch, OFBIZ-10578-promotions.patch, OFBIZ-10578.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10296) Add Document Content: acc-financial-accounts.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Jain updated OFBIZ-10296: - Attachment: OFBIZ-10296.patch > Add Document Content: acc-financial-accounts.adoc > - > > Key: OFBIZ-10296 > URL: https://issues.apache.org/jira/browse/OFBIZ-10296 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Vaibhav Jain >Priority: Minor > Attachments: OFBIZ-10296.patch > > > Add content for acc-financial-accounts.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10296) Add Document Content: acc-financial-accounts.adoc
[ https://issues.apache.org/jira/browse/OFBIZ-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Jain reassigned OFBIZ-10296: Assignee: Vaibhav Jain > Add Document Content: acc-financial-accounts.adoc > - > > Key: OFBIZ-10296 > URL: https://issues.apache.org/jira/browse/OFBIZ-10296 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sharan Foga >Assignee: Vaibhav Jain >Priority: Minor > > Add content for acc-financial-accounts.adoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9743) updateContent service does not return an error/success message
[ https://issues.apache.org/jira/browse/OFBIZ-9743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1034#comment-1034 ] Aditya Sharma commented on OFBIZ-9743: -- Fixed for 16.11 at r1844953. Additional change: Added success message to createContent and removeContent service too. Thanks Rohit Rai for reporting the issue. It is already handled for createContent is converted to entity-auto under OFBIZ-10401 and updateContent & removeContent service can also be converted to entity-auto service. I will check for 17.12 > updateContent service does not return an error/success message > --- > > Key: OFBIZ-9743 > URL: https://issues.apache.org/jira/browse/OFBIZ-9743 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12 >Reporter: Rohit Rai >Assignee: Aditya Sharma >Priority: Major > > 1. Go to Content, > 2. Click on Find in the search options to get a list of all the contents in > the system. > 3. Select a content from the list of content. > 4. Edit Content form should get opened. > 5. Click on update, the user is not presented with success or error message > on the screen. > Although, the service works and the content gets updated. > Here is a link to the issue, > https://demo-trunk.ofbiz.apache.org/content/control/editContent?contentId=TEMPLATE_MASTER -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10622) Success message should be displayed after updating Forum Group
[ https://issues.apache.org/jira/browse/OFBIZ-10622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anushi Gupta updated OFBIZ-10622: - Summary: Success message should be displayed after updating Forum Group (was: Success message should be displayed on updating Forum Group) > Success message should be displayed after updating Forum Group > -- > > Key: OFBIZ-10622 > URL: https://issues.apache.org/jira/browse/OFBIZ-10622 > Project: OFBiz > Issue Type: Improvement > Components: content >Affects Versions: 16.11.05 >Reporter: Anushi Gupta >Priority: Major > > 1) Login to demo-trunk or demo-stable instance with details: > URL - [https://demo-trunk.ofbiz.apache.org/content/control/findForumGroups] > admin/ ofbiz OR > URl - [https://demo-stable.ofbiz.apache.org/content/control/findForumGroups] > 2) Navigate to Forum from Content component > 3) Update the Forum Group > Expected : There should be success message if Forum group is updated > successfully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10622) Success message should be displayed on updating Forum Group
Anushi Gupta created OFBIZ-10622: Summary: Success message should be displayed on updating Forum Group Key: OFBIZ-10622 URL: https://issues.apache.org/jira/browse/OFBIZ-10622 Project: OFBiz Issue Type: Improvement Components: content Affects Versions: 16.11.05 Reporter: Anushi Gupta 1) Login to demo-trunk or demo-stable instance with details: URL - [https://demo-trunk.ofbiz.apache.org/content/control/findForumGroups] admin/ ofbiz OR URl - [https://demo-stable.ofbiz.apache.org/content/control/findForumGroups] 2) Navigate to Forum from Content component 3) Update the Forum Group Expected : There should be success message if Forum group is updated successfully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10584) Error in updating product content
[ https://issues.apache.org/jira/browse/OFBIZ-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Khandelwal closed OFBIZ-10584. -- Resolution: Cannot Reproduce > Error in updating product content > - > > Key: OFBIZ-10584 > URL: https://issues.apache.org/jira/browse/OFBIZ-10584 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Chandan Khandelwal >Priority: Minor > Attachments: UpdateProductContent.png > > > 1. Create Product Content > 2. Update Product Content > Getting error (lookedUpValue is empty) in updating product content because of > the incorrect value of PK. > This is because fromDate is editable and passed without milliseconds > (-MM-dd HH:mm:ss") from the UI but the stored value is with millisecond > (-MM-dd HH:mm:ss.SSS"). > From date is the part of the primary key and it should not be editable. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
