Decin t Feat

Embed Size (px)

Citation preview

  • 8/21/2019 Decin t Feat

    1/15

     

    Requiring Decimal or NumericFeatures

     An Oracle White Paper

     March2006

  • 8/21/2019 Decin t Feat

    2/15

     

    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

  • 8/21/2019 Decin t Feat

    3/15

    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 bemade required. However, for a Model that has many such Numeric Features, the overhead of thenecessary 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 includesan Option Feature, ‘MyIntegerFeature Required’, whose Minimum is defined as 0, and which has twoOptions.

    Requiring Decimal or Numeric Features Page 3

  • 8/21/2019 Decin t Feat

    4/15

     

     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

  • 8/21/2019 Decin t Feat

    5/15

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

    Requiring Decimal or Numeric Features Page 5

  • 8/21/2019 Decin t Feat

    6/15

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

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

    Requiring Decimal or Numeric Features Page 6

  • 8/21/2019 Decin t Feat

    7/15

    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

  • 8/21/2019 Decin t Feat

    8/15

    Edit the Unsatisfied Indicator of the Numeric Input.

    Requiring Decimal or Numeric Features Page 8

  • 8/21/2019 Decin t Feat

    9/15

    Change the Unsatisfied Indicator’s Associated Model Node to the Option Feature.

    Requiring Decimal or Numeric Features Page 9

  • 8/21/2019 Decin t Feat

    10/15

     Test.

    Requiring Decimal or Numeric Features Page 10

  • 8/21/2019 Decin t Feat

    11/15

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

    Requiring Decimal or Numeric Features Page 11

  • 8/21/2019 Decin t Feat

    12/15

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

    Requiring Decimal or Numeric Features Page 12

  • 8/21/2019 Decin t Feat

    13/15

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

    Requiring Decimal or Numeric Features Page 13

  • 8/21/2019 Decin t Feat

    14/15

    …and the configuration is now satisfied.

    Requiring Decimal or Numeric Features Page 14

  • 8/21/2019 Decin t Feat

    15/15

    Requiring Decimal or Numeric Feature

    March] 2006

     Author : Eog an O’Donnel l

    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 anyother warranties or conditi ons, whether expressed orally or implied

    in law, including impl ied 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 b y this document. This document

    may not be reproduced or t ransmitted in any form or by any means,

    electronic or mechanical, for any purpose, without our prior w ritten 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.