[
https://issues.apache.org/jira/browse/OFBIZ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935698#comment-13935698
]
Heidi Dehaes edited comment on OFBIZ-5573 at 3/25/14 3:55 PM:
--------------------------------------------------------------
Hello Adrian, Ioannis,
I propose the following roles and i added also the first possible two use cases.
Open for comments !!
Actors Roles Privileges
Type
an external vendor VENDOR ?
Party
an administrator VENDOR_ADMIN ? Party
the customer CUSTOMER ?
Party
the e-com company COMPANY ?
Partygroup
Use Case 1:
Title:
A user with role VENDOR logs in into the ecommerce ofbiz site.
Conditions:
- The user clicks on the button login on the homepage of the ecommerce site.
- The role VENDOR is already created by the ofbiz administrator and privileges.
- A special facility for the inventory is created by the administrator for the
vendor products. A facility of type "vendor" for example.
Action:
- The user logs in with his userid and password.
When he clicks on the SUBMIT button, a webpage appears with the following data.
- button "list and update categories"
- button "list and update inventory"
- button "list products"
Use Case 2:
Title: A user with role VENDOR_ADMIN logs into the ecommerce ofbiz site.
Conditions:
- The user clicks on the button login on the homepage of the ecommerce site.
- The role VENDOR_ADMIN is already created by the ofbiz administrator and
privileges.
- A special facility for the inventory is created by the administrator for the
vendor products. A facility of type "vendor" for example.
Action:
- The user logs in with his userid and password.
When he clicks on the SUBMIT button, a webpage appears with the following data.
- button "list and update categories"
- button "list and update inventory"
- button "list products"
- button "view and update registration information"
- button "delete vendor"
Use Case 3:
Title: A user with role VENDOR chooses and clicks the button CATALOG_VENDOR in
the menu.
Conditions:
- The user is logged in as VENDOR.
- The user sees a few buttons above in the horizontal menu of the page. One of
this is CATALOG_VENDOR button.
Actions:
- The Catalog Vendor Administration Page appears.
- This page is similar to the Catalog Administration Main Page in Ofbiz. It is
however simplified.
- Only categories which are VENDOR enabled, are visualized.
- Buttons which are available on the page are : EDIT CATEGORY.
There is no Create Category button available.
- There is also a screenlet available with BROWSE CATALOGS/CATEGORIES VENDOR.
- There is a screenlet available with "PRODUCTS FROM THIS CATEGORY".
- The Catalog Vendor has the following Tab's available in the horizontal menu:
MAIN & PRODUCTS.
Use Case 4:
Title: A user with role VENDOR enters a category name and clicks on the button
EDIT CATEGORY.
Condition:
- The user is logged in as a vendor.
- The user is in the page CATALOG VENDOR MANAGER under the tab CATEGORIES and
further under the tab CATEGORY.
- The user can find this page also by clicking on the EDIT CATEGORY button in
the CATALOG VENDOR ADMINISTRATION PAGE.
Action:
- All fields are greyed. They are in mode read-only.
- The user has the following buttons available in the horizontal menu:
CATEGORY, PRODUCTS.
- He is able to click on the button PRODUCTS.
Use Case 5:
Title: A user with role VENDOR is in the products page and clicks on a product
line or clicks on the button create product in the category.
Conditions:
The user is logged in as VENDOR.
The user is in the page PRODUCTS (from the catalog vendor manager page) which
he has selected in use case 4.
Actions:
- All products are hidden but the vendor products.
- The buttons in the horizontal menu above are : CREATE PRODUCT IN CATEGORY
- The data shown are: <Product Name, Id>, <From Date Time>, <Thru Date Time> ,
<Sequence>, <Quantity> , <Comments>.
- The buttons beside the product lines are DELETE and UPDATE.
- The user is able to click on a product line in order to enter the PRODUCT
page.
Use Case 6:
Title: User with role VENDOR creates a vendor product.
Conditions:
- The user is logged in as a VENDOR.
- The user is in the catalog vendor management subpage: "create product in
category".
Actions:
- The user sees fields "Internal Name", "Product Name", "Short Description",
"Default price".
- The user has to fill in the fields or ??????????? has to accept the proposed
Internal Name and Product Name. He fills in the short description and default
price.
Use Case 7:
Title: The "product edit" page.
Conditions:
- The user is logged in as vendor.
- The user is on the PRODUCT VENDOR EDIT page.
Actions:
- On the product vendor edit page following items are taken over from the
original
product edit page:
- Wording and Comment
- Dates
- Amount
- Measures
- Shipping
- Shopping Cart
-
was (Author: info.ola...@gmail.com):
Hello Adrian, Ioannis,
I propose the following roles and i added also the first possible two use cases.
Open for comments !!
Actors Roles Privileges
Type
an external vendor VENDOR ?
Party
an administrator VENDOR_ADMIN ? Party
the customer CUSTOMER ?
Party
the e-com company COMPANY ?
Partygroup
Use Case 1:
Title:
A user with role VENDOR logs in into the ecommerce ofbiz site.
Conditions:
- The user clicks on the button login on the homepage of the ecommerce site.
- The role VENDOR is already created by the ofbiz administrator and privileges.
- A special facility for the inventory is created by the administrator for the
vendor products. A facility of type "vendor" for example.
Action:
- The user logs in with his userid and password.
When he clicks on the SUBMIT button, a webpage appears with the following data.
- button "list and update categories"
- button "list and update inventory"
- button "list products"
Use Case 2:
Title: A user with role VENDOR_ADMIN logs into the ecommerce ofbiz site.
Conditions:
- The user clicks on the button login on the homepage of the ecommerce site.
- The role VENDOR_ADMIN is already created by the ofbiz administrator and
privileges.
- A special facility for the inventory is created by the administrator for the
vendor products. A facility of type "vendor" for example.
Action:
- The user logs in with his userid and password.
When he clicks on the SUBMIT button, a webpage appears with the following data.
- button "list and update categories"
- button "list and update inventory"
- button "list products"
- button "view and update registration information"
- button "delete vendor"
Use Case 3:
Title: A user with role VENDOR chooses and clicks the button CATALOG_VENDOR in
the menu.
Conditions:
- The user is logged in as VENDOR.
- The user sees a few buttons above in the horizontal menu of the page. One of
this is CATALOG_VENDOR button.
Actions:
- The Catalog Vendor Administration Page appears.
- This page is similar to the Catalog Administration Main Page in Ofbiz. It is
however simplified.
- Only categories which are VENDOR enabled, are visualized.
- Buttons which are available on the page are : EDIT CATEGORY.
There is no Create Category button available.
- There is also a screenlet available with BROWSE CATALOGS/CATEGORIES VENDOR.
- There is a screenlet available with "PRODUCTS FROM THIS CATEGORY".
- The Catalog Vendor has the following Tab's available in the horizontal menu:
MAIN & PRODUCTS.
Use Case 4:
Title: A user with role VENDOR enters a category name and clicks on the button
EDIT CATEGORY.
Condition:
- The user is logged in as a vendor.
- The user is in the page CATALOG VENDOR MANAGER under the tab CATEGORIES and
further under the tab CATEGORY.
- The user can find this page also by clicking on the EDIT CATEGORY button in
the CATALOG VENDOR ADMINISTRATION PAGE.
Action:
- All fields are greyed. They are in mode read-only.
- The user has the following buttons available in the horizontal menu:
CATEGORY, PRODUCTS.
- He is able to click on the button PRODUCTS.
Use Case 5:
Title: A user with role VENDOR is in the products page and clicks on a product
line or clicks on the button create product in the category.
Conditions:
The user is logged in as VENDOR.
The user is in the page PRODUCTS (from the catalog vendor manager page) which
he has selected in use case 4.
Actions:
- All products are hidden but the vendor products.
- The buttons in the horizontal menu above are : CREATE PRODUCT IN CATEGORY
- The data shown are: <Product Name, Id>, <From Date Time>, <Thru Date Time> ,
<Sequence>, <Quantity> , <Comments>.
- The buttons beside the product lines are DELETE and UPDATE.
- The user is able to click on a product line in order to enter the PRODUCT
page.
Use Case 6:
Title: User with role VENDOR creates a vendor product.
Conditions:
- The user is logged in as a VENDOR.
- The user is in the catalog vendor management subpage: "create product in
category".
Actions:
- The user sees fields "Internal Name", "Product Name", "Short Description",
"Default price".
- The user has to fill in the fields or ??????????? has to accept the proposed
Internal Name and Product Name. He fills in the short description and default
price.
> Implementation of VENDOR MANAGEMENT software in Ofbiz in ecommerce component
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-5573
> URL: https://issues.apache.org/jira/browse/OFBIZ-5573
> Project: OFBiz
> Issue Type: Improvement
> Components: specialpurpose/ecommerce
> Environment: Software platform, Ecommerce component, Party Component
> Reporter: Heidi Dehaes
> Priority: Trivial
> Attachments: vendor_spec-1.pdf, vendor_spec.doc, vendor_spec.doc
>
>
> Wants to initiate the development of a VENDOR ENVIRONMENT AND MANAGEMENT for
> ofbiz in the ecommerce component as exists also in the Amazon ecommerce
> websites. An external vendor must be able to put products and sell the
> products on the ecommerce platform of the owner.
> Involved:
> - ioannis ntantis <giannis...@gmail.com>
> - Heidi & Eric <info.ola...@gmail.com>
> Requirements:
> - ... to be added.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
