Vous êtes sur la page 1sur 15

Requiring Decimal or Numeric

Features
An Oracle White Paper
March 2006

Requiring Decimal or Numeric Features

Introduction ....................................................................................................... 3
Making an integer feature a required input in oracle configurator............. 3

Requiring Decimal or Numeric Features

Page 2

Requiring Decimal or Numeric Features

INTRODUCTION

[he following screenshots demonstrate a workaround for making an Integer Feature a required input in Oracle
Configurator. The same scenario is equally applicable to Decimal Features.
MAKING AN INTEGER FEATURE A REQUIRED INPUT IN ORACLE CONFIGURATOR

The approach is reasonable when there is a limited number of Numeric Features that need to be
made required. However, for a Model that has many such Numeric Features, the overhead of the
necessary Model Structure and Rules can quickly become burdensome.
For the example, a Boolean Feature, Require MyIntegerFeature?, specifies that the Integer Feature,
MyIntegerFeature, is required. This could be any condition, however. The structure also includes
an Option Feature, MyIntegerFeature Required, whose Minimum is defined as 0, and which has two
Options.

Requiring Decimal or Numeric Features

Page 3

Two rules are utilized, one to specify when the Option Feature is required, and another to specify
when it has been satisfied.

Requiring Decimal or Numeric Features

Page 4

The first rule specifies that when the condition for requiring the Integer Feature is true, then the
Option Feature is turned on (that is, Minimum dynamically goes from 0 to 1).

Requiring Decimal or Numeric Features

Page 5

The second rules specifies that once a value has been entered for the Integer Feature, one of the
Option Features Options gets selected, thereby satisfying the Option Feature.

To this point, the workaround will enforce that the configuration is invalid unless a value is specified
for the Integer Feature. That is, if the Integer Feature is required but a value is not entered, the
Summary Page will note that the configuration is not valid. However, the Integer Feature will not be
displayed as being required in the User Interface without further modifications.

Requiring Decimal or Numeric Features

Page 6

In the User Interface, go to the control that represents the Integer Feature, select it, and perform the
Convert Template Reference action on it.

Requiring Decimal or Numeric Features

Page 7

Edit the Unsatisfied Indicator of the Numeric Input.

Requiring Decimal or Numeric Features

Page 8

Change the Unsatisfied Indicators Associated Model Node to the Option Feature.

Requiring Decimal or Numeric Features

Page 9

Test.

Requiring Decimal or Numeric Features

Page 10

When the condition requiring the Integer Feature becomes true, the Integer Feature displays as a
required input.

Requiring Decimal or Numeric Features

Page 11

Looking at the Configuration Summary, we see that the configuration is unsatisfied, pending an input
to the Integer Feature.

Requiring Decimal or Numeric Features

Page 12

Once a value is specified for the Integer Feature, its Unsatisfied Indicator disappears

Requiring Decimal or Numeric Features

Page 13

and the configuration is now satisfied.

Requiring Decimal or Numeric Features

Page 14

Requiring Decimal or Numeric Feature


March] 2006
Author: Eogan ODonnell
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright 2007, Oracle. All rights reserved.
This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.