Order Entry Screens Driven by PPfA

Overview

Certain AFFIRM Order Entry screens are driven by PPfA. Below is a description of the fields on the Participants, Participant Details, Features, Feature Details, and Sub Accounts tabs that are driven by PPfA.

Note: See our article on updating PPfA to version 2.37.

Participants Tab

The Participants tab is used to gather the names of all Participants (except the Order Taker and the Agent) that have the role on the application being added. The PPfA does not control the format or content of the name string fields, including the Prefix, First Name, Middle Initial, Last Name, Suffix or Entity Name fields. General AFFIRM business rules control format, optional/required, etc.

Role Drop Down

The Role drop down is controlled by the PPfA. Each Primary Role / Secondary Role / Additional Role drop down list box will contain the Description of the RelatedRole type codes which are available in the Ownership instance which “survived” the PPfACutDown for the transaction being processed. The list of Roles which may be selected are then presented on the Participants tab in the role drop down.

Note: Affirm assumes the Annuitant is always a person, so this Role will only appear in the Individuals section of the page. Regardless of the PPfA, the Owner Type will determine in which section of the page the Owner Role is available. If the user selects a Person ownership type (e.g. Individually Owned) on the Product tab, then the Owner role will appear in the Individuals drop down. If an entity ownership type, then the Entities section will contain the Owner role.

Participant Details Tab

The Participant Detail tab is used to gather the remaining information about all Participants (except the Order Taker and the Agent) that have the role on the application being added.

Relationship To Field

Relationship To: The PolicyProduct\ParticipantBasedOn controls if the “Relationship To Owner” and/or “Relationship To Annuitant” fields are present on the Participant Details page.

Relationship To Owner: will be visible and required if the ParticipantBasedOn is equal to “Owner” or “Both Owner and Annuitant” or equal to “Owner if Person” and the Owner Type (from the Order Info tab) is Person.
Relationship to Annuitant: will be visible and required if the ParticipantBasedOn is equal to “Annuitant” or “Both Owner and Annuitant” or equal to “Owner if Person” and the Owner Type (from the Product tab) is not a Person OwnershipType.

Relationship To Drop Down

The contents of the Relationship To drop down is also controlled by the PPfA and contains a list of all relationships that are available in the PPfA for all Roles the Participant plays.

For example, if the Participant is the Annuitant and Beneficiary, and the AllowedRelationship\RelationshipCC between Owner and Annuitant contains relationships A, B, C, D and E, and the AllowedRelationship\RelationshipCC between Owner and Beneficiary contains relationships A, B, C, D and F, then the Relationship To box will contain A and B and C and D (E and F will not, since they are not available to both roles).

If the Relationship To Owner field is present and the Participant is the Owner (and has no other role), “Self” will be automatically selected and the field will be greyed out.

If only one relationship is available, the relationship will be selected and the Relationship To Owner field will be greyed out.

The Ownership/IrrevokableInd indicates if the carrier allows beneficiaries to be designated as irrevocable. This property is used by AFFIRM to determine if the Irrevocable? radio button on the Participant Details tab is enabled or not enabled for Participants that are beneficiaries or contingent beneficiaries. The default of this field is No. If IrrevokableInd = False, then the radio buttons will be read-only; if the IrrevokableInd = True or not defined, the radio buttons are editable during order entry. There is also a configuration that can be set to hide the field from both the Participants screen as well as the Order Summary.

PolicyProduct/Authorization is used to determine if any authorization questions should display for participants with specified roles. These questions enabled via the Authorization aggregate will be included in the DTCC APP file IF and only if the answer is “yes” (i.e. the checkbox next to the question is checked). Note that, if questions are enabled for the writing agent and/or additional writing agents, the agent(s) will appear on the Participant Details tab such that the questions can be presented.

Note: There are several properties on the Ownership node which are used to validate the age and number of Participants. Note that the ages of the Participants will be validated against the MinIssueAge, MaxIssueAge, MinIssueAgeOwner, MaxIssueAgeOwner properties from FeatureOptProduct on the Summary tab since the Feature and Feature Detail tabs are after the Participant Detail tab in the AFFIRM workflow.

Features Tab

The Features tab is used to present the available features and feature options available for selection by this new business transaction, and enforce “conflicts and requisites.”

Feature Tab Sections

One row appears on the Features tab for every available FeatureProduct which survived the PPfA Cut Down. The three sections of the Features tab are determined using the FeatureProduct/SelectionRule:

Required Features

Features with FeatureProduct/SelectionRule = 3 (Feature Mandatory/Default Allowed) or 4 (Feature Mandatory/User Selection Required) will appear in the “Required Features” box.

The order in which features are displayed within this section may be controlled by the carrier using FeatureProduct/Sequence. iPipeline recommends that the Initial Premium feature uses either one of these codes.

Optional Riders

Features with FeatureProduct\SelectionRule = 1 (Feature Optional/Default Allowed) or 2 (Feature Optional/User Selection Required) AND the FeatureMappingCode is 86 (Rider) will appear in the “Optional Riders” section.

The order in which features is displayed within this section may be controlled by the carrier using FeatureProduct\Sequence.

Optional Service Features

Feature with FeatureProduct\SelectionRule = 1 (Feature Optional/Default Allowed) or 2 (Feature Optional/User Selection Required) AND the FeatureMappingCode is 89 (Arrangement) will appear in the “Optional Service Features” section.

The order in which features are displayed within this section may be controlled by the carrier using FeatureProduct\Sequence.

Features Tab Fields

The following fields on the Features tab are driven by PPfA.

Field Name	PPfA Control	Comment
“Select” Checkbox	FeatureProduct/ SelectionRule	Checkbox will be checked and greyed out if SelectionRule type code indicates the feature is mandatory (tc = 3 or 4).
Feature Name	Type code literal associated with the FeatureOptProduct> RiderTypeCode or ArrType	None
Feature Type	Type code literal associated with the FeatureOptProduct\RiderSubTypeCode or ArrSubType.	While all RiderSubTypeCode and ArrSubType type codes can be included in the PPfA, the literals for only “supported” codes will be displayed. Literals for “tolerated” codes will not be displayed. The sub-type literal is followed by a ” / ” and is concatenated together with Marketing Name in the Feature Option Name field on the Feature page.
Marketing Name	FeatureOptProduct/Name	Concatenated with Feature Type

Feature Ordering and Options

Feature Ordering

iPipeline recommends valuing the FeatureOptProduct\Sequence = 1 on the Initial Premium feature, so that this feature appears first in the Required Features box. If a feature is mandatory per FeatureProduct\SelectionRule, the Select checkbox will be automatically checked.

The order in which features is displayed within each section may be controlled by the carrier using FeatureProduct>Sequence. The order in which the feature options are displayed in the drop down list box may be controlled by the carrier using FeatureOptProduct\Sequence.

Feature Option Selections

FeatureRequisite, FeatureConflict, FeatureOptRequisite and FeatureOptConflict are used to ensure that the appropriate feature options are selected. AFFIRM business rules will ensure appropriate selection.

If another feature is a requisite of the Inital Premium feature or an Initial Premium feature option, AFFIRM will automatically check the Select box when the Feature page is refreshed.

If another feature option is a requisite of an Initial Premium feature option, that feature and feature option will be defaulted/selected.

If a feature or feature option is in conflict with the Inital Premium feature or feature option, the feature or feature option will be removed from the Feature page when the Feature page is refreshed.

If another feature or feature option is a conflict or requisite of a feature or feature option that is NOT the Initial Premium.

Defaulting the Feature Option

All feature options which survive the PPfA Cut Down appear in the feature option drop down unless they are a conflict of the selected initial premium feature or feature option. FeatureOptProduct\Description will be present at the bottom of the Feature pages in the Help box as “mouse over” text. The FeatureOptProduct/DefaultInd is used if the SelectionRule = 1 or 3.

If the SelectionRule = Default Allowed (tc=1 or 3) and a feature option has DefaultInd = True, then the feature option will appear in the drop down list box. If more than one feature option has DefaultInd = True, AFFIRM will use one. iPipeline recommends one and only one feature option (with a common ProductCode) uses DefaultInd = True.

If a feature is mandatory (SelectionRule = 3 or 4), and there is no default available, (either due to the SelectionRule = 4 or if there is not DefaultInd = True), then –SELECT—will appear in the drop down and there will be a red asterisk next to the feature option field.

If a feature is not mandatory (SelectionRule = 2 or 4), then a blank line will appear in the drop down. If a feature is selected (the Select checkbox is checked), then one feature option is required to be selected.

If one and only one feature option is available for a FeatureProduct, we recommend using SelectionRule = 1 or 3 and FeatureOptProduct\DefaultInd = True to automatically select the feature option for the user.

Feature Details Tab

The Feature Details tab is used to gather optional or required information which pertains to the selected feature options which were selected on the Features tab.

Feature Selection Sections

One section will appear on the Feature Details page for every feature option that was selected on the Features tab.

The information in the table below depends on the FeatureMappingCode, as well as the information provided in the PPfA for each selected FeatureOptProduct. Unless otherwise noted, if the PPfA Control noted is present on the FeatureOptProduct, then the Field will be present, and/or enable user entry, and/or not be greyed out.

The only Controls noted below that are expected on riders include: FeatureProduct\Name, FeatureOptProduct\Name and MinTerm/MaxTerm/TermQualifier.

Field Name	PPfA Control	Comment
Destination Allocation Type	FeatureOptProduct\ AllocTypeProduct\ DestTransferAmtType	A collection of all type codes provided in the PPfA will be presented. Since selection of one value is required, the control is a radio button.
Source Allocation Type	FeatureOptProduct\ AllocTypeProduct\ SourceTransferAmtType	A collection of all type codes provided in the PPfA will be presented. Since selection of one value is required, the control is a radio button.
Duration	FeatureOptProduct\MinTerm (and MaxTerm and TermQualifier) AND FeatureMappingCode = 86 – Rider	Numeric entry field; if MinTerm = MaxTerm, Affirm defaults the value, however the field is also available for user input.
Total Number of Occurrences	FeatureOptProduct\MinTerm (and MaxTerm and TermQualifier) AND FeatureMappingCode = 86 – Rider	Numeric entry field; if MinTerm = MaxTerm, Affirm defaults the value, however the field is also available for user input.
Frequency of Payment	FeatureOptProduct\ PaymentModeMethProduct\ PaymentMode	Drop down list box which contains a collection of all PaymentModes for all PaymentModeMethProducts. Selection is required if one or more values are provided in the PPfA.
Day of Month	Enabled if DateCollection\ EffDateEntryRule = 3 or 4	Numeric entry field. Field is required EffDateEntryRule = 3 and optional if EffDateEntryRule = 4. The value entered must be available in the collection of all AllowedDays for the selected Frequency.
Start Date	Enabled if DateCollection\EffDateEntryRule = 5 or 6	Date format. Field is required EffDateEntryRule = 5 and optional if EffDateEntryRule = 6.
Payment Form	FeatureOptProduct\ PaymentModeMethProduct\PaymentForm	Drop down list box which contains a collection of all PaymentForms for all PaymentModeMethProducts. Selection is required if one or more values are provided in the PPfA.
Amount Per Occurrence	FeatureOptProduct\ MinTransactionAmt	Required and must be greater than or equal if property is used.
Percentage	FeatureOptProduct\MinPct (and MaxPct)	Numeric user entry. Required if MaxPct is used, optional if only MinPct is used. Value must be greater than or equal to the MinPct, and, if MaxPct is used, equal to or less than the MaxPct. If both are equal, Affirm defaults the value and the field is not available.
Tax Withholding	TaxWithholdingProduct	Tax withholding instructions may be allowed for Systematic Withdrawal arrangements based on the PPfA. If TaxWithholdingProduct must be present on FeatureOptProduct for federal and/or state withholding instructions to allow entry.
Payee Selection	Not controlled by PPfA	Payee is always present for Systematic Investment and Systematic Withdrawal arrangements. Selection of one Participant with Role = Payee is allowed per arrangement.
Financial Institution	Not controlled by PPfA	Always present for Systematic Investment and Systematic Withdrawal arrangements based on PaymentForm (EFT or Check). Note that the PPfA drives business rules on AFFIRM.

Note: If both SourceTransferAmtType and DestTransferAmtType are used on AllocTypeProduct, an Affirm Business Rule will be validated to ensure the selected combination is present in the PPfA.

Sub Accounts Tab

The Sub Accounts tab collects fund information about the arrangements that were selected on the Feature page.

Fund Manager and Fund Name

The Sub Accounts tab is driven first by PolicyProduct\InvestProductInfo and second by the FeatureOptProduct aggregates associated with the features selected on the Features page. The left-hand columns on the page contain the Fund Manager and Fund Names. A fund will appear if the fund CarrierCode and ProductCode:

Is present in PolicyProduct > InvestProductInfo
InvestProduct\InvestProductTypeCode = 15 (Variable Annuity) or 23 = Model.
Is used in any SourceInvestProduct or DestInvestProduct aggregate on any feature option selected on the Feature page*.
Is NOT included in ExclusionInvestProduct on any feature option. Specifically, in any feature option where the Arrangement\ProductCode is equal to the FeatureOptProduct\ProductCode.

Note: The system uses Sequence on InvestProductInfo to sort Complex Asset Allocation funds on the SubAccount page. The exception to this is when Complex Asset Allocation is selected, in which case the Sequence from InvestProductInfo on each individual model and category is used to sort the categories, and then the funds within each category.

Fund Selection

A column will appear for every Arrangement that was selected where the (Source or Dest)TransferAmtType = Percentage, Amounts or Prorata Across Selected Funds.

If the MaxNumSourceInvestProd or MaxNumDestinationInvestProd = 1, the controls in the column for that arrangement will be radio buttons so only one can be selected.
If only one SourceInvestProduct or DestInvestProduct is available, it should be automatically selected for the user on the page.
If (Source or Dest)TransferAmtType is Prorata Across Selected Funds, the controls should be checkboxes such that one or several can be selected.

Initial Allocation Input Type

The DestTransferAmtType and SourceTransferAmtType is selected on the Feature page. The selected value controls whether the input is expected to be a percentage (and all selections must total 100), an amount (the total must equal the Amount Per Occurrence on the Feature Detail page), or a checkbox (used for Prorata Across Selected Funds).