Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0031147 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Modules] Service Contract Management | minor | always | 2015-10-14 10:28 | 2015-10-14 13:35 | |||
| Reporter | ngarcia | View Status | public | |||||
| Assigned To | Triage Omni OMS | |||||||
| Priority | high | Resolution | invalid | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Merge Request Status | ||||||||
| Regression date | ||||||||
| Regression introduced by commit | ||||||||
| Regression level | ||||||||
| Review Assigned To | vmromanos | |||||||
| Support ticket | 38788 | |||||||
| OBNetwork customer | OBPS | |||||||
| Regression introduced in release | ||||||||
| Summary | 0031147: Search Key of Contracts is not automatically filled although you define a Document Sequence | |||||||
| Description | Search Key of Contracts is not automatically filled although you define a Document Sequence | |||||||
| Steps To Reproduce | As group admin role: Create a Document Sequence for F&B España, S.A. Set its name as Contract Auto Numbering = 'Y' Create a new contract and check the Search Key is not filled automatically as it is explained in the documentation: http://wiki.openbravo.com/wiki/Service_Contracts_Management#Contract_Header [^] | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  OBTHC_SEQUENCE_NEXT.xml [^] (1,635 bytes) 2015-10-14 13:33 | |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0081007) vmromanos (viewer) 2015-10-14 13:35 |
This is a feature that it's not included in the Service Contract Management (it was included as a customization in some coworking environments) However it can be easily developed as a customization: 1. Create a customer template where we can export the changes 2. Modify the application dictionary. Table:C_Project, Column=DEFAULTVALUE. Add the following defaultvalue (replace the OBTHC by the custom module db prefix): @SQL=SELECT '<' || OBTHC_SEQUENCE_NEXT('Contract', '@AD_Org_ID@', 'N') || '>' from dual 3. Create a new function similar to the one attached (replace the OBTHC by the custom module db prefix) 4. The configuration is the one explained in the steps to reproduce: Create a Document Sequence for the right organization Set its name as Contract Auto Numbering = 'Y' |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-10-14 10:28 | ngarcia | New Issue | |
| 2015-10-14 10:28 | ngarcia | Assigned To | => Triage Finance |
| 2015-10-14 10:28 | ngarcia | Support ticket | => 38788 |
| 2015-10-14 10:28 | ngarcia | OBNetwork customer | => Yes |
| 2015-10-14 10:28 | ngarcia | Issue Monitored: networkb | |
| 2015-10-14 13:33 | vmromanos | File Added: OBTHC_SEQUENCE_NEXT.xml | |
| 2015-10-14 13:35 | vmromanos | Review Assigned To | => vmromanos |
| 2015-10-14 13:35 | vmromanos | Note Added: 0081007 | |
| 2015-10-14 13:35 | vmromanos | Status | new => closed |
| 2015-10-14 13:35 | vmromanos | Resolution | open => invalid |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |