Change the type of relation for Postal Address to GeoPoint from one to many. Because of the elevation field in GeoPoint. A bit scifi for now, but maybe useful one day...)
Thanks to a discussion with Erwan "Relation title not needed on Facility entity" at https://issues.apache.org/jira/browse/OFBIZ-3153 - OFBIZ-3153
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@833113 13f79535-47bb-0310-9956-ffa450edef68
The work flow is based on following steps:
1) If for a return both finAccountId and billingAccountId are supplied, then preference goes to the setting on Product Store. A warning message is shown so that the
user know which account is used.
2) If a finAcccountId is supplied then first billing account with -ve amount are searched and if it is found then amount is credit to the billing account else it goes to
financial account.
3) If a billingAccountId is supplied then it is used to credit the refund amount.
4) If none of them is supplied, then preference again goes to the setting on Product Store.
Patch applied from Mridul Pathak, part of OFBIZ-2502 (https://issues.apache.org/jira/browse/OFBIZ-2502)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@781804 13f79535-47bb-0310-9956-ffa450edef68
1) Moved the view entity to correct package.
2) Changed the view name as well as the entities used. Now the records are coming as expected.
3) Corresponding changes in the findOrdersToPickMove service.
The main purpose of this view entity is to find out the location (areaId) of the inventory item that is reserved/picked for a particular order. For example if an order has two
order items X and Y and items X is picked from area A and item Y is picked from area B of a facility (where obviously area A and B are associated to a pick/primary location),
then while grouping this order in facility > picking screen by "Group by Warehouse Area" method will show order under Multi Locations group. To clarify more on this grouping
method, grouping is done only with the areaId and the locationSeqId (which is a combination of areaId, aisleId, sectionId, levelId, positionId).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@779041 13f79535-47bb-0310-9956-ffa450edef68
ProductStore. A new field lastInventoryCount on ProductFacility is also added and it is a mirror of availableToPromiseTotal of a product at a certain point of time and is
being updated every hour by a schedule service to reflect the current value of inventory count in the system.
If showOutOfStockProducts is equals to N and for a particular product lastInventoryCount is <= zero, then this particular product will not be shown on the site. If the inventory
count becomes +ve again then the product will be again available on the site, in minimum one hour time but could possibly take long depending on the inventory levels.
Patch from Ratnesh Upadhyay, part of OFBIZ-2480 (https://issues.apache.org/jira/browse/OFBIZ-2480).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@778451 13f79535-47bb-0310-9956-ffa450edef68
Product entity to Y/N where Y means item is out of stock and N means item is in stock. This process will be efficient in a way that the database interaction to check
whether item is out of stock will not take place everytime products are loaded on the ecommerce site.
Applied my patch (initially contributed by Amit Sharma, I have done some improvements over this patch), part of OFBIZ-2480 (https://issues.apache.org/jira/browse/OFBIZ-2480)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@777498 13f79535-47bb-0310-9956-ffa450edef68
[ \t]+$ => "" (empty)
Should be easier to review when committing changes with trailing spaces removed automatically by anyedit or such tool (please refer to http://docs.ofbiz.org/x/mg)
Of course this effort to remove trailing spaces has no functional implications.
Actually, I was doing a 1st commit and as it's long to upload, I got conflicts with r763135
In the meantime I did some refactoring also in *.java and *.groovy files :
){ => ) {
if( => if (
while( => while (
}else => } else
else{ => else {
switch( => switch (
try{ => try {
}catch => } catch
catch( => catch (
}finally{ => } finally {
So these changes are also in this commit, should not be a problem anyway.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@763175 13f79535-47bb-0310-9956-ffa450edef68
The ProductStore entity has now a visualThemeId that selects the VisualTheme to be used in the Ecommerce.
This can be set in the EditProductStore form selecting a theme between the themes that belong to the "ECOMMERCE" VisualThemeSet
To the following ProductStore fields has been applied the entity deprecation pattern:
<field name="oldStyleSheet" col-name="STYLE_SHEET" type="url"></field>
<field name="oldHeaderLogo" col-name="HEADER_LOGO" type="url"></field>
<field name="oldHeaderMiddleBackground" col-name="HEADER_MIDDLE_BACKGROUND" type="url"></field>
<field name="oldHeaderRightBackground" col-name="HEADER_RIGHT_BACKGROUND" type="url"></field>
The first part of the ecommerce header.ftl (the part defining the <HEAD> tag content) has been moved to a new headerHead.ftl file. This allows all the theme defined header.ftl to include this common part that is mainly inclusion of theme defined resources and should never change (code reuse).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@746544 13f79535-47bb-0310-9956-ffa450edef68
I simply added a dynamic directories creation. This patch works but maybe we could use and API for better result (see Jira issue)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@739042 13f79535-47bb-0310-9956-ffa450edef68
Added support for migrating FacilityRole to FacilityParty.
Thanks Surya Kusumakar for your contribution.
Special thanks to Mr. Pranay Pandey for his support :-).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@698159 13f79535-47bb-0310-9956-ffa450edef68
But I quickly realized, as David explained, that "We can't document every little thing".
The best in such case is simply to use he relations view in entity maintenance feature in Webtools to see which fields relate with which entities
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@686636 13f79535-47bb-0310-9956-ffa450edef68
Added a new entity ConfigOptionProductOption to store selected variant products per configuration.
Moved a code snippet about products with VV_FEATURETREE from ShoppingCartEvents to ProductWorker.
Added a demo product PIZZA to test demonstrate Configurable products with Virtual product options.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@685807 13f79535-47bb-0310-9956-ffa450edef68
I added a CommonEntityChildren UI label to CommonUiLabels.xml because a number of components implement parent->child relationships and they all have their own "Children" UI label. This will help reduce UI label redundancy. I'll make the change in the other components in another commit.
Internationalization note: this commit contains new UI labels.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@680016 13f79535-47bb-0310-9956-ffa450edef68