Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0010019
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 09. Financial managementmajorhave not tried2009-07-23 14:002011-10-28 18:02
ReporterarunkumarView Statuspublic 
Assigned Toiperdomo 
PriorityhighResolutionout of dateFixed in Versionpi
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP3SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0010019: Using autosave in settlement , after creating lines does not display process completion successful message

DescriptionCreate a settlement. Click Create lines form.After creating lines it does not display the process completion message
Steps To ReproduceGo to Financial Management -> Receivables and Payable -> Transactions -> Settlement
Click a new record.
Do not save that.
Click create lines from
Select lines form the popup window.
After creating the lines it does not show the message "Process completed successfully".

But if I save the settlement then I create lines after that I have got the Process completion message.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0019716)
AinhoaPagola (reporter)
2009-09-10 11:41

Hello,

I can also reproduce this issue in the Human Capital Management module.

In a tab where there is a button:

If a new record is entered ant the button is clicked without previously saving the record, the result message is not displayed.

This is particularly important if the answer message is an error, as the user will not know what happened. If the button is pressed a second time the message will be properly displayed.

Let me know if further information is needed.

Ainhoa.
(0042226)
dmitry_mezentsev (developer)
2011-10-28 13:00

Iván,

Could you please check if this issue is still valid for OB3?


Thanks.
(0042274)
iperdomo (reporter)
2011-10-28 17:47

@Dimitry:
The Autosave components/architecture in OB3 is completely different than 2.50. If is still valid, only applies to 2.50
(0042275)
dmitry_mezentsev (developer)
2011-10-28 18:02

Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved UI and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed.

Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription.

You can find more details about our Support policy in the following blog post
http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^]

- Issue History
Date Modified Username Field Change
2009-07-23 14:00 arunkumar New Issue
2009-07-23 14:00 arunkumar Assigned To => rafaroda
2009-07-24 11:07 psarobe Assigned To rafaroda => iperdomo
2009-07-24 11:07 psarobe Priority low => high
2009-07-24 11:07 psarobe Severity minor => major
2009-07-24 11:07 psarobe Status new => scheduled
2009-09-10 11:41 AinhoaPagola Note Added: 0019716
2011-10-28 13:00 dmitry_mezentsev Note Added: 0042226
2011-10-28 17:47 iperdomo Note Added: 0042274
2011-10-28 18:02 dmitry_mezentsev Note Added: 0042275
2011-10-28 18:02 dmitry_mezentsev Status scheduled => closed
2011-10-28 18:02 dmitry_mezentsev Resolution open => out of date
2011-10-28 18:02 dmitry_mezentsev Fixed in Version => pi


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker