Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0018152Openbravo ERPA. Platformpublic2011-08-01 22:192023-07-04 12:29
Reporterjecharri 
Assigned ToTriage Platform Base 
PriorityhighSeverityminorReproducibilityalways
StatusnewResolutionout of date 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browserGoogle Chrome
ModulesCore
Support ticket12258
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0018152: The new record or insert row button must be disabled
DescriptionThe new record or insert row button must be disabled when you have the order or invoice booked and you try to create a new line for the order or invoice.
Steps To ReproduceGo to sales order and create one with one line for example.
Book it.
Go to lines tab and you will see that both buttons are activated.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 00181532.50MP35 closed alostale The new record or insert row button must be disabled 
has duplicate defect 00161933.0MP5 closed mtaal Do no allow adding lines when a document is completed/posted etc. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-08-01 22:19jecharriNew Issue
2011-08-01 22:19jecharriAssigned To => alostale
2011-08-01 22:19jecharriWeb browser => Google Chrome
2011-08-01 22:19jecharriModules => Core
2011-08-01 22:19jecharriOBNetwork customer => Yes
2011-08-01 22:19jecharriSupport ticket => 12258
2011-08-01 22:19jecharriResolution time => 1319320800
2011-08-01 22:20jecharriStatusnew => scheduled
2011-08-01 22:20jecharrifix_in_branch => pi
2011-09-28 17:56iperdomoAssigned Toalostale => dbaz
2011-09-29 12:10iperdomoWeb browserGoogle Chrome => Google Chrome
2011-09-29 12:10iperdomoTarget Version3.0MP4 => 3.0MP6
2011-09-29 12:10iperdomofix_in_branchpi =>
2011-09-29 12:10iperdomoWeb browserGoogle Chrome => Google Chrome
2011-09-29 12:10iperdomoTypedefect => feature request
2011-10-27 10:49mtaalRelationship addedhas duplicate 0016193
2011-11-03 17:22mtaalWeb browserGoogle Chrome => Google Chrome
2011-11-03 17:22mtaalNote Added: 0042504
2011-11-03 17:22mtaalAssigned Todbaz => mtaal
2011-11-03 17:22mtaalTarget Version3.0MP6 => 3.0MP7
2011-11-15 10:30iperdomoWeb browserGoogle Chrome => Google Chrome
2011-11-15 10:30iperdomoTarget Version3.0MP7 =>
2016-10-21 11:00mtaalStatusscheduled => closed
2016-10-21 11:00mtaalResolutionopen => out of date
2016-10-21 13:17mtaalTag Attached: MT_closed_out_of_date
2016-10-21 14:08mtaalAssigned Tomtaal => platform
2016-10-21 14:09mtaalStatusclosed => new
2016-10-21 14:11mtaalTag Detached: MT_closed_out_of_date
2022-02-01 08:07alostaleAssigned Toplatform => Triage Platform Base
2023-07-04 12:29jarmendarizWeb browserGoogle Chrome => Google Chrome
2023-07-04 12:29jarmendarizTriggers an Emergency Pack => No

Notes
(0042504)
mtaal   
2011-11-03 17:22   
This issue should be solved as part of a larger development to define buttons in the AD, the disabled/visibility of the buttons can then be controlled with displaylogic/readonlylogic type of functionality. Moving to a later MP as we probably won't have time to address this topic before.