ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BJ Freeman <bjf...@free-man.net>
Subject Re: hiding functionality in ofbiz.
Date Tue, 26 Apr 2011 15:15:10 GMT
I agree that many application are a hog pog, no business sense to them,
just functionality.
I vote for Roles permissions, with role groups. This way a company can
define  a beginner, to any roles and/or groups they want.

But first I think a definition, of the intutiveness of the UI should be
addressed, which goes against the current thinking of just putting up
functtinoality based on the Enitity layout.

If the business flow is in the UI there won't be much need for hiding
functionality since the more complex functions would be naturally hidden.

So if the permissions are in the menu then you don't have to go down
into the pages, though one can. Just have to have permission on the
pages which has sort of fallen through the cracks.

This should be done at the Menu level as a I suggested many years ago.

Adrian Crum sent the following on 4/26/2011 7:20 AM:
> The problem with the Party component isn't that it's too advanced for a
> beginning user. The problem is it is poorly designed, or has no design
> at all. The Party component has become a dumping ground for all kinds of
> things that don't belong there. Not only does that make it hard to use,
> it also makes it dependent on every other component in the project.
> -Adrian
> On 4/25/2011 11:27 PM, Hans Bakker wrote:
>> I agree, this function is not so suitable for the order and facility
>> components.
>> I was however thinking of the product and party component. These are far
>> to big for the starting user and here it could be a big advantage to
>> show only a limited functionality....
>> Regards,
>> Hans
>> On Mon, 2011-04-25 at 22:57 -0700, David E Jones wrote:
>>> Yeah, that's kind of what I was thinking too. If only we had the
>>> Moqui style authorization stuff in OFBiz... ;)
>>> -David
>>> On Apr 25, 2011, at 10:13 PM, Sam Hamilton wrote:
>>>> This is starting to sound to me like user permissions that can be
>>>> customised to show or hide functions? Then it can be customised if a
>>>> organisation wants to or left default.
>>>> Rather than beginner, intermediate and full it would be role based
>>>> e.g. Warehouse Picker, Warehouse Packer, PO Creator, PO Approver,
>>>> Product Manager etc.
>>>> Sam
>>>> On 26 Apr 2011, at 02:09, David E Jones wrote:
>>>>> Is it even possible to have a single decision about what would go
>>>>> in each level, or would this tend to vary in different user
>>>>> organizations?
>>>>> If this were something configurable would it need to be on a screen
>>>>> level, on a form field level, or something even more detailed?
>>>>> -David
>>>>> On Apr 25, 2011, at 10:50 AM, Jacques Le Roux wrote:
>>>>>> I like the idea and have already suggested
>>>>>> http://markmail.org/message/rrre2cslfou32vnp
>>>>>> http://markmail.org/message/7wzti5asolef5njz)
>>>>>> Also I tend to agree with Ruth: the difficulties is to categorize
>>>>>> features before, I begin in French long time ago, never ended...
>>>>>> other priorities came along...
>>>>>> http://www.les7arts.com/assist/OFBiz/Principales%20Caracteristiques%20Fonctionnelles.htm
>>>>>> Jacques
>>>>>> From: "Ruth Hoffman"<rhoffman@aesolves.com>
>>>>>>> Hi Hans:
>>>>>>> IMHO, you would just be adding to the confusion. How does someone
>>>>>>> know if they are a beginner? And, what are the basic features
>>>>>>> each component? Who decides basic vs. full featured?
>>>>>>> On the other hand, now that I'm thinking about it, maybe this
>>>>>>> a good idea. In the process of deciding what is basic and what
>>>>>>> "full featured" you will need to do some documenting. At a
>>>>>>> minimum you will need to record functional capabilities on a
>>>>>>> component by component level. A much needed addition to the OFBiz
>>>>>>> community if you ask me!
>>>>>>> Just my 2 cents.
>>>>>>> Ruth
>>>>>>> On 4/25/11 11:50 AM, Hans Bakker wrote:
>>>>>>>> In general it is accepted that OFBiz is having too much
>>>>>>>> functionality
>>>>>>>> which can be really overwhelming.
>>>>>>>> We are thinking about introducing a user preference in function
>>>>>>>> levels:
>>>>>>>> for example:
>>>>>>>> 1. beginner
>>>>>>>> 2. intermediate
>>>>>>>> 3. full feature.
>>>>>>>> The beginner will only see the basic features in the components
>>>>>>>> however
>>>>>>>> the system will be fully functional.
>>>>>>>> The intermediate person will see more functions but not
>>>>>>>> everything..
>>>>>>>> And the full feature will show everything what is there.
>>>>>>>> Anybody any opinions or thoughts about this?
>>>>>>>> Regards,
>>>>>>>> Hans

View raw message