Clone
 

pawan verma <pawan.verma@hotwaxsystems.com> in ofbiz-framework

Fixed: Issue in which Agreement Item can't be removed from Agreement (OFBIZ-11410)

Reason for the issue was incorrect use of service IN parameters for entity-auto delete invoke.

Thanks, Pierre Smits for the report.

Fixed: Issue in which Agreement Item can't be removed from Agreement (OFBIZ-11410)

Reason for the issue was incorrect use of service IN parameters for entity-auto delete invoke.

Thanks, Pierre Smits for the report.

Fixed: Issue in which Agreement Item can't be removed from Agreement (OFBIZ-11410)

Reason for the issue was incorrect use of service IN parameters for entity-auto delete invoke.

Thanks, Pierre Smits for the report.

Fixed: Error showing on Allocation Plan screen (OFBIZ-11338)

Thanks: Yashwant Dhakad for the report and Aman Mishra for the patch.

Improved: Enhance the Programmable Export feature for EntityQuery support (OFBIZ-11158)

EntityQuery usage to perform data fetching is increasing, we should also add support for EntityQuery in ProgramExport feature.

Thanks: Devanshu Vyas for report and patch and Suraj Khurana, Nicolas Malin for the review.

Revert "Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail for CommunicationEvent.subject field" (OFBIZ-10879)

This reverts commit 9706acf064e26c291c0bd10081df8286ae6b359b.

Revert "Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail for CommunicationEvent.subject field" (OFBIZ-10879)

This reverts commit bbcc4692dccdf573aa0205f927b56bc271719031.

Revert "Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail for CommunicationEvent.subject field" (OFBIZ-10879)

This reverts commit 832076ce91dbca182ffab38d27ea72ca5e2cb0be.

Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail for CommunicationEvent.subject field (OFBIZ-10879)

CommunicationEventServices#updateCommEventAfterEmail could generate wrong result. If general.properties value 'mail.notifications.redirectTo' is used, it is possible that the subject string has more than 255 character.

Thanks, Ulrich Heidfeld for your contribution.

Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail for CommunicationEvent.subject field (OFBIZ-10879)

CommunicationEventServices#updateCommEventAfterEmail could generate wrong result. If general.properties value 'mail.notifications.redirectTo' is used, it is possible that the subject string has more than 255 character.

Thanks, Ulrich Heidfeld for your contribution.

Fixed: Potensial bug under CommunicationEventServices#updateCommEventAfterEmail for CommunicationEvent.subject field (OFBIZ-10879)

CommunicationEventServices#updateCommEventAfterEmail could generate wrong result. If general.properties value 'mail.notifications.redirectTo' is used, it is possible that the subject string has more than 255 character.

Thanks, Ulrich Heidfeld for your contribution.

Fixed: Same content uploaded twice, if refresh the page after uploading the content (OFBIZ-11171)

Thanks, Humera Khan and Shubham Goswami for your contribution.

Fixed: Same content uploaded twice, if refresh the page after uploading the content (OFBIZ-11171)

Thanks, Humera Khan and Shubham Goswami for your contribution.

Fixed: Same content uploaded twice, if refresh the page after uploading the content (OFBIZ-11171)

Thanks, Humera Khan and Shubham Goswami for your contribution.

Fixed: Order Status History section broken for anonymous order (OFBIZ-11231)

Reason for the issue: Anonymous orders doen't have associated User login record, so shown statusUserLogin in that case.

Fixed: Order Status History section broken for anonymous order (OFBIZ-11231)

Reason for the issue: Anonymous orders doen't have associated User login record, so shown statusUserLogin in that case.

Fixed: Order Status History section broken for anonymous order (OFBIZ-11231)

Reason for the issue: Anonymous orders doen't have associated User login record, so shown statusUserLogin in that case.

Fixed: updatePassword does not save optional parameter requirePasswordChange (OFBIZ-11320)

When changing the password of a User Login through the Party Manager the Require Password Change dropdown menu selection does not save the selected value. The corresponding process is missing from the LoginMapProcs.xml.

Thanks: Ingo Könemann for your contribution.

Fixed: updatePassword does not save optional parameter requirePasswordChange (OFBIZ-11320)

When changing the password of a User Login through the Party Manager the Require Password Change dropdown menu selection does not save the selected value. The corresponding process is missing from the LoginMapProcs.xml.

Thanks: Ingo Könemann for your contribution.

Fixed: updatePassword does not save optional parameter requirePasswordChange (OFBIZ-11320)

When changing the password of a User Login through the Party Manager the Require Password Change dropdown menu selection does not save the selected value. The corresponding process is missing from the LoginMapProcs.xml.

Thanks: Ingo Könemann for your contribution.

Fixed: Add button for 'Gift Message is shown on completed order (OFBIZ-11160)

Thanks: Pierre Smits for report and Shivanand Chhatre for the fix.

Fixed: Add button for 'Gift Message is shown on completed order (OFBIZ-11160)

Thanks: Pierre Smits for report and Shivanand Chhatre for the fix.

Fixed: Add button for 'Gift Message is shown on completed order (OFBIZ-11160)

Thanks: Pierre Smits for report and Shivanand Chhatre for the fix.

Fixed: liniting issues introduced by commit d00208c (OFBIZ-10585)

Thanks: Mathieu Lirzin for report

Fixed: liniting issues introduced by commit d00208c (OFBIZ-10585)

Thanks: Mathieu Lirzin for report

Fixed: liniting issues introduced by commit d00208c (OFBIZ-10585)

Thanks: Mathieu Lirzin for report

Fixed: Corrected variable name. Nothing functional. (OFBIZ-10585)

Fixed: Production run not created for marketing package auto type product if component inventory is not available (OFBIZ-10585)

When we create an order for marketing package auto, the system checks the component inventory and if found then it creates the production run job and produce marketing package inventory, but if component quantity not available then it does not create the job. So if we don't have an inventory item of component then production run should be created with created status.

Thanks: Yashwant Dhakad for report and Ankush Upadhyay for the patch.

Fixed: Production run not created for marketing package auto type product if component inventory is not available (OFBIZ-10585)

When we create an order for marketing package auto, the system checks the component inventory and if found then it creates the production run job and produce marketing package inventory, but if component quantity not available then it does not create the job. So if we don't have an inventory item of component then production run should be created with created status.

Thanks: Yashwant Dhakad for report and Ankush Upadhyay for the patch.

Fixed: Production run not created for marketing package auto type product if component inventory is not available (OFBIZ-10585)

When we create an order for marketing package auto, the system checks the component inventory and if found then it creates the production run job and produce marketing package inventory, but if component quantity not available then it does not create the job. So if we don't have an inventory item of component then production run should be created with created status.

Thanks: Yashwant Dhakad for report and Ankush Upadhyay for the patch.