|
|
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 |
|