Re: Updates to EntityQuery

[Pritam Kute]

Hello Gareth,

Looks like a nice addition to EntityQuery API. Thanks for that. As
mentioned by Arun, please provide more details to understand about
"forUpdate" and "forEach" methods.

Regards
--
Pritam Kute

On Wed, Oct 25, 2017 at 10:18 AM, Arun Patidar <
arun.pati...@hotwaxsystems.com> wrote:

> Hello Gareth,
>
> Please provide some more details or patch to understand  - forUpdate
> and forEach
> method utility.
>
> getFieldMap method looks good to me.
>
>
>
> --
> Thanks & Regards
> ---
> Arun Patidar
> Manager, Enterprise Software Development
>
> HotWax Systems Pvt Ltd.
>
> www.hotwaxsystems.com
>
>
> On Tue, Oct 24, 2017 at 9:06 PM, Gareth Carter <
> gareth.car...@stannah.co.uk>
> wrote:
>
> > Hi all
> >
> > We have internally patched EntityQuery with some additional functionality
> > and before I create a Jira was going to see what the community thinks.
> >
> > New functionality:
> >
> > -   New method getFieldMap which returns a Map object of selected
> > fields from GenericValue objects, useful for creating cache map objects
> for
> > lookup
> >
> > -   Support forUpdate
> >
> > -   forEach method to accept Consumer
> >
> > We have found these useful and believe the project can benefit, let me
> > know what you think
> >
> > Regards
> >
> > Gareth Carter
> >
> >
> > Software Development Analyst
> >
> >
> > Stannah Management Services Ltd
> >
> >
> > IT Department
> >
> >
> > Ext:
> >
> >
> > 7036
> >
> >
> > DDI:
> >
> >
> > 01264 364311
> >
> >
> >
> >
> > [http://logos.stannah.co.uk/stan150.jpg]
> >
> >
> > [http://logos.stannah.co.uk/enviro.jpg]Please consider the environment
> > before printing this email.
> >
> >
> >
> > This email is intended only for the above addressee. It may contain
> > privileged information. If you are not the addressee you must not copy,
> > distribute, disclose or use any of the information in it. If you have
> > received it in error, please delete it and notify the sender.
> >
> > Stannah Lift Holdings Ltd registered No. 686996, Stannah Management
> > Services Ltd registered No. 2483693, Stannah Lift Services Ltd registered
> > No. 1189799, Stannah Microlifts Ltd registered No. 964804, Stannah Lifts
> > Ltd registered No. 1189836, Stannah Stairlifts Ltd registered No.
> 1401451,
> > Global Upholstery Solutions Ltd registered No. 02452728.
> >
> > All registered offices at Watt Close, East Portway, Andover, Hampshire,
> > SP10 3SD, England.
> >
> > All Registered in England and Wales.
> >
> > This message has been scanned for malware by Websense. www.websense.com
> >
>

Re: Updates to EntityQuery

[Arun Patidar]

Hello Gareth,

Please provide some more details or patch to understand  - forUpdate
and forEach
method utility.

getFieldMap method looks good to me.



-- 
Thanks & Regards
---
Arun Patidar
Manager, Enterprise Software Development

HotWax Systems Pvt Ltd.

www.hotwaxsystems.com


On Tue, Oct 24, 2017 at 9:06 PM, Gareth Carter 
wrote:

> Hi all
>
> We have internally patched EntityQuery with some additional functionality
> and before I create a Jira was going to see what the community thinks.
>
> New functionality:
>
> -   New method getFieldMap which returns a Map object of selected
> fields from GenericValue objects, useful for creating cache map objects for
> lookup
>
> -   Support forUpdate
>
> -   forEach method to accept Consumer
>
> We have found these useful and believe the project can benefit, let me
> know what you think
>
> Regards
>
> Gareth Carter
>
>
> Software Development Analyst
>
>
> Stannah Management Services Ltd
>
>
> IT Department
>
>
> Ext:
>
>
> 7036
>
>
> DDI:
>
>
> 01264 364311
>
>
>
>
> [http://logos.stannah.co.uk/stan150.jpg]
>
>
> [http://logos.stannah.co.uk/enviro.jpg]Please consider the environment
> before printing this email.
>
>
>
> This email is intended only for the above addressee. It may contain
> privileged information. If you are not the addressee you must not copy,
> distribute, disclose or use any of the information in it. If you have
> received it in error, please delete it and notify the sender.
>
> Stannah Lift Holdings Ltd registered No. 686996, Stannah Management
> Services Ltd registered No. 2483693, Stannah Lift Services Ltd registered
> No. 1189799, Stannah Microlifts Ltd registered No. 964804, Stannah Lifts
> Ltd registered No. 1189836, Stannah Stairlifts Ltd registered No. 1401451,
> Global Upholstery Solutions Ltd registered No. 02452728.
>
> All registered offices at Watt Close, East Portway, Andover, Hampshire,
> SP10 3SD, England.
>
> All Registered in England and Wales.
>
> This message has been scanned for malware by Websense. www.websense.com
>

RE: RE: RE: Quantity missing for inventory transfer records

[Swapnil Shah]

Let's keep in mind that in reality it's the same single shipment that needs
to change hands between source and destination facility as a part of single
operational system. If we are willing to take Order model route, then is it
possible that we introduce a new order type 'Replenishment Order (RO)' or
'Transfer Order' along with new Shipment Type ‘Transfer Shipment’. And
allow to have these ROs processed through this single transfer shipment.
What it would mean is that:

   1. Create RO with Shipping Facility (i.e. originating
   DC/Warehouse/Store) and Receiving Facility (i.e. destination
   DC/Warehouse/Store). Possibly with same ‘Bill/Ship From Vendor’ and
   ‘Bill/Ship to Customer’ party id (as long as both originating and
   destination facilities are owned by same registered company or business
   entity).
   2. Allow to selectively reserve Inventory Items against RO items (even
   if it means overriding existing reservations).
   3. Allow warehouse/facility to group all common destination RO in a
   single ‘Transfer Shipment’ during picking.
   4. Once shipment is packed/shipped from originating facility then move
   its status to ‘Shipped’. At the same time linked RO’s status can also be
   marked as ‘Shipped’. This should affect the on Hand to the tune of shipped
   units.
   5. Generate only a separate Tax Invoice (if applicable) against linked
   RO.
   6. Allow Destination Facility to ‘Receive’ the ‘Shipped’ RO (similar to
   PO receiving) but under the very same linked Transfer Shipment that was
   shipped from originating facility. This should affect the On hand to the
   tune of received units.
   7. Once whole Shipment is successfully received, move the shipment to
   ‘Received’ status. And at the same time linked RO can also be marked as
   ‘Completed’.
   8. Hit the necessary and relevant GL accounts and posting in the process
   wherever needed.



I am not sure about level of technical changes involved against other
suggested approaches, so please feel free to ignore if it looks over
complicated.



Thanks,

Swapnil



-Original Message-
From: Vaibhav Jain [mailto:vaibhav.j...@hotwaxsystems.com]
Sent: Tuesday, October 24, 2017 6:46 PM
To: dev@ofbiz.apache.org
Subject: Re: RE: RE: Quantity missing for inventory transfer records



Hello All,



Thanks Swapnil for the detailed business scenarios.



Thanks James for the reply.



I just want to convey that there is no need to use a separate data model
for inventory transfer. We can use order data model for inventory transfer.



We can create a SO from one facility which create an automated PO for
another facility. Inventory transfer will be done using sales/purchase
order.



Stock move is used for intra-warehouse inventory transfer while inventory
transfer is for inter-warehouse inventory transfer.



We can achieve inventory transfer using order data model instead of using
separate data model for inventory transfer.



   1. On the basis of from party and to party we can identify that order is

   transfer order(In transfer order fromParty and toParty are same).

   2. status of inventory transfer can be maintained in OrderStatus entity.

   3. Tax is applied or not can be configurable.

   4. Shipment is already associated with order data model.

   5. Order adjustment can be used to record adjustments.

   6. The Orderitem entity can be used to transfer multiple products at a

   time.

   7. Reservation and issuance are already working in order data model.

   8. The OrderContent entity can be used to attach Stock transfer

   document(legal document vary according to country law) with inventory

   transfer.



Please correct me if I missed something.



Thanks & Regards

--



Vaibhav Jain

Hotwax Systems,

vaibhav.j...@hotwaxsystems.com



On Tue, Oct 24, 2017 at 3:54 PM, James Yong  wrote:



> Hi Swapnil,

>

> You may want to consider having the following modifications:

>

> 1) Item Issuance & Shipment Receipt entities: Add columns (i.e.

> InventoryTransferHeaderId & InventoryTransferId ) to support inventory

> transfer with shipment.

>

> 2) Inventory Transfer Adjustment entity: For the tax.

>

> 3) Inventory Transfer Header entity: For group transfer (as discussed

> earlier)

>

> Regards,

> James Yong

>

> On 2017-10-19 19:12, Swapnil Shah  wrote:

> > Let me try adding few more insights/details with regard to stock

> > transfer flow.

> >

> >

> >

> > As we are referring to intra-organizational goods movement i.e., so

> > movement of goods would be for and within the same business entity.

> > Here are few pointers (if it can help in assessing any kind of

> > technical trade-off that needs to be made with respect to current
implementation) :

> >

> >- Stock Transfer per se are going to involve goods exchange but

> > there

> is

> >no real time money exchange involved between shipper and receiver

> > as

> they

> >are both the very 

Re: svn commit: r1719660 - in /ofbiz/trunk/framework/webapp: config/requestHandler.properties dtd/site-conf.xsd src/org/ofbiz/webapp/control/ConfigXMLReader.java src/org/ofbiz/webapp/control/RequestHa

[Michael Brohl]

Hi Jacques,

how can I configure a view so that no x-frame-options header is set?

While it is great to have these security options and also have a secure 
default, there are cases where you might want to switch this header 
settings off.


Thanks and regards,

Michael


Am 12.12.15 um 12:37 schrieb jler...@apache.org:

Author: jleroux
Date: Sat Dec 12 11:37:56 2015
New Revision: 1719660

URL: http://svn.apache.org/viewvc?rev=1719660=rev
Log:
1st step for "Secure HTTP headers" 
https://issues.apache.org/jira/browse/OFBIZ-6766

Here are X-Frame-Options and Strict-Transport-Security, just a start...

Modified:
 ofbiz/trunk/framework/webapp/config/requestHandler.properties
 ofbiz/trunk/framework/webapp/dtd/site-conf.xsd
 
ofbiz/trunk/framework/webapp/src/org/ofbiz/webapp/control/ConfigXMLReader.java
 
ofbiz/trunk/framework/webapp/src/org/ofbiz/webapp/control/RequestHandler.java

Modified: ofbiz/trunk/framework/webapp/config/requestHandler.properties
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/framework/webapp/config/requestHandler.properties?rev=1719660=1719659=1719660=diff
==
--- ofbiz/trunk/framework/webapp/config/requestHandler.properties (original)
+++ ofbiz/trunk/framework/webapp/config/requestHandler.properties Sat Dec 12 
11:37:56 2015
@@ -5,6 +5,10 @@ throwRequestHandlerExceptionOnMissingLoc
  status-code=302
  
  # -- Default Content-Disposition type

-#-- attachment might be replaced by inline if you prefer to offer this option 
to your users.
+#   attachment might be replaced by inline if you prefer to offer this option 
to your users.
  #   attachment is supposed to be more secure, but this is a bit unclear see 
OFBIZ-6702 for details
-content-disposition-type=attachment
\ No newline at end of file
+content-disposition-type=attachment
+
+# -- Should we use strict-transport-security? True by default.
+#Use false if you don't have a certificate or not a signed one and it annoys you to 
set "none" for each HTTP request!
+#strict-transport-security=false
\ No newline at end of file

Modified: ofbiz/trunk/framework/webapp/dtd/site-conf.xsd
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/framework/webapp/dtd/site-conf.xsd?rev=1719660=1719659=1719660=diff
==
--- ofbiz/trunk/framework/webapp/dtd/site-conf.xsd (original)
+++ ofbiz/trunk/framework/webapp/dtd/site-conf.xsd Sat Dec 12 11:37:56 2015
@@ -774,5 +774,38 @@ under the License.
  
  
  
+
+
+
+Provides clickjacking protection by instructing browsers 
that this page should not be placed within a frame.
+Possible values are:
+deny - no rendering within a frame,
+sameorigin - no rendering if origin mismatch, and
+allow-from: - allow rendering if framing page is within 
the specified URI domain.
+Allow from is supported by IE and Firefox, but not Chrome 
or Safari.
+It will also interfere with In Page Google Analytics since 
it requires your page to be framed by Google.
+
+
+
+
+
+
+
+
+
+
+
+
+
+HTTP Strict-Transport-Security (HSTS) enforces secure 
(HTTP over SSL/TLS) connections to the server.
+This reduces impact of bugs in web applications leaking 
session data through cookies and external links and defends against 
Man-in-the-middle attacks.
+HSTS also disables the ability for users to ignore SSL 
negotiation warnings.
+If the security of the connection cannot be ensured (e.g. 
the server's TLS certificate is not trusted),
+it shows an error message and do not allow the user to 
access the web application.
+As recommended by OWASP, by default "max-age=31536000; 
includeSubDomains" is used except if the server is localhost or 127.0.0.1.
+If the strict-transport-security is "none" then it will 
not be used.
+
+
+
  
  

Modified: 
ofbiz/trunk/framework/webapp/src/org/ofbiz/webapp/control/ConfigXMLReader.java
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/framework/webapp/src/org/ofbiz/webapp/control/ConfigXMLReader.java?rev=1719660=1719659=1719660=diff
==
--- 
ofbiz/trunk/framework/webapp/src/org/ofbiz/webapp/control/ConfigXMLReader.java 
(original)
+++ 
ofbiz/trunk/framework/webapp/src/org/ofbiz/webapp/control/ConfigXMLReader.java 
Sat Dec 12 11:37:56 2015
@@ -622,6 +622,8 @@ public class ConfigXMLReader {
  public String 

Updates to EntityQuery

[Gareth Carter]

Hi all

We have internally patched EntityQuery with some additional functionality and 
before I create a Jira was going to see what the community thinks.

New functionality:

-   New method getFieldMap which returns a Map object of selected fields 
from GenericValue objects, useful for creating cache map objects for lookup

-   Support forUpdate

-   forEach method to accept Consumer

We have found these useful and believe the project can benefit, let me know 
what you think

Regards

Gareth Carter


Software Development Analyst


Stannah Management Services Ltd


IT Department


Ext:


7036


DDI:


01264 364311




[http://logos.stannah.co.uk/stan150.jpg]


[http://logos.stannah.co.uk/enviro.jpg]Please consider the environment before 
printing this email.



This email is intended only for the above addressee. It may contain privileged 
information. If you are not the addressee you must not copy, distribute, 
disclose or use any of the information in it. If you have received it in error, 
please delete it and notify the sender.

Stannah Lift Holdings Ltd registered No. 686996, Stannah Management Services 
Ltd registered No. 2483693, Stannah Lift Services Ltd registered No. 1189799, 
Stannah Microlifts Ltd registered No. 964804, Stannah Lifts Ltd registered No. 
1189836, Stannah Stairlifts Ltd registered No. 1401451, Global Upholstery 
Solutions Ltd registered No. 02452728.

All registered offices at Watt Close, East Portway, Andover, Hampshire, SP10 
3SD, England.

All Registered in England and Wales.

This message has been scanned for malware by Websense. www.websense.com

Re: RE: RE: Quantity missing for inventory transfer records

[Vaibhav Jain]

Hello All,

Thanks Swapnil for the detailed business scenarios.

Thanks James for the reply.

I just want to convey that there is no need to use a separate data model
for inventory transfer. We can use order data model for inventory transfer.

We can create a SO from one facility which create an automated PO for
another facility. Inventory transfer will be done using sales/purchase
order.

Stock move is used for intra-warehouse inventory transfer while inventory
transfer is for inter-warehouse inventory transfer.

We can achieve inventory transfer using order data model instead of using
separate data model for inventory transfer.

   1. On the basis of from party and to party we can identify that order is
   transfer order(In transfer order fromParty and toParty are same).
   2. status of inventory transfer can be maintained in OrderStatus entity.
   3. Tax is applied or not can be configurable.
   4. Shipment is already associated with order data model.
   5. Order adjustment can be used to record adjustments.
   6. The Orderitem entity can be used to transfer multiple products at a
   time.
   7. Reservation and issuance are already working in order data model.
   8. The OrderContent entity can be used to attach Stock transfer
   document(legal document vary according to country law) with inventory
   transfer.

Please correct me if I missed something.

Thanks & Regards
--

Vaibhav Jain
Hotwax Systems,
vaibhav.j...@hotwaxsystems.com

On Tue, Oct 24, 2017 at 3:54 PM, James Yong  wrote:

> Hi Swapnil,
>
> You may want to consider having the following modifications:
>
> 1) Item Issuance & Shipment Receipt entities: Add columns (i.e.
> InventoryTransferHeaderId & InventoryTransferId ) to support inventory
> transfer with shipment.
>
> 2) Inventory Transfer Adjustment entity: For the tax.
>
> 3) Inventory Transfer Header entity: For group transfer (as discussed
> earlier)
>
> Regards,
> James Yong
>
> On 2017-10-19 19:12, Swapnil Shah  wrote:
> > Let me try adding few more insights/details with regard to stock transfer
> > flow.
> >
> >
> >
> > As we are referring to intra-organizational goods movement i.e., so
> > movement of goods would be for and within the same business entity. Here
> > are few pointers (if it can help in assessing any kind of technical
> > trade-off that needs to be made with respect to current implementation) :
> >
> >- Stock Transfer per se are going to involve goods exchange but there
> is
> >no real time money exchange involved between shipper and receiver as
> they
> >are both the very same business entity in the legal sense. So business
> >might not be necessarily interested in generating any sales or
> purchase
> >invoice against such transactions. Nor will there be any real time
> payment
> >or invoice settlement required at either end.
> >- In financial terms there are tax implications but its applicability
> >varies depending upon the laws of the land or country/state-specific
> tax
> >regulations. For example:
> >   - In US the very same item transferred in certain state might be
> >   taxable at certain rate but totally exempted or taxed at
> > different rate in
> >   another (someone with better understanding of US or EUR tax
> > regulations can
> >   throw more light and let us know if currently intra-company
> > goods transfer
> >   are even taxable or not)
> >   - In India, the tax implications in the case of goods transfer is
> now
> >   shifted on the supply of goods. As a result:
> >  - For inter-state transfer *there is tax liability and in this
> >  case, only a separate “Tax Invoice”* needs to be issued along
> with
> >  stock transfer note and supporting document (depending on the
> > inter-state
> >  regulations while crossing the state borders)
> >  - For intra-state transfers if business entity is having single
> >  registration for originating and receiving branches with tax
> > authority then *there
> >  is no tax liability and hence no Tax Invoice *needs to be issue.
> >  Only Delivery Note should suffice to transfer the goods.
> >  - For intra-state transfers if business entity is having
> different
> >  registration for originating and receiving branches with tax
> > authority then *there
> >  is tax liability and in this case, only a separate “Tax
> Invoice”*
> >  needs to be issued along with stock transfer note.
> >   - Any kind of applicable tax (if any) needs to be paid to the state
> >   only and a separate Tax Invoice needs to be generated in this case.
> >- The transfer shipment needs to follow certain status transitioning
> >i.e. ‘Requested’ à ‘In-review’ à ‘Shipped’ (from originating
> facility) à
> >‘In-transit’ à ‘Received’ (at destination facility). As it needs to be
> >tracked internally.
> >- The deemed 

Re: Move buildbot messages out of DEV mailing lists

[Jacques Le Roux]

I tried a small fix, let's see

If it does not work, the best is to fill at request here 
https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3

In the meantime you could create a specific buildbot folder in your email client and a rule to send buildbot emails there (mails come from 
build...@apache.org, easy)


Jacques


Le 24/10/2017 à 12:57, Taher Alkhateeb a écrit :

Buildbot messages should not be too many, having that many is a faulty
implementation (false positives)

So, perhaps we shouldn't necessarily move the notifications away,
instead, we should fix the buildbot scripts.

On Tue, Oct 24, 2017 at 1:32 PM, James Yong  wrote:

Hi all,

The Buildbot messages are filling considerable spaces in the DEV mailing list.
Wonder if we should move them elsewhere...

Regards,
James Yong

Re: Move buildbot messages out of DEV mailing lists

[Taher Alkhateeb]

Buildbot messages should not be too many, having that many is a faulty
implementation (false positives)

So, perhaps we shouldn't necessarily move the notifications away,
instead, we should fix the buildbot scripts.

On Tue, Oct 24, 2017 at 1:32 PM, James Yong  wrote:
> Hi all,
>
> The Buildbot messages are filling considerable spaces in the DEV mailing list.
> Wonder if we should move them elsewhere...
>
> Regards,
> James Yong
>
>

Move buildbot messages out of DEV mailing lists

[James Yong]

Hi all,

The Buildbot messages are filling considerable spaces in the DEV mailing list.
Wonder if we should move them elsewhere...

Regards,
James Yong

Re: RE: RE: Quantity missing for inventory transfer records

[James Yong]

Hi Swapnil,

You may want to consider having the following modifications:

1) Item Issuance & Shipment Receipt entities: Add columns (i.e. 
InventoryTransferHeaderId & InventoryTransferId ) to support inventory transfer 
with shipment.

2) Inventory Transfer Adjustment entity: For the tax.

3) Inventory Transfer Header entity: For group transfer (as discussed earlier)

Regards,
James Yong

On 2017-10-19 19:12, Swapnil Shah  wrote: 
> Let me try adding few more insights/details with regard to stock transfer
> flow.
> 
> 
> 
> As we are referring to intra-organizational goods movement i.e., so
> movement of goods would be for and within the same business entity. Here
> are few pointers (if it can help in assessing any kind of technical
> trade-off that needs to be made with respect to current implementation) :
> 
>- Stock Transfer per se are going to involve goods exchange but there is
>no real time money exchange involved between shipper and receiver as they
>are both the very same business entity in the legal sense. So business
>might not be necessarily interested in generating any sales or purchase
>invoice against such transactions. Nor will there be any real time payment
>or invoice settlement required at either end.
>- In financial terms there are tax implications but its applicability
>varies depending upon the laws of the land or country/state-specific tax
>regulations. For example:
>   - In US the very same item transferred in certain state might be
>   taxable at certain rate but totally exempted or taxed at
> different rate in
>   another (someone with better understanding of US or EUR tax
> regulations can
>   throw more light and let us know if currently intra-company
> goods transfer
>   are even taxable or not)
>   - In India, the tax implications in the case of goods transfer is now
>   shifted on the supply of goods. As a result:
>  - For inter-state transfer *there is tax liability and in this
>  case, only a separate “Tax Invoice”* needs to be issued along 
> with
>  stock transfer note and supporting document (depending on the
> inter-state
>  regulations while crossing the state borders)
>  - For intra-state transfers if business entity is having single
>  registration for originating and receiving branches with tax
> authority then *there
>  is no tax liability and hence no Tax Invoice *needs to be issue.
>  Only Delivery Note should suffice to transfer the goods.
>  - For intra-state transfers if business entity is having different
>  registration for originating and receiving branches with tax
> authority then *there
>  is tax liability and in this case, only a separate “Tax Invoice”*
>  needs to be issued along with stock transfer note.
>   - Any kind of applicable tax (if any) needs to be paid to the state
>   only and a separate Tax Invoice needs to be generated in this case.
>- The transfer shipment needs to follow certain status transitioning
>i.e. ‘Requested’ à ‘In-review’ à ‘Shipped’ (from originating 
> facility) à
>‘In-transit’ à ‘Received’ (at destination facility). As it needs 
> to be
>tracked internally.
>- The deemed transaction value and tax liability against the transferred
>goods should hit the accounting books against appropriate GL accounts per
>store and a separate GL account against the tax authority (in accordance
>with business rules).
>- Later at some point of time we may also like to systemically build the
>Transfer Requirement Planning and consolidate all the individual
>product-wise transfer ad-hoc or planned requests/requirement for a common
>destination facility (i.e., once any feature like
>https://issues.apache.org/jira/browse/OFBIZ-6964 gets implemented)
> 
> 
> 
> I hope it should help to come up with a generic enough solution that can
> work across geographies with required level of flexibility.
> 
> 
> 
> Thanks,
> 
> Swapnil
> 
> 
> 
> -Original Message-
> From: James Yong [mailto:jamesy...@apache.org]
> Sent: Wednesday, October 18, 2017 9:56 PM
> To: dev@ofbiz.apache.org
> Subject: Re: RE: Quantity missing for inventory transfer records
> 
> 
> 
> Hi Vaibhav,
> 
> 
> 
> My random thoughts on the possible implementation:
> 
> 
> 
> We can have a new InventoryTransferHeader (ITH) entity as mentioned earlier
> to manage group transfer.
> 
> 
> 
> Having Quality attribute to InventoryTransfer entity is reasonable since we
> may have an approval process before actual transfer.
> 
> 
> 
> User doing inventory transfer can have an Shipment option to enable
> shipment.
> 
> 
> 
> When inventory transfer is approval and Shipment option is selected, a
> corresponding Sales Order (SO) and Purchase Order (PO) will be created.
> 
> 
> 
> You may want to use a different 

Re: Date model original source files, was: Re: [ANNOUNCE] The Big Book for Apache OFBiz Data Model 2017 Released

[Aditya Sharma]

Hi Michael, Jacques,

I have uploaded the Graffle files on OFBIZ-9857
. You can move it now to
the desired directory

Thanks and Regards,

*Aditya Sharma* | Enterprise Software Engineer
HotWax Systems 


On Tue, Oct 17, 2017 at 6:03 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Le 11/10/2017 à 14:27, Jacques Le Roux a écrit :
>
>> Hi Michael,
>>
>> I think a good place for them is in tools. I'd create a sub-dir
>> documentation and even a sub-sub-dir data-model
>>
> Maybe now if we create a documentation folder under OFBiz root the best
> place would be there...
>
>
>
>> Jacques
>>
>>
>> Le 11/10/2017 à 13:14, Michael Brohl a écrit :
>>
>>> Hi everyone,
>>>
>>> I think we should somehow store the Omnigraffle source files and keep
>>> them up-to-date in our repository.
>>>
>>> I'm not sure where to store them, maybe a new repository path
>>> /ofbiz/ofbiz-framework-doc and /ofbiz/ofbiz-plugins-doc ?
>>>
>>> Another idea is to convert them into a format which can be edited by
>>> freely available diagram tools like draw.io, yEd or else to make them
>>> accessible for everyone without the need of buying a program. What do you
>>> think?
>>>
>>> Regards,
>>>
>>> Michael
>>>
>>>
>>> Am 04.10.17 um 13:15 schrieb Aditya Sharma:
>>>
 Hello All,

 It gives me immense pleasure informing you all that we have updated
 *The Big
 Book of Apache OFBiz Data Model* according to the latest trunk version.

 The key features:
 * Colored content with titles according to the internal color pattern.
 * Addition of a separate page for integration specific entities.
 * Removal of technical process diagrams, making it specific for
 entities.
 * Addition of 77 new entities.
 * Removal of 8 entities.
 * Addition of around 200+ new fields in entities (Though major portion
 includes the addition of description or attrDescription fields in
 *Attribute or *TypeAttr entities).
 * Removal of 24 fields.

 I have uploaded the files on Data Model Diagrams page. Here is the link
 .

 Cheers!

 *Aditya Sharma* | Enterprise Software Engineer
 HotWax Systems 
 


>>>
>>>
>>
>>
>