K-Rise Systems

NameValue Objects
Right now objects can only be pages and widgets
EASYCommerce Roles currently are something like:

OrderCreator
Objects: ShoppingCart, ReviewOrderPage, OrderConfirmationPage
OrderHistory
Objects: OrderHistory,OrderDetails, OrdersWidget

but then there are rules I need to keep that cant be in the roles.
Like the different participants in a feature called "orders for approval" where one person submits it for approval and another actually sends it to JDE.
Or in determining who can see the availability of an item and what value they see it as

I would like to set it up in the roles as:

OrdersForApproval
Objects
Object
Name: Approver
Value: True
Object
Name: Submitter
Value: True
Object
Name: CreateOrder
Value: True
Availability
Objects
Object
Name: DisplayType
Value: Label ---other possible values: NonZeroNumeric, Numeric


Example of using objects like it currently exists Example of using objects with name value option. Shows options like creating a config variable Currently there is a "UserDefined" type of object lists, but it cant have any children. Feature Suggestion 1: make UserDefined types of object lists able to have children or value selections. make the value selections able to use NVC to give possible selections.

This is a real example where role security was used that could have benefited from the above feature suggestion.

We had a case in easyitem base where we needed to categorize statuses. Each role is named after the section and workflow status it gives the user access to (with the exception of Final review which gives access to all sections). To name these in an intuitive way, they are named:
Status[Section name]

But EASYItem can also have multiple workflows. We could set it up like:

Workflow1
Workflow2
NewItemStatusMasterData
NewItemStatusCategoryCodes
NewItemStatusManufacturing
NewItemStatusPackaging
NewItemStatusCustomerService
NewItemStatusPrintMessage
NewItemStatusSupplementalItemData
NewItemStatusMediaObject
NewItemStatusXRef
NewItemStatusItemLocation
NewItemStatusUOMDefinition
NewItemStatusBillOfMaterials
NewItemStatusFinalReview

and then if you are a user that has access to workflow1 and some statuses, you are given those roles.

The downside is that workflow1 could only have some of the statuses, while workflow 2 has all of them.

So you could give a user these roles:
Workflow1
NewItemStatusSupplementalItemData

but then find out that SupplementalData status and section do not exist within workflow1 and youve made an invalid but very possible selection.

To bypass this and make the feature more intuitive, we would have to do one of the following:

1. create an admin page in the application. we cant use the IDE because it makes these impossible selections able to happen. In that application admin page, add validation so this is not possible. (lots of work - maybe equal to the time it takes to set up the easyitem app)
2. name the roles like this:
Workflow1StatusMasterData
Workflow1StatusCategoryCodes
Workflow1StatusManufacturing
Workflow1StatusPackaging
Workflow1StatusCustomerService
Workflow1StatusPrintMessage
Workflow1StatusSupplementalItemData
Workflow1StatusMediaObject
Workflow1StatusXRef
Workflow1StatusItemLocation
Workflow1StatusUOMDefinition
Workflow1StatusBillOfMaterials
Workflow1StatusFinalReview
This is real long and now I worry it might hit character limits, but is definitely not very readable.

I would have liked to instead give the role an object list that is userdefined which accepts an NVC list of the types of statuses in the workflow and is selectable as a drop down.