GroupCustomerScreen

The Group Customer screen allows for the addition or editing of Group Customer clients. The business rule can be overridden at the Primary Company level.

The opening and closing tag of the MultiFields element. This element is used to turn on/off the multifields section. The statement can occur in any part of the Transaction/Screen XML.
GroupCustomerScreen Elements/Attributes
Element/Tag Attribute Definition Element/Attribute Value and Description

<GroupCustomerScreen>

 

The opening and closing elements of the screen rule

 

<AutomaticCustomerNumber>   Optional element: Allows generating automatic customer number when a new group customer is created as per the format specified in AutomaticCustomerNumber business rule. m

Yes: Allows generating automatic customer number when new group customer is created.

Optional: If a number is entered, then the value will be considered and recorded. If it is not entered, then the system will automatically generate a customer number.

No: Automatic customer number will not be generated when a new customer is created and allows the user to enter the customer number in the CustomerNumber field. If this element is not present, default is "No".

<DisplayPhoneScreen>  

Optional element:

Specifies whether the Phone screen should be enabled or disabled.

Yes: The Phone screen will be enabled.

No: The Phone screen will be disabled. This is the default value.

<Client>  

Required element:

This element defines the Client Type, ActivityPlan and Relationship Activity Plan for each Client Type.

 

TYPECODE

Required attribute:

Specifies the client's TypeCode

TypeCode: As defined in AsCodeClientType in the AsCode database table.

 

ACTIVITYPLAN

Required attribute:

Specifies the activity plan for the client type.

String:The Group Customer plan name.
RELATIONSHIPACTIVITYPLAN

Required attribute:

Defines which plan to use when the Relationship link is selected in OIPA.

.String: The relationship plan name. The group customer relationship transactions configured for the specified plan name will be available for group customer relationship activity processing.

<FixedFields>  

Optional element:

Standard fixed field configuration. See the Fixed Fields page for more information.

Note: Any column can from AsClient can be used with the fixed fields except ClientGUID and XML Data.

Note: Additionally the below fields will be available on the screen

  • PrimaryEnrollmentRelationsip
  • EnrollemntClassGroupType
  • HierarchyRelationship: This will identify the primary relationship type used to build a hierarchy of group customers. Its Primary Relationship types defined in AsCodePrimaryRelationshipType.

 

<Field>   The opening and closing tag for each Fixed Field being configured.  
<Display>   Provides the label text that will display on the screen. See the Fields Elements.
<DataType>   DataType of the field. See the Fields Elements.
<Expanded>     See the Fields Elements.
<Query>     See the Fields Elements.
<Hidden>   Indicates if fixed field should be hidden. See the Fields Elements.
<Disabled>   Indicates if fixed field should be visible, but no entry is allowed. See the Fields Elements.
<Required>   Indicates if the field is a required field for entry. See the Fields Elements.
<Subsections>  

Optional element:   

The fields configured inside subsections will be grouped together and the display can be collapsed or expanded.

 
<Subsection>   Required, Repeatable element:   

Defines an individual subsection. This element is required if the <Subsections> element is configured.

 
TITLE Optional attribute: 

Defines the title to be displayed on the subsection header.

String: The title to be displayed on the subsection header.
SECTIONNODES Optional attribute:

Specifies whether the subsection nodes should be expanded or collapsed.

Expanded: The nodes will be expanded.

Collapsed  The nodes will be collapsed. This is the default value.

<Fields>  

Optional element:

Standard field configuration. See the Fields page for more information.

 
<DisplayFormat>  

Required element:

The opening and closing tag for the <Parts> section, which designates Client Fields’ order, alignment, and any symbols or codes for the “finished”, viewable Client Name.

 
<Part>  

Required, repeatable element:

<Part> sub-elements define individual “parts” of the “finished” product, which will be visible in the Customer Detail table, the Group Customer Search Results table, and any other screen or peripheral where the Group Customer’s Name may be viewed or passed to.

String: Fixed columns of the AsClient, AsGroupCustomer and AsClientField tables that contain text data.
PRE

Optional attribute:

Specifies a character to concatenate to the beginning of the part's text

String: A comma, hyphen, space or other delimiting character.
POST

Optional attribute:

Specifies a character to concatenate to the end of the part's text

String: A comma, hyphen, space or other delimiting character.
<MultiFields>   Required: The opening and closing tag of the MultiFields element. This element is used to turn on/off the multifields section. The statement can occur in any part of the Transaction/Screen XML. Required element value: Yes
  RULE   A literal value referencing the exact rule name of a MultiFields business rule (AsBusinessRules.RuleName).

XML Schema

<GroupCustomerScreen>
<DisplayPhoneScreen>[Yes|No]</DisplayPhoneScreen>
<Client TYPECODE="" ACTIVITYPLAN="" RELATIONSHIPACTIVITYPLAN="">
<FixedFields>
<Field>
...
</Field>
</FixedFields>
<Subsections SECTIONNODES="[Collapsed|Expanded]">
<Subsection TITLE="" SECTIONNODES="[Collapsed|Expanded]">
<Fields>
...
</Fields>
</Subsection>
</Subsections>
<DisplayFormat>
<Part PRE="" POST="">
</Part>
</DisplayFormat>
</Client>
<MultiFields RULE="[business rule name]">Yes</MultiFields>
</GroupCustomerScreen>

Group Customer Screen XML Example

<GroupCustomerScreen>
<Client TYPECODE="20" ACTIVITYPLAN="Customer Plan" RELATIONSHIPACTIVITYPLAN="Relationship Plan">
............
............
...........
<AutomaticCustomerNumber>Yes</AutomaticCustomerNumber>
</Client>
</GroupCustomer>
 

 

 

Oracle Insurance Logo Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us