[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490134#comment-16490134 ] Scott Gray commented on OFBIZ-4274: --- I had pictured that GraphQL could be layered on top of the model I was describing to allow for custom queries. I haven't looked into GraphQL mutations enough to know if it would be remotely suitable for OFBiz beyond reading data. I'd be interested in hearing more details about what you envisage. I'll be too busy for the next few months to do much beyond discussion. I do have an early rough version PoC of what I've been describing, I could share that if there's any interest but I'd need to do some cleanup and upgrade it to gradle first. All it really does so far is allow CRUD to/from the database based on a resource model and an RSQL (Rest Query Language) implementation for querying resources. There's no ECA implementation for business logic, no authorization handling etc. The most important thing to me though, is that whatever approach is taken is useful both to an external client and also within OFBiz itself. The best way to battle test something is to try and have our thousands of services and data prep scripts use it. When I get time again I'll probably do the ECA implementation for my approach and then have a go at replacing all shipment related interactions OFBiz with the new model. Doesn't mean I don't want to see alternative approaches though, it's just that I'd like to see how it works out. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Major > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10410) Refactor `JavaEventHandler` class
[ https://issues.apache.org/jira/browse/OFBIZ-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10410. --- Resolution: Implemented > Refactor `JavaEventHandler` class > - > > Key: OFBIZ-10410 > URL: https://issues.apache.org/jira/browse/OFBIZ-10410 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-10410-refactor-java-event-handler.patch > > > Instead of relying on manual synchronisation, use a concurrent map for > caching loaded classes. Inline private `invoke` delegate which intent was > fuzzy. Spread arguments when calling `Method::invoke` and `Class::getMethod`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10410) Refactor `JavaEventHandler` class
[ https://issues.apache.org/jira/browse/OFBIZ-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489773#comment-16489773 ] Jacques Le Roux commented on OFBIZ-10410: - Thanks Mathieu, As I say in my commit comment: bq. jleroux: interesting, it's the 1st use in OFBiz of the "::" syntax for calling methods (cf. https://docs.oracle.com/javase/specs/jls/se8/html/jls-15.html#jls-15.13-500) I note that the string "::" is used in many places as a separator, notably in caches, as cache key separator but this should not be confusing. So you made me install Groovy Console 3.0 :) Your patch is in trunk at revision: 1832199 > Refactor `JavaEventHandler` class > - > > Key: OFBIZ-10410 > URL: https://issues.apache.org/jira/browse/OFBIZ-10410 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-10410-refactor-java-event-handler.patch > > > Instead of relying on manual synchronisation, use a concurrent map for > caching loaded classes. Inline private `invoke` delegate which intent was > fuzzy. Spread arguments when calling `Method::invoke` and `Class::getMethod`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10410) Refactor `JavaEventHandler` class
[ https://issues.apache.org/jira/browse/OFBIZ-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-10410: --- Assignee: Jacques Le Roux > Refactor `JavaEventHandler` class > - > > Key: OFBIZ-10410 > URL: https://issues.apache.org/jira/browse/OFBIZ-10410 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-10410-refactor-java-event-handler.patch > > > Instead of relying on manual synchronisation, use a concurrent map for > caching loaded classes. Inline private `invoke` delegate which intent was > fuzzy. Spread arguments when calling `Method::invoke` and `Class::getMethod`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489467#comment-16489467 ] Taher Alkhateeb commented on OFBIZ-4274: Hi Scott and everyone The way you described the solution makes me think GraphQL might seems like a better fit, because it works almost the same way. Anyway, I have a few ideas for a PoC now, but I don't know if anyone is working on this so far? If not, should I submit an initial patch for discussion? Or do you folks want to collaborate somehow? Ideas > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Major > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10413) Remove unused code in `CommonEvents::setFollowerPage`
[ https://issues.apache.org/jira/browse/OFBIZ-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489112#comment-16489112 ] Jacques Le Roux commented on OFBIZ-10413: - Mathieu, If I refer to the data model, in WebUserPreference visitId is used for: To be able to keep preferences for a non loggin in user for the current session > Remove unused code in `CommonEvents::setFollowerPage` > - > > Key: OFBIZ-10413 > URL: https://issues.apache.org/jira/browse/OFBIZ-10413 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Priority: Minor > Attachments: OFBIZ-10413-Improve-setFollowerPage.patch > > > `CommonEvents::setFollowerPage` contains two unused variable definition. > After basic search I found that this request handler is used only in > `webapp/partymgr/controller.xml` however I was unable to understand its > purpose, so I have added a comment to add some kind of docstring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489084#comment-16489084 ] Jacques Le Roux commented on OFBIZ-4274: Thanks Mathieu, That's what I surmised after reading a bit more in it :) > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Major > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10412) Remove `UtilValidate::isEmpty(String)` method
[ https://issues.apache.org/jira/browse/OFBIZ-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10412. --- Resolution: Implemented Fix Version/s: Upcoming Branch Thanks Mathieu, Your patch is in trunk at revision: 1832170 > Remove `UtilValidate::isEmpty(String)` method > - > > Key: OFBIZ-10412 > URL: https://issues.apache.org/jira/browse/OFBIZ-10412 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10412-remove-isEmpty-for-strings.patch > > > UtilValidate class contains a `isEmpty` method both for `CharSequence` and > for `String` types but since the first is an interface for the other and that > the implementation are the same we don't need to keep the one for the > concrete type. > Additionnaly I have removed the unused Generic type for the remaining > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10412) Remove `UtilValidate::isEmpty(String)` method
[ https://issues.apache.org/jira/browse/OFBIZ-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-10412: --- Assignee: Jacques Le Roux > Remove `UtilValidate::isEmpty(String)` method > - > > Key: OFBIZ-10412 > URL: https://issues.apache.org/jira/browse/OFBIZ-10412 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-10412-remove-isEmpty-for-strings.patch > > > UtilValidate class contains a `isEmpty` method both for `CharSequence` and > for `String` types but since the first is an interface for the other and that > the implementation are the same we don't need to keep the one for the > concrete type. > Additionnaly I have removed the unused Generic type for the remaining > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1642#comment-1642 ] Mathieu Lirzin commented on OFBIZ-4274: --- Hi Jacques, The Camel REST DSL will only serve as an inspiration in this project. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Major > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1642#comment-1642 ] Mathieu Lirzin edited comment on OFBIZ-4274 at 5/24/18 12:18 PM: - Hi Jacques, The Camel REST DSL will only serve as an inspiration. was (Author: mthl): Hi Jacques, The Camel REST DSL will only serve as an inspiration in this project. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Major > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10385) Cart summary section distroted
[ https://issues.apache.org/jira/browse/OFBIZ-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488854#comment-16488854 ] Jacques Le Roux commented on OFBIZ-10385: - I don't see the same on Windows 7 FF 56.0.2 (64 bits) but I don't like how the checkout section is written, see OFBIZ-10414 > Cart summary section distroted > -- > > Key: OFBIZ-10385 > URL: https://issues.apache.org/jira/browse/OFBIZ-10385 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Padmavati Rawat >Assignee: Garima jain >Priority: Major > Attachments: CartSummaryDistroted.png > > > Steps > Navigate to the storefront. > https://demo-trunk.ofbiz.apache.org/ecomseo/additeme > Add items to the cart. > Check the cart summary section. > Actual: > Cart summary section getting distorted on adding items to the cart. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488813#comment-16488813 ] Jacques Le Roux commented on OFBIZ-4274: Hi Mathieu, After having a cursory look at the Camel REST DSL I was wondering why and how you want to use it? Or do you only want to draw your inspiration from it? > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Major > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10410) Refactor `JavaEventHandler` class
[ https://issues.apache.org/jira/browse/OFBIZ-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488733#comment-16488733 ] Mathieu Lirzin commented on OFBIZ-10410: Hello Shi, Even if I effectively worked on this while diving on OFBiz code for the REST thing, it is not related to OFBIZ-4274. :-) > Refactor `JavaEventHandler` class > - > > Key: OFBIZ-10410 > URL: https://issues.apache.org/jira/browse/OFBIZ-10410 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Priority: Minor > Attachments: OFBIZ-10410-refactor-java-event-handler.patch > > > Instead of relying on manual synchronisation, use a concurrent map for > caching loaded classes. Inline private `invoke` delegate which intent was > fuzzy. Spread arguments when calling `Method::invoke` and `Class::getMethod`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10410) Refactor `JavaEventHandler` class
[ https://issues.apache.org/jira/browse/OFBIZ-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488619#comment-16488619 ] Shi Jinghai commented on OFBIZ-10410: - Thank you Mathieu! I'm not sure whether the get/post method attribute of request-map is included in this issue scope, I saw you mentioned it in your comment in OFBIZ-4274. > Refactor `JavaEventHandler` class > - > > Key: OFBIZ-10410 > URL: https://issues.apache.org/jira/browse/OFBIZ-10410 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Priority: Minor > Attachments: OFBIZ-10410-refactor-java-event-handler.patch > > > Instead of relying on manual synchronisation, use a concurrent map for > caching loaded classes. Inline private `invoke` delegate which intent was > fuzzy. Spread arguments when calling `Method::invoke` and `Class::getMethod`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10370) Migrate promotion condition and action rule
[
https://issues.apache.org/jira/browse/OFBIZ-10370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-10370.
-
Resolution: Implemented
Done,
I commit the corrective patch on trunk at revision 1832141.
> Migrate promotion condition and action rule
> ---
>
> Key: OFBIZ-10370
> URL: https://issues.apache.org/jira/browse/OFBIZ-10370
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Major
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10370.patch
>
>
> Currently promotion rule engine works with :
> * entities ProductPromoCond et ProductPromoAction
> * java linear function ProductPromoWorker.checkCondition()
> (ProductPromoWorker:910) and ProductPromoWorker.performAction
> (ProductPromoWorker:1423)
> * Enumeration list to indicate on java function what piece of code to
> activate the control or action
> The problem with this structure is when you want to create a new case of
> condition or action, you need to modify the framework code base.
> We propose an other way with convert the 2 big java leaner function to
> service representation with one service by case.
> To realize it we introduce a relation with CustomMethod :
> ProductPromoRule --> ProductPromoCond -> CustomMethod
> \-> ProductPromoAction -> CustomMethod
> Each functions's case are converted to service with a related CustomMethod.
> With this pattern now you can write your own condition rule and action rule
> on your plugin and link it on the promo engine
> When it's possible we associate a unit test to the service
> For backware compatibility current enumeration receive on enumCode the
> customMethodId to ensure that old data work fine with the new engine
> {code}
> customMethodTypeId="PRODUCT_PROMO_COND"
> customMethodName="productPromoCondProductAmount" description="Product
> amount"/>
> enumCode="PPC_PRODUCT_AMOUNT"/>
> {code}
> {code}
> //for backware compatibility resolve customMethodId from enumCode
> GenericValue condEnum =
> EntityQuery.use(delegator).from("Enumeration").where("enumId",
> inputParamEnumId).cache().queryOne();
> if (condEnum != null) {
> customMethod =
> EntityQuery.use(delegator).from("CustomMethod").where("customMethodId",
> condEnum.get("enumCode")).cache().queryOne();
> serviceName = customMethod.getString("customMethodName");
> }
> {code}
> Related dev [discussion
> |https://lists.apache.org/thread.html/47730b60c9d1bab875e77577c2b4f16b99ede6dcdf68030f5cfc1203@%3Cdev.ofbiz.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9304) refactor lists related to globalGlAccounts in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9304: --- Assignee: (was: Pierre Smits) > refactor lists related to globalGlAccounts in accounting > > > Key: OFBIZ-9304 > URL: https://issues.apache.org/jira/browse/OFBIZ-9304 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9304-accounting-GlobalGlAccounts.patch > > > Refactor various list forms into grids. > Refactor various list form references in screen widgets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10205) The setToComplete of ofbizsetup run in error when running demo General Chart Of Accounts.
[ https://issues.apache.org/jira/browse/OFBIZ-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10205: Assignee: (was: Pierre Smits) > The setToComplete of ofbizsetup run in error when running demo General Chart > Of Accounts. > - > > Key: OFBIZ-10205 > URL: https://issues.apache.org/jira/browse/OFBIZ-10205 > Project: OFBiz > Issue Type: Bug > Components: commonext >Affects Versions: Trunk >Reporter: fumiyoshi.to >Priority: Critical > Attachments: SetupEvents.xml.patch > > > The file name of demo General Chart Of Accounts is wrong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9367) remove unused labels from humanres
[ https://issues.apache.org/jira/browse/OFBIZ-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9367: --- Assignee: (was: Pierre Smits) > remove unused labels from humanres > -- > > Key: OFBIZ-9367 > URL: https://issues.apache.org/jira/browse/OFBIZ-9367 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Attachments: OFBIZ-9367-HumanResUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6189) Have configuration options for accounting
[ https://issues.apache.org/jira/browse/OFBIZ-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6189: --- Assignee: (was: Pierre Smits) > Have configuration options for accounting > - > > Key: OFBIZ-6189 > URL: https://issues.apache.org/jira/browse/OFBIZ-6189 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: configuration, multi-tenant > Attachments: OFBIZ-6189-accounting-systemproperties.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9139) Refactor list related forms into grids in ProjectMgr
[ https://issues.apache.org/jira/browse/OFBIZ-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9139: --- Assignee: (was: Pierre Smits) > Refactor list related forms into grids in ProjectMgr > > > Key: OFBIZ-9139 > URL: https://issues.apache.org/jira/browse/OFBIZ-9139 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9139-ProjectMgr-grid.patch, > ofbiz-9139-projctmgr-widgets-grid.patch > > > Refactoring various list forms into grids. > Refactoring various list form references into grid references in screens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10363) Improve Dutch UiLabels
[ https://issues.apache.org/jira/browse/OFBIZ-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10363: Assignee: (was: Pierre Smits) > Improve Dutch UiLabels > -- > > Key: OFBIZ-10363 > URL: https://issues.apache.org/jira/browse/OFBIZ-10363 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Minor > Attachments: ofbiz-10363-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9307) refactor lists related to financial accounts in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9307: --- Assignee: (was: Pierre Smits) > refactor lists related to financial accounts in accounting > -- > > Key: OFBIZ-9307 > URL: https://issues.apache.org/jira/browse/OFBIZ-9307 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9307-accounting -FinAccounts.patch > > > Refactor various list forms into grids. > Refactor various list form references in screen widgets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9294) refactor lists related to invoice item types in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9294: --- Assignee: (was: Pierre Smits) > refactor lists related to invoice item types in accounting > -- > > Key: OFBIZ-9294 > URL: https://issues.apache.org/jira/browse/OFBIZ-9294 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9294-accounting-invoiceitemtypes.patch > > > Refactor various list forms into grids. > Refactor various list form references in screen widgets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9352) Remove unused labels from AccountingUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-9352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9352: --- Assignee: (was: Pierre Smits) > Remove unused labels from AccountingUiLabels.xml > > > Key: OFBIZ-9352 > URL: https://issues.apache.org/jira/browse/OFBIZ-9352 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Reporter: Pierre Smits >Priority: Minor > Attachments: OFBIZ-9352-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9288) refactor lists related to invoices in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9288: --- Assignee: (was: Pierre Smits) > refactor lists related to invoices in accounting > > > Key: OFBIZ-9288 > URL: https://issues.apache.org/jira/browse/OFBIZ-9288 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9288-accounting-invoice.patch > > > Refactor various list forms into grids. > Refactor various list form references in screen widgets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9364) Remove unused labels from content
[ https://issues.apache.org/jira/browse/OFBIZ-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9364: --- Assignee: (was: Pierre Smits) > Remove unused labels from content > - > > Key: OFBIZ-9364 > URL: https://issues.apache.org/jira/browse/OFBIZ-9364 > Project: OFBiz > Issue Type: Improvement > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Attachments: OFBIZ-9364-ContentUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9271) refactor lists related to tax authorities in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9271: --- Assignee: (was: Pierre Smits) > refactor lists related to tax authorities in accounting > --- > > Key: OFBIZ-9271 > URL: https://issues.apache.org/jira/browse/OFBIZ-9271 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9271-Accounting-taxauthority.patch > > > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9332) refactor lists related to payments in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9332: --- Assignee: (was: Pierre Smits) > refactor lists related to payments in accounting > > > Key: OFBIZ-9332 > URL: https://issues.apache.org/jira/browse/OFBIZ-9332 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9332-accounting-payments.patch > > > Refactor various lists forms into grids. > Refactor various list form references in screen widgets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9267) refactor lists related to fixed assets in accounting
[ https://issues.apache.org/jira/browse/OFBIZ-9267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9267: --- Assignee: (was: Pierre Smits) > refactor lists related to fixed assets in accounting > > > Key: OFBIZ-9267 > URL: https://issues.apache.org/jira/browse/OFBIZ-9267 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring, widget > Attachments: OFBIZ-9267-Accounting-fixedasset.patch > > > Refactor various lists forms into grids. > Refactor various list form references in screen widgets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9140) Adding 'navigation-grid-name' to widget-screen.xsd
[ https://issues.apache.org/jira/browse/OFBIZ-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9140: --- Assignee: (was: Pierre Smits) > Adding 'navigation-grid-name' to widget-screen.xsd > -- > > Key: OFBIZ-9140 > URL: https://issues.apache.org/jira/browse/OFBIZ-9140 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: widget > Attachments: OFBIZ-9140-widget-screen.xsd.patch > > > In screenlets in screen widgets we have the option to set the > 'navigation-form-name' which is used for pagination and list length changes > when the associated form of type='list' warrants such. > As there is also the possibility to use a grid definition as an alternative > to the form definition with type='list', there should also be the ability to > set such grid navigation option in the screenlet. > In order to be able to work with this while developing widget oriented > solutions, there should be a reference included in the widget-screen.xsd. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6955) Have editProductionRunRoutingTask set the appropriate workEffortPurposeTypeId
[ https://issues.apache.org/jira/browse/OFBIZ-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6955: --- Assignee: (was: Pierre Smits) > Have editProductionRunRoutingTask set the appropriate workEffortPurposeTypeId > - > > Key: OFBIZ-6955 > URL: https://issues.apache.org/jira/browse/OFBIZ-6955 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Attachments: OFBIZ-6955-ProductionRunSimpleEvents.xml.patch > > > Same as in OFBIZ-6954 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6072) Improves parties assignments to production run tasks
[ https://issues.apache.org/jira/browse/OFBIZ-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6072: --- Assignee: (was: Pierre Smits) > Improves parties assignments to production run tasks > > > Key: OFBIZ-6072 > URL: https://issues.apache.org/jira/browse/OFBIZ-6072 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > Fix For: 17.12.01 > > > After OFBIZ-5706 parties can be assigned to production run tasks. But we can > improve how it's managed: > * Be able to set the life span of an assignment (start and through date) upon > creation of an assignment > * Being able to expire a party assignment by setting the through date (when > none is set) > * Show the parties in the EditProductionRun and ShowProductionRun screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-5563) Cannot delete production run task materials when only one material record exists for first task
[ https://issues.apache.org/jira/browse/OFBIZ-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5563: --- Assignee: (was: Pierre Smits) > Cannot delete production run task materials when only one material record > exists for first task > --- > > Key: OFBIZ-5563 > URL: https://issues.apache.org/jira/browse/OFBIZ-5563 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Minor > > When accessing a production run "Materials" tab before confirmation, > materials associated with other tasks besides the first are not able to be > deleted if the first task contains only 1 material assignment. Therefore a > bogus material record must be created for the first task in order to gain the > delete functionality of the other tasks material associations. > To reproduce: > 1. Create a production run for PIZZA > 2. Click on the "Materials" tab > 3. Assign any product at any quantity as material for the first task and > second task > 4. Try to delete the second tasks material record > 5. Notice nothing happens when clicking the delete button. This is because > the javascript:submitFormDisableSubmits(this) is preventing submission based > on some rules -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-5548) Improve production run task declarations to track operators responsible for rejects
[ https://issues.apache.org/jira/browse/OFBIZ-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5548: --- Assignee: (was: Pierre Smits) > Improve production run task declarations to track operators responsible for > rejects > --- > > Key: OFBIZ-5548 > URL: https://issues.apache.org/jira/browse/OFBIZ-5548 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Major > > I think the production run task declaration form that allows by-products to > be created should be improved to allow relations to time entries created from > the other declaration form. > This improvement will be dependent on the added production run declaration > time entry functionality provided in OFBIZ-5532. It would be nice to be able > to declare quantityRejected in the by-product declaration form and have it > automatically update the workEffort.quantityRejected of the time entry that > will be specified. I think the timeEntryId field should be added to the > InventoryItemDetail entity to relate the by-products to the worker > responsible for the rejects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6197) Allow production runs to be generated based on OrderItemShipGroupAssoc instead of only Shipment
[ https://issues.apache.org/jira/browse/OFBIZ-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6197: --- Assignee: (was: Pierre Smits) > Allow production runs to be generated based on OrderItemShipGroupAssoc > instead of only Shipment > --- > > Key: OFBIZ-6197 > URL: https://issues.apache.org/jira/browse/OFBIZ-6197 > Project: OFBiz > Issue Type: New Feature > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Major > Attachments: OFBIZ-6197.patch > > > Manufacturing Shipment Plan requires a shipment to be created before a > production run can be generated to fulfill the corresponding > OrderItemShipGroupAssoc. I propose adding the capability to generate > production runs based on OrderItemShipGroupAssoc without having to create a > shipment for it first. It seems unnecesarily cumbersome and redundant to > require users to create a shipment and plan each order items corresponding > the OrderItemShipGroupAssoc they already created. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6187) WorkWithShipmentPlans.groovy to show "Generate Production Runs" button for more than one OrderItemShipGroupAssoc shipment
[ https://issues.apache.org/jira/browse/OFBIZ-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6187: --- Assignee: (was: Pierre Smits) > WorkWithShipmentPlans.groovy to show "Generate Production Runs" button for > more than one OrderItemShipGroupAssoc shipment > - > > Key: OFBIZ-6187 > URL: https://issues.apache.org/jira/browse/OFBIZ-6187 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Major > > WorkWithShipmentPlans.groovy sets workInProgress = "true" whenever a > WorkOrderItemFulfillment exists for an OrderItemShipGroupAssoc. However, > multiple shipments may be created to fulfill the schedule. The code should > be improved to support creation of multiple production runs for multiple > shipments. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6204) createProductionRunsForOrder to create OrderItemWorkFulfillment for all mandatory preceeding production runs
[ https://issues.apache.org/jira/browse/OFBIZ-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6204: --- Assignee: (was: Pierre Smits) > createProductionRunsForOrder to create OrderItemWorkFulfillment for all > mandatory preceeding production runs > > > Key: OFBIZ-6204 > URL: https://issues.apache.org/jira/browse/OFBIZ-6204 > Project: OFBiz > Issue Type: New Feature > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Major > Attachments: OFBIZ-6204.patch > > > createProductionRunsForOrder service creates OrderItemWorkFulfillment for the > top level production run to fulfill and OrderItemShipGroupAssoc but not for > the child mandatory preceeding ones. I need OrderItemWorkFulfillments > created for all mandatory production runs as well to generate a department > load report which determines the work that must be done based on orders. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7376) Routing Task should not be allowed to update with empty task name
[ https://issues.apache.org/jira/browse/OFBIZ-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7376: Summary: Routing Task should not be allowed to update with empty task name (was: Routing Task should not be allow to update with empty task name) > Routing Task should not be allowed to update with empty task name > - > > Key: OFBIZ-7376 > URL: https://issues.apache.org/jira/browse/OFBIZ-7376 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Pierre Smits >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-7376-trunk.patch > > > Steps to regenerate - > 1) Navigate to manufacturing -> Routing Task > 2) Press New Routing Task button. > 3) Try to create a new routing task without entering Task Name. It will not > allow to create the record as routing task name is mandatory field. > 4) Create Routing Task by adding proper details. > 5) Now, select newly create Routing Task from manufacturing -> Routing Task. > 6) Try to update selected Routing Task with empty Task Name. > Actual : Routing Task can be update with empty Task Name. > Expected : Routing Task should not allow to update with empty Task Name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7376) Routing Task should not be allowed to update with empty task name
[ https://issues.apache.org/jira/browse/OFBIZ-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-7376: --- Assignee: (was: Pierre Smits) > Routing Task should not be allowed to update with empty task name > - > > Key: OFBIZ-7376 > URL: https://issues.apache.org/jira/browse/OFBIZ-7376 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Trunk >Reporter: Ankit Joshi >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-7376-trunk.patch > > > Steps to regenerate - > 1) Navigate to manufacturing -> Routing Task > 2) Press New Routing Task button. > 3) Try to create a new routing task without entering Task Name. It will not > allow to create the record as routing task name is mandatory field. > 4) Create Routing Task by adding proper details. > 5) Now, select newly create Routing Task from manufacturing -> Routing Task. > 6) Try to update selected Routing Task with empty Task Name. > Actual : Routing Task can be update with empty Task Name. > Expected : Routing Task should not allow to update with empty Task Name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-5580) Extend production run actual materials screen to support returns
[ https://issues.apache.org/jira/browse/OFBIZ-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5580: --- Assignee: (was: Pierre Smits) > Extend production run actual materials screen to support returns > > > Key: OFBIZ-5580 > URL: https://issues.apache.org/jira/browse/OFBIZ-5580 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Major > Attachments: productionrun-materialpage-task.png, > productionrun-returngoods.png > > > The Actual Materials page of production runs should be extended to support > material returns. As of right now the production run page has to be used to > return materials, however it only allows return of materials for the > currently running task. Actual Materials returns should allow returns > regardless of the currently running task. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
