[jira] [Commented] (OFBIZ-7544) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Manufacturing' component

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369433#comment-15369433
 ] 

Swapnil Shah commented on OFBIZ-7544:
-

I tried to use and test jquery multi select for partyrole over Find 
Order(https://ofbiz-vm.apache.org:18443/ordermgr/control/findorders) but 
somehow finding it not fully functionally yet as it doesn't not retain the 
selected roles once user hits 'Show lookup fields' again. 

In comparision, i still find the checkbox based multi-select over Order List 
(https://ofbiz-vm.apache.org:18443/ordermgr/control/orderlist) more cleaner and 
simple where user has to make less moves on UI to choose amongst multiple 
options and secondly, all search options never lose any visibility from user's 
eyes.

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Manufacturing' component
> ---
>
> Key: OFBIZ-7544
> URL: https://issues.apache.org/jira/browse/OFBIZ-7544
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7544.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7608) On Product>>Agreement screen rename the button label to create new agreement from "Edit Agreement" to "Create Agreement"

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7608:

Assignee: Divesh Dutta  (was: Swapnil Shah)

> On Product>>Agreement screen rename the button label to create new agreement 
> from "Edit Agreement" to "Create Agreement"
> 
>
> Key: OFBIZ-7608
> URL: https://issues.apache.org/jira/browse/OFBIZ-7608
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
>Priority: Minor
> Attachments: OFBIZ-7608.patch, PA.png
>
>
> Please refer to attached screenshot and change the button label to "Create 
> Agreement" as currently no agreement exists for given product



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7544) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Manufacturing' component

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364693#comment-15364693
 ] 

Swapnil Shah commented on OFBIZ-7544:
-

I agree that check box is more convenient when there are comparatively fewer 
options to select from (i.e. less than 8-9 options). At the same time other 
patterns like multi-select jquery or multi-select within drop-down itself could 
be preferred choice when there are relatively large number to choose from (i.e 
>10 options) as in those cases showing all options at a time in form of 
checkboxes would distort UI and consume lot of screen real estate 

> OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 
> 'Manufacturing' component
> ---
>
> Key: OFBIZ-7544
> URL: https://issues.apache.org/jira/browse/OFBIZ-7544
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL COMPONENTS
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7544.patch
>
>
> Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OFBIZ-7512) 'Issue Component' option after partial issuance against required component quantity is not accounting for already issued quantity

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah resolved OFBIZ-7512.
-
Resolution: Fixed

> 'Issue Component' option after partial issuance against required component 
> quantity is not accounting for already issued quantity
> -
>
> Key: OFBIZ-7512
> URL: https://issues.apache.org/jira/browse/OFBIZ-7512
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, 14.12.01, Release Branch 15.12, 
> 15.12.01
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Attachments: OFBIZ-7173.png, OFBIZ-7512.patch
>
>
> Once we issue the required component partially (i.e. by producing partial 
> quantity while task is still is still running or in case full ATP against 
> required quantity is not available for issuance) then "Issue Component" is 
> not honoring the already made issuance and hence issuing the whole required 
> quantity once again. (please refer to attached screenshot)
> !https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7512) 'Issue Component' option after partial issuance against required component quantity is not accounting for already issued quantity

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364661#comment-15364661
 ] 

Swapnil Shah commented on OFBIZ-7512:
-

Thanks [~anuj.jain] I have validated the fixes and its working as expected.

[~diveshdut] You may like to close this one after backporting the changes so 
assigning back to you for closure..

> 'Issue Component' option after partial issuance against required component 
> quantity is not accounting for already issued quantity
> -
>
> Key: OFBIZ-7512
> URL: https://issues.apache.org/jira/browse/OFBIZ-7512
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, 14.12.01, Release Branch 15.12, 
> 15.12.01
>Reporter: Swapnil Shah
>Assignee: Divesh Dutta
> Attachments: OFBIZ-7173.png, OFBIZ-7512.patch
>
>
> Once we issue the required component partially (i.e. by producing partial 
> quantity while task is still is still running or in case full ATP against 
> required quantity is not available for issuance) then "Issue Component" is 
> not honoring the already made issuance and hence issuing the whole required 
> quantity once again. (please refer to attached screenshot)
> !https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (OFBIZ-7522) Hide user inputs for Location/Lot# for fully issued components against production run task

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah reopened OFBIZ-7522:
-
  Assignee: Anuj Jain  (was: Swapnil Shah)

> Hide user inputs for Location/Lot# for fully issued components against 
> production run task
> --
>
> Key: OFBIZ-7522
> URL: https://issues.apache.org/jira/browse/OFBIZ-7522
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Anuj Jain
>Priority: Minor
> Attachments: OFBIZ-7522.patch, PR_1.png
>
>
> Once any component item gets fully issued then also we allow user to enter 
> the location/lot# etc. under 'Materials Required By The Running Task' panel, 
> like we do for un-issued or partially issued components. 
> We can possible hide user selection and text entry against such fully issued 
> items and show it only if remaining to be issued qty > 0
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7522) Hide user inputs for Location/Lot# for fully issued components against production run task

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362001#comment-15362001
 ] 

Swapnil Shah commented on OFBIZ-7522:
-

[~anuj.jain] I have tested the patch and finding that editable fields are still 
shown for fully issued items under 'Materials Required By The Running Task' 
section. Can you please fix this.

> Hide user inputs for Location/Lot# for fully issued components against 
> production run task
> --
>
> Key: OFBIZ-7522
> URL: https://issues.apache.org/jira/browse/OFBIZ-7522
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Minor
> Attachments: OFBIZ-7522.patch, PR_1.png
>
>
> Once any component item gets fully issued then also we allow user to enter 
> the location/lot# etc. under 'Materials Required By The Running Task' panel, 
> like we do for un-issued or partially issued components. 
> We can possible hide user selection and text entry against such fully issued 
> items and show it only if remaining to be issued qty > 0
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7725) Extend EftAccount entity with 'branchCode' and provide necessary support in code and UI

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7725:

 Assignee: (was: Swapnil Shah)
Affects Version/s: (was: 15.12.01)
   (was: 14.12.01)
   Upcoming Branch

> Extend EftAccount entity with 'branchCode' and provide necessary support in 
> code and UI
> ---
>
> Key: OFBIZ-7725
> URL: https://issues.apache.org/jira/browse/OFBIZ-7725
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>
> Let's extend EftAccount by adding 'BranchCode' that could indicate the branch 
> code of the Bank through which Eft Account is linked, It could be allowed to 
> optionally set for any existing and new EftAccount in Ofbiz system.
> Let's ask for 'Branch Code' with other details while Eft Account is being 
> added/edited from UI (e..g Party >> Profile etc.).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7725) Extend EftAccount entity with 'branchCode' and provide necessary support in code and UI

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360953#comment-15360953
 ] 

Swapnil Shah edited comment on OFBIZ-7725 at 7/4/16 7:23 AM:
-

Sorry i couldn't trace any dedicated field to set 'branchCode' in EFT_ACCOUNT 
(https://ofbiz-vm.apache.org:8443/webtools/control/FindGeneric?entityName=EftAccount).
 Are we referring it from any other entity? 


was (Author: swash78):
Sorry i couldn't trace it in EFT_ACCOUNT 
(https://ofbiz-vm.apache.org:8443/webtools/control/FindGeneric?entityName=EftAccount).
 Are we referring it from any other entity? 

> Extend EftAccount entity with 'branchCode' and provide necessary support in 
> code and UI
> ---
>
> Key: OFBIZ-7725
> URL: https://issues.apache.org/jira/browse/OFBIZ-7725
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Let's extend EftAccount by adding 'BranchCode' that could indicate the branch 
> code of the Bank through which Eft Account is linked, It could be allowed to 
> optionally set for any existing and new EftAccount in Ofbiz system.
> Let's ask for 'Branch Code' with other details while Eft Account is being 
> added/edited from UI (e..g Party >> Profile etc.).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7725) Extend EftAccount entity with 'branchCode' and provide necessary support in code and UI

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360953#comment-15360953
 ] 

Swapnil Shah commented on OFBIZ-7725:
-

Sorry i couldn't trace it in EFT_ACCOUNT 
(https://ofbiz-vm.apache.org:8443/webtools/control/FindGeneric?entityName=EftAccount).
 Are we referring it from any other entity? 

> Extend EftAccount entity with 'branchCode' and provide necessary support in 
> code and UI
> ---
>
> Key: OFBIZ-7725
> URL: https://issues.apache.org/jira/browse/OFBIZ-7725
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Let's extend EftAccount by adding 'BranchCode' that could indicate the branch 
> code of the Bank through which Eft Account is linked, It could be allowed to 
> optionally set for any existing and new EftAccount in Ofbiz system.
> Let's ask for 'Branch Code' with other details while Eft Account is being 
> added/edited from UI (e..g Party >> Profile etc.).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7725) Extend EftAccount entity with 'branchCode' and provide necessary support in code and UI

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360902#comment-15360902
 ] 

Swapnil Shah commented on OFBIZ-7725:
-

I am not sure but i don't think many countries have fully adopted to the 
practice of having branch code(swift code) embedded in bank account number for 
both domestic and international fund transfer. If its only true for limited set 
of countries e.g. within SEPA, then we can try to keep it separate as well from 
Bank account number to keep the feature more generic. 

> Extend EftAccount entity with 'branchCode' and provide necessary support in 
> code and UI
> ---
>
> Key: OFBIZ-7725
> URL: https://issues.apache.org/jira/browse/OFBIZ-7725
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Let's extend EftAccount by adding 'BranchCode' that could indicate the branch 
> code of the Bank through which Eft Account is linked, It could be allowed to 
> optionally set for any existing and new EftAccount in Ofbiz system.
> Let's ask for 'Branch Code' with other details while Eft Account is being 
> added/edited from UI (e..g Party >> Profile etc.).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7682) Define and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360806#comment-15360806
 ] 

Swapnil Shah commented on OFBIZ-7682:
-

Yes, In fact i have checked with few clients using EFT very frequently and they 
have already customized it by extending 'Branch Code'. I have create OFBIZ-7725 
for it now.  

> Define and add new entity for 'Check' as Payment Method
> ---
>
> Key: OFBIZ-7682
> URL: https://issues.apache.org/jira/browse/OFBIZ-7682
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Jacques Le Roux
> Attachments: OFBIZ-7682.patch
>
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
> entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store 
> all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7725) Extend EftAccount entity with 'branchCode' and provide necessary support in code and UI

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7725:
---

 Summary: Extend EftAccount entity with 'branchCode' and provide 
necessary support in code and UI
 Key: OFBIZ-7725
 URL: https://issues.apache.org/jira/browse/OFBIZ-7725
 Project: OFBiz
  Issue Type: New Feature
  Components: accounting
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Let's extend EftAccount by adding 'BranchCode' that could indicate the branch 
code of the Bank through which Eft Account is linked, It could be allowed to 
optionally set for any existing and new EftAccount in Ofbiz system.

Let's ask for 'Branch Code' with other details while Eft Account is being 
added/edited from UI (e..g Party >> Profile etc.).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360268#comment-15360268
 ] 

Swapnil Shah edited comment on OFBIZ-7650 at 7/2/16 6:15 PM:
-

Yes, i have created OFBIZ-7722 for it now


was (Author: swash78):
Yes, i have create OFBIZ-7722 for it now

> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Ankush Upadhyay
>Priority: Minor
> Attachments: OFBIZ-7650.patch
>
>
> To begin with can start fixing it under :
> # "Add Product Price" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000
> # "Add Product Cost Component Calc" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000
> # "Add Content to Product" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000
> Let's keep on adding other screens where it could be fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360268#comment-15360268
 ] 

Swapnil Shah commented on OFBIZ-7650:
-

Yes, i have create OFBIZ-7722 for it now

> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Ankush Upadhyay
>Priority: Minor
> Attachments: OFBIZ-7650.patch
>
>
> To begin with can start fixing it under :
> # "Add Product Price" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000
> # "Add Product Cost Component Calc" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000
> # "Add Content to Product" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000
> Let's keep on adding other screens where it could be fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7722) Sub-menu looks overlapping in Tomahawk theme

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7722:

Attachment: Theme.png

> Sub-menu looks overlapping in Tomahawk theme
> 
>
> Key: OFBIZ-7722
> URL: https://issues.apache.org/jira/browse/OFBIZ-7722
> Project: OFBiz
>  Issue Type: Bug
>  Components: themes
>Affects Versions: Trunk
>Reporter: Swapnil Shah
> Attachments: Theme.png
>
>
> Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7722) Sub-menu looks overlapping in Tomahawk theme

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7722:
---

 Summary: Sub-menu looks overlapping in Tomahawk theme
 Key: OFBIZ-7722
 URL: https://issues.apache.org/jira/browse/OFBIZ-7722
 Project: OFBiz
  Issue Type: Bug
  Components: themes
Affects Versions: Trunk
Reporter: Swapnil Shah


Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7718) Shipment Id goes missing on PO receiving screen once PO is received partially

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7718:

Attachment: PO_Receiving.png
PO_Shipment.png

> Shipment Id goes missing on PO receiving screen once PO is received partially
> -
>
> Key: OFBIZ-7718
> URL: https://issues.apache.org/jira/browse/OFBIZ-7718
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PO_Receiving.png, PO_Shipment.png
>
>
> Once PO Is received partially and then remaining qty is attempted to be 
> received then shipment id for earlier shipment goes missing
> Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7718) Shipment Id goes missing on PO receiving screen once PO is received partially

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7718:
---

 Summary: Shipment Id goes missing on PO receiving screen once PO 
is received partially
 Key: OFBIZ-7718
 URL: https://issues.apache.org/jira/browse/OFBIZ-7718
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Swapnil Shah
Assignee: Swapnil Shah
 Attachments: PO_Receiving.png, PO_Shipment.png

Once PO Is received partially and then remaining qty is attempted to be 
received then shipment id for earlier shipment goes missing

Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with Suppliers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7714:

Description: 
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a buyer or procurement 
users doesn't have direct accounting permission in case quick pricing agreement 
needs to be placed with Supplier for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Purchase" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
hitting this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder
!PPA.png|thumbnail!

  was:
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a buyer or procurement 
users doesn't have direct accounting permission in case quick pricing agreement 
needs to be placed with Supplier for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Purchase" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
hitting this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder


> Introduce a quick way for adding Purchase Price agreements with Suppliers for 
> any specific product from Catalog
> ---
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a buyer or 
> procurement users doesn't have direct accounting permission in case quick 
> pricing agreement needs to be placed with Supplier for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Purchase" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
> hitting this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase 
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement 
> and AgreementItem & SupplierProduct between Supplier and organization by 
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder
> !PPA.png|thumbnail!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with Suppliers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7714:

Description: 
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a buyer or procurement 
users doesn't have direct accounting permission in case quick pricing agreement 
needs to be placed with Supplier for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Purchase" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
hitting this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder

  was:
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a buyer or procurement 
users doesn't have direct accounting permission in case quick pricing agreement 
needs to be placed with Supplier for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
hitting this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder


> Introduce a quick way for adding Purchase Price agreements with Suppliers for 
> any specific product from Catalog
> ---
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a buyer or 
> procurement users doesn't have direct accounting permission in case quick 
> pricing agreement needs to be placed with Supplier for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Purchase" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
> hitting this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase 
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement 
> and AgreementItem & SupplierProduct between Supplier and organization by 
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with Suppliers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7714:

Description: 
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a buyer or procurement 
users doesn't have direct accounting permission in case quick pricing agreement 
needs to be placed with Supplier for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
hitting this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder

  was:
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a catalog or sales 
manager doesn't have accounting permission in case quick pricing agreement 
needs to be placed with customer for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder


> Introduce a quick way for adding Purchase Price agreements with Suppliers for 
> any specific product from Catalog
> ---
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a buyer or 
> procurement users doesn't have direct accounting permission in case quick 
> pricing agreement needs to be placed with Supplier for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and 
> hitting this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase 
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement 
> and AgreementItem & SupplierProduct between Supplier and organization by 
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with Suppliers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7714:

Summary: Introduce a quick way for adding Purchase Price agreements with 
Suppliers for any specific product from Catalog  (was: Introduce a quick way 
for adding Purchase Price agreements with customers for any specific product 
from Catalog)

> Introduce a quick way for adding Purchase Price agreements with Suppliers for 
> any specific product from Catalog
> ---
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase 
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement 
> and AgreementItem & SupplierProduct between Supplier and organization by 
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with customers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7714:

Description: 
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a catalog or sales 
manager doesn't have accounting permission in case quick pricing agreement 
needs to be placed with customer for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:

# Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
this link could ask user to enter following very basic parameters:
#- Party Id From (Default it to facility's owner party id)
#- Party Id To (show list of suppliers like we show at the time of Purchase 
Order entry screen)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
#- Supplier Product Id
# Upon successful submission of above details system should create Agreement 
and AgreementItem & SupplierProduct between Supplier and organization by 
passing following default values:
#- Role Type Id From = 'Internal Organization'
#- Role Type Id To = ''Supplier"
#- Agreement Type Id = 'Purchase'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder

  was:
Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a catalog or sales 
manager doesn't have accounting permission in case quick pricing agreement 
needs to be placed with customer for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:
Have a 'Create Price Agreement' link/button on the Sales Panel and hitting this 
link could ask user to enter following very basic parameters:
Party Id From (Default it to facility's owner party id)
Party Id To (show list of suppliers like we show at the time of Purchase Order 
entry screen)
>From Date (default it to show as now() timestamp)
Through Date
Description
Price
Currency
Supplier Product Id
Upon successful submission of above details system should create Agreement and 
AgreementItem & SupplierProduct between Supplier and organization by passing 
following default values:
Role Type Id From = 'Internal Organization'
Role Type Id To = ''Supplier"
Agreement Type Id = 'Purchase'
Agreement Item Type Id = 'Pricing'
Product Id= ''

Please refer to attached screenshot for reference placeholder


> Introduce a quick way for adding Purchase Price agreements with customers for 
> any specific product from Catalog
> ---
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase 
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement 
> and AgreementItem & SupplierProduct between Supplier and organization by 
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with customers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7714:

Attachment: PPA.png

> Introduce a quick way for adding Purchase Price agreements with customers for 
> any specific product from Catalog
> ---
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase 
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement 
> and AgreementItem & SupplierProduct between Supplier and organization by 
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7714) Introduce a quick way for adding Purchase Price agreements with customers for any specific product from Catalog

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7714:
---

 Summary: Introduce a quick way for adding Purchase Price 
agreements with customers for any specific product from Catalog
 Key: OFBIZ-7714
 URL: https://issues.apache.org/jira/browse/OFBIZ-7714
 Project: OFBiz
  Issue Type: New Feature
  Components: product
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a catalog or sales 
manager doesn't have accounting permission in case quick pricing agreement 
needs to be placed with customer for specific product(s).
We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:
Have a 'Create Price Agreement' link/button on the Sales Panel and hitting this 
link could ask user to enter following very basic parameters:
Party Id From (Default it to facility's owner party id)
Party Id To (show list of suppliers like we show at the time of Purchase Order 
entry screen)
>From Date (default it to show as now() timestamp)
Through Date
Description
Price
Currency
Supplier Product Id
Upon successful submission of above details system should create Agreement and 
AgreementItem & SupplierProduct between Supplier and organization by passing 
following default values:
Role Type Id From = 'Internal Organization'
Role Type Id To = ''Supplier"
Agreement Type Id = 'Purchase'
Agreement Item Type Id = 'Pricing'
Product Id= ''

Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7713) Introduce a quick way for adding Sales Price agreements with customers for any specific product from Catalog

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7713:

Attachment: SPA.png

> Introduce a quick way for adding Sales Price agreements with customers for 
> any specific product from Catalog
> 
>
> Key: OFBIZ-7713
> URL: https://issues.apache.org/jira/browse/OFBIZ-7713
> Project: OFBiz
>  Issue Type: New Feature
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: SPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where 
> it is quite an long and arduous process. And many a times a catalog or sales 
> manager doesn't have accounting permission in case quick pricing agreement 
> needs to be placed with customer for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen 
> over "Sales" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
> this link could ask user to enter following very basic parameters:
> #- Party Id From
> #- Party Id To (Default it to product store's owner party id)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> # Upon successful submission of above details system should create Agreement 
> and Agreement Item between customer and organization by passing following 
> default values:
> #- Role Type Id From = 'Customer'
> #- Role Type Id To = 'Internal Organization'
> #- Agreement Type Id = 'Sales'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= ''
> Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7713) Introduce a quick way for adding Sales Price agreements with customers for any specific product from Catalog

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7713:
---

 Summary: Introduce a quick way for adding Sales Price agreements 
with customers for any specific product from Catalog
 Key: OFBIZ-7713
 URL: https://issues.apache.org/jira/browse/OFBIZ-7713
 Project: OFBiz
  Issue Type: New Feature
  Components: product
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Currently new pricing agreements creation takes user to Accounting app where it 
is quite an long and arduous process. And many a times a catalog or sales 
manager doesn't have accounting permission in case quick pricing agreement 
needs to be placed with customer for specific product(s).

We can provide a quick option from Catalog >> Product >> Agreement screen over 
"Sales" section that could unfold as follows:
# Have a 'Create Price Agreement' link/button on the Sales Panel and hitting 
this link could ask user to enter following very basic parameters:
#- Party Id From
#- Party Id To (Default it to product store's owner party id)
#- From Date (default it to show as now() timestamp)
#- Through Date
#- Description
#- Price
#- Currency
# Upon successful submission of above details system should create Agreement 
and Agreement Item between customer and organization by passing following 
default values:
#- Role Type Id From = 'Customer'
#- Role Type Id To = 'Internal Organization'
#- Agreement Type Id = 'Sales'
#- Agreement Item Type Id = 'Pricing'
#- Product Id= ''

Please refer to attached screenshot for reference placeholder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7682) Define and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358339#comment-15358339
 ] 

Swapnil Shah edited comment on OFBIZ-7682 at 7/1/16 4:01 AM:
-

I feel checkbook number is also one kind of recurring information (like check#) 
although with lesser frequency. i.e., As soon as all check leafs are consumed 
then it is definitely bound to lose its existence physically and would no 
longer be in use. Not too sure but it might be better fit for payment reference 
(something like Payment.paymentRefNum)

Apart from this i think all other field mapping makes sense and are in sync 
with ticket description.




was (Author: swash78):
I feel checkbook number is also one kind of recurring information (like check#) 
although with lesser frequency. i.e., As soon as all check leafs are consumed 
then it is definitely bound to lose its existence physically and would no 
longer be in use. Not too sure but it might be better fit for payment reference.

Apart from this i think all other field mapping makes sense and are in sync 
with ticket description.



> Define and add new entity for 'Check' as Payment Method
> ---
>
> Key: OFBIZ-7682
> URL: https://issues.apache.org/jira/browse/OFBIZ-7682
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
> entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store 
> all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7682) Define and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358339#comment-15358339
 ] 

Swapnil Shah edited comment on OFBIZ-7682 at 7/1/16 4:03 AM:
-

I feel checkbook number is also one kind of recurring information (like check#) 
although with lesser frequency. i.e., As soon as all check leafs are consumed 
then it is definitely bound to lose its existence physically and would no 
longer be in use. Not too sure but it might be better fit for payment reference 
(something like Payment.paymentRefNum)

Apart from this i think all other field mapping makes sense and are in sync 
with ticket description. One addition detail probably we can add here is 
"BRANCH_CODE" so that it completes the trail for storing all Bank related 
information




was (Author: swash78):
I feel checkbook number is also one kind of recurring information (like check#) 
although with lesser frequency. i.e., As soon as all check leafs are consumed 
then it is definitely bound to lose its existence physically and would no 
longer be in use. Not too sure but it might be better fit for payment reference 
(something like Payment.paymentRefNum)

Apart from this i think all other field mapping makes sense and are in sync 
with ticket description.



> Define and add new entity for 'Check' as Payment Method
> ---
>
> Key: OFBIZ-7682
> URL: https://issues.apache.org/jira/browse/OFBIZ-7682
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
> entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store 
> all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7682) Define and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358339#comment-15358339
 ] 

Swapnil Shah commented on OFBIZ-7682:
-

I feel checkbook number is also one kind of recurring information (like check#) 
although with lesser frequency. i.e., As soon as all check leafs are consumed 
then it is definitely bound to lose its existence physically and would no 
longer be in use. Not too sure but it might be better fit for payment reference.

Apart from this i think all other field mapping makes sense and are in sync 
with ticket description.



> Define and add new entity for 'Check' as Payment Method
> ---
>
> Key: OFBIZ-7682
> URL: https://issues.apache.org/jira/browse/OFBIZ-7682
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
> entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store 
> all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7682) Deffine and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7682:

Description: 
Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store all 
relevant details related to Check used as payment method for any party.

PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
BANK_NAME
ROUTING_NUMBER
ACCOUNT_TYPE
ACCOUNT_NUMBER
NAME_ON_ACCOUNT
COMPANY_NAME_ON_ACCOUNT
CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
LAST_UPDATED_STAMP
LAST_UPDATED_TX_STAMP
CREATED_STAMP
CREATED_TX_STAMP


  was:
Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store all 
relevant details related to Check used as payment method for any party.

PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
CHECK_TYPE (Can add related enumerations as PERSONAL_CHECK,COMPANY_CHECK & 
CERTIFIED_CHECK)
BANK_NAME
ROUTING_NUMBER
ACCOUNT_TYPE
ACCOUNT_NUMBER
NAME_ON_ACCOUNT
COMPANY_NAME_ON_ACCOUNT
CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
LAST_UPDATED_STAMP
LAST_UPDATED_TX_STAMP
CREATED_STAMP
CREATED_TX_STAMP



> Deffine and add new entity for 'Check' as Payment Method
> 
>
> Key: OFBIZ-7682
> URL: https://issues.apache.org/jira/browse/OFBIZ-7682
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
> entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store 
> all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7682) Deffine and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7682:

Description: 
Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store all 
relevant details related to Check used as payment method for any party.

PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
CHECK_TYPE (Can add related enumerations as PERSONAL_CHECK,COMPANY_CHECK & 
CERTIFIED_CHECK)
BANK_NAME
ROUTING_NUMBER
ACCOUNT_TYPE
ACCOUNT_NUMBER
NAME_ON_ACCOUNT
COMPANY_NAME_ON_ACCOUNT
CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
LAST_UPDATED_STAMP
LAST_UPDATED_TX_STAMP
CREATED_STAMP
CREATED_TX_STAMP


  was:
Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store all 
relevant details related to Check used as payment method for any party.

PAYMENT_METHOD_ID (PK)
CHECK_TYPE
BANK_NAME
ROUTING_NUMBER
ACCOUNT_TYPE
ACCOUNT_NUMBER
NAME_ON_ACCOUNT
COMPANY_NAME_ON_ACCOUNT
CONTACT_MECH_ID
LAST_UPDATED_STAMP
LAST_UPDATED_TX_STAMP
CREATED_STAMP
CREATED_TX_STAMP



> Deffine and add new entity for 'Check' as Payment Method
> 
>
> Key: OFBIZ-7682
> URL: https://issues.apache.org/jira/browse/OFBIZ-7682
> Project: OFBiz
>  Issue Type: New Feature
>  Components: accounting
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
> entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store 
> all relevant details related to Check used as payment method for any party.
> PAYMENT_METHOD_ID (PK & FK with PAYMENT_METHOD)
> CHECK_TYPE (Can add related enumerations as PERSONAL_CHECK,COMPANY_CHECK & 
> CERTIFIED_CHECK)
> BANK_NAME
> ROUTING_NUMBER
> ACCOUNT_TYPE
> ACCOUNT_NUMBER
> NAME_ON_ACCOUNT
> COMPANY_NAME_ON_ACCOUNT
> CONTACT_MECH_ID (FK with CONTACT_MECH & POSTAL_ADDRESS)
> LAST_UPDATED_STAMP
> LAST_UPDATED_TX_STAMP
> CREATED_STAMP
> CREATED_TX_STAMP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6899) Overview of payment methods in party profile misses function to set company check payment

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355705#comment-15355705
 ] 

Swapnil Shah commented on OFBIZ-6899:
-

Based on the discussed and concluded requirement let's use OFBIZ-7682 for 
defining/adding new entity with regard to 'CHECK'. Once done let's come back to 
this ticket to complete rest of the implementation.

> Overview of payment methods in party profile misses function to set company 
> check payment
> -
>
> Key: OFBIZ-6899
> URL: https://issues.apache.org/jira/browse/OFBIZ-6899
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting, order, party, specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Divesh Dutta
>  Labels: check, payment
> Fix For: Upcoming Branch
>
> Attachments: CC_1.png, CC_2.png, CC_3.png, CC_4.png, OFBIZ-6899.patch
>
>
> The payment methods overview in the party profile shows various options to 
> define and create a payment method.
> However there is no option to create payment method for a company check



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7682) Deffine and add new entity for 'Check' as Payment Method

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7682:
---

 Summary: Deffine and add new entity for 'Check' as Payment Method
 Key: OFBIZ-7682
 URL: https://issues.apache.org/jira/browse/OFBIZ-7682
 Project: OFBiz
  Issue Type: New Feature
  Components: accounting
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Based on the concluded requirement on OFBIZ-6899. Let's define Check as new 
entity as follows (somewhat on similar lines as EFT_ACCOUNT) so as to store all 
relevant details related to Check used as payment method for any party.

PAYMENT_METHOD_ID (PK)
CHECK_TYPE
BANK_NAME
ROUTING_NUMBER
ACCOUNT_TYPE
ACCOUNT_NUMBER
NAME_ON_ACCOUNT
COMPANY_NAME_ON_ACCOUNT
CONTACT_MECH_ID
LAST_UPDATED_STAMP
LAST_UPDATED_TX_STAMP
CREATED_STAMP
CREATED_TX_STAMP




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7666) OFBIZ-7649: Display From date with default now() on all screens under Project Application

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7666:
---

 Summary: OFBIZ-7649: Display From date with default now() on all 
screens under Project Application
 Key: OFBIZ-7666
 URL: https://issues.apache.org/jira/browse/OFBIZ-7666
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


To begin with can start fixing it under
# 
https://ofbiz-vm.apache.org:8443/projectmgr/control/ListWorkEffortPartyAssigns?projectId=9000
# 
https://ofbiz-vm.apache.org:8443/projectmgr/control/EditTaskPartyAssigns?workEffortId=9106
# 
https://ofbiz-vm.apache.org:8443/projectmgr/control/EditWorkEffortSurveyAppls?workEffortId=9106
# 
https://ofbiz-vm.apache.org:8443/projectmgr/control/listResourcesProject?partyId=admin
# 
https://ofbiz-vm.apache.org:8443/projectmgr/control/listResourcesTask?partyId=admin




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7665) OFBIZ-7649: Display From date with default now() on all screens under Content Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7665:

Description: 
To begin with can start fixing it under 
# 
https://ofbiz-vm.apache.org:8443/content/control/ListWebSiteContent?webSiteId=WebStore
# https://ofbiz-vm.apache.org:8443/content/control/createWebSiteContactList
# 
https://ofbiz-vm.apache.org:8443/content/control/findForums?forumGroupId=WebStoreFORUM
# 
https://ofbiz-vm.apache.org:8443/content/control/forumGroupRoles?forumGroupId=WebStoreFORUM
# 
https://ofbiz-vm.apache.org:8443/content/control/EditContentRole?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:8443/content/control/EditContentAssoc?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:8443/content/control/EditContentWorkEfforts?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:8443/content/control/EditDataResourceRole?dataResourceId=STDWRAP001
# https://ofbiz-vm.apache.org:8443/content/control/EditAddContenta

  was:
To begin with can start fixing it under 
# 
https://ofbiz-vm.apache.org:18443/content/control/ListWebSiteContent?webSiteId=WebStore
# https://ofbiz-vm.apache.org:18443/content/control/createWebSiteContactList
# 
https://ofbiz-vm.apache.org:18443/content/control/findForums?forumGroupId=WebStoreFORUM
# 
https://ofbiz-vm.apache.org:18443/content/control/forumGroupRoles?forumGroupId=WebStoreFORUM
# 
https://ofbiz-vm.apache.org:18443/content/control/EditContentRole?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:18443/content/control/EditContentAssoc?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:18443/content/control/EditContentWorkEfforts?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:18443/content/control/EditDataResourceRole?dataResourceId=STDWRAP001
# https://ofbiz-vm.apache.org:18443/content/control/EditAddContenta


> OFBIZ-7649: Display From date with default now() on all screens under Content 
> Application
> -
>
> Key: OFBIZ-7665
> URL: https://issues.apache.org/jira/browse/OFBIZ-7665
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>
> To begin with can start fixing it under 
> # 
> https://ofbiz-vm.apache.org:8443/content/control/ListWebSiteContent?webSiteId=WebStore
> # https://ofbiz-vm.apache.org:8443/content/control/createWebSiteContactList
> # 
> https://ofbiz-vm.apache.org:8443/content/control/findForums?forumGroupId=WebStoreFORUM
> # 
> https://ofbiz-vm.apache.org:8443/content/control/forumGroupRoles?forumGroupId=WebStoreFORUM
> # 
> https://ofbiz-vm.apache.org:8443/content/control/EditContentRole?contentId=BLOGROOTBIGAL
> # 
> https://ofbiz-vm.apache.org:8443/content/control/EditContentAssoc?contentId=BLOGROOTBIGAL
> # 
> https://ofbiz-vm.apache.org:8443/content/control/EditContentWorkEfforts?contentId=BLOGROOTBIGAL
> # 
> https://ofbiz-vm.apache.org:8443/content/control/EditDataResourceRole?dataResourceId=STDWRAP001
> # https://ofbiz-vm.apache.org:8443/content/control/EditAddContenta



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7665) OFBIZ-7649: Display From date with default now() on all screens under Content Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7665:

Description: 
To begin with can start fixing it under 
# 
https://ofbiz-vm.apache.org:18443/content/control/ListWebSiteContent?webSiteId=WebStore
# https://ofbiz-vm.apache.org:18443/content/control/createWebSiteContactList
# 
https://ofbiz-vm.apache.org:18443/content/control/findForums?forumGroupId=WebStoreFORUM
# 
https://ofbiz-vm.apache.org:18443/content/control/forumGroupRoles?forumGroupId=WebStoreFORUM
# 
https://ofbiz-vm.apache.org:18443/content/control/EditContentRole?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:18443/content/control/EditContentAssoc?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:18443/content/control/EditContentWorkEfforts?contentId=BLOGROOTBIGAL
# 
https://ofbiz-vm.apache.org:18443/content/control/EditDataResourceRole?dataResourceId=STDWRAP001
# https://ofbiz-vm.apache.org:18443/content/control/EditAddContenta

  was:To begin with can start fixing it under 


> OFBIZ-7649: Display From date with default now() on all screens under Content 
> Application
> -
>
> Key: OFBIZ-7665
> URL: https://issues.apache.org/jira/browse/OFBIZ-7665
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>
> To begin with can start fixing it under 
> # 
> https://ofbiz-vm.apache.org:18443/content/control/ListWebSiteContent?webSiteId=WebStore
> # https://ofbiz-vm.apache.org:18443/content/control/createWebSiteContactList
> # 
> https://ofbiz-vm.apache.org:18443/content/control/findForums?forumGroupId=WebStoreFORUM
> # 
> https://ofbiz-vm.apache.org:18443/content/control/forumGroupRoles?forumGroupId=WebStoreFORUM
> # 
> https://ofbiz-vm.apache.org:18443/content/control/EditContentRole?contentId=BLOGROOTBIGAL
> # 
> https://ofbiz-vm.apache.org:18443/content/control/EditContentAssoc?contentId=BLOGROOTBIGAL
> # 
> https://ofbiz-vm.apache.org:18443/content/control/EditContentWorkEfforts?contentId=BLOGROOTBIGAL
> # 
> https://ofbiz-vm.apache.org:18443/content/control/EditDataResourceRole?dataResourceId=STDWRAP001
> # https://ofbiz-vm.apache.org:18443/content/control/EditAddContenta



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7665) OFBIZ-7649: Display From date with default now() on all screens under Content Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7665:

Affects Version/s: 15.12.01
   14.12.01

> OFBIZ-7649: Display From date with default now() on all screens under Content 
> Application
> -
>
> Key: OFBIZ-7665
> URL: https://issues.apache.org/jira/browse/OFBIZ-7665
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>
> To begin with can start fixing it under 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7665) OFBIZ-7649: Display From date with default now() on all screens under Content Application

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7665:
---

 Summary: OFBIZ-7649: Display From date with default now() on all 
screens under Content Application
 Key: OFBIZ-7665
 URL: https://issues.apache.org/jira/browse/OFBIZ-7665
 Project: OFBiz
  Issue Type: Sub-task
  Components: content
Reporter: Swapnil Shah


To begin with can start fixing it under 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7662) OFBIZ-7649: Display From date with default now() on all screens under WorkEffort Application

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7662:
---

 Summary: OFBIZ-7649: Display From date with default now() on all 
screens under WorkEffort Application
 Key: OFBIZ-7662
 URL: https://issues.apache.org/jira/browse/OFBIZ-7662
 Project: OFBiz
  Issue Type: Sub-task
  Components: workeffort
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


To begin with we can start fixing it under
# 
https://ofbiz-vm.apache.org:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=10001
# 
https://ofbiz-vm.apache.org:8443/workeffort/control/EditWorkEffortContents?workEffortId=10001
# 
https://ofbiz-vm.apache.org:8443/workeffort/control/EditWorkEffortGoodStandards?workEffortId=10001
# 
https://ofbiz-vm.apache.org:8443/workeffort/control/ListWorkEffortFixedAssetAssigns?workEffortId=10001
# https://ofbiz-vm.apache.org:8443/workeffort/control/EditICalendar
# 
https://ofbiz-vm.apache.org:8443/workeffort/control/ICalendarParties?workEffortId=1
# 
https://ofbiz-vm.apache.org:8443/workeffort/control/ICalendarFixedAssets?workEffortId=1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7660) OFBIZ-7649: Display From date with default now() on all screens under HR Application

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7660:
---

 Summary: OFBIZ-7649: Display From date with default now() on all 
screens under HR Application
 Key: OFBIZ-7660
 URL: https://issues.apache.org/jira/browse/OFBIZ-7660
 Project: OFBiz
  Issue Type: Sub-task
  Components: humanres
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


To begin with we can start fixing it under
# "Edit Employment" over 
https://ofbiz-vm.apache.org:8443/humanres/control/EditEmployment
# "Add Position Fulfillment" over 
https:/ofbiz-vm.apache.org:8443/humanres/control/EditEmplPositionFulfillments?emplPositionId=DEMO100
# "Add Position Responsibility" over 
https://ofbiz-vm.apache.org:8443/humanres/control/createEmplPositionResponsibility
# "Add Empl Position Reporting Struct" over 
https://ofbiz-vm.apache.org:8443/humanres/control/EditEmplPositionReportingStructs?emplPositionId=DEMO100
# "New Party Qualification" over 
https://ofbiz-vm.apache.org:8443/humanres/control/NewPartyQual
# "Add Employee Leave" over 
https://ofbiz-vm.apache.org:8443/humanres/control/EditEmplLeave



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6899) Overview of payment methods in party profile misses function to set company check payment

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352730#comment-15352730
 ] 

Swapnil Shah commented on OFBIZ-6899:
-

Knock Knock :)

Let's have conclusion on it so we can proceed on fixing it accordingly.

> Overview of payment methods in party profile misses function to set company 
> check payment
> -
>
> Key: OFBIZ-6899
> URL: https://issues.apache.org/jira/browse/OFBIZ-6899
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting, order, party, specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Divesh Dutta
>  Labels: check, payment
> Fix For: Upcoming Branch
>
> Attachments: CC_1.png, CC_2.png, CC_3.png, CC_4.png, OFBIZ-6899.patch
>
>
> The payment methods overview in the party profile shows various options to 
> define and create a payment method.
> However there is no option to create payment method for a company check



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-7385) Allow user to select multiple options in "Sales By Store" report from basic search criteria while generating report

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah reassigned OFBIZ-7385:
---

Assignee: Mohammad Kathawala  (was: Swapnil Shah)

Assigning back to [~Mohammad K] for taking care of suggested changes 

> Allow user to select multiple options in "Sales By Store" report from basic 
> search criteria while generating report
> ---
>
> Key: OFBIZ-7385
> URL: https://issues.apache.org/jira/browse/OFBIZ-7385
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Mohammad Kathawala
> Attachments: OFBIZ-7385.patch, Salebystore.png
>
>
> Currently system allow user to select any specific search criteria link and 
> hence report is generated only based on any one given selected criteria. 
> We can add the feature for generating single report based on multiple values 
> (possibly via checkbox?) within basic search criteria in this report namely:
> 1) Product Store
> 2) Order Status
> and show the results based on all the selected values. Please refer attached 
> screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352545#comment-15352545
 ] 

Swapnil Shah commented on OFBIZ-7650:
-

Yes, i have been noticing this on Tomahawk theme only on most of the pages for 
sometime.

> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> To begin with can start fixing it under :
> # "Add Product Price" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000
> # "Add Product Cost Component Calc" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000
> # "Add Content to Product" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000
> Let's keep on adding other screens where it could be fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352544#comment-15352544
 ] 

Swapnil Shah commented on OFBIZ-7650:
-

Done..Thanks for pointing it out.

> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> To begin with can start fixing it under :
> # "Add Product Price" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000
> # "Add Product Cost Component Calc" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000
> # "Add Content to Product" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000
> Let's keep on adding other screens where it could be fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7650:

Description: 
To begin with can start fixing it under :
# "Add Product Price" form on 
https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000
# "Add Product Category" form on 
https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000
# "Add Product Cost Component Calc" form on 
https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000
# "Add Content to Product" form on 
https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000

Let's keep on adding other screens where it could be fixed

  was:
To begin with can start fixing it under :
# "Add Product Price" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000
# "Add Product Category" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCategories?productId=SV-1000
# "Add Product Cost Component Calc" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCosts?productId=SV-1000
# "Add Content to Product" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductContent?productId=GZ-1000

Let's keep on adding other screens where it could be fixed


> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> To begin with can start fixing it under :
> # "Add Product Price" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCategories?productId=SV-1000
> # "Add Product Cost Component Calc" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductCosts?productId=SV-1000
> # "Add Content to Product" form on 
> https://ofbiz-vm.apache.org:18443/catalog/control/EditProductContent?productId=GZ-1000
> Let's keep on adding other screens where it could be fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7653) OFBIZ-7649: Display From date with default now() on all screens under Manufacturing Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7653:

Description: 
To begin with we can start fixing it under 
# https://ofbiz-vm.apache.org:18443/manufacturing/control/CreateProductionRun
# "Edit Routing Task Association" on 
https://ofbiz-vm.apache.org:18443/manufacturing/control/EditRoutingTaskAssoc?workEffortId=DEFAULT_ROUTING
# "Edit Routing-Product Link" over 
https://ofbiz-vm.apache.org:18443/manufacturing/control/EditRoutingProductLink?workEffortId=DEFAULT_ROUTING
# "Add Routing Task Costs" over 
https://ofbiz-vm.apache.org:18443/manufacturing/control/EditRoutingTaskCosts?workEffortId=DEFAULT_TASK
# "Edit Routing Task Product" over 
https://ofbiz-vm.apache.org:18443/manufacturing/control/ListRoutingTaskProducts?workEffortId=DEFAULT_TASK
# https://ofbiz-vm.apache.org:18443/manufacturing/control/EditProductBom

  was:
To begin with we can start fixing it under 
# 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/CreateProductionRun
# "Edit Routing Task Association" on 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditRoutingTaskAssoc?workEffortId=DEFAULT_ROUTING
# "Edit Routing-Product Link" over 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditRoutingProductLink?workEffortId=DEFAULT_ROUTING
# "Add Routing Task Costs" over 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditRoutingTaskCosts?workEffortId=DEFAULT_TASK
# "Edit Routing Task Product" over 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/ListRoutingTaskProducts?workEffortId=DEFAULT_TASK
# https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditProductBom


> OFBIZ-7649: Display From date with default now() on all screens under 
> Manufacturing Application
> ---
>
> Key: OFBIZ-7653
> URL: https://issues.apache.org/jira/browse/OFBIZ-7653
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: manufacturing
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> To begin with we can start fixing it under 
> # https://ofbiz-vm.apache.org:18443/manufacturing/control/CreateProductionRun
> # "Edit Routing Task Association" on 
> https://ofbiz-vm.apache.org:18443/manufacturing/control/EditRoutingTaskAssoc?workEffortId=DEFAULT_ROUTING
> # "Edit Routing-Product Link" over 
> https://ofbiz-vm.apache.org:18443/manufacturing/control/EditRoutingProductLink?workEffortId=DEFAULT_ROUTING
> # "Add Routing Task Costs" over 
> https://ofbiz-vm.apache.org:18443/manufacturing/control/EditRoutingTaskCosts?workEffortId=DEFAULT_TASK
> # "Edit Routing Task Product" over 
> https://ofbiz-vm.apache.org:18443/manufacturing/control/ListRoutingTaskProducts?workEffortId=DEFAULT_TASK
> # https://ofbiz-vm.apache.org:18443/manufacturing/control/EditProductBom



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7651) OFBIZ-7649: Display From date with default now() on all screens under Party Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7651:

Description: 
To begin with let's start fixing it under
# "Add Party Content" form on 
https://ofbiz-vm.apache.org:18443/partymgr/control/EditPartyContents?partyId=DemoCustCompany
# "Edit Product Store Roles" from on 
https://ofbiz-vm.apache.org:18443/partymgr/control/ViewProductStoreRoles?partyId=DemoCustCompany

  was:
To begin with let's start fixing it under
# "Add Party Content" form on 
https://ofbiz-trunk.hotwaxsystems.com/partymgr/control/EditPartyContents?partyId=DemoCustCompany
# "Edit Product Store Roles" from on 
https://ofbiz-trunk.hotwaxsystems.com/partymgr/control/ViewProductStoreRoles?partyId=DemoCustCompany


> OFBIZ-7649: Display From date with default now() on all screens under Party 
> Application
> ---
>
> Key: OFBIZ-7651
> URL: https://issues.apache.org/jira/browse/OFBIZ-7651
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: party
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> To begin with let's start fixing it under
> # "Add Party Content" form on 
> https://ofbiz-vm.apache.org:18443/partymgr/control/EditPartyContents?partyId=DemoCustCompany
> # "Edit Product Store Roles" from on 
> https://ofbiz-vm.apache.org:18443/partymgr/control/ViewProductStoreRoles?partyId=DemoCustCompany



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7653) OFBIZ-7649: Display From date with default now() on all screens under Manufacturing Application

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7653:
---

 Summary: OFBIZ-7649: Display From date with default now() on all 
screens under Manufacturing Application
 Key: OFBIZ-7653
 URL: https://issues.apache.org/jira/browse/OFBIZ-7653
 Project: OFBiz
  Issue Type: Sub-task
  Components: manufacturing
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


To begin with we can start fixing it under 
# 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/CreateProductionRun
# "Edit Routing Task Association" on 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditRoutingTaskAssoc?workEffortId=DEFAULT_ROUTING
# "Edit Routing-Product Link" over 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditRoutingProductLink?workEffortId=DEFAULT_ROUTING
# "Add Routing Task Costs" over 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditRoutingTaskCosts?workEffortId=DEFAULT_TASK
# "Edit Routing Task Product" over 
https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/ListRoutingTaskProducts?workEffortId=DEFAULT_TASK
# https://ofbiz-trunk.hotwaxsystems.com/manufacturing/control/EditProductBom



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7651) OFBIZ-7649: Display From date with default now() on all screens under Party Application

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7651:
---

 Summary: OFBIZ-7649: Display From date with default now() on all 
screens under Party Application
 Key: OFBIZ-7651
 URL: https://issues.apache.org/jira/browse/OFBIZ-7651
 Project: OFBiz
  Issue Type: Sub-task
  Components: party
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Priority: Minor


To begin with let's start fixing it under
# "Add Party Content" form on 
https://ofbiz-trunk.hotwaxsystems.com/partymgr/control/EditPartyContents?partyId=DemoCustCompany
# "Edit Product Store Roles" from on 
https://ofbiz-trunk.hotwaxsystems.com/partymgr/control/ViewProductStoreRoles?partyId=DemoCustCompany



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7650:

Description: 
To begin with can start fixing it under :
# "Add Product Price" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000
# "Add Product Category" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCategories?productId=SV-1000
# "Add Product Cost Component Calc" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCosts?productId=SV-1000
# "Add Content to Product" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductContent?productId=GZ-1000

Let's keep on adding other screens where it could be fixed

  was:
Please fix it under 
# "Add Product Price" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000
# "Add Product Category" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCategories?productId=SV-1000


> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> To begin with can start fixing it under :
> # "Add Product Price" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCategories?productId=SV-1000
> # "Add Product Cost Component Calc" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCosts?productId=SV-1000
> # "Add Content to Product" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductContent?productId=GZ-1000
> Let's keep on adding other screens where it could be fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7649) Display "From Date" with default now() time-stamp and asterix sign on all forms where its part of Primary Key

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7649:

Description: 
Currently on many create/edit/add forms, where From Date is part of primary key 
is shown as blank, If user leaves it as blank then system either doesn't stop 
submitting the form but simply set it with now() timestamp implicitly or errors 
out.

As part of common UX practice, In all such forms/screen we could always try 
defaulting and display From Date with now() time stamp (with asterix sign)  
rather than showing it blank. So user is aware what would be set and its one of 
the required fields on given form

  was:
Currently on many create/edit/add forms, where From Date is part of primary key 
is shown as blank, If user leaves it as blank then system doesn't stop 
submitting the form but simply set it with now() timestamp implicitly.

As part of common UX practice, In all such forms/screen we could always try 
defaulting and display From Date with now() time stamp (with asterix sign)  
rather than showing it blank. So user is aware what would be set and its one of 
the required fields on given form


> Display "From Date" with default now() time-stamp and asterix sign on all 
> forms where its part of Primary Key
> -
>
> Key: OFBIZ-7649
> URL: https://issues.apache.org/jira/browse/OFBIZ-7649
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Currently on many create/edit/add forms, where From Date is part of primary 
> key is shown as blank, If user leaves it as blank then system either doesn't 
> stop submitting the form but simply set it with now() timestamp implicitly or 
> errors out.
> As part of common UX practice, In all such forms/screen we could always try 
> defaulting and display From Date with now() time stamp (with asterix sign)  
> rather than showing it blank. So user is aware what would be set and its one 
> of the required fields on given form



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7468) Define constraints while adding new material to the task which is in completed/cancel status.

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7468:

Summary: Define constraints while adding new material to the task which is 
in completed/cancel status.  (was: [OFBIZ-7173] Define constraints while adding 
new material to the task which is in completed/cancel status.)

> Define constraints while adding new material to the task which is in 
> completed/cancel status.
> -
>
> Key: OFBIZ-7468
> URL: https://issues.apache.org/jira/browse/OFBIZ-7468
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Anuj Jain
> Attachments: OFBIZ-7468.patch
>
>
> Define actions on adding new material to the task which is in 
> completed/cancel status. 
> Actions suggested by Swapnil :-
> # We can begin with simple constraint of allowing new material against the 
> only those routing task that has not cancelled yet within a production run
> # Any completed taks for uncomplete Production Run should have WEGS created 
> in COMPLETED status and WEIA created as well by issuing the added item's qty.
> # If production is already completed (aka all its routing task also 
> completed/cancelled) then don't allow new material to be added from Actual 
> Material screen 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7650:

Description: 
Please fix it under 
# "Add Product Price" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000
# "Add Product Category" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCategories?productId=SV-1000

  was:Please fix it under "Add Product Price" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000


> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> Please fix it under 
> # "Add Product Price" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000
> # "Add Product Category" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductCategories?productId=SV-1000



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on all screens under Catalog Application

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7650:

Summary: OFBIZ-7649: Display From date with default now() on all screens 
under Catalog Application  (was: OFBIZ-7649: Display From date with default 
now() on Edit Product Price screen)

> OFBIZ-7649: Display From date with default now() on all screens under Catalog 
> Application
> -
>
> Key: OFBIZ-7650
> URL: https://issues.apache.org/jira/browse/OFBIZ-7650
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Priority: Minor
>
> Please fix it under "Add Product Price" form on 
> https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7650) OFBIZ-7649: Display From date with default now() on Edit Product Price screen

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7650:
---

 Summary: OFBIZ-7649: Display From date with default now() on Edit 
Product Price screen
 Key: OFBIZ-7650
 URL: https://issues.apache.org/jira/browse/OFBIZ-7650
 Project: OFBiz
  Issue Type: Sub-task
  Components: product
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Priority: Minor


Please fix it under "Add Product Price" form on 
https://ofbiz-trunk.hotwaxsystems.com/catalog/control/EditProductPrices?productId=SV-1000



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7649) Display "From Date" with default now() time-stamp and asterix sign on all forms where its part of Primary Key

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7649:
---

 Summary: Display "From Date" with default now() time-stamp and 
asterix sign on all forms where its part of Primary Key
 Key: OFBIZ-7649
 URL: https://issues.apache.org/jira/browse/OFBIZ-7649
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Currently on many create/edit/add forms, where From Date is part of primary key 
is shown as blank, If user leaves it as blank then system doesn't stop 
submitting the form but simply set it with now() timestamp implicitly.

As part of common UX practice, In all such forms/screen we could always try 
defaulting and display From Date with now() time stamp (with asterix sign)  
rather than showing it blank. So user is aware what would be set and its one of 
the required fields on given form



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7468) [OFBIZ-7173] Define constraints while adding new material to the task which is in completed/cancel status.

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7468:

Summary: [OFBIZ-7173] Define constraints while adding new material to the 
task which is in completed/cancel status.  (was: [OFBIZ-7173] Actions on adding 
new material to the task  which is in completed/cancel status.)

> [OFBIZ-7173] Define constraints while adding new material to the task which 
> is in completed/cancel status.
> --
>
> Key: OFBIZ-7468
> URL: https://issues.apache.org/jira/browse/OFBIZ-7468
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Anuj Jain
>
> Define actions on adding new material to the task which is in 
> completed/cancel status. 
> Actions suggested by Swapnil :-
> # We can begin with simple constraint of allowing new material against the 
> only those routing task that has not cancelled yet within a production run
> # Any completed taks for uncomplete Production Run should have WEGS created 
> in COMPLETED status and WEIA created as well by issuing the added item's qty.
> # If production is already completed (aka all its routing task also 
> completed/cancelled) then don't allow new material to be added from Actual 
> Material screen 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7128) Purchase Order created out of Approved Product Requirement are not getting linked/shown over Requirement>>Order screen

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah closed OFBIZ-7128.
---

Thanks [~rahul.bhooteshwar] for the fixes. I have tested it and found it 
working as per expected behavior outlines in description. 

Here are test results:
# Run MRP and generate multiple requirements,
# Approve the requirement and use the same during purchase ordering by 
selecting eligible supplier
# Submit the order and found the Requirement>>Order tab reflecting the correct 
order id linking with used requirement (*PASS*)

> Purchase Order created out of Approved Product Requirement are not getting 
> linked/shown over Requirement>>Order screen
> --
>
> Key: OFBIZ-7128
> URL: https://issues.apache.org/jira/browse/OFBIZ-7128
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7128, ReqtoPO_1.png, ReqtoPO_2.png, ReqtoPO_3.png, 
> ReqtoPO_4.png, ReqtoPO_5.png
>
>
> Once any product requirement created out of MRP run or independently get 
> approved, becomes eligible for being used/converted to purchase order. But 
> once PO is created out of such requirements, it doesn't get linked/listed on 
> Requirement >> Order screen
> Please refer to attached screenshots for chain of events and reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7610) Product Price set based on 'Purchase Price Agreement' isn't honored while same is used during ordering

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7610:

Attachment: SA_5.png
SA_4.png
SA_3.png
SA_2.png
SA_1.png

> Product Price set based on 'Purchase Price Agreement' isn't honored while 
> same is used during ordering
> --
>
> Key: OFBIZ-7610
> URL: https://issues.apache.org/jira/browse/OFBIZ-7610
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: SA_1.png, SA_2.png, SA_3.png, SA_4.png, SA_5.png
>
>
> Once any Purchase Agreement is created with supplier for certain products at 
> pre-determined price, its get successfully transformed into SupplierProduct. 
> But at the time of Purchase order creation is same agreement is enforced then 
> agreement prices for products are ignored while setting the price on cart and 
> eventually on order itself.
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7610) Product Price set based on 'Purchase Price Agreement' isn't honored while same is used during ordering

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7610:
---

 Summary: Product Price set based on 'Purchase Price Agreement' 
isn't honored while same is used during ordering
 Key: OFBIZ-7610
 URL: https://issues.apache.org/jira/browse/OFBIZ-7610
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Swapnil Shah
Assignee: Swapnil Shah
 Attachments: SA_1.png, SA_2.png, SA_3.png, SA_4.png, SA_5.png

Once any Purchase Agreement is created with supplier for certain products at 
pre-determined price, its get successfully transformed into SupplierProduct. 

But at the time of Purchase order creation is same agreement is enforced then 
agreement prices for products are ignored while setting the price on cart and 
eventually on order itself.

Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7608) On Product>>Agreement screen rename the button label to create new agreement from "Edit Agreement" to "Create Agreement"

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7608:

Attachment: PA.png

> On Product>>Agreement screen rename the button label to create new agreement 
> from "Edit Agreement" to "Create Agreement"
> 
>
> Key: OFBIZ-7608
> URL: https://issues.apache.org/jira/browse/OFBIZ-7608
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Minor
> Attachments: PA.png
>
>
> Please refer to attached screenshot and change the button label to "Create 
> Agreement" as currently no agreement exists for given product



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7608) On Product>>Agreement screen rename the button label to create new agreement from "Edit Agreement" to "Create Agreement"

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7608:
---

 Summary: On Product>>Agreement screen rename the button label to 
create new agreement from "Edit Agreement" to "Create Agreement"
 Key: OFBIZ-7608
 URL: https://issues.apache.org/jira/browse/OFBIZ-7608
 Project: OFBiz
  Issue Type: Improvement
Affects Versions: Trunk
Reporter: Swapnil Shah
Assignee: Swapnil Shah
Priority: Minor


Please refer to attached screenshot and change the button label to "Create 
Agreement" as currently no agreement exists for given product



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7607) Promotions Shouldn't get auto-applied when "Sales/Price Agreement" is in force on sales order

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7607:

Description: 
More often than not if any sales(price) agreement with customer on any product 
is in play on any order then other active promotions/discounts/price rules 
(which are supposed to get auto-applied on List/Default price on any normal 
order) should take back seat unless specified otherwise. 

Currently, it seems to be happening otherwise, all the normal 
adjustments/discounts gets activated on Agreement Price itself (that are 
supposed to be applied on List/Default prices) whenever agreement is  enforced 
while placing the sales order.

Even if we need to do so, it could be allowed to be done on case by case basis 
as follows:

*Proposed solution:*
# Let's add the flag (checkbox) on screen Order Entry where any active 
agreements is allowed to be selected with label "Apply Active Promotions"
## If above flag is not checked, then order should be placed only and only with 
prices set on selected active agreement
## If above flag is checked then as its happening currently, do apply all 
active promotions/discounts/rules on agreement prices.
## By default the flag should remain unchecked, so it gets activated only if 
user specially select it to give other promotions on such order and it doesn't 
happen inadvertently.

Please refer to attached screenshot for references.

  was:
More often than not if any sales(price) agreement with customer on any product 
is in play on any order then other active promotions/discounts/price rules 
(which are supposed to get auto-applied on List/Default price on any normal 
order) should take back seat unless specified otherwise. 

Currently, it seems to be happening otherwise, all the normal 
adjustments/discounts gets activated on Agreement Price itself (that are 
supposed to be applied on List/Default prices) whenever agreement is  enforced 
while placing the sales order.

Even if we need to do so, it could be allowed to be done on case by case basis 
as follows:

*Proposed solution:*
# Let's add the flag (checkbox) on screen Order Entry where any active 
agreements is allowed to be selected with label "Apply Active Promotions"
## If above flag is not checked, then order should be placed only and only with 
prices set on selected active agreement
## If above flag is not checked then as its happening currently, do apply all 
active promotions/discounts/rules on agreement prices.
## By default the flag should remain unchecked, so it gets activated only if 
user specially select it to give other promotions on such order and it doesn't 
happen inadvertently.

Please refer to attached screenshot for references.


> Promotions Shouldn't get auto-applied when "Sales/Price Agreement" is in 
> force on sales order
> -
>
> Key: OFBIZ-7607
> URL: https://issues.apache.org/jira/browse/OFBIZ-7607
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PA_1.png, PA_2.png, PA_3.png
>
>
> More often than not if any sales(price) agreement with customer on any 
> product is in play on any order then other active promotions/discounts/price 
> rules (which are supposed to get auto-applied on List/Default price on any 
> normal order) should take back seat unless specified otherwise. 
> Currently, it seems to be happening otherwise, all the normal 
> adjustments/discounts gets activated on Agreement Price itself (that are 
> supposed to be applied on List/Default prices) whenever agreement is  
> enforced while placing the sales order.
> Even if we need to do so, it could be allowed to be done on case by case 
> basis as follows:
> *Proposed solution:*
> # Let's add the flag (checkbox) on screen Order Entry where any active 
> agreements is allowed to be selected with label "Apply Active Promotions"
> ## If above flag is not checked, then order should be placed only and only 
> with prices set on selected active agreement
> ## If above flag is checked then as its happening currently, do apply all 
> active promotions/discounts/rules on agreement prices.
> ## By default the flag should remain unchecked, so it gets activated only if 
> user specially select it to give other promotions on such order and it 
> doesn't happen inadvertently.
> Please refer to attached screenshot for references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7607) Promotions Shouldn't get auto-applied when "Sales/Price Agreement" is in force on sales order

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7607:

Attachment: PA_3.png
PA_2.png
PA_1.png

> Promotions Shouldn't get auto-applied when "Sales/Price Agreement" is in 
> force on sales order
> -
>
> Key: OFBIZ-7607
> URL: https://issues.apache.org/jira/browse/OFBIZ-7607
> Project: OFBiz
>  Issue Type: New Feature
>  Components: order
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: PA_1.png, PA_2.png, PA_3.png
>
>
> More often than not if any sales(price) agreement with customer on any 
> product is in play on any order then other active promotions/discounts/price 
> rules (which are supposed to get auto-applied on List/Default price on any 
> normal order) should take back seat unless specified otherwise. 
> Currently, it seems to be happening otherwise, all the normal 
> adjustments/discounts gets activated on Agreement Price itself (that are 
> supposed to be applied on List/Default prices) whenever agreement is  
> enforced while placing the sales order.
> Even if we need to do so, it could be allowed to be done on case by case 
> basis as follows:
> *Proposed solution:*
> # Let's add the flag (checkbox) on screen Order Entry where any active 
> agreements is allowed to be selected with label "Apply Active Promotions"
> ## If above flag is not checked, then order should be placed only and only 
> with prices set on selected active agreement
> ## If above flag is not checked then as its happening currently, do apply all 
> active promotions/discounts/rules on agreement prices.
> ## By default the flag should remain unchecked, so it gets activated only if 
> user specially select it to give other promotions on such order and it 
> doesn't happen inadvertently.
> Please refer to attached screenshot for references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7607) Promotions Shouldn't get auto-applied when "Sales/Price Agreement" is in force on sales order

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7607:
---

 Summary: Promotions Shouldn't get auto-applied when "Sales/Price 
Agreement" is in force on sales order
 Key: OFBIZ-7607
 URL: https://issues.apache.org/jira/browse/OFBIZ-7607
 Project: OFBiz
  Issue Type: New Feature
  Components: order
Affects Versions: 14.12.01, 15.12.01
Reporter: Swapnil Shah
Assignee: Swapnil Shah


More often than not if any sales(price) agreement with customer on any product 
is in play on any order then other active promotions/discounts/price rules 
(which are supposed to get auto-applied on List/Default price on any normal 
order) should take back seat unless specified otherwise. 

Currently, it seems to be happening otherwise, all the normal 
adjustments/discounts gets activated on Agreement Price itself (that are 
supposed to be applied on List/Default prices) whenever agreement is  enforced 
while placing the sales order.

Even if we need to do so, it could be allowed to be done on case by case basis 
as follows:

*Proposed solution:*
# Let's add the flag (checkbox) on screen Order Entry where any active 
agreements is allowed to be selected with label "Apply Active Promotions"
## If above flag is not checked, then order should be placed only and only with 
prices set on selected active agreement
## If above flag is not checked then as its happening currently, do apply all 
active promotions/discounts/rules on agreement prices.
## By default the flag should remain unchecked, so it gets activated only if 
user specially select it to give other promotions on such order and it doesn't 
happen inadvertently.

Please refer to attached screenshot for references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7485) Documentation: Unit Test (Use)Cases for OFBIZ-7173

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah closed OFBIZ-7485.
---

> Documentation: Unit Test (Use)Cases for OFBIZ-7173
> --
>
> Key: OFBIZ-7485
> URL: https://issues.apache.org/jira/browse/OFBIZ-7485
> Project: OFBiz
>  Issue Type: Task
>  Components: manufacturing
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Fix For: Upcoming Branch
>
>
> Here is the list of use cases that could be validated upon fixes made in 
> OFBIZ-7173
> # *CASE-01 -Production Run is created/confirmed but routing task is still not 
> started*
> ## As soon as new Material is added via "Actual Material" screen for any 
> task, the WorkEffortGoodStandard (WEGS) record should be created in 
> WEGS_CREATED Status
> ## The above created WEGS should be reflected over "Production Run 
> Declaration tab" under "Materials Required By The Running Task" section along 
> with other material requirements created out of pre-defined BoM for to be 
> produced item.
> # *CASE-02-Routing task for any active Production Run is already started*
> ## As soon as new Material is added via "Actual Material" screen for any 
> running routing task, the WorkEffortGoodStandard (WEGS) record should be 
> created in WEGS_CREATED Status
> ## The above created WEGS should be reflected over "Production Run 
> Declaration tab" under "Materials Required By The Running Task" section along 
> with other material requirements created out of pre-defined BoM for to be 
> produced item.
> ## Once user "Issue Component(ATP)" then available ATP against above newly 
> created material requirement (WEGS) should get issued and new 
> WorkEffortInventoryAssign (WEIA) should be created.
> ## The issued qty should also be reflected over "Production Run Declaration 
> tab" under "Return Unused Materials To Warehouse" against respective task and 
> be allowed to returned back to warehouse.
> # *CASE-03-Production Run is not completed yet the Routing task get Completed*
> ##  As soon as new Material is added via "Actual Material" screen for any 
> running routing task, the WorkEffortGoodStandard (WEGS) record should be 
> created in WEGS_COMPLETED Status and subsequently the added material 
> requirement should get issued and new WorkEffortInventoryAssign (WEIA) should 
> be created in same transaction itself.
> ## The issued qty should also be reflected over "Production Run Declaration 
> tab" under "Return Unused Materials To Warehouse" against respective task and 
> be allowed to returned back to warehouse.
> # *CASE-04-Routing task for any active Production Run is cancelled*
> ## New Material shouldn't be allowed to be added via Actual Material screen 
> for any already cancelled task with proper error message
> # *CASE-05-Production Run is already Completed (aka all Routing task are also 
> completed/cancelled)*
> ## New Material shouldn't be allowed to be added via Actual Material screen 
> for any already cancelled task with proper error message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7485) Documentation: Unit Test (Use)Cases for OFBIZ-7173

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7485:

Fix Version/s: Upcoming Branch

> Documentation: Unit Test (Use)Cases for OFBIZ-7173
> --
>
> Key: OFBIZ-7485
> URL: https://issues.apache.org/jira/browse/OFBIZ-7485
> Project: OFBiz
>  Issue Type: Task
>  Components: manufacturing
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Fix For: Upcoming Branch
>
>
> Here is the list of use cases that could be validated upon fixes made in 
> OFBIZ-7173
> # *CASE-01 -Production Run is created/confirmed but routing task is still not 
> started*
> ## As soon as new Material is added via "Actual Material" screen for any 
> task, the WorkEffortGoodStandard (WEGS) record should be created in 
> WEGS_CREATED Status
> ## The above created WEGS should be reflected over "Production Run 
> Declaration tab" under "Materials Required By The Running Task" section along 
> with other material requirements created out of pre-defined BoM for to be 
> produced item.
> # *CASE-02-Routing task for any active Production Run is already started*
> ## As soon as new Material is added via "Actual Material" screen for any 
> running routing task, the WorkEffortGoodStandard (WEGS) record should be 
> created in WEGS_CREATED Status
> ## The above created WEGS should be reflected over "Production Run 
> Declaration tab" under "Materials Required By The Running Task" section along 
> with other material requirements created out of pre-defined BoM for to be 
> produced item.
> ## Once user "Issue Component(ATP)" then available ATP against above newly 
> created material requirement (WEGS) should get issued and new 
> WorkEffortInventoryAssign (WEIA) should be created.
> ## The issued qty should also be reflected over "Production Run Declaration 
> tab" under "Return Unused Materials To Warehouse" against respective task and 
> be allowed to returned back to warehouse.
> # *CASE-03-Production Run is not completed yet the Routing task get Completed*
> ##  As soon as new Material is added via "Actual Material" screen for any 
> running routing task, the WorkEffortGoodStandard (WEGS) record should be 
> created in WEGS_COMPLETED Status and subsequently the added material 
> requirement should get issued and new WorkEffortInventoryAssign (WEIA) should 
> be created in same transaction itself.
> ## The issued qty should also be reflected over "Production Run Declaration 
> tab" under "Return Unused Materials To Warehouse" against respective task and 
> be allowed to returned back to warehouse.
> # *CASE-04-Routing task for any active Production Run is cancelled*
> ## New Material shouldn't be allowed to be added via Actual Material screen 
> for any already cancelled task with proper error message
> # *CASE-05-Production Run is already Completed (aka all Routing task are also 
> completed/cancelled)*
> ## New Material shouldn't be allowed to be added via Actual Material screen 
> for any already cancelled task with proper error message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7173) The Product Added from 'Actual Material' screen could be consumed for producing end product during routing task execution

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah closed OFBIZ-7173.
---

> The Product Added from 'Actual Material' screen could be consumed for 
> producing end product during routing task execution 
> --
>
> Key: OFBIZ-7173
> URL: https://issues.apache.org/jira/browse/OFBIZ-7173
> Project: OFBiz
>  Issue Type: New Feature
>  Components: manufacturing
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Fix For: Upcoming Branch
>
> Attachments: AM.png, OFBIZ-7173.patch, OFBIZ-7173.png
>
>
> Currently any new product added against given routing task via Actual 
> Material screen just reflects the inventory statistics it. 
> We could try to add the feature of having the added products actually be 
> added in conjunction with Actual projected Material requirement based on 
> original BoM associated with the routing. 
> # This could be done by creating fresh WorkEffortGoodStandard (WEGS) with 
> such added products against specified routing.
> # We can begin with simple constraint of allowing new material against the 
> only those routing task that has not cancelled yet within a production run
> # Any completed taks should have WEGS created in COMPLETED status and WEIA 
> created as well by issuing the added item's qty.
> # Start showing such newly added material requirement in conjunction with 
> original requirement (based on BoM) under all relevant sections over 
> Production Declaration Screen
> Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7180) Completed Service Order Items are being allowed to be edited over Approved PO

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah closed OFBIZ-7180.
---

Thanks [~upadhyay.ratnesh] for the fixes. I have tested and found them working 
as expected

> Completed Service Order Items are being allowed to be edited over Approved PO 
> --
>
> Key: OFBIZ-7180
> URL: https://issues.apache.org/jira/browse/OFBIZ-7180
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Critical
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIZ-7180.patch, SV_1.png, SV_2.png, SV_3.png
>
>
> Currently PO line items having service type products are completed on 
> Approval itself. But system still allows the Completed service items to be 
> edited over any Approved PO (e.g. if PO has both service and finished good 
> items that still need to be received). This lead to difference in invoice and 
> order valuation.
> We could possibly restrict the editing for any completed order items via Edit 
> Items option over Order view.
> Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7105) Purchase Return shipments not allowing to select received inventory within auto-completer search against the returned item

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7105:

Fix Version/s: Release Branch 14.12
   Release Branch 15.12

> Purchase Return shipments not allowing to select received inventory within 
> auto-completer search against the returned item
> --
>
> Key: OFBIZ-7105
> URL: https://issues.apache.org/jira/browse/OFBIZ-7105
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 14.12, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Minor
> Fix For: Release Branch 14.12, Release Branch 15.12, 13.07.04
>
> Attachments: OFBIZ-7105.patch, OFBIZ-7105.patch
>
>
> When any return shipment is created against a Purchase Order and product's 
> inventory is attempted to be selected via auto-completer then it doesn't 
> return anything,
> Expected behavior: The auto-completer search should always show the all 
> inventory item supplied by the given vendor and having ATP > 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7105) Purchase Return shipments not allowing to select received inventory within auto-completer search against the returned item

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah closed OFBIZ-7105.
---

Thanks [~ankush.upadhyay] i have tested and found the fix working as expected

> Purchase Return shipments not allowing to select received inventory within 
> auto-completer search against the returned item
> --
>
> Key: OFBIZ-7105
> URL: https://issues.apache.org/jira/browse/OFBIZ-7105
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 14.12, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Minor
> Fix For: Release Branch 14.12, Release Branch 15.12, 13.07.04
>
> Attachments: OFBIZ-7105.patch, OFBIZ-7105.patch
>
>
> When any return shipment is created against a Purchase Order and product's 
> inventory is attempted to be selected via auto-completer then it doesn't 
> return anything,
> Expected behavior: The auto-completer search should always show the all 
> inventory item supplied by the given vendor and having ATP > 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7105) Purchase Return shipments not allowing to select received inventory within auto-completer search against the returned item

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7105:

Fix Version/s: 13.07.04

> Purchase Return shipments not allowing to select received inventory within 
> auto-completer search against the returned item
> --
>
> Key: OFBIZ-7105
> URL: https://issues.apache.org/jira/browse/OFBIZ-7105
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Release Branch 14.12, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Minor
> Fix For: Release Branch 14.12, Release Branch 15.12, 13.07.04
>
> Attachments: OFBIZ-7105.patch, OFBIZ-7105.patch
>
>
> When any return shipment is created against a Purchase Order and product's 
> inventory is attempted to be selected via auto-completer then it doesn't 
> return anything,
> Expected behavior: The auto-completer search should always show the all 
> inventory item supplied by the given vendor and having ATP > 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7374) Add capability to Expire or Remove the added content for a party

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah closed OFBIZ-7374.
---

Thanks [~ankush.upadhyay] I have tested the fixes and found them working fine:

Unit Tests:
# Expired the existing content by setting thru dateand it stopped getting 
applied (*PASS*)
# Added content with from date in future and it didn't get applied (*PASS*)
# Added content with from date in past and it correctly got applied (*PASS*)

> Add capability to Expire or Remove the added content for a party
> 
>
> Key: OFBIZ-7374
> URL: https://issues.apache.org/jira/browse/OFBIZ-7374
> Project: OFBiz
>  Issue Type: New Feature
>  Components: party
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Fix For: Upcoming Branch
>
> Attachments: EditPartyContent.png, OFBIZ-7374.patch, 
> Party_content_1.png
>
>
> Currently when any content is uploaded/added with respect to any party via 
> Party Manager >> Parties >> Party Content tab, there is no option for user to 
> Expire or remove such added content in any form
> We could try adding this feature that could allow user to 
> # Expire any content by setting thru_date to now() on click of "Expire" 
> button against each content row
> # Or option to update the From/Thru date by showing these dates as editable 
> against each content row
> # Remove any added content on click of a "Delete" button 
> (Please refer to attached screenshot for reference)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7559) Material requirements is allowed to be added against already 'Cancelled' Production Run (task)

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7559:

Attachment: P1.png
P2.png
P3.png

> Material requirements is allowed to be added against already 'Cancelled' 
> Production Run (task)
> --
>
> Key: OFBIZ-7559
> URL: https://issues.apache.org/jira/browse/OFBIZ-7559
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: P1.png, P2.png, P3.png
>
>
> Currently system allows user to add/issue the new material requirement 
> against cancelled routing tasks. 
> Expected Behavior:
> System should allow user to add the new material requirement against only 
> non-cancelled tasks
> Please refer to attached screenshot for reference
> !|width=800px!
> !|width=800px!
> !|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7559) Material requirements is allowed to be added against already 'Cancelled' Production Run (task)

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7559:

Description: 
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812787/P2.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812786/P3.png|width=800px!

  was:
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812787/P2.png|width=800px!
!|width=800px!


> Material requirements is allowed to be added against already 'Cancelled' 
> Production Run (task)
> --
>
> Key: OFBIZ-7559
> URL: https://issues.apache.org/jira/browse/OFBIZ-7559
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: P1.png, P2.png, P3.png
>
>
> Currently system allows user to add/issue the new material requirement 
> against cancelled routing tasks. 
> Expected Behavior:
> System should allow user to add the new material requirement against only 
> non-cancelled tasks
> Please refer to attached screenshot for reference
> !https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812787/P2.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812786/P3.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7559) Material requirements is allowed to be added against already 'Cancelled' Production Run (task)

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7559:

Description: 
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
!|width=800px!
!|width=800px!

  was:
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!|width=800px!
!|width=800px!
!|width=800px!


> Material requirements is allowed to be added against already 'Cancelled' 
> Production Run (task)
> --
>
> Key: OFBIZ-7559
> URL: https://issues.apache.org/jira/browse/OFBIZ-7559
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: P1.png, P2.png, P3.png
>
>
> Currently system allows user to add/issue the new material requirement 
> against cancelled routing tasks. 
> Expected Behavior:
> System should allow user to add the new material requirement against only 
> non-cancelled tasks
> Please refer to attached screenshot for reference
> !https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
> !|width=800px!
> !|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7559) Material requirements is allowed to be added against already 'Cancelled' Production Run (task)

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7559:

Description: 
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812787/P2.png|width=800px!
!|width=800px!

  was:
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
!|width=800px!
!|width=800px!


> Material requirements is allowed to be added against already 'Cancelled' 
> Production Run (task)
> --
>
> Key: OFBIZ-7559
> URL: https://issues.apache.org/jira/browse/OFBIZ-7559
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: P1.png, P2.png, P3.png
>
>
> Currently system allows user to add/issue the new material requirement 
> against cancelled routing tasks. 
> Expected Behavior:
> System should allow user to add the new material requirement against only 
> non-cancelled tasks
> Please refer to attached screenshot for reference
> !https://issues.apache.org/jira/secure/attachment/12812788/P1.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812787/P2.png|width=800px!
> !|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7559) Material requirements is allowed to be added against already 'Cancelled' Production Run (task)

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7559:

Description: 
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference

!|width=800px!
!|width=800px!
!|width=800px!

  was:
Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference


> Material requirements is allowed to be added against already 'Cancelled' 
> Production Run (task)
> --
>
> Key: OFBIZ-7559
> URL: https://issues.apache.org/jira/browse/OFBIZ-7559
> Project: OFBiz
>  Issue Type: Improvement
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Currently system allows user to add/issue the new material requirement 
> against cancelled routing tasks. 
> Expected Behavior:
> System should allow user to add the new material requirement against only 
> non-cancelled tasks
> Please refer to attached screenshot for reference
> !|width=800px!
> !|width=800px!
> !|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7559) Material requirements is allowed to be added against already 'Cancelled' Production Run (task)

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7559:
---

 Summary: Material requirements is allowed to be added against 
already 'Cancelled' Production Run (task)
 Key: OFBIZ-7559
 URL: https://issues.apache.org/jira/browse/OFBIZ-7559
 Project: OFBiz
  Issue Type: Improvement
  Components: manufacturing
Affects Versions: Trunk
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Currently system allows user to add/issue the new material requirement against 
cancelled routing tasks. 

Expected Behavior:
System should allow user to add the new material requirement against only 
non-cancelled tasks

Please refer to attached screenshot for reference



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7558) Any update made for 'Qty to produce' in a newly created production run not saved

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7558:

Description: 
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812779/PR2.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812780/PR3.png|width=800px!

  was:
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812780/PR2.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812780/PR3.png|width=800px!


> Any update made for 'Qty to produce' in a newly created production run not 
> saved 
> -
>
> Key: OFBIZ-7558
> URL: https://issues.apache.org/jira/browse/OFBIZ-7558
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Critical
> Attachments: PR1.png, PR2.png, PR3.png
>
>
> Whenever quantity to produce is revised for any production run (in created 
> status) the material requirement at WEGS (per BoM) gets readjusted 
> accordingly but the same is not saved correctly (under 
> WorkEffort.quantityToProduce)
> Now when production run is confirmed, the quantity to produce is original 
> quantity but all material requirements at WEGS level are projected and 
> readjusted.
> Expected Behavior:
> Any changes made to Quantity to Produce for production run should be saved 
> correctly
> Please refer to attached screenshot
> !https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812779/PR2.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812780/PR3.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7558) Any update made for 'Qty to produce' in a newly created production run not saved

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7558:

Description: 
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812780/PR2.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812780/PR3.png|width=800px!

  was:
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px!


> Any update made for 'Qty to produce' in a newly created production run not 
> saved 
> -
>
> Key: OFBIZ-7558
> URL: https://issues.apache.org/jira/browse/OFBIZ-7558
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Critical
> Attachments: PR1.png, PR2.png, PR3.png
>
>
> Whenever quantity to produce is revised for any production run (in created 
> status) the material requirement at WEGS (per BoM) gets readjusted 
> accordingly but the same is not saved correctly (under 
> WorkEffort.quantityToProduce)
> Now when production run is confirmed, the quantity to produce is original 
> quantity but all material requirements at WEGS level are projected and 
> readjusted.
> Expected Behavior:
> Any changes made to Quantity to Produce for production run should be saved 
> correctly
> Please refer to attached screenshot
> !https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812780/PR2.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812780/PR3.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7558) Any update made for 'Qty to produce' in a newly created production run not saved

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7558:

Description: 
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812779/PR2.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812778/PR3.png|width=800px!

  was:
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812779/PR2.png|width=800px!
!https://issues.apache.org/jira/secure/attachment/12812780/PR3.png|width=800px!


> Any update made for 'Qty to produce' in a newly created production run not 
> saved 
> -
>
> Key: OFBIZ-7558
> URL: https://issues.apache.org/jira/browse/OFBIZ-7558
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Critical
> Attachments: PR1.png, PR2.png, PR3.png
>
>
> Whenever quantity to produce is revised for any production run (in created 
> status) the material requirement at WEGS (per BoM) gets readjusted 
> accordingly but the same is not saved correctly (under 
> WorkEffort.quantityToProduce)
> Now when production run is confirmed, the quantity to produce is original 
> quantity but all material requirements at WEGS level are projected and 
> readjusted.
> Expected Behavior:
> Any changes made to Quantity to Produce for production run should be saved 
> correctly
> Please refer to attached screenshot
> !https://issues.apache.org/jira/secure/attachment/12812780/PR1.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812779/PR2.png|width=800px!
> !https://issues.apache.org/jira/secure/attachment/12812778/PR3.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7558) Any update made for 'Qty to produce' in a newly created production run not saved

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7558:

Attachment: PR1.png
PR2.png
PR3.png

> Any update made for 'Qty to produce' in a newly created production run not 
> saved 
> -
>
> Key: OFBIZ-7558
> URL: https://issues.apache.org/jira/browse/OFBIZ-7558
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Critical
> Attachments: PR1.png, PR2.png, PR3.png
>
>
> Whenever quantity to produce is revised for any production run (in created 
> status) the material requirement at WEGS (per BoM) gets readjusted 
> accordingly but the same is not saved correctly (under 
> WorkEffort.quantityToProduce)
> Now when production run is confirmed, the quantity to produce is original 
> quantity but all material requirements at WEGS level are projected and 
> readjusted.
> Expected Behavior:
> Any changes made to Quantity to Produce for production run should be saved 
> correctly
> Please refer to attached screenshot
> !https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7558) Any update made for 'Qty to produce' in a newly created production run not saved

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7558:

Description: 
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot

!https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px!

  was:
Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot


> Any update made for 'Qty to produce' in a newly created production run not 
> saved 
> -
>
> Key: OFBIZ-7558
> URL: https://issues.apache.org/jira/browse/OFBIZ-7558
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>Priority: Critical
>
> Whenever quantity to produce is revised for any production run (in created 
> status) the material requirement at WEGS (per BoM) gets readjusted 
> accordingly but the same is not saved correctly (under 
> WorkEffort.quantityToProduce)
> Now when production run is confirmed, the quantity to produce is original 
> quantity but all material requirements at WEGS level are projected and 
> readjusted.
> Expected Behavior:
> Any changes made to Quantity to Produce for production run should be saved 
> correctly
> Please refer to attached screenshot
> !https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7558) Any update made for 'Qty to produce' in a newly created production run not saved

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7558:
---

 Summary: Any update made for 'Qty to produce' in a newly created 
production run not saved 
 Key: OFBIZ-7558
 URL: https://issues.apache.org/jira/browse/OFBIZ-7558
 Project: OFBiz
  Issue Type: Bug
  Components: manufacturing
Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12
Reporter: Swapnil Shah
Assignee: Swapnil Shah
Priority: Critical


Whenever quantity to produce is revised for any production run (in created 
status) the material requirement at WEGS (per BoM) gets readjusted accordingly 
but the same is not saved correctly (under WorkEffort.quantityToProduce)

Now when production run is confirmed, the quantity to produce is original 
quantity but all material requirements at WEGS level are projected and 
readjusted.

Expected Behavior:
Any changes made to Quantity to Produce for production run should be saved 
correctly

Please refer to attached screenshot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-6899) Overview of payment methods in party profile misses function to set company check payment

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345891#comment-15345891
 ] 

Swapnil Shah edited comment on OFBIZ-6899 at 6/23/16 6:38 AM:
--

I reckon outgoing payment treatment is more or less same whether its towards 
Purchase made from suppliers or its towards Refund made to Customers (e.g, 
Sales Return of Refund type). Though we could validate it once but if we can 
gauge these all transactions correctly via standard Payment Type and Payment 
statuses then ledger entry should fall in place.

Apart from it, if there is indeed any real time need of electronically 
transferring Check details to different financial institutions like Bank etc., 
(similar to what we mostly do for Credit Card/EFT), then we could add Check as 
new entity to store all relevant details as discussed above. Although, we 
haven't came across any real requirement around that from our clients so far 
who are dealing inbound/outbound payments through checks.  

And if add this as new entity on OFbiz data model then we can also tag this as 
"New Feature" instead of improvement as its missing till now in OFbiz.


was (Author: swash78):
I reckon outgoing payment treatment is more or less same whether its towards 
Purchase made from suppliers or its towards Refund made to Customers (e.g, 
Sales Return of Refund type). Though we could validate it once but if we can 
gauge these all transactions correctly via standard Payment Type and Payment 
statuses then ledger entry should fall in place.

Apart from it, if there are is indeed any real time need of electronically 
transferring Check details to different financial institutions like Bank etc., 
(similar to what we mostly do for Credit Card/EFT), then we could add Check as 
new entity to store all relevant details as discussed above. Although, we 
haven't came across any real requirement around that from our clients so far 
who are dealing inbound/outbound payments through checks.  

And if add this as new entity on OFbiz data model then we can also tag this as 
"New Feature" instead of improvement as its missing till now in OFbiz.

> Overview of payment methods in party profile misses function to set company 
> check payment
> -
>
> Key: OFBIZ-6899
> URL: https://issues.apache.org/jira/browse/OFBIZ-6899
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting, order, party, specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Divesh Dutta
>  Labels: check, payment
> Fix For: Upcoming Branch
>
> Attachments: CC_1.png, CC_2.png, CC_3.png, CC_4.png, OFBIZ-6899.patch
>
>
> The payment methods overview in the party profile shows various options to 
> define and create a payment method.
> However there is no option to create payment method for a company check



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6899) Overview of payment methods in party profile misses function to set company check payment

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345891#comment-15345891
 ] 

Swapnil Shah commented on OFBIZ-6899:
-

I reckon outgoing payment treatment is more or less same whether its towards 
Purchase made from suppliers or its towards Refund made to Customers (e.g, 
Sales Return of Refund type). Though we could validate it once but if we can 
gauge these all transactions correctly via standard Payment Type and Payment 
statuses then ledger entry should fall in place.

Apart from it, if there are is indeed any real time need of electronically 
transferring Check details to different financial institutions like Bank etc., 
(similar to what we mostly do for Credit Card/EFT), then we could add Check as 
new entity to store all relevant details as discussed above. Although, we 
haven't came across any real requirement around that from our clients so far 
who are dealing inbound/outbound payments through checks.  

And if add this as new entity on OFbiz data model then we can also tag this as 
"New Feature" instead of improvement as its missing till now in OFbiz.

> Overview of payment methods in party profile misses function to set company 
> check payment
> -
>
> Key: OFBIZ-6899
> URL: https://issues.apache.org/jira/browse/OFBIZ-6899
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting, order, party, specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Divesh Dutta
>  Labels: check, payment
> Fix For: Upcoming Branch
>
> Attachments: CC_1.png, CC_2.png, CC_3.png, CC_4.png, OFBIZ-6899.patch
>
>
> The payment methods overview in the party profile shows various options to 
> define and create a payment method.
> However there is no option to create payment method for a company check



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7547) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Content' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7547:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'Content' component
 Key: OFBIZ-7547
 URL: https://issues.apache.org/jira/browse/OFBIZ-7547
 Project: OFBiz
  Issue Type: Sub-task
  Components: content
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7550) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Project' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7550:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'Project' component
 Key: OFBIZ-7550
 URL: https://issues.apache.org/jira/browse/OFBIZ-7550
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7549) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'HR' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7549:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'HR' component
 Key: OFBIZ-7549
 URL: https://issues.apache.org/jira/browse/OFBIZ-7549
 Project: OFBiz
  Issue Type: Sub-task
  Components: humanres
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7548) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'WorkEffort' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7548:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'WorkEffort' component
 Key: OFBIZ-7548
 URL: https://issues.apache.org/jira/browse/OFBIZ-7548
 Project: OFBiz
  Issue Type: Sub-task
  Components: workeffort
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7546) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Accounting' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7546:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'Accounting' component
 Key: OFBIZ-7546
 URL: https://issues.apache.org/jira/browse/OFBIZ-7546
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7544) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Manufacturing' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7544:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'Manufacturing' component
 Key: OFBIZ-7544
 URL: https://issues.apache.org/jira/browse/OFBIZ-7544
 Project: OFBiz
  Issue Type: Sub-task
Reporter: Swapnil Shah


Please refer to details shared over OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7543) OFBIZ-7542: Convert search criteria on 'Status' into multi-select pattern for 'Order' component

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7543:
---

 Summary: OFBIZ-7542: Convert search criteria on 'Status' into 
multi-select pattern for 'Order' component
 Key: OFBIZ-7543
 URL: https://issues.apache.org/jira/browse/OFBIZ-7543
 Project: OFBiz
  Issue Type: Sub-task
  Components: order
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


Please refer the details provided on OFBIZ-7542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7542) Convert search criteria on 'Status' into multi-select pattern on all search screens

[Swapnil Shah (JIRA)]

Swapnil Shah created OFBIZ-7542:
---

 Summary: Convert search criteria on 'Status' into multi-select 
pattern on all search screens
 Key: OFBIZ-7542
 URL: https://issues.apache.org/jira/browse/OFBIZ-7542
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: Upcoming Branch
Reporter: Swapnil Shah
Assignee: Swapnil Shah


There are many screens where search can be performed on on given status at a 
time as its shown in form of dropdown and user can select only one value from 
it.

Like Order list screen, we can try using this multi-select as generic search 
pattern starting with 'Status' and leveraging upon it for any other eligible 
search criteria. It should behave as follows:
# Selecting "All" (via checkbox) should auto-select all applicable statuses 
# De-selecting "All" should remove selection from all selected statuses
# After selecting "All" if any other status(es) are selected and "All" should 
be de-selected automatically
# Multiple statuses should be selectable simultaneously
# The search result should honor the selected statuses



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7533) Not able to set new Lot Id to existing inventory item

[Swapnil Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapnil Shah updated OFBIZ-7533:

Affects Version/s: (was: 15.12.01)
   (was: 14.12.01)
   Upcoming Branch

> Not able to set new Lot Id to existing inventory item
> -
>
> Key: OFBIZ-7533
> URL: https://issues.apache.org/jira/browse/OFBIZ-7533
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Affects Versions: Upcoming Branch
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: II_LOT.png
>
>
> When any new lot is assigned to exiting inventory item then it ends up 
> throwing foreign key constraint.
> We could allow it by creating first new lot (if its not found already 
> existent in DB) and then associate the same with given inventory item. (Also 
> currently i couldn't find any screen to create new lot in given facility)
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7533) Not able to set new Lot Id to existing inventory item

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343846#comment-15343846
 ] 

Swapnil Shah edited comment on OFBIZ-7533 at 6/22/16 7:28 AM:
--

Thanks for sharing the reference [~pfm.smits]. I have tried to walk through the 
discussion but it seems there is still no conclusion made. So irrespective of 
fact what design approach we follow under OFBIZ-5704, i feel the feature for 
updating Lot id over an inventory item should still hold water and hence we can 
possibly attempt to fix this ticket independently for now and later once we 
have implementation detail concluded with regard to lot, Lot Id provision via 
inventory item could proved to be an add on.


was (Author: swash78):
Thanks for sharing the reference [~pfm.smits]. I have tried to walk through the 
discussion but it seems there is still no conclusion made. So irrespective of 
fact what design approach we follow under OFBIZ-5704, i feel the feature for 
updating Lot id over an inventory item should still hold water and hence we can 
possibly attempt to fix this ticket independently for now and later we have 
implementation detail concluded with regard to lot, Lot Id provision via 
inventory item could proved to be an add on.

> Not able to set new Lot Id to existing inventory item
> -
>
> Key: OFBIZ-7533
> URL: https://issues.apache.org/jira/browse/OFBIZ-7533
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: II_LOT.png
>
>
> When any new lot is assigned to exiting inventory item then it ends up 
> throwing foreign key constraint.
> We could allow it by creating first new lot (if its not found already 
> existent in DB) and then associate the same with given inventory item. (Also 
> currently i couldn't find any screen to create new lot in given facility)
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7533) Not able to set new Lot Id to existing inventory item

[Swapnil Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343846#comment-15343846
 ] 

Swapnil Shah edited comment on OFBIZ-7533 at 6/22/16 7:28 AM:
--

Thanks for sharing the reference [~pfm.smits]. I have tried to walk through the 
discussion but it seems there is still no conclusion made. So irrespective of 
fact what design approach we follow under OFBIZ-5704, i feel the feature for 
updating Lot id over an inventory item should still hold water and hence we can 
possibly attempt to fix this ticket independently for now and later we have 
implementation detail concluded with regard to lot, Lot Id provision via 
inventory item could proved to be an add on.


was (Author: swash78):
Thanks for sharing the reference [~pfm.smits]. I have tried to walk through the 
discussion but it seems there is still no conclusion made. But irrespective of 
fact what design approach we follow under OFBIZ-5704, i feel the feature for 
updating Lot id over an inventory item should still be working and hence we can 
possibly attempt to fix this ticket independently for now and later we have 
implementation detail concluded with regard to lot, Lot Id provision via 
inventory item could proved to be an add on.

> Not able to set new Lot Id to existing inventory item
> -
>
> Key: OFBIZ-7533
> URL: https://issues.apache.org/jira/browse/OFBIZ-7533
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Affects Versions: 14.12.01, 15.12.01
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
> Attachments: II_LOT.png
>
>
> When any new lot is assigned to exiting inventory item then it ends up 
> throwing foreign key constraint.
> We could allow it by creating first new lot (if its not found already 
> existent in DB) and then associate the same with given inventory item. (Also 
> currently i couldn't find any screen to create new lot in given facility)
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)