Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0018834 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [Openbravo ERP] A. Platform | major | always | 2011-10-21 15:09 | 2022-02-01 08:08 | ||||||
| Reporter | gorkaion | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Linux 32 bit | Database | Oracle | Java version | 1.5.0_15 | ||||||
| OS Version | Gentoo | Database version | 11g | Ant version | 1.7.0 | ||||||
| Product Version | pi | SCM revision | |||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0018834: Columns used on validation rules of process parameters are not correctly calculated | ||||||||||
| Description | It is not possible to use a validation rule that uses more than one column to filter the drop down in a process' parameter. Consider a process called from a window that has a parameter filtered using a validation rule. If this validation rule uses more than one column to filter only the first one is used. | ||||||||||
| Steps To Reproduce | 1. Go to the 'Payment In' window and remove the filter to get one that it is processed. Click on the 'Reactivate' button and check that 'Reactivate' and 'Void' actions are available. 2. Change to System Admin role and go to the ''Process Payment valid actions'' validation setup that it is used to filter the available actions to process a payment. Change the code from: ((@EM_APRM_Process_Payment@ = 'P' AND AD_Ref_List.value='P') OR (@EM_APRM_Process_Payment@ = 'R' AND AD_Ref_List.value IN ('R', 'V')) OR (@EM_APRM_Process_Payment@ is null)) to: (@isActive@ = @isActive@ AND (@EM_APRM_Process_Payment@ = 'P' AND AD_Ref_List.value='P') OR (@EM_APRM_Process_Payment@ = 'R' AND AD_Ref_List.value IN ('R', 'V')) OR (@EM_APRM_Process_Payment@ is null)) 3. Compile the window using 'ant compile -Dtab="Payment In"' 4. Refresh tomcat and go again to the same payment and click the 'Reactivate' button. Check that the available actions have been changed although the validation should return the same values. 5. Check that the org.openbravo.erpWindows.PaymentIn.Header class is only setting the isActive value and not setting the 'EM_APRM_Process_Payment' field's value. | ||||||||||
| Proposed Solution | The issue is on the getComboParaCode() method of WadActionButton class. The selectComboParams() query is parsing the code of the validation rule and getting the first value it finds between "@". | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0045688) alostale (manager) 2012-03-02 09:31 |
Moving to design defect: -Fixing this bug requires quite a big refactoring in WAD processes generation. -These kind of processes should be replaced in mid-term by process param windows. |
|
(0052419) AugustoMauch (administrator) 2012-09-24 21:06 |
Effort: 5 Impact: mid Plan: mid |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-10-21 15:09 | gorkaion | New Issue | |
| 2011-10-21 15:09 | gorkaion | Assigned To | => alostale |
| 2011-10-21 15:09 | gorkaion | Modules | => Core |
| 2011-10-21 15:15 | gorkaion | Relationship added | related to 0018835 |
| 2012-03-02 09:31 | alostale | Note Added: 0045688 | |
| 2012-03-02 09:31 | alostale | Type | defect => design defect |
| 2012-09-24 21:06 | AugustoMauch | Note Added: 0052419 | |
| 2012-09-24 21:06 | AugustoMauch | Status | new => scheduled |
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged |
| 2017-04-10 14:33 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |