Re: svn commit: r1768154 - /ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml

[Arun Patidar]

Thanks Jacques.

-- 
Thanks & Regards
---
Arun Patidar
Manager,Enterprise Software Development
HotWax Mediawww.hotwaxsystems.com


On Tue, Nov 8, 2016 at 3:06 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Thanks Arun,
>
> I partially (but enough IMO) completed at revision: 1768649
>
> Jacques
>
>
> Le 05/11/2016 à 07:26, arunpati...@apache.org a écrit :
>
>> Author: arunpatidar
>> Date: Sat Nov  5 06:26:58 2016
>> New Revision: 1768154
>>
>> URL: http://svn.apache.org/viewvc?rev=1768154=rev
>> Log:
>> Fixed: Arranged sequence of CRUD services to make consistency.
>> (OFBIZ-8461)
>>
>> Thanks: Jacques for reviewing and reporting.
>>
>> Modified:
>>  ofbiz/trunk/applications/product/servicedef/services_shipme
>> ntgateway.xml
>>
>> Modified: ofbiz/trunk/applications/product/servicedef/services_shipmen
>> tgateway.xml
>> URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/produc
>> t/servicedef/services_shipmentgateway.xml?rev=1768154=
>> 1768153=1768154=diff
>> 
>> ==
>> --- ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml
>> (original)
>> +++ ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml
>> Sat Nov  5 06:26:58 2016
>> @@ -31,13 +31,13 @@ under the License.
>>   > include="nonpk" mode="IN" optional="true"/>
>>   
>>   -> engine="entity-auto" invoke="update" default-entity-name="ShipmentGatewayDhl"
>> auth="true">
>> -Update a ShipmentGatewayDhl record
>> +> default-entity-name="ShipmentGatewayDhl" engine="entity-auto"
>> invoke="create" auth="true">
>> +Create a ShipmentGatewayDhl
>>   
>>   
>>   
>> -> default-entity-name="ShipmentGatewayDhl" engine="entity-auto"
>> invoke="create" auth="true">
>> -Create a ShipmentGatewayDhl
>> +> default-entity-name="ShipmentGatewayDhl" engine="entity-auto"
>> invoke="update" auth="true">
>> +Update a ShipmentGatewayDhl record
>>   
>>   
>>   
>> @@ -46,13 +46,13 @@ under the License.
>>   
>>   
>>   -> engine="entity-auto" invoke="update" 
>> default-entity-name="ShipmentGatewayFedex"
>> auth="true">
>> -Update a ShipmentGatewayFedex record
>> +> default-entity-name="ShipmentGatewayFedex" engine="entity-auto"
>> invoke="create" auth="true">
>> +Create a ShipmentGatewayFedex
>>   
>>   
>>   
>> -> default-entity-name="ShipmentGatewayFedex" engine="entity-auto"
>> invoke="create" auth="true">
>> -Create a ShipmentGatewayFedex
>> +> default-entity-name="ShipmentGatewayFedex" engine="entity-auto"
>> invoke="update" auth="true">
>> +Update a ShipmentGatewayFedex record
>>   
>>   
>>   
>>
>>
>>
>>
>

Re: Business Process and Use Case Library for Ecommerce ERP

[Taher Alkhateeb]

Hi Pranay,

It is a good idea of course to keep multiple versions of documentation for
multiple releases.

Talking in terms of priority, however, I think perhaps we need to spend
most of our energy into first organizing and cleaning up our documentation.
We need an API section, a user manual, a developer manual, and a set of
tutorials. All of these need to be categorized and point to each other in
hyperlinks. Right now, the documentation is heavily scattered in different
and confusing sections. There is no "one location" for getting a piece of
information. So for example, the business processes could be maybe part of
the "User Manual" right? We don't have such a categorization at the moment
which dilutes value.

Also if you think about it, good organization of this information would
make it easier to create release-specific documentation because you're
building on the same organized skeleton. So in short I agree with your
approach but trying to convince you to perhaps try to focus your energy on
organizing our documentation if you have the time for it.

Thank you as always for your initiative.

Cheers,

Taher Alkhateeb

On Tue, Nov 8, 2016 at 2:08 PM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> Hello Everyone,
>
> I am thinking to make a change in document hierarchy for Business Process
> and Use Case Library for Ecommerce ERP
> . I think we can rename it
> for branch or release.
> E.g. we can prepare first set of documents for branch Release 14.12. So the
> document hierarchy will look like:
>
> - Business Process and Use Case Library for Ecommerce ERP
> -- Release 14.12
> -- Release 16.12
> -- and so on
>
> So the idea is to dedicatedly build documents for specific branch or
> releases. This way a set of the documents will be declared to be used for a
> specific release being used. As we start preparing for the new release, we
> can copy from old release and append the additions to it. We can then also
> add test cases(with a mark of success or failure for each for all the
> components) along with User Stories and Use Cases which will add more value
> to it.
>
> With its current name and structure it indicates, it's for trunk and having
> it managed on release basis will bring in more attention to it.
>
> Please let me know your thoughts on it. If no objections are seen I would
> like to make this change in a day or two.
>
> Best regards,
>
> Pranay Pandey
> HotWax Systems
> http://www.hotwaxsystems.com/
>

Business Process and Use Case Library for Ecommerce ERP

[Pranay Pandey]

Hello Everyone,

I am thinking to make a change in document hierarchy for Business Process
and Use Case Library for Ecommerce ERP
. I think we can rename it
for branch or release.
E.g. we can prepare first set of documents for branch Release 14.12. So the
document hierarchy will look like:

- Business Process and Use Case Library for Ecommerce ERP
-- Release 14.12
-- Release 16.12
-- and so on

So the idea is to dedicatedly build documents for specific branch or
releases. This way a set of the documents will be declared to be used for a
specific release being used. As we start preparing for the new release, we
can copy from old release and append the additions to it. We can then also
add test cases(with a mark of success or failure for each for all the
components) along with User Stories and Use Cases which will add more value
to it.

With its current name and structure it indicates, it's for trunk and having
it managed on release basis will bring in more attention to it.

Please let me know your thoughts on it. If no objections are seen I would
like to make this change in a day or two.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

Re: svn commit: r1767965 - in /ofbiz/trunk: applications/content/servicedef/ applications/order/servicedef/ applications/product/servicedef/ applications/workeffort/servicedef/ framework/common/servic

[Jacques Le Roux]

Ah indeed, thanks Rishi!

Jacques


Le 08/11/2016 à 09:57, Rishi Solanki a écrit :

Jacques,

We mentioned this in the ticket details OFBIZ-8769 that is why dev didn't
submit the update service for ProductStoreGroupRole. The reason was this
entity will only have the PKs and no non-PKs exist for this entity.

Thanks for checking it again and support.



Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Mon, Nov 7, 2016 at 1:47 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Thanks Arun,

Is there a reason why we have no updateProductStoreGroupRole?

Jacques



Le 05/11/2016 à 06:59, Arun Patidar a écrit :


Hi Jacques,

I moved service near to create and update at rev:1768152

Re: svn commit: r1768154 - /ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml

[Jacques Le Roux]

Thanks Arun,

I partially (but enough IMO) completed at revision: 1768649

Jacques

Le 05/11/2016 à 07:26, arunpati...@apache.org a écrit :

Author: arunpatidar
Date: Sat Nov  5 06:26:58 2016
New Revision: 1768154

URL: http://svn.apache.org/viewvc?rev=1768154=rev
Log:
Fixed: Arranged sequence of CRUD services to make consistency.
(OFBIZ-8461)

Thanks: Jacques for reviewing and reporting.

Modified:
 ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml

Modified: 
ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml?rev=1768154=1768153=1768154=diff
==
--- ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml 
(original)
+++ ofbiz/trunk/applications/product/servicedef/services_shipmentgateway.xml 
Sat Nov  5 06:26:58 2016
@@ -31,13 +31,13 @@ under the License.
  
  
  
-

-Update a ShipmentGatewayDhl record
+
+Create a ShipmentGatewayDhl
  
  
  
-
-Create a ShipmentGatewayDhl
+
+Update a ShipmentGatewayDhl record
  
  
  
@@ -46,13 +46,13 @@ under the License.
  
  
  
-

-Update a ShipmentGatewayFedex record
+
+Create a ShipmentGatewayFedex
  
  
  
-
-Create a ShipmentGatewayFedex
+
+Update a ShipmentGatewayFedex record
  
  
  

Re: svn commit: r1767965 - in /ofbiz/trunk: applications/content/servicedef/ applications/order/servicedef/ applications/product/servicedef/ applications/workeffort/servicedef/ framework/common/servic

[Rishi Solanki]

Jacques,

We mentioned this in the ticket details OFBIZ-8769 that is why dev didn't
submit the update service for ProductStoreGroupRole. The reason was this
entity will only have the PKs and no non-PKs exist for this entity.

Thanks for checking it again and support.



Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Mon, Nov 7, 2016 at 1:47 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Thanks Arun,
>
> Is there a reason why we have no updateProductStoreGroupRole?
>
> Jacques
>
>
>
> Le 05/11/2016 à 06:59, Arun Patidar a écrit :
>
>> Hi Jacques,
>>
>> I moved service near to create and update at rev:1768152
>>
>>
>