[jira] [Resolved] (OFBIZ-10371) Add a link onto a crashed Job to reset it
[ https://issues.apache.org/jira/browse/OFBIZ-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-10371. -- Resolution: Invalid > Add a link onto a crashed Job to reset it > - > > Key: OFBIZ-10371 > URL: https://issues.apache.org/jira/browse/OFBIZ-10371 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10371.patch > > > When a job crash due to OFBiz interruption, there is no easy way to replan it. > Everything exists in the code base to do it, just adding a link onto crashed > job in webtools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OFBIZ-10371) Add a link onto a crashed Job to reset it
[ https://issues.apache.org/jira/browse/OFBIZ-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne reopened OFBIZ-10371: -- Reverting the improvement, that should not be needed, since crashed job are to be rescheduled. The problem I met lies somewhere else. Thanks [~lektran] for the suggestion > Add a link onto a crashed Job to reset it > - > > Key: OFBIZ-10371 > URL: https://issues.apache.org/jira/browse/OFBIZ-10371 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10371.patch > > > When a job crash due to OFBiz interruption, there is no easy way to replan it. > Everything exists in the code base to do it, just adding a link onto crashed > job in webtools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-10365: Description: h2. *Design Approach #1:* * Create Header entity *InventoryTransferHeader (ITH)* ** inventoryTransferId* ** statusId ** facilityId ** locationSeqId ** facilityIdTo ** locationSeqIdTo ** primaryShipmentId * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so as to support item level details as follows: ** inventoryTransferId* ** InvtransferItemSeqId* ** inventoryItemId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items under same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create *TransferItemBilling* entity to support invoicing (if needed) ** inventoryTransferId* ** InvtransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** Amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId* *Screenflow for Approach #1:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements will be disabled. * User can select multiple Approved Transfer Requirements between any two given facilities to create Single Inventory Transfer between them. * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers would be created by consolidating all products/items requirements between any two given locations. * System would auto-assign the required quantity from existing inventoryItems based on FIFO. * Add a new *View Inventory Transfer* screen ** From here user can manually override the auto-assigned InventoryItems against each product. ** User can Add/Edit/Delete the Transfer Items. ** After assigning InventoryItems user can Approve the Inventory Transfer. ** Upon Approval ATP would get reduced to the tune of assigned quantity from each inventory item. * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available to pack. * Upon completion of packing reduce the QOH from assigned inventory items to the tune of packed quantity. * After completing packing, shipment will be created in shipped status and Inventory Transfer will be marked as 'SENT'. * Once received at destination location the ATP/QOH would be increased up to the transferred quantity per product and shipment will be marked as 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. *To Be Business Process for Approach #1:* *!InventoryTransferModelLevel1.png!* h2. *Design Approach #2:* * Alter *InventoryTransfer* entity as header entity as follows: ** Add primaryShipmentId ** Remove inventoryItemId * Add new entity *InventoryTransferItem* ** inventoryTransferId* ** InvtransferItemSeqId* ** inventoryItemId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items for same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create TransferItemBilling entity to support tax invoice ** inventoryTransferId* ** InvtransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId* *Screenflow for Approach #2:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements will be disabled. * User can select multiple Approved
[jira] [Comment Edited] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455787#comment-16455787 ] Pawan Verma edited comment on OFBIZ-10365 at 4/27/18 5:43 AM: -- Removing inventoryItemId from PK of InventoryTransferItem entity. As one inventoryItem can be available in single InventoryTransfer only one time as we are consolidating item quantity. Also removing fromDate and thruDate from RequirementInventoryTransfer entity. was (Author: pawan.verma): Removing inventoryItemId from PK of InventoryTransferItem entity. As one inventoryItem can be available in single InventoryTransfer only one time as we are consolidating item quantity. > Document design approaches for Inventory Transfer > -- > > Key: OFBIZ-10365 > URL: https://issues.apache.org/jira/browse/OFBIZ-10365 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Pawan Verma >Priority: Minor > Attachments: InventoryTransferModelLevel1.png, > OrderModelActivityLevel1.png > > > h2. *Design Approach #1:* > * Create Header entity *InventoryTransferHeader (ITH)* > ** inventoryTransferId* > ** statusId > ** facilityId > ** locationSeqId > ** facilityIdTo > ** locationSeqIdTo > ** primaryShipmentId > > * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so > as to support item level details as follows: > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** inventoryItemId > ** shipmentId > ** shipmentItemSeqId > ** quantity > ** unitPrice > > Having InventoryItem detail at InventoryTransferItem level will help us to > manage multiple Items under same InventoryTransfer and each > InventoryTransferItem can be fulfilled via multiple Inventory items and/or > multiple Shipments. > > * Create *TransferItemBilling* entity to support invoicing (if needed) > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** invoiceId* > ** invoiceItemSeqId* > ** itemIssuanceId > ** shipmentReceiptId > ** quantity > ** Amount > * Create *InventoryTransferContanctMech* entity to support InventoryTransfer > Contact Mechanism > ** inventoryTransferId* > ** contactMechPurposeTypeId* > ** contactMechId* > * Create *RequirementInventoryTransfer* entity > ** requirementId* > ** inventoryTransferId* > ** fromDate* > ** thruDate > * Refactor existing *InventoryItemDetail* entity > ** inventoryTransferId* > *Screenflow for Approach #1:* > * Add a new *Find Transfer Requirements* screen. > ** Transfer Requirements can be searched with following parameters: > *** Requirement ID > *** Status ID > *** Shipment ID > *** Origin Facility ID > *** Destination Facility ID > *** Product ID > *** Description > *** Requirement Start Date > *** Required By Date > > * Option for creating Inventory Transfer for Un-approved requirements will > be disabled. > * User can select multiple Approved Transfer Requirements between any two > given facilities to create Single Inventory Transfer between them. > * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers > would be created by consolidating all products/items requirements between any > two given locations. > * System would auto-assign the required quantity from existing > inventoryItems based on FIFO. > * Add a new *View Inventory Transfer* screen > ** From here user can manually override the auto-assigned InventoryItems > against each product. > ** User can Add/Edit/Delete the Transfer Items. > ** After assigning InventoryItems user can Approve the Inventory Transfer. > ** Upon Approval ATP would get reduced to the tune of assigned quantity from > each inventory item. > * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory > Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available > to pack. > * Upon completion of packing reduce the QOH from assigned inventory items to > the tune of packed quantity. > * After completing packing, shipment will be created in shipped status and > Inventory Transfer will be marked as 'SENT'. > * Once received at destination location the ATP/QOH would be increased up to > the transferred quantity per product and shipment will be marked as > 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. > > *To Be Business Process for Approach #1:* > *!InventoryTransferModelLevel1.png!* > > h2. *Design Approach #2:* > * Alter *InventoryTransfer* entity as header entity as follows: > ** Add primaryShipmentId > ** Remove inventoryItemId > > * Add new entity *InventoryTransferItem* > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** inventoryItemId > ** shipmentId > **
[jira] [Commented] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455787#comment-16455787 ] Pawan Verma commented on OFBIZ-10365: - Removing inventoryItemId from PK of InventoryTransferItem entity. As one inventoryItem can be available in single InventoryTransfer only one time as we are consolidating item quantity. > Document design approaches for Inventory Transfer > -- > > Key: OFBIZ-10365 > URL: https://issues.apache.org/jira/browse/OFBIZ-10365 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Pawan Verma >Priority: Minor > Attachments: InventoryTransferModelLevel1.png, > OrderModelActivityLevel1.png > > > h2. *Design Approach #1:* > * Create Header entity *InventoryTransferHeader (ITH)* > ** inventoryTransferId* > ** statusId > ** facilityId > ** locationSeqId > ** facilityIdTo > ** locationSeqIdTo > ** primaryShipmentId > > * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so > as to support item level details as follows: > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** inventoryItemId > ** shipmentId > ** shipmentItemSeqId > ** quantity > ** unitPrice > > Having InventoryItem detail at InventoryTransferItem level will help us to > manage multiple Items under same InventoryTransfer and each > InventoryTransferItem can be fulfilled via multiple Inventory items and/or > multiple Shipments. > > * Create *TransferItemBilling* entity to support invoicing (if needed) > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** invoiceId* > ** invoiceItemSeqId* > ** itemIssuanceId > ** shipmentReceiptId > ** quantity > ** Amount > * Create *InventoryTransferContanctMech* entity to support InventoryTransfer > Contact Mechanism > ** inventoryTransferId* > ** contactMechPurposeTypeId* > ** contactMechId* > * Create *RequirementInventoryTransfer* entity > ** requirementId* > ** inventoryTransferId* > ** fromDate* > ** thruDate > * Refactor existing *InventoryItemDetail* entity > ** inventoryTransferId* > *Screenflow for Approach #1:* > * Add a new *Find Transfer Requirements* screen. > ** Transfer Requirements can be searched with following parameters: > *** Requirement ID > *** Status ID > *** Shipment ID > *** Origin Facility ID > *** Destination Facility ID > *** Product ID > *** Description > *** Requirement Start Date > *** Required By Date > > * Option for creating Inventory Transfer for Un-approved requirements will > be disabled. > * User can select multiple Approved Transfer Requirements between any two > given facilities to create Single Inventory Transfer between them. > * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers > would be created by consolidating all products/items requirements between any > two given locations. > * System would auto-assign the required quantity from existing > inventoryItems based on FIFO. > * Add a new *View Inventory Transfer* screen > ** From here user can manually override the auto-assigned InventoryItems > against each product. > ** User can Add/Edit/Delete the Transfer Items. > ** After assigning InventoryItems user can Approve the Inventory Transfer. > ** Upon Approval ATP would get reduced to the tune of assigned quantity from > each inventory item. > * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory > Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available > to pack. > * Upon completion of packing reduce the QOH from assigned inventory items to > the tune of packed quantity. > * After completing packing, shipment will be created in shipped status and > Inventory Transfer will be marked as 'SENT'. > * Once received at destination location the ATP/QOH would be increased up to > the transferred quantity per product and shipment will be marked as > 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. > > *To Be Business Process for Approach #1:* > *!InventoryTransferModelLevel1.png!* > > h2. *Design Approach #2:* > * Alter *InventoryTransfer* entity as header entity as follows: > ** Add primaryShipmentId > ** Remove inventoryItemId > > * Add new entity *InventoryTransferItem* > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** inventoryItemId > ** shipmentId > ** shipmentItemSeqId > ** quantity > ** unitPrice > Having InventoryItem detail at InventoryTransferItem level will help us to > manage multiple Items for same InventoryTransfer and each > InventoryTransferItem can be fulfilled via multiple Inventory items and/or > multiple Shipments. > * Create TransferItemBilling entity to support tax invoice > **
[jira] [Commented] (OFBIZ-9800) French translation of OFBiz website
[ https://issues.apache.org/jira/browse/OFBIZ-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454455#comment-16454455 ] Olivier Heintz commented on OFBIZ-9800: --- I will do a mail on Dev mailing-list to ask all French contributors and committers for tying to find at minima 3 peoples which accept to contribute to sync between EN et FR. If there are enough people, we will create a wiki page with the list to be able to ask them directly if a commit on website is not manage after 1 week. If the French version is just a perfect translation of the original content, it's very easy and not a long work to do sync or to translate new content. > French translation of OFBiz website > --- > > Key: OFBIZ-9800 > URL: https://issues.apache.org/jira/browse/OFBIZ-9800 > Project: OFBiz > Issue Type: Improvement > Components: site >Reporter: Olivier Heintz >Assignee: Deepak Dixit >Priority: Minor > Attachments: website-fr.tar, website-fr.tar, website-fr.tar.gz, > website-fr.tar.gz, website-fr.tar.gz, website-fr.tar.gz, website-fr.tar.gz > > > To evaluate the workload of translate all the ofbiz website page in french, > and so to maintain the translation when there are some modifications, I have > start to translate them. > There are between 10 and 15 page to translate, and translate one is between 1 > and 2 hours. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10371) Add a link onto a crashed Job to reset it
[ https://issues.apache.org/jira/browse/OFBIZ-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-10371. > Add a link onto a crashed Job to reset it > - > > Key: OFBIZ-10371 > URL: https://issues.apache.org/jira/browse/OFBIZ-10371 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10371.patch > > > When a job crash due to OFBiz interruption, there is no easy way to replan it. > Everything exists in the code base to do it, just adding a link onto crashed > job in webtools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-10371) Add a link onto a crashed Job to reset it
[ https://issues.apache.org/jira/browse/OFBIZ-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne resolved OFBIZ-10371. -- Resolution: Implemented Commited in trunk rev : 1830236 > Add a link onto a crashed Job to reset it > - > > Key: OFBIZ-10371 > URL: https://issues.apache.org/jira/browse/OFBIZ-10371 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10371.patch > > > When a job crash due to OFBiz interruption, there is no easy way to replan it. > Everything exists in the code base to do it, just adding a link onto crashed > job in webtools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10371) Add a link onto a crashed Job to reset it
[ https://issues.apache.org/jira/browse/OFBIZ-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne updated OFBIZ-10371: - Attachment: OFBIZ-10371.patch > Add a link onto a crashed Job to reset it > - > > Key: OFBIZ-10371 > URL: https://issues.apache.org/jira/browse/OFBIZ-10371 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10371.patch > > > When a job crash due to OFBiz interruption, there is no easy way to replan it. > Everything exists in the code base to do it, just adding a link onto crashed > job in webtools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10371) Add a link onto a crashed Job to reset it
Gil Portenseigne created OFBIZ-10371: Summary: Add a link onto a crashed Job to reset it Key: OFBIZ-10371 URL: https://issues.apache.org/jira/browse/OFBIZ-10371 Project: OFBiz Issue Type: Improvement Components: framework/webtools Affects Versions: Upcoming Branch Reporter: Gil Portenseigne Assignee: Gil Portenseigne Fix For: Upcoming Branch When a job crash due to OFBiz interruption, there is no easy way to replan it. Everything exists in the code base to do it, just adding a link onto crashed job in webtools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10245) File transfer management with communicationEvent and new contactMech FTP_ADDRESS
[
https://issues.apache.org/jira/browse/OFBIZ-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454341#comment-16454341
]
Gil Portenseigne commented on OFBIZ-10245:
--
Hi [~rishisolankii],
I finally found the time to progress on the subject, i made a review, and now
can provide a patch with a better quality implementation.
I'll commit it in few days if there is no bad or "ask to wait" feedback about
it :)
> File transfer management with communicationEvent and new contactMech
> FTP_ADDRESS
>
>
> Key: OFBIZ-10245
> URL: https://issues.apache.org/jira/browse/OFBIZ-10245
> Project: OFBiz
> Issue Type: Improvement
> Components: content, party
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
>Priority: Minor
> Attachments: OFBIZ-10245.patch
>
>
> This Jira introduce a new way to manage file transfer in OFBiz.
> Inspired by mailing communication event management, a new
> communicationEventTypeId is created ('FILE_TRANSFER_COMM').
> Such commEvent with classics :
> partyIdFrom/partyIdTo/contactMechIdTo/entryDate etc. are analysed by a job
> (like sendEmailDated), to send associated contents to a configured
> FTP/SFTP/FTPS server. If failure happens, it is catched and stored in
> communicationEvent, waiting for a new try.
> For this purpose :
> # A new contactMechTypeId is introduced (FtpAddress), with its corresponding
> table. This contactMech store needed information for basic user/password
> authentication (server url and protocol, port, username, password, etc.)
> # A new service sendFileTransferDated (wip) that will look for pending file
> transfer and call following service.
> # A new service sendCommEventAsFtp that take a selected commEvent, check its
> structure and manage its status after trying the associated content file
> transfers
> # A new service sendContentToFtp, that take a content and transfer it to a
> given FtpAddress
> # A seca createCommEventFromFtpTransfer on sendContentToFtp to manage plural
> content file transfer, creating children communicationEvent to follow each
> content transfer separately (only for several content transfers).
> # A new Interface FtpClientInterface, with the 3 implementations of FTP,
> FTPS (To be Done), SFTP clients to manage Ftp connection and transfer
> # A new property file to enable and manage redirection for testing purpose
> With this implementation, creating a communicationEvent, with a FtpAddress
> contactMechIdTo, and sendFileTransferDated job planned :
> * The file is transfered to the ftp : communication event status set to
> COM_COMPLETE
> * Error occured : communication event status set to COM_BOUNCED with error
> message on communicationEvent note
> The POC is working nicely for our customer, i adapted and tested it on trunk
> here :
> https://labs.nereide.fr/10031/Communautaire/compare/trunk...SendCommEventToFtp
> (some more job to be done, but in a working state)
> I can provide the current patch on demand but i will propose more polished
> work in some days.
> Looking forward reading you !
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10245) File transfer management with communicationEvent and new contactMech FTP_ADDRESS
[
https://issues.apache.org/jira/browse/OFBIZ-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne updated OFBIZ-10245:
-
Attachment: OFBIZ-10245.patch
> File transfer management with communicationEvent and new contactMech
> FTP_ADDRESS
>
>
> Key: OFBIZ-10245
> URL: https://issues.apache.org/jira/browse/OFBIZ-10245
> Project: OFBiz
> Issue Type: Improvement
> Components: content, party
>Reporter: Gil Portenseigne
>Assignee: Gil Portenseigne
>Priority: Minor
> Attachments: OFBIZ-10245.patch
>
>
> This Jira introduce a new way to manage file transfer in OFBiz.
> Inspired by mailing communication event management, a new
> communicationEventTypeId is created ('FILE_TRANSFER_COMM').
> Such commEvent with classics :
> partyIdFrom/partyIdTo/contactMechIdTo/entryDate etc. are analysed by a job
> (like sendEmailDated), to send associated contents to a configured
> FTP/SFTP/FTPS server. If failure happens, it is catched and stored in
> communicationEvent, waiting for a new try.
> For this purpose :
> # A new contactMechTypeId is introduced (FtpAddress), with its corresponding
> table. This contactMech store needed information for basic user/password
> authentication (server url and protocol, port, username, password, etc.)
> # A new service sendFileTransferDated (wip) that will look for pending file
> transfer and call following service.
> # A new service sendCommEventAsFtp that take a selected commEvent, check its
> structure and manage its status after trying the associated content file
> transfers
> # A new service sendContentToFtp, that take a content and transfer it to a
> given FtpAddress
> # A seca createCommEventFromFtpTransfer on sendContentToFtp to manage plural
> content file transfer, creating children communicationEvent to follow each
> content transfer separately (only for several content transfers).
> # A new Interface FtpClientInterface, with the 3 implementations of FTP,
> FTPS (To be Done), SFTP clients to manage Ftp connection and transfer
> # A new property file to enable and manage redirection for testing purpose
> With this implementation, creating a communicationEvent, with a FtpAddress
> contactMechIdTo, and sendFileTransferDated job planned :
> * The file is transfered to the ftp : communication event status set to
> COM_COMPLETE
> * Error occured : communication event status set to COM_BOUNCED with error
> message on communicationEvent note
> The POC is working nicely for our customer, i adapted and tested it on trunk
> here :
> https://labs.nereide.fr/10031/Communautaire/compare/trunk...SendCommEventToFtp
> (some more job to be done, but in a working state)
> I can provide the current patch on demand but i will propose more polished
> work in some days.
> Looking forward reading you !
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454203#comment-16454203 ] Rishi Solanki commented on OFBIZ-10365: --- [~pawan.verma]: Thanks for the detailed design. I'm up for the approach #1 or #2 with following suggestion/concern; - I'm not able to think of any use of fromDate and thruDate in RequirementInventoryTransfer entity design. If not required then can we remove them? - In TransferItemBilling from where the shipmentReceiptId value come. Could you please help me to understand. Thanks for explaining the design approaches in person. > Document design approaches for Inventory Transfer > -- > > Key: OFBIZ-10365 > URL: https://issues.apache.org/jira/browse/OFBIZ-10365 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Pawan Verma >Priority: Minor > Attachments: InventoryTransferModelLevel1.png, > OrderModelActivityLevel1.png > > > h2. *Design Approach #1:* > * Create Header entity *InventoryTransferHeader (ITH)* > ** inventoryTransferId* > ** statusId > ** facilityId > ** locationSeqId > ** facilityIdTo > ** locationSeqIdTo > ** primaryShipmentId > > * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so > as to support item level details as follows: > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** inventoryItemId* > ** shipmentId > ** shipmentItemSeqId > ** quantity > ** unitPrice > > Having InventoryItem detail at InventoryTransferItem level will help us to > manage multiple Items under same InventoryTransfer and each > InventoryTransferItem can be fulfilled via multiple Inventory items and/or > multiple Shipments. > > * Create *TransferItemBilling* entity to support invoicing (if needed) > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** invoiceId* > ** invoiceItemSeqId* > ** itemIssuanceId > ** shipmentReceiptId > ** quantity > ** Amount > * Create *InventoryTransferContanctMech* entity to support InventoryTransfer > Contact Mechanism > ** inventoryTransferId* > ** contactMechPurposeTypeId* > ** contactMechId* > * Create *RequirementInventoryTransfer* entity > ** requirementId* > ** inventoryTransferId* > ** fromDate* > ** thruDate > * Refactor existing *InventoryItemDetail* entity > ** inventoryTransferId* > *Screenflow for Approach #1:* > * Add a new *Find Transfer Requirements* screen. > ** Transfer Requirements can be searched with following parameters: > *** Requirement ID > *** Status ID > *** Shipment ID > *** Origin Facility ID > *** Destination Facility ID > *** Product ID > *** Description > *** Requirement Start Date > *** Required By Date > > * Option for creating Inventory Transfer for Un-approved requirements will > be disabled. > * User can select multiple Approved Transfer Requirements between any two > given facilities to create Single Inventory Transfer between them. > * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers > would be created by consolidating all products/items requirements between any > two given locations. > * System would auto-assign the required quantity from existing > inventoryItems based on FIFO. > * Add a new *View Inventory Transfer* screen > ** From here user can manually override the auto-assigned InventoryItems > against each product. > ** User can Add/Edit/Delete the Transfer Items. > ** After assigning InventoryItems user can Approve the Inventory Transfer. > ** Upon Approval ATP would get reduced to the tune of assigned quantity from > each inventory item. > * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory > Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available > to pack. > * Upon completion of packing reduce the QOH from assigned inventory items to > the tune of packed quantity. > * After completing packing, shipment will be created in shipped status and > Inventory Transfer will be marked as 'SENT'. > * Once received at destination location the ATP/QOH would be increased up to > the transferred quantity per product and shipment will be marked as > 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. > > *To Be Business Process for Approach #1:* > *!InventoryTransferModelLevel1.png!* > > h2. *Design Approach #2:* > * Alter *InventoryTransfer* entity as header entity as follows: > ** Add primaryShipmentId > ** Remove inventoryItemId > > * Add new entity *InventoryTransferItem* > ** inventoryTransferId* > ** InvtransferItemSeqId* > ** inventoryItemId* > ** shipmentId > ** shipmentItemSeqId > ** quantity > ** unitPrice > Having InventoryItem detail at InventoryTransferItem
[jira] [Commented] (OFBIZ-10369) ConfigXMLReader - Events are not executed in the order defined
[
https://issues.apache.org/jira/browse/OFBIZ-10369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453857#comment-16453857
]
Rishi Solanki commented on OFBIZ-10369:
---
+1
> ConfigXMLReader - Events are not executed in the order defined
> --
>
> Key: OFBIZ-10369
> URL: https://issues.apache.org/jira/browse/OFBIZ-10369
> Project: OFBiz
> Issue Type: Bug
> Components: ALL APPLICATIONS
>Affects Versions: Release Branch 16.11
>Reporter: Vikas Mayur
>Priority: Major
>
> The events contained in the controller configuration for first-visit,
> pre-post processor and before-after login are executed in arbitrary order
> rather than the defined order. This results in unexpected results.
> For example,
> {code}
>
> path="org.apache.ofbiz.order.shoppingcart.ShoppingCartEvents"
> invoke="keepCartUpdated"/>
> path="org.apache.ofbiz.order.shoppinglist.ShoppingListEvents"
> invoke="restoreAutoSaveList"/>
> path="org.apache.ofbiz.order.shoppinglist.ShoppingListEvents"
> invoke="saveCartToAutoSaveList"/>
>
> {code}
> While debugging I have found that the event 'restoreAutoSaveList' run before
> 'keepCartUpdated'. I would expect the events to run from top (first) to
> bottom (last).
>
> I am unable to attach a patch but below are the changes to fix the issue. I
> have tested the issue on release 16 and it may be an issue in trunk.
> {code}
> Index:
> framework/webapp/src/main/java/org/apache/ofbiz/webapp/control/ConfigXMLReader.java
> ===
> ---
> framework/webapp/src/main/java/org/apache/ofbiz/webapp/control/ConfigXMLReader.java
> (revision 1830130)
> +++
> framework/webapp/src/main/java/org/apache/ofbiz/webapp/control/ConfigXMLReader.java
> (working copy)
> @@ -25,6 +25,7 @@
> import java.util.ArrayList;
> import java.util.HashMap;
> import java.util.HashSet;
> +import java.util.LinkedHashMap;
> import java.util.LinkedList;
> import java.util.List;
> import java.util.Map;
> @@ -182,11 +183,11 @@
> private String defaultRequest;
> private String statusCode;
> private List includes = new ArrayList();
> - private Map firstVisitEventList = new HashMap Event>();
> - private Map preprocessorEventList = new
> HashMap();
> - private Map postprocessorEventList = new
> HashMap();
> - private Map afterLoginEventList = new HashMap Event>();
> - private Map beforeLogoutEventList = new
> HashMap();
> + private Map firstVisitEventList = new
> LinkedHashMap();
> + private Map preprocessorEventList = new
> LinkedHashMap();
> + private Map postprocessorEventList = new
> LinkedHashMap();
> + private Map afterLoginEventList = new
> LinkedHashMap();
> + private Map beforeLogoutEventList = new
> LinkedHashMap();
> private Map eventHandlerMap = new HashMap String>();
> private Map viewHandlerMap = new HashMap String>();
> private Map requestMapMap = new HashMap RequestMap>();
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-10365: Description: h2. *Design Approach #1:* * Create Header entity *InventoryTransferHeader (ITH)* ** inventoryTransferId* ** statusId ** facilityId ** locationSeqId ** facilityIdTo ** locationSeqIdTo ** primaryShipmentId * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so as to support item level details as follows: ** inventoryTransferId* ** InvtransferItemSeqId* ** inventoryItemId* ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items under same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create *TransferItemBilling* entity to support invoicing (if needed) ** inventoryTransferId* ** InvtransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** Amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* ** fromDate* ** thruDate * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId* *Screenflow for Approach #1:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements will be disabled. * User can select multiple Approved Transfer Requirements between any two given facilities to create Single Inventory Transfer between them. * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers would be created by consolidating all products/items requirements between any two given locations. * System would auto-assign the required quantity from existing inventoryItems based on FIFO. * Add a new *View Inventory Transfer* screen ** From here user can manually override the auto-assigned InventoryItems against each product. ** User can Add/Edit/Delete the Transfer Items. ** After assigning InventoryItems user can Approve the Inventory Transfer. ** Upon Approval ATP would get reduced to the tune of assigned quantity from each inventory item. * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available to pack. * Upon completion of packing reduce the QOH from assigned inventory items to the tune of packed quantity. * After completing packing, shipment will be created in shipped status and Inventory Transfer will be marked as 'SENT'. * Once received at destination location the ATP/QOH would be increased up to the transferred quantity per product and shipment will be marked as 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. *To Be Business Process for Approach #1:* *!InventoryTransferModelLevel1.png!* h2. *Design Approach #2:* * Alter *InventoryTransfer* entity as header entity as follows: ** Add primaryShipmentId ** Remove inventoryItemId * Add new entity *InventoryTransferItem* ** inventoryTransferId* ** InvtransferItemSeqId* ** inventoryItemId* ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items for same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create TransferItemBilling entity to support tax invoice ** inventoryTransferId* ** InvtransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* ** fromDate* ** thruDate * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId* *Screenflow for Approach #2:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements
[jira] [Commented] (OFBIZ-10340) Changing visual them from product store overrides context parameter
[ https://issues.apache.org/jira/browse/OFBIZ-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453782#comment-16453782 ] Leila Mekika commented on OFBIZ-10340: -- Hello [~suraj.khurana], it seems to be because Lookup display override session attribute _LAST_VIEW_NAME_. Request selectTheme is then trying to redirect to LookupPartyName > Changing visual them from product store overrides context parameter > --- > > Key: OFBIZ-10340 > URL: https://issues.apache.org/jira/browse/OFBIZ-10340 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Upcoming Branch >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > > Steps to regenerate: > Go to product store detail page from catalog menu. > Change visual theme and press Update. > Due to change in visual theme of ecommerce, context parameter gets updated > and page renders with no theme. > Context parameter should not gets override and Updating visual them should > result in proper detail page as required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10370) Migrate promotion condition and action rule
Nicolas Malin created OFBIZ-10370:
-
Summary: Migrate promotion condition and action rule
Key: OFBIZ-10370
URL: https://issues.apache.org/jira/browse/OFBIZ-10370
Project: OFBiz
Issue Type: Improvement
Components: product
Affects Versions: Trunk
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Currently promotion rule engine works with :
* entities ProductPromoCond et ProductPromoAction
* java linear function ProductPromoWorker.checkCondition()
(ProductPromoWorker:910) and ProductPromoWorker.performAction
(ProductPromoWorker:1423)
* Enumeration list to indicate on java function what piece of code to activate
the control or action
The problem with this structure is when you want to create a new case of
condition or action, you need to modify the framework code base.
We propose an other way with convert the 2 big java leaner function to service
representation with one service by case.
To realize it we introduce a relation with CustomMethod :
ProductPromoRule --> ProductPromoCond -> CustomMethod
\-> ProductPromoAction -> CustomMethod
Each functions's case are converted to service with a related CustomMethod.
With this pattern now you can write your own condition rule and action rule on
your plugin and link it on the promo engine
When it's possible we associate a unit test to the service
For backware compatibility current enumeration receive on enumCode the
customMethodId to ensure that old data work fine with the new engine
{code}
{code}
{code}
//for backware compatibility resolve customMethodId from enumCode
GenericValue condEnum =
EntityQuery.use(delegator).from("Enumeration").where("enumId",
inputParamEnumId).cache().queryOne();
if (condEnum != null) {
customMethod =
EntityQuery.use(delegator).from("CustomMethod").where("customMethodId",
condEnum.get("enumCode")).cache().queryOne();
serviceName = customMethod.getString("customMethodName");
}
{code}
Related dev [discussion
|https://lists.apache.org/thread.html/47730b60c9d1bab875e77577c2b4f16b99ede6dcdf68030f5cfc1203@%3Cdev.ofbiz.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453723#comment-16453723 ] Leila Mekika commented on OFBIZ-7741: - Hello [~pfm.smits], I tried to reproduce in a recent trunk and didn't encounter the problem. I tested it with DemoEmployee1 and DemoEmployee3 who can only see their project Do you always encounter the problem ? And if yes, can you give us details (user, etc) so that we can reproduce ? Thanks > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Reporter: Pierre Smits >Priority: Critical > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-7357) OFBIZ-6964: Prepare Demo Data based on the propsed design to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453677#comment-16453677 ] Pawan Verma edited comment on OFBIZ-7357 at 4/26/18 8:45 AM: - Attaching updated patch for the demo data for implementation and testing purpose based on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356. Please review the attached patch and let me know your feedback about this implementation. was (Author: pawan.verma): Attaching updated patch for the demo data for implementation and testing purpose based on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356. > OFBIZ-6964: Prepare Demo Data based on the propsed design to support > replenishment planning through any inter-company facility > -- > > Key: OFBIZ-7357 > URL: https://issues.apache.org/jira/browse/OFBIZ-7357 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Affects Versions: 15.12.01 >Reporter: Swapnil Shah >Assignee: Pawan Verma >Priority: Major > Fix For: 17.12.01 > > Attachments: OFBIZ-7357.patch, OFBIZ-7357.patch > > > We can start preparing demo data for implementation and testing purpose based > on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453697#comment-16453697 ] Pawan Verma edited comment on OFBIZ-9506 at 4/26/18 8:44 AM: - Attaching modified patch for this task. A new wrapper service is written to support facility Group functionality this can be run via webtools or scheduled services. Discussion about facility group is initiated by following [mail|https://markmail.org/message/7scklhrbdwhedea3] thread. Please review the attached patch and let me know your feedback about this implementation. was (Author: pawan.verma): Attaching modified patch for this task. A new wrapper service is written to support facility Group functionality this can be run via webtools or scheduled services. Discussion about facility group is initiated at following [mail|https://markmail.org/message/7scklhrbdwhedea3] thread. > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Pawan Verma >Priority: Major > Attachments: OFBIZ-9506.patch, OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9506) OFBIZ-6964: Implementation to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-9506: --- Attachment: OFBIZ-9506.patch > OFBIZ-6964: Implementation to support replenishment planning through any > inter-company facility > --- > > Key: OFBIZ-9506 > URL: https://issues.apache.org/jira/browse/OFBIZ-9506 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Reporter: Swapnil M Mane >Assignee: Yashwant Dhakad >Priority: Major > Attachments: OFBIZ-9506.patch, OFBIZ-9506.patch > > > For support of replenishment planning through any inter-company facility, > This task is for the code implementation on the basis of design/information > shared in the ticket https://issues.apache.org/jira/browse/OFBIZ-7356. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7357) OFBIZ-6964: Prepare Demo Data based on the propsed design to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453677#comment-16453677 ] Pawan Verma commented on OFBIZ-7357: Attaching updated patch for the demo data for implementation and testing purpose based on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356. > OFBIZ-6964: Prepare Demo Data based on the propsed design to support > replenishment planning through any inter-company facility > -- > > Key: OFBIZ-7357 > URL: https://issues.apache.org/jira/browse/OFBIZ-7357 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Affects Versions: 15.12.01 >Reporter: Swapnil Shah >Assignee: Pawan Verma >Priority: Major > Fix For: 17.12.01 > > Attachments: OFBIZ-7357.patch, OFBIZ-7357.patch > > > We can start preparing demo data for implementation and testing purpose based > on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7357) OFBIZ-6964: Prepare Demo Data based on the propsed design to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-7357: --- Attachment: OFBIZ-7357.patch > OFBIZ-6964: Prepare Demo Data based on the propsed design to support > replenishment planning through any inter-company facility > -- > > Key: OFBIZ-7357 > URL: https://issues.apache.org/jira/browse/OFBIZ-7357 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Affects Versions: 15.12.01 >Reporter: Swapnil Shah >Assignee: Pawan Verma >Priority: Major > Fix For: 17.12.01 > > Attachments: OFBIZ-7357.patch, OFBIZ-7357.patch > > > We can start preparing demo data for implementation and testing purpose based > on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7357) OFBIZ-6964: Prepare Demo Data based on the propsed design to support replenishment planning through any inter-company facility
[ https://issues.apache.org/jira/browse/OFBIZ-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma reassigned OFBIZ-7357: -- Assignee: Pawan Verma (was: Swapnil M Mane) > OFBIZ-6964: Prepare Demo Data based on the propsed design to support > replenishment planning through any inter-company facility > -- > > Key: OFBIZ-7357 > URL: https://issues.apache.org/jira/browse/OFBIZ-7357 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing, order, product >Affects Versions: 15.12.01 >Reporter: Swapnil Shah >Assignee: Pawan Verma >Priority: Major > Fix For: 17.12.01 > > Attachments: OFBIZ-7357.patch > > > We can start preparing demo data for implementation and testing purpose based > on requirement and design details shared over OFBIZ-7355 & OFBIZ-7356 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
