Hi to all,
during the migration to the new styles of the lookup screens into facility
application I have seen that there is a Lookup Shipment screen into the
LookupScreen.xml but there is any request into controller.xml.
May I can add the request into the controller.xml or remove the screen
Marco,
chances are that the screen is used by another component; but even if it
is not, I wouldn't remove it, because it could be used in the future.
Jacopo
[EMAIL PROTECTED] wrote:
Hi to all,
during the migration to the new styles of the lookup screens into facility
application I have
From: David E Jones [EMAIL PROTECTED]
REST is a more general architectural concept... what does it have to
do with this? In other words, I'm not quite sure what you mean by
REST along with other ways.
-David
As BJ suggested in http://www.xfront.com/REST-Web-Services.html you can create Web
[
https://issues.apache.org/jira/browse/OFBIZ-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
santosh malviya updated OFBIZ-1468:
---
Attachment: PartyCommunication.patch
Modified patch according to comments.
JUNIT test
On Jan 7, 2008, at 5:14 AM, Jacques Le Roux wrote:
From: David E Jones [EMAIL PROTECTED]
REST is a more general architectural concept... what does it have to
do with this? In other words, I'm not quite sure what you mean by
REST along with other ways.
-David
As BJ suggested in
While testing the GL accounting transactions I've found something that
could be an issue in the procedure that computes the sales tax
adjustment for the invoice.
I've noticed that the InvoiceItem.amount for sales tax contains
sometimes a number with 3 decimals, even if the arithmetic.properties
Hi all,
we may use some help/advices/suggestions for the implementation of fixed
asset depreciation.
Here are the details:
https://issues.apache.org/jira/browse/OFBIZ-1539
Main points are:
1) is it ok to remove DepreciationMethod entity and use the more general
CustomMethod entity instead?
In the same format of UPS, FedEx, USPS web tools.
and leave the UI up to further interpretation.
By using templates both for sending and receiving
the actual format of the data does not have to conform to Ofbiz.
Use of URL redirects to java or simple methods allows the return data to
be recieved.
I believe the best solution is to step back and make some high level
design decisions having to do with math.
I believe a complete path map of processes first needs to be generated
to see when the final figure is done. for instance when an invoice is
sent.
It may be time to refactor where the
Hi Jacopo
My understanding of calc and final:
calc - adjustment level rounding
final - the sum of all tax adjustments (tax total) is rounded to this
precision
Perhaps AcctgTransEntry.amount needs to store to a higher precision as well?
Regards
Scott
On 08/01/2008, Jacopo Cappellato [EMAIL
[
https://issues.apache.org/jira/browse/OFBIZ-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti updated OFBIZ-1556:
--
Attachment: new_facility_styles6.patch
This patch is for facility group/lookup forms.
New
[
https://issues.apache.org/jira/browse/OFBIZ-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556661#action_12556661
]
Marco Risaliti commented on OFBIZ-1556:
---
Patch new_facility_styles6.patch committed
On Jan 7, 2008, at 5:14 AM, Jacques Le Roux wrote:
From: David E Jones [EMAIL PROTECTED]
REST is a more general architectural concept... what does it have to
do with this? In other words, I'm not quite sure what you mean by
REST along with other ways.
-David
As BJ suggested in
[
https://issues.apache.org/jira/browse/OFBIZ-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti updated OFBIZ-1556:
--
Attachment: new_facility_styles7.patch
This is the last patch that contains some little
[
https://issues.apache.org/jira/browse/OFBIZ-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556707#action_12556707
]
Marco Risaliti commented on OFBIZ-1556:
---
Patch new_facility_styles7.patch committed
[
https://issues.apache.org/jira/browse/OFBIZ-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti closed OFBIZ-1556.
-
Resolution: Fixed
Last commit in rev. 609782
New Styles For Facility application
[
https://issues.apache.org/jira/browse/OFBIZ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti updated OFBIZ-1545:
--
Attachment: new_order_styles1.patch
First patch for the new style to the Lookup forms.
New
[
https://issues.apache.org/jira/browse/OFBIZ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556728#action_12556728
]
Marco Risaliti commented on OFBIZ-1545:
---
Patch new_order_styles1.patch is in trunk
[
https://issues.apache.org/jira/browse/OFBIZ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556747#action_12556747
]
Marco Risaliti commented on OFBIZ-1545:
---
Patch new_order_styles2.patch is in trunk
[
https://issues.apache.org/jira/browse/OFBIZ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti updated OFBIZ-1545:
--
Attachment: new_order_styles2.patch
Second patch for the new style to the Quote forms.
New
[
https://issues.apache.org/jira/browse/OFBIZ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti updated OFBIZ-1545:
--
Attachment: new_order_styles3.patch
Third patch for the new style to the Requests forms.
New
[
https://issues.apache.org/jira/browse/OFBIZ-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556757#action_12556757
]
Marco Risaliti commented on OFBIZ-1545:
---
Patch new_order_styles3.patch is in trunk
From: Scott Gray [EMAIL PROTECTED]
Hi Jacopo
My understanding of calc and final:
calc - adjustment level rounding
final - the sum of all tax adjustments (tax total) is rounded to this
precision
Perhaps AcctgTransEntry.amount needs to store to a higher precision as well?
Yes, I agree with
On Jan 7, 2008, at 12:53 PM, Jacques Le Roux wrote:
On Jan 7, 2008, at 5:14 AM, Jacques Le Roux wrote:
From: David E Jones [EMAIL PROTECTED]
REST is a more general architectural concept... what does it have to
do with this? In other words, I'm not quite sure what you mean by
REST along with
+1
On Jan 7, 2008, at 6:21 PM, Jacques Le Roux wrote:
From: Scott Gray [EMAIL PROTECTED]
Hi Jacopo
My understanding of calc and final:
calc - adjustment level rounding
final - the sum of all tax adjustments (tax total) is rounded to this
precision
Perhaps AcctgTransEntry.amount needs to store
On Jan 7, 2008, at 11:04 AM, Scott Gray wrote:
Hi Jacopo
My understanding of calc and final:
calc - adjustment level rounding
final - the sum of all tax adjustments (tax total) is rounded to this
precision
Perhaps AcctgTransEntry.amount needs to store to a higher precision
as well?
What
Perhaps we need to do 2 things:
1. Summarize AcctgTransEntries so that you have one entry per TaxAuthority
rather than for each tax adjustment
2. During order/invoice processing, calc and final should be applied on a
per TaxAuthority basis, so that we are only ever collecting final rounded
amounts
Based on the requirement described in the commit log it sounds like
using another RateType for that would be the way to go.
Could you describe why this is needed instead of using another
RateType (along with PartyRate)?
-David
On Jan 7, 2008, at 10:47 PM, [EMAIL PROTECTED] wrote:
Hi David,
it is not the point that another ratetype will help we already have
that. When employees however fill in their timesheet we have employees
that are charged full rate because they are fully trained, and have
employees who are in training and should be charged half. We indeed have
a rate
[
https://issues.apache.org/jira/browse/OFBIZ-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Porwal updated OFBIZ-1552:
Attachment: TaxAuthorityGlAccount_Entries_Jan5.patch
Hi All,
I was working on this issue and
[
https://issues.apache.org/jira/browse/OFBIZ-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pankaj Savita updated OFBIZ-1462:
-
Attachment: (was: Ecommerce_OnePage_CheckoutProcess.patch)
One Page Checkout Process
[
https://issues.apache.org/jira/browse/OFBIZ-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Meshram updated OFBIZ-1462:
--
Attachment: (was: Ecommerce_OnePage_CheckoutProcess.patch)
One Page Checkout Process
[
https://issues.apache.org/jira/browse/OFBIZ-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Meshram updated OFBIZ-1462:
--
Attachment: Ecommerce_OnePage_CheckoutProcess.patch
One Page Checkout Process implemented in
From a data modeling perspective this doesn't constrain having a
single default rate type... perhaps it would be better to add a
defaultRateTypeId field to the Person entity (would say Party, but I
don't know if we'll need to bill for an entire organization... maybe
so though... so maybe
Yes David you are right, it is now the user responsibility that there is
only one 'Y' flag.
I looked at the PartyProfileDefault to add it there, but then how do we
maintain it? As it is now via the partyRate entity and updating the
field in the PartyProfileDefault entity in the partyrate
35 matches
Mail list logo
