[jira] [Commented] (OFBIZ-4805) Change shipping order address failed
[ https://issues.apache.org/jira/browse/OFBIZ-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13253793#comment-13253793 ] Nicolas Malin commented on OFBIZ-4805: -- Hi Jacques, Strange, I have the problem on customer production site and I try on my local. The service updateOrderItemShipGroup failed on call-bsh element to decompose shipmentMethod keys. But on demo-trunk, I haven't the problem. I apply this patch to unblock the production site. The problem would be present with shipmentMethod NoShipping, _NA_, CARRIER. Sorry for the noise, if I reproduce this problem on demo-trunk, I will complete this issue. Thanks jacques for your review ! Change shipping order address failed Key: OFBIZ-4805 URL: https://issues.apache.org/jira/browse/OFBIZ-4805 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Reporter: Nicolas Malin Priority: Minor Attachments: OFBIZ-4805.patch, OFBIZ-4805.patch When you select a new shipping address in order view, operation failed because the service that update orderItemShipGroup haven't all information on carrier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4602) Null values are not synchronized in http mode
[ https://issues.apache.org/jira/browse/OFBIZ-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1361#comment-1361 ] Nicolas Malin commented on OFBIZ-4602: -- Hi Jacques, I tested the entity-sync process, and I confirm the [null-field] break it when an entity field is an other type that String. I not solve it, I will check it if I need implement the entity-sync. Null values are not synchronized in http mode - Key: OFBIZ-4602 URL: https://issues.apache.org/jira/browse/OFBIZ-4602 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release 4.0, Release 09.04, Release 09.04.01, Release 10.04, SVN trunk Environment: Using entity synchronization over HTTP (not RMI) Reporter: Patrick Antivackis Assignee: Jacques Le Roux Fix For: Release Branch 4.0, Release Branch 09.04, Release Branch 10.04, Release Branch 11.04, SVN trunk Attachments: patch-OFBIZ-4602.txt In order to send over http the values to create, store and remove, Ofbiz is Xml serializing the values. GenericValue xml serialization is managed in GenericEntity.makeXmlElement, unfortunately this method just don't serialized null valued fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4699) Error in getProductInventoryAvailable with french formated number
[ https://issues.apache.org/jira/browse/OFBIZ-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210142#comment-13210142 ] Nicolas Malin commented on OFBIZ-4699: -- I check the patch and I think that there is a misunderstanding. parameters.quantityOnHandTotal is a BigDecimal and inventoryItem.quantityOnHandTotal is also a BigDecimal. The problem that solve pierre is to call directly operation with BigDecimal instead of use a flexible string that convert BigDecimal to String and String to BigDecimal for return value. For me, pierre solve with a good solution. On other point, I am little surprised by replace calculate by uel. Simple method is a high level language, use mainly by the functional, uel need to know conversion problem. It's a regression for me to use uel inseated of mini-lang, uel is pretty good but not on functional context (this is my opinion ;) ) On mini-lang xsd or wiki I don't found information on obsoleted calculate code, where I can found most information on the reason ? Nicolas Error in getProductInventoryAvailable with french formated number - Key: OFBIZ-4699 URL: https://issues.apache.org/jira/browse/OFBIZ-4699 Project: OFBiz Issue Type: Bug Components: product Affects Versions: SVN trunk Reporter: Gaudin Pierre Attachments: InventoryServices.xml.patch The calculation of the available quantities by location does not take into account the local formatting of the numbers. How to see the problem: - Be in French local - Create for the same product several inventory items with ATP and QOH 999. - Go to the product inventory view - The values are not correct for locations The patch corrects this problem by using the standard methods of the minilanguage -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3913) Automated action triggered by event
[ https://issues.apache.org/jira/browse/OFBIZ-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13174284#comment-13174284 ] Nicolas Malin commented on OFBIZ-3913: -- Jacques, I will tried your process to understand why you have this error. Thanks your review ! Automated action triggered by event --- Key: OFBIZ-3913 URL: https://issues.apache.org/jira/browse/OFBIZ-3913 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Attachments: ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.png, OFBIZ-3913.ogv, OFBIZ-3913.patch, OFBIZ-3913.patch, PDFCreator.png, What I did with PDFCreator.jpg Following a thread on the dev list, related to a printer automated selection, by an user and an event, here is a first draft. I added a new entity, ExternalDevice, which list all devices OFBiz can reach (and the associated command). This entity is related to an ExternalDeviceType and each record has a status, so we know if the device is available, out of order, in maintenance, waiting, etc... Then I added another entity, ExternalDeviceUserAction, which defines a device for an user, and/or an action through Enumeration. Finally, I added a service which find the commnand to execute based on an action and/or an user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3913) Automated action triggered by event
[ https://issues.apache.org/jira/browse/OFBIZ-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13172094#comment-13172094 ] Nicolas Malin commented on OFBIZ-3913: -- Jacques, do you uncomment seca ? Index: framework/example/servicedef/secas.xml === --- framework/example/servicedef/secas.xml (révision 1207784) +++ framework/example/servicedef/secas.xml (copie de travail) @@ -27,4 +27,13 @@ condition-field field-name=statusId operator=not-equals to-field-name=oldStatusId/ action service=createExampleStatus mode=sync/ /eca +!-- Active this seca to use externalDevice with demo data - +eca service=createExample event=return +set field-name=userLoginId env-name=userLogin.userLoginId/ +set field-name=screenLocation value=component://example/widget/example/ExampleScreens.xml#ExampleReport/ +set field-name=content-type value=application/pdf/ +set field-name=screenContext.exampleId env-name=exampleId/ +action service=sendPrintFromScreenByUserAction mode=sync/ +/eca +-- /service-eca Automated action triggered by event --- Key: OFBIZ-3913 URL: https://issues.apache.org/jira/browse/OFBIZ-3913 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Attachments: ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.png, OFBIZ-3913.ogv, OFBIZ-3913.patch, OFBIZ-3913.patch, PDFCreator.png, What I did with PDFCreator.jpg Following a thread on the dev list, related to a printer automated selection, by an user and an event, here is a first draft. I added a new entity, ExternalDevice, which list all devices OFBiz can reach (and the associated command). This entity is related to an ExternalDeviceType and each record has a status, so we know if the device is available, out of order, in maintenance, waiting, etc... Then I added another entity, ExternalDeviceUserAction, which defines a device for an user, and/or an action through Enumeration. Finally, I added a service which find the commnand to execute based on an action and/or an user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162827#comment-13162827 ] Nicolas Malin commented on OFBIZ-3894: -- thanks Erwan, I check it, and continue refactoring. Nicolas Refactor Email handling --- Key: OFBIZ-3894 URL: https://issues.apache.org/jira/browse/OFBIZ-3894 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: BJ Freeman Assignee: Erwan de FERRIERES Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch Original Estimate: 1,344h Remaining Estimate: 1,344h with the addition of the Website for each component 1) create product store for Order entry, or use the B2C product store. 2) move the email widgets from ecommerce to order compontent. 3) modify the seed data so that Order entry has it own emails from order component.this would be to add emails to note: as I go through the different items this is turning out to be a bigger project than I first anticipated. so consider this so far just ideas. Maybe break down in to small tasks as I have time to do something. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13159520#comment-13159520 ] Nicolas Malin commented on OFBIZ-3894: -- It's possible for a commiter to create a branch ? It's really difficult to progress with big patch and this issue is really interesting for refactoring mail system thanks by advanced ;) Nicolas Refactor Email handling --- Key: OFBIZ-3894 URL: https://issues.apache.org/jira/browse/OFBIZ-3894 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: BJ Freeman Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch Original Estimate: 1,344h Remaining Estimate: 1,344h with the addition of the Website for each component 1) create product store for Order entry, or use the B2C product store. 2) move the email widgets from ecommerce to order compontent. 3) modify the seed data so that Order entry has it own emails from order component.this would be to add emails to note: as I go through the different items this is turning out to be a bigger project than I first anticipated. so consider this so far just ideas. Maybe break down in to small tasks as I have time to do something. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13149627#comment-13149627 ] Nicolas Malin commented on OFBIZ-3894: -- Nobody interested by this refactoring ? Refactor Email handling --- Key: OFBIZ-3894 URL: https://issues.apache.org/jira/browse/OFBIZ-3894 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: BJ Freeman Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch Original Estimate: 1,344h Remaining Estimate: 1,344h with the addition of the Website for each component 1) create product store for Order entry, or use the B2C product store. 2) move the email widgets from ecommerce to order compontent. 3) modify the seed data so that Order entry has it own emails from order component.this would be to add emails to note: as I go through the different items this is turning out to be a bigger project than I first anticipated. so consider this so far just ideas. Maybe break down in to small tasks as I have time to do something. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4021) Adding columns filtering fields in form widget
[
https://issues.apache.org/jira/browse/OFBIZ-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141019#comment-13141019
]
Nicolas Malin commented on OFBIZ-4021:
--
Hi Bruno, good idea.
I try to review your work but thelast patch fail on revision 1195864.
{quote}
patching file framework/widget/templates/htmlFormMacroLibrary.ftl
Hunk #1 succeeded at 368 (offset 107 lines).
Hunk #2 succeeded at 705 with fuzz 1 (offset 220 lines).
Hunk #3 FAILED at 504.
{quote}
Adding columns filtering fields in form widget
--
Key: OFBIZ-4021
URL: https://issues.apache.org/jira/browse/OFBIZ-4021
Project: OFBiz
Issue Type: Sub-task
Components: framework
Reporter: Bruno Busco
Priority: Minor
Attachments: FilterForm.patch, FilterForm.patch,
column_filter_disabled.JPG, column_filter_enabled.JPG, content_list.JPG,
img_for_tomahawk.zip
This patch includes an initial implementation of a list-form column filtering
feature.
The aim is to add the possibility to configure a list form to show, in its
header, some fields that could be used to filter the rows displayed in the
form.
This is a feature quite standard in many systems and could be seen into OFBiz
as a quick search; the standard way of searching using a complete
single-type form could be seen as an advanced search.
Please find attached to this JIRA two screenshots that show you how the
filtering option appears on the screen.
*How the user uses this feature*
The part of the screen that is normally used for the pagination controls
(only the upper one) has been extended so that two icons are shown on the
left.
The first one (a funnel) is used to show or hide the filtering fields. The
second one (a magnifing glass) is used to run the search with the filter
content.
*How the developer uses this feature*
The filtering feature can be enabled on any list-type form specifying the
filter-form-name attribute.
This must be the name of a form that contains the details about how the
filtering fields should be rendered.
When a list form with the filter-form-name option set is rendered, any column
field is searched for in the filter-form.
If a field with the same name is found, its field rendering options are used
to render the filter field.
A new field attribute filter-field has also been added.
This defaults to true but if it is set to false the filter field is not
rendered for this column, even if a field with the same name is present in
the filter-form.
This feature allows to use as filter-form an already existent form such as a
regular FindXXX form.
In the patch the ListExample form has been changed to use this feature. You
can check it there.
Unfortunately the patch does not work yet 100% but I hope that if someone
finds it interesting could help me.
*What is there still to do*
1) There is a FIXME in MacroFormRenderer.java file. I cannot make it work. If
I enable the code that is commented there I get an error when a search is run.
2) I cannot make the filtering fields show the actual content after a search
is run. They are always rendered as empty.
3) The filter row hide/show status should be saved so that it is maintained
after a pagination.
I submit this patch as it is becouse I cannot easily improve it further but I
hope someone could help.
The img_for_tamahawk.zip file includes imgs that should be added in the
tomahawk images folder to make the patch work.
Thank you for any help!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4472) New element auto-parameters-entity for link/hyperlink
[
https://issues.apache.org/jira/browse/OFBIZ-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13136263#comment-13136263
]
Nicolas Malin commented on OFBIZ-4472:
--
You are absolutely right adrian, auto-parameters-service will be a better
solution on my example. My origin case was only on entity, but if you are
interested to extend on service, I can improve this issue.
New element auto-parameters-entity for link/hyperlink
-
Key: OFBIZ-4472
URL: https://issues.apache.org/jira/browse/OFBIZ-4472
Project: OFBiz
Issue Type: New Feature
Components: framework
Affects Versions: SVN trunk
Reporter: Nicolas Malin
Priority: Minor
Attachments: OFBIZ-4472.patch, OFBIZ-4472.patch, OFBIZ-4472.patch
When you want edit/remove an entity from link call it's needed to give all pk
on parameter element as like :
{quote} field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
parameter param-name=exampleId/
parameter param-name=exampleFeatureId/
parameter param-name=fromDate/
hyperlink/
/field
{quote}
To simplify, I introduce auto-parameters-entity like this :
{quote}
field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
auto-parameters-entity entity-name=ExampleFeatureAppl/
hyperlink/
/field
{quote}
or
{quote}
form name=ListExampleFeatureAppls type=list
default-entity-name=ExampleFeatureAppl
field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
auto-parameters-entity/
hyperlink/
/field
{quote}
This method is inspired from auto-fields-entity and I homogenized on widget
renderer screen (link), menu (link) and form (hyperlink, sub-link)
Any comments are welcome
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4480) Need to have an option to pass file name as OrderId for the generated confirmation or invoice PDF.
[ https://issues.apache.org/jira/browse/OFBIZ-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13131449#comment-13131449 ] Nicolas Malin commented on OFBIZ-4480: -- I look the patch, quick and powerful improvement to solve this issue, but improve directly ViewHandler to support a generic attribute (as example responseFileName) would be more usable for other report. Nicolas Need to have an option to pass file name as OrderId for the generated confirmation or invoice PDF. -- Key: OFBIZ-4480 URL: https://issues.apache.org/jira/browse/OFBIZ-4480 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: SVN trunk Environment: OS - Ubuntu Reporter: Ganesh Bawne Labels: filename, order, pdf Attachments: orderPdf-FileName.patch Need to have set the order pdf file name to its order number when we open the pdf from backoffice orderdetail page (/ordermgr/control/order.pdf?orderId=X). Currently, the default name of the pdf is always order.pdf, instead need to have an option to set the default pdf name to its order number? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[ https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13129638#comment-13129638 ] Nicolas Malin commented on OFBIZ-3894: -- I work to create new service for send mail with new model and alert you well is done. The next step with content merge to send email, I wish separate on two commits. At this time the patch is so bigger and adding all improvement with content will be difficult to review. Refactor Email handling --- Key: OFBIZ-3894 URL: https://issues.apache.org/jira/browse/OFBIZ-3894 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: BJ Freeman Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch Original Estimate: 1,344h Remaining Estimate: 1,344h with the addition of the Website for each component 1) create product store for Order entry, or use the B2C product store. 2) move the email widgets from ecommerce to order compontent. 3) modify the seed data so that Order entry has it own emails from order component.this would be to add emails to note: as I go through the different items this is turning out to be a bigger project than I first anticipated. so consider this so far just ideas. Maybe break down in to small tasks as I have time to do something. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3913) Automated action triggered by event
[ https://issues.apache.org/jira/browse/OFBIZ-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127592#comment-13127592 ] Nicolas Malin commented on OFBIZ-3913: -- Strange, all my system on UTF-8 Jacques, I will try to create a movie or/and few step. Thanks for your time ! Nicolas Automated action triggered by event --- Key: OFBIZ-3913 URL: https://issues.apache.org/jira/browse/OFBIZ-3913 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Attachments: ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.png, OFBIZ-3913.patch Following a thread on the dev list, related to a printer automated selection, by an user and an event, here is a first draft. I added a new entity, ExternalDevice, which list all devices OFBiz can reach (and the associated command). This entity is related to an ExternalDeviceType and each record has a status, so we know if the device is available, out of order, in maintenance, waiting, etc... Then I added another entity, ExternalDeviceUserAction, which defines a device for an user, and/or an action through Enumeration. Finally, I added a service which find the commnand to execute based on an action and/or an user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-3913) Automated action triggered by event
[ https://issues.apache.org/jira/browse/OFBIZ-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13126598#comment-13126598 ] Nicolas Malin commented on OFBIZ-3913: -- Hi Jacques, It's a old patch :) I try update it this night Nicolas -- MALIN Nicolas Trésorier de l'association Néogia Tél : 06.17.66.40.06 http://www.neogia.org/ Automated action triggered by event --- Key: OFBIZ-3913 URL: https://issues.apache.org/jira/browse/OFBIZ-3913 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Attachments: ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.png Following a thread on the dev list, related to a printer automated selection, by an user and an event, here is a first draft. I added a new entity, ExternalDevice, which list all devices OFBiz can reach (and the associated command). This entity is related to an ExternalDeviceType and each record has a status, so we know if the device is available, out of order, in maintenance, waiting, etc... Then I added another entity, ExternalDeviceUserAction, which defines a device for an user, and/or an action through Enumeration. Finally, I added a service which find the commnand to execute based on an action and/or an user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
