|
Notes |
|
|
(0010065)
|
|
svnbot
|
|
2008-11-07 09:18
|
|
Repository: openbravo
Revision: 9772
Author: vmromanos
Date: 2008-11-07 09:18:49 +0100 (Fri, 07 Nov 2008)
Fixed bug 0005872: Check calendar restrinctions after changing the organization's calendar
---
A branches/modularity/src-db/database/model/triggers/AD_ORG_STLE_TRG.xml
---
https://dev.openbravo.com/websvn/openbravo/?rev=9772&sc=1 [^]
|
|
|
|
|
|
Victor, please specify what exactly QA has to review |
|
|
|
|
When you are changing the calendar of a ready organization and this organization is marked as "Legal Entity", the new calendar must fulfill some rules:
- Every legal entity must have itself or an ancestor at least a calendar attached to it
- All the organizations that belong to the same legal entity must have a unique calendar
To test it you can, for example, create a new legal entity organization, assign to it a calendar (and an accounting schema) and set it as ready. Then remove the organization's calendar and try to save it; the application should not allow it.
Another test you can do is:
1- Create two calendars
2- Create one legal entity (summary level), assign to it the first calendar and set it as ready
3- Create another legal entity, assign to it the same calendar, make it a child of the previous one and set it as ready.
4- Then try to change the assigned calendar for these organizations to other calendar. The application should not allow it. |
|
|
|
|
QA has tested this case:
To test it you can, for example, create a new legal entity organization, assign to it a calendar (and an accounting schema) and set it as ready. Then remove the organization's calendar and try to save it; the application should not allow it |
|