Navigation :

Profiles

Configuration - Profiles

The Oracle OCNCC CCS solution supports the concept of “profile blocks”. These profile blocks are binary-encoded tag/value fields. CCS Accounts (aka Subscribers) can have profiles, and so can CCS Account Types (aka Product Types) and other CCS objects.

The N2C5 product supports the display and management of information that is stored in these OCNCC profile blocks. Because the actual data stored in profile blocks can vary greatly from site to site, it is necessary to configure N2C5 to describe which profile tags should be visible.

This is done with the “profiles” element in the N2C5 Configuration file. The following sub-elements apply:

<acct_reference> : Configure “Subscriber” profile structure.
<acct_type> : Configure “Products” profile structure.

Note: The “acct_reference” configuration relates to OCNCC column CCS_ACCT_REFERENCE.PROFILE, while “acct_type” corresponds to OCNCC column CCS_ACCT_TYPE.PROFILE.

Example Configuration

An example configuring both profiles is:

<profiles>
  <acct_type>
    <group id="credit" name="Credit Card Limits" 
        collapsible="no" collapsed="no">
      <field tag="136" writers="*" name="Daily Limit $" 
        render="integer" type="long" minval="0" maxlen="4"/>
      <field tag="137" writers="*" name="Weekly Limit $" 
        render="integer" type="long" minval="0" maxlen="4"/>
      <field tag="138" writers="*" name="Monthly Limit $" 
        render="integer" type="long" minval="0" maxlen="4"/>
    </group>
  </acct_type>
  <acct_reference>
    <group id="default" name="Base Details" 
        collapsible="no" collapsed="no">
      <field tag="200" writers="*" name="First Name" 
        render="string" type="string"/>
      <field tag="201" writers="*" name="Last Name" 
        render="string" type="string"/>
      <field tag="37" writers="*"  name="Language" 
        render="language" type="long"/>
      <field tag="private_secret" writers="*" name="PIN" 
        render="password" type="string" maxlen="4" regex="^(|[0-9]{4}|\*\*\*\*)$"/>
      <field tag="204" name="First Recharge" 
        render="checkbox" type="byte"/>
    </group>
    <group id="credit" name="Credit Card Limits" 
        collapsible="no" collapsed="no">
      <field tag="136" writers="*" name="Daily Limit $" 
        render="integer" type="long" minval="0" maxlen="4"/>
      <field tag="137" writers="*" name="Weekly Limit $" 
        render="integer" type="long" minval="0" maxlen="4"/>
      <field tag="138" writers="*" name="Monthly Limit $" 
        render="integer" type="long" minval="0" maxlen="4"/>
    </group>
    <group id="announcement" name="Disable Pre-call Announcements"
        collapsible="no" collapsed="no">
      <field tag="203" writers="*" name="Balance" 
        render="checkbox" type="byte"/>
      <field tag="240" writers="*" name="Time" 
        render="checkbox" type="byte"/>
    </group>
    <group id="speed" name="Speed Dials"
        collapsible="yes" collapsed="yes">
      <field tag="231" writers="*" name="Speed Dial #1" 
        render="string" regex="^[0-9]*$" maxlen="20" type="string"/>
      <field tag="232" writers="*" name="Speed Dial #2" 
        render="string" regex="^[0-9]*$" maxlen="20" type="string"/>
      <field tag="233" writers="*" name="Speed Dial #3" 
        render="string" regex="^[0-9]*$" maxlen="20" type="string"/>
    </group>
    <group id="originating" name="Originating Filters" 
        collapsible="yes" collapsed="yes">
      <field tag="210" writers="*" name="Originating Whitelist Active" 
        render="checkbox" type="byte"/>
      <field tag="211" writers="*"  name="Originating Whitelist" 
        render="list" regex="^[0-9]*$" maxlen="20" type="tree"/>
      <field tag="212" writers="*"  name="Originating Whitelist Exceptions" 
        render="list" regex="^[0-9]*$" maxlen="20" type="tree"/>
      <field tag="213" writers="*" name="Originating Blacklist Active" 
        render="checkbox" type="byte"/>
      <field tag="214" writers="*"  name="Originating Blacklist" 
        render="list" regex="^[0-9]*$" maxlen="20" type="tree"/>
      <field tag="215" writers="*"  name="Originating Blacklist Exceptions" 
        render="list" regex="^[0-9]*$" maxlen="20" type="tree"/>
    </group>
    <group id="info2" collapsible="no" collapsed="no">
      <field tag="414" name="Account Sub-Type:" render="span" type="string"/>
    </group>
  </acct_reference>
</profiles>

Grouping Profile Items

For each profile type (“acct_type” or “acct_reference”) specify one or more “group” elements. Each group element has the following attributes.

id = “credit” : Unique prefix to identify this group in the HTML document. Lowercase characters and numbers. Use underscore “_” instead of spaces.
name = “First Recharge” : Human-readable label to show next to this group.
collapsible = “no” : Is the group collapsible? Specify “yes”/“no”. Default = “no”.
collapsed = “no” : Is the group collapsed when first shown? Specify “yes”/“no”. Default = “no”.

Pre-Existing Groups

Note: The group will be created in the “profile” area if it does not already exist. Some pre-existing groups already exist in the standard templates. For example, two pre-existing subscriber groups are available:

Subscriber Group “info1” : This is the second column in the header area, which starts with the “Serial Number:” label. Specify the “info1” group for “acct_reference” profile fields to add profile fields to this column.
Subscriber Group “info2” : This is the third column in the header area, which starts with the “Account Class:” label. Specify the “info2” group for “acct_reference” profile fields to add profile fields to this column.

The example configuration adds tag 414 to the pre-existing “info2” group in the header area.

The same pre-existing groups are also available on the “Products” page.

Products Group “info1” : This is the second column in the header area, which starts with the “Partition Name:” label. Specify the “info1” group for “acct_type” profile fields to add profile fields to this column.
Products Group “info2” : This is the third column in the header area, which starts with the “Pre-Use Expiry:” label. Specify the “info2” group for “acct_type” profile fields to add profile fields to this column.

Field Configuration

Within each group, one or more fields may be specified. E.g.

<field tag="136" writers="*" name="Daily Limit $" 
  render="integer" type="long" minval="0" maxlen="4"/>

The attributes for each field are:

tag = “136” : Decimal tag number in the profile. Refer to OCNCC documentation for further information on profile encoding.
writers = “*” : Comma-separated list of SMF Templates permitted to edit this field. Specify “*” to allow all SMF Users to edit.
name = “Daily Limit $” : Human-readable label to show next to this field.
type = “long” : How is the profile value stored in the profile? Options are “long”, “byte”, “string”, “profile” or “tree”.
render = “integer” : How should the contained data be rendered on the page? Options are “checkbox”, “language”, “password”, “string”, “integer”, “span” or “list”.
maxlen = “4” : Optional maximum length for strings.
minlen = “0” : Optional minimum value for integers.
maxlen = “2000” : Optional maximum value for integers.

Note: The “profile” element is a custom parameter for N2C5. It is not part of the base Jarvis framework.