Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0010687 | Openbravo ERP | 01. General setup | public | 2009-09-22 10:34 | 2009-10-23 00:00 |
|
| Reporter | networkb | |
| Assigned To | rafaroda | |
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.50MP5 | |
| Target Version | 2.50MP8 | Fixed in Version | 2.50MP7 | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | OBPS |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0010687: Some alerts are wrong defined |
| Description | Some alerts defined in the application does not work. Some of them do not work just in Postgre, and other ones, in both databases.
Here, you are the ones that do not work in both databases (AD_Alertrule_ID):
*1000018,1000020, FDA0D6B303CD4F289A04FA41844C4B0C
And this ones, do not work just in Postgre:
*800003, 1000007, 1000021, 1000022 |
| Steps To Reproduce | Connect directly with the database and execute:
select * from ad_alertrule
Obtain "SQL" column from the query, taking into account only the AD_Alertrule_ID provided above.
Try to execute the query. Different errors will appear. |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | has duplicate | defect | 0010587 | | closed | rafaroda | Some alerts in sourcedata are wrong |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-09-22 10:34 | networkb | New Issue | |
| 2009-09-22 10:34 | networkb | Assigned To | => rafaroda |
| 2009-09-22 10:34 | networkb | OBNetwork customer | => Yes |
| 2009-09-22 10:34 | networkb | version | => 2.50MP5 |
| 2009-09-22 10:53 | rafaroda | Note Added: 0020256 | |
| 2009-09-22 10:53 | rafaroda | Priority | immediate => high |
| 2009-09-22 10:53 | rafaroda | Status | new => scheduled |
| 2009-09-22 10:55 | rafaroda | Relationship added | has duplicate 0010587 |
| 2009-09-22 15:14 | galderromo | Issue Monitored: galderromo | |
| 2009-09-23 07:49 | rafaroda | Note Added: 0020292 | |
| 2009-10-01 10:12 | hgbot | Checkin | |
| 2009-10-01 10:12 | hgbot | Note Added: 0020619 | |
| 2009-10-01 10:12 | hgbot | Status | scheduled => resolved |
| 2009-10-01 10:12 | hgbot | Resolution | open => fixed |
| 2009-10-01 10:12 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/4b516ef751acabdda4f3dc8bfecda7d0966ae7b7 [^] |
| 2009-10-01 11:28 | jeneivemalarkodi | Note Added: 0020623 | |
| 2009-10-22 09:25 | arunkumar | Status | resolved => closed |
| 2009-10-22 09:25 | arunkumar | Note Added: 0021308 | |
| 2009-10-22 09:25 | arunkumar | Fixed in Version | => 2.50MP7 |
| 2009-10-23 00:00 | anonymous | sf_bug_id | 0 => 2884249 |
|
Notes |
|
|
|
More wrong alerts:
1- "Columns with search reference and reference value null". It is necessary to change: WHERE AD_REFERENCE_ID = 30 by WHERE AD_REFERENCE_ID = '30'
2- "Process Execution Failed". The view ad_process_run_v doesn't exist
3- "Vendor or Customer BPs without Bill To address" SQL is wrong, replace it by:
select c_bpartner_id as referencekey_id,
name as record_id,
0 as ad_role_id,
null as ad_user_id,
name ||'has not bill to address' as description,
'Y' as isActive,
ad_org_id,
ad_client_id,
now() as created,
0 as createdBy,
now() as updated,
0 as updatedBy
from c_bpartner bp
where (isvendor='Y' or iscustomer='Y')
and not exists (select 1
from c_bpartner_location l
where l.c_bpartner_id = bp.c_bpartner_id
and isbillto='Y') |
|
|
|
|
|
A collateral issue related is that, if any of these wrong alerts is active, it will break the alert background process. |
|
|
|
(0020619)
|
|
hgbot
|
|
2009-10-01 10:12
|
|
|
|
|
|
* Nine alert quries are modified out of 20 records in OB
Test Cases:
1. Enable all alerts in OB (General Setup -> Application -> Alert)
2. Ensure that all alerts have 'Alert Recipient' Entry
3. Create new process request(General Setup -> Process Scheduling -> Process Request)
4. Can view alerts in 'Alert Management' (General Setup -> Application -> Alert management)
5. Have to test in both the databases |
|
|
|
|
|