Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0004716 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Openbravo ERP] 03. Procurement management | trivial | always | 2008-08-26 14:14 | 2009-02-05 06:32 | |||
| Reporter | RenateNieuwkoop | View Status | public | |||||
| Assigned To | pjuvara | |||||||
| Priority | normal | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | 2.40beta | 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 | 0004716: Requisition and Manage Requisitions form are almost identical | |||||||
| Description | There are two screen, the Requisition form and Manage Requisitions form. The only function the Manage Requisitions form has is that there is a button to generate the Purchase Order. However, when you click 'Create a New Record' you see the exact same screen as the Requisition form. After the Purchase order has been created, the screens look actually identical | |||||||
| Proposed Solution | The two screens should be just one screen as far as I see it. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0008768) RenateNieuwkoop (reporter) 2008-08-27 17:12 |
I read now that the second screen is for restricted access, so that makes sense. However, there should now be a 'new record' button on the manage requisition screen |
|
(0013162) pjuvara (reporter) 2009-02-05 06:32 |
Renate, I apologize for closing this request after such a long time and after having it initially acknowledged. There is a strong reason why we need two windows that look similar and this is the intended behavior. Please let me explain. The business flow that we intend to support is one where employees can request products and services to be purchased by the enterprise on their behalf. These could be, for instance, raw materials that the VP of manufacturing needs to produce, products purchased for resale, but also expense items such as office supply or services such as legal services, consulting services, etc. One of the requirements to support this flow is that only the employee that requested the product or service and the purchasing agent that will process it are able to view the requisition. For instance, if I request to purchase a new set of business cards, only myself and the person who is responsible to find the most appropriate printing company and order the card need to know about it. For this reason, we have introduced two windows who look similar but have different behavior. - Requisitions: where employee create requisitions; to handle the above requirement, only the user who created the record is able to see it - Manage Requisitions: where purchasing agents can see and process all the requisitions that have been created according to the normal organization based security. Please notice that, while in an unconfigured system this might look a bit confusing because both windows sit side by side, in a properly configured system these two windows would not belong to the same role. You should configure the system with at least two roles: - Employee: having access to Requistions - Purchasing agent: having access to Manage Requisition Please feel free to reopen this feature request if you disagree with this explanation. Paolo |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-08-26 14:14 | RenateNieuwkoop | New Issue | |
| 2008-08-26 14:14 | RenateNieuwkoop | Assigned To | => cromero |
| 2008-08-26 14:15 | RenateNieuwkoop | sf_bug_id | 0 => 2075752 |
| 2008-08-27 17:12 | RenateNieuwkoop | Note Added: 0008768 | |
| 2008-11-10 13:10 | cromero | Assigned To | cromero => pjuvara |
| 2008-11-16 18:45 | pjuvara | Tag Attached: Usability | |
| 2008-11-16 18:45 | pjuvara | Status | new => acknowledged |
| 2009-02-05 06:29 | pjuvara | Status | acknowledged => scheduled |
| 2009-02-05 06:29 | pjuvara | fix_in_branch | => trunk |
| 2009-02-05 06:32 | pjuvara | Regression testing | => No |
| 2009-02-05 06:32 | pjuvara | Status | scheduled => closed |
| 2009-02-05 06:32 | pjuvara | Note Added: 0013162 | |
| 2009-02-05 06:32 | pjuvara | Resolution | open => no change required |
| 2009-02-05 06:32 | pjuvara | Tag Detached: Usability | |
| 2009-02-05 06:32 | pjuvara | Relationship added | related to 0007311 |
| 2009-02-05 06:43 | pjuvara | Relationship added | related to 0007374 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |