Value rule of an attribute in WPC specification has precedent over the effect of "My Settings" customization.
In WPC, whenever there is a value rule in effect for an attribute, it will take precedence over the changes in My Settings. Generally, users can do one of the following:
* go to Home > My Settings to adjust the customized screen settings, such as time format, language, and so on.
* achieve a similar type of result using the value rule scripts when defining an attribute's specification.
However, if the setting in the value rule contradicts with that from My Settings, the result of the value rule will supersede the action performed in My Settings.
User can adjust, for example, the time/date format in My Settings. In this case, let us assume that the setting has been changed from US format (MM/DD/YYYY) to International format (DD/MM/YYYY). User will now be thinking that he/she will see the International time/date format in the item edit screen.
However, in the primary specification of this attribute, there is a value rule that affects the time display - either through an external trigger script or other type of scripting, and the script is written so that the time/date display will be in the US format.
The result is that the time/date display will be in US format (MM/DD/YYYY)- as according to the value rule. The changes in the time/date format in My Settings will have no effect on this attribute.
Note: This technote is specifically for the Time/Date format issue, but can generally be applicable to various issues in My Settings as well.
Resolving the problem
If a user wants to prevent the issue from happening, there are two ways to do so:
1. Do not use Value Rule scripts in the primary specification that will contradict with the My Setting's changes. Be sure to pay close attention if an external trigger script is involved.
2. Use operations from the WPC API library for Value Rule scripts. For example, user can use "Dates( )" in the value rule script. Changes in My Setting will now be reflected in the attribute.
This is NOT a WPC defect, but the way WPC has been designed to work.
As stated above, for illustration purpose, this example uses the time/date format, but this situation applies to other parameters in My Settings too.
|Information Management||InfoSphere Master Data Management Server for Product Information Management||AIX, Linux, Solaris||6.0, 9.0, 9.1|
|Information Management||InfoSphere Master Data Management Collaboration Server||AIX, Linux, Solaris||10.0|
Infosphere Master Data Management Collaboration Server
MDM Server for PIM
WebSphere Product Center
InfoSphere MDM Server for PIM
InfoSphere Master Data Management Server for Product Information Management
More support for:
WebSphere Product Center
Software version: 5.3.2
Operating system(s): AIX, Linux, Solaris
Reference #: 1259483
Modified date: 2012-11-02