These are the mods I'd like to commit:
a) ecommerce>wishlists (dropdowns): display all the shopping lists
created by the logged in user + the shopping lists with isPublic=Y
b) ecommerce>wishlists (edit screen): hide the isPublic flag and always
set it to N (i.e. ecommerce users cannot create public lists)
c) (not completely sure about this): add the field
ShoppingListType.parentShoppingListTypeId (hmmm... we need a shorter
name here... any ideas?) and add seed data for new shopping list type:
I'd leke to create two parent types "PUBLIC_LIST" and "INTERNAL_LIST"
and then associate to the former the list types available to ecommerce
users (when they create a shopping list) and to the latter the ones that
are only available when the lists are created in the backend (e.g.
"Special Purpose").
What do you think?
Jacopo
Jacopo Cappellato wrote:
What is the best way to model a shopping list that is public, i.e it is
available to all the users (not just the one that created it)?
I've noticed that the ShoppingList.isPublic flag is not used in any
process. We could use this flag, but I don't think that we should allow
an ecommerce user to set the flag to Y (the list will then appear in the
drop down boxes for all the users): it should really be done by a manager.
What is the best way to model a shopping list that is available only to
a limited set of users?
I could use a special type for the ShoppingList and add custom code to
show the lists of that type only to qualified users but, again, I don't
like the idea of letting the ecommerce users select the type of the
shopping list: we should at least define a way to separate the publicly
available types from the backend only ones (adding a flag to the
ShoppingListType? or using a parent type to group them together?)
I'd love to get your feedback on this because I'd like to provide some
enhancements (if needed) soon.
Thanks,
Jacopo
