OBEROn - Bug Trace - ALEXIA PLM
Viewing Issue Advanced Details
56 General feature N/A 2011-05-16 13:32 2011-05-16 15:08
g_prajeesh  
 
normal  
new  
open  
none    
none  
0000056: Preference Module for Application

Preference can be of two type

USER Preference - Preference that can be specific to individual user / team /assignment (USER)

SYSTEM Preference - Preference applied to the system for application behaviour( SYSTEM)


Preference can be represented in a unique way


CONTEXT-PREFERENCETYPE-OVERRIDABLE-PREFERENCENAME=VALUE

CONTEXT - Consist of PARENT-CHILD Heirarchy ( APPLICATION-MODULE-SUBMODULE..-USERID/TEAMID/ASSIGNMENTID)

eg. Assume Preference Type is SYSTEM and defined at APPLICATION Level

ALEXIA-SYSTEM-TRUE-PN1=value1. This means that the the preference PN1 is applicable to Application "ALEXIA" and its sub module

and sub module can override it's value


so if I define following CONTEXT

ALEXIA-ALEXIAPPM (Parent Node-ChildNode)

ALEXIAPPM-SUB1 (Parent Node- Child Node)

I can override at these context


ALEXIA-ALEXIAPPM-SYSTEM-TRUE-PN1=Value2

and

ALEIXAPPM-SUB1-SYSTEM-FALSE-PN1=Value3



in this case, assume I defined following CONTEXT

ALEXIAPPM-SUB2

SUB1-SUBSUB1

Here the PN1 can be only overriden for ALEXIAPPM-SUB2 and not for SUB1-SUBSUB1( Reason is in ALEIXAPPM-SUB1-SYSTEM-FALSE-PN1, oveeridable= FALSE )

The overrided value can be as follows

ALEIXAPPM-SUB1-SYSTEM-FALSE-PN1=Value4

Now Assume a PN2 of type USER and defined at Application Level


ALEXIA-USER-TRUE-PN2=Value1

So when we as for PN2 for a Particular User say user1, it will get value1


if user1 override the value

ALEXIA-USER-TRUE-user1-PN2=value5
Issue History
2011-05-16 13:32 g_prajeesh New Issue
2011-05-16 15:08 g_prajeesh Project Oberon Platform => ALEXIA PLM

There are no notes attached to this issue.