Segment Definition to include User Enterable and Static fields
Currently in case of Group customer s ‘Plan Segment’ section, when a user edits a segment, the details displayed on the screen for editing are the actual Segment fields and the same is saved under AsPlanSegmentNameFields table. This data currently is obsolete as the data is pertaining to a specific segment instance and not specific to a Plan Segment Name. This functionality is enabled to capture PlanSegmentName level fields based on the configuration of PlanSegmentName definition
Prototype Configuration DetailOverview
Currently in case of Group customers ‘Plan Segment’ section when a user edits a segment, the details displayed on the screen for editing are the actual Segment fields and the same is saved under AsPlanSegmentNameFields table.
This data currently is obsolete as the data is pertaining to a specific segment instance and not specific to a Plan Segment Name.
This functionality will enable us to capture PlanSegmentName level fields based on the configuration of PlanSegmentName definition.
PrerequisitesUser should have access to the BaseCoverageBasic Segment of Group Prototype Product.
Changes to Existing ItemsSegment name: BaseCoverageBasic
New Item: PlanSegment
Company name: Prototype Group Child Company
Product name: Group Prototype Product
Configuration DetailsBaseCoverageBasic Segment and PlanSegment :Existing BaseCoverageBasic segment is used for the prototype configuration. Along with the existing configuration of the BaseCoverageBasic segment which will be in the Xml section, PlanSegmentFields, PlanSegmentEvents and PlanSegment tabs are added.
When the user load the Segment in Palette it will be having three more tabs along with the existing ones:PlanSegmentFields – Provides the visual editor for PlanSegment Fields
PlanSegmentEvent - Provides the option for PlanSegment Action/events configured
PlanSegment - Provides the configuration of PlanSegment.
Xml under Segment tab will go in XMLData column as the way it does today
ResolveRule option will give two option i.e Segment and PlanSegment to allow user choose which rule to resolve.
SegmentMaturityAge : Specify the duration of the Segment which is set to 60.
In the Application when the user navigates to the 'PlanSegment' section of the Agreement of a GroupCustomer, user should be able to view the fields SegmentMaximumFaceAmount and SegmentMaturityAge in PlanSegment section instead of the fields configured the Xml section of the Segment.