Hi Wai,
It was more a question. I also think UserLogin fits
Jacques
Le 14/08/2017 à 23:52, Wai a écrit :
Since entity:UserPreference provides a reference to entity:UserLogin, it
seems a good fit for what I need.
You implied that a party-based preference would be more appropriate. What
would
Since entity:UserPreference provides a reference to entity:UserLogin, it
seems a good fit for what I need.
You implied that a party-based preference would be more appropriate. What
would be the advantage of a party-based version.
If I were to use a party-based version then I would have to create
The confusion was my original posting containing 2 separate items.
1) request to add readWriteType and valueType into entity:SystemProperty.
2) A question about user specific properties.
This reply addresses item#1. I request to add 2 fields called readWriteType
(formerly called accessType) and
Hello Wai,
To try to better understand your examples, i will reformulate :
* A user can access a functionality using an oauth2 settings that is
configured only by an administrator ? But the concerned user can view it.
The way i would implement that is using *security group* granting
Hello Wai,
My apologies, I read, reread your response but I didn't understand your
example :(
Maybe I wrong but I already have the feel in your problematic isn't only
a technical problem and I'm more in favor the anaylse more
UserPreference, with party relation instead of change a low brick
Le 13/08/2017 à 07:10, Wai a écrit :
Is anyone interested in this enhancement?
Thanks
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Re-Request-for-enhance-entity-SystemProperty-tp4709235p4709546.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Hi Wai,
Is anyone interested in this enhancement?
Thanks
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Re-Request-for-enhance-entity-SystemProperty-tp4709235p4709546.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Regarding the need for a user specific entity to store user specific
settings, the structure for entity:UserPreference looks like a good match
for what I need. Seeing that there is only one value defined for
userPrefGroupTypeId (ie. GLOBAL_PREFERENCES), I can define USER_PREFERENCES
for this
There was also a second question for this posting. It was whether another
entity should be created to address party specific properties.
Arun Patidar-2, made reference to entity:PartyAcctgPreference. I shall take
a look at that to see if that would meet my needs.
Thanks.
--
View this message
Sorry it took so long to reply. I was not notified by Nabble that anybody
responded.When I use the term "access", it is _not_ related to ofbiz
security. Perhaps I should have used a different term to describe these
fields. I shall replace "access" with readWriteType.readWriteType means how
ofbiz
Hi Wai,
Can you give us some examples on the reason to set a specific access to
a property or have a UserProperty.
Because my first react would be says when you use a property, it's
always through a service or screen so the limit access is manage by
them. And for the user property it seems
Hi Wai,
This is typically the kind of questions which can go in dev ML, copying there
Thanks
Jacques
Le 07/08/2017 à 04:44, Wai a écrit :
I would like to get some comments on a request to enhance the SystemProperty
entity.
It would be useful to add the following fields:
field: access
12 matches
Mail list logo
