1. In the header of Dev Studio, click ConfigureProduct composer systemConfiguration.
2. Click the Flow settings tab.
3. In the Benefit mapping section, click the Add a row icon to add a new benefit definition option.
4. Enter the information in the fields, and then select from the lists.
5. When you are finished, click ActionsSave as system configuration.
   Saving the settings as personal configuration saves the changes only for the logged in user. To save the configuration as system settings, save the settings as system configuration.
   Result: The changes to the benefit mapping apply to new benefits. The changes do not apply to existing benefits in the system.

The following list shows the metadata fields that you can extend and the name of the corresponding class:

• Line of business (PegaHC-Data-LineOfBusiness)
• Market segment (PegaHC-Data-MarketSegment)
• Coverage level (PegaHC-Data-BenefitCoverageLevel)
• Product line (PegaHC-Data-PlanType)
• Exchange level (PegaHC-Data-PlanExchangeLevel)

1. In the navigation panel of Dev Studio, click Data types and then in the search field, enter and search for the class name from the list above that corresponds to the item that you want to extend.
2. On the Data Type page, click the Records tab.
3. Click the Add record icon.
4. In the field that corresponds to the name of the class that you are extending, enter a name for display.
   For example: You might enter Mental Health as a new line of business.
5. Save your changes.
6. Repeat these steps for each metadata field that you want to extend.

1. In the navigation panel of Dev Studio, click App and then enter the name of a class at the top of the navigation panel.
   For example: Enter PegaPCS-Data-Plan.
2. Click SysAdmin, and then click Class.
3. Click the class, for example, PegaPCS-Data-Plan.
   Result: The General tab displays the ContractID key.
4. Modify the key as necessary and click Save.

1. In the navigation panel of Dev Studio, click AppAcceleratorNetworkUser Interface.
2. Click Section, and then click the section where you want to add details.
   For additional details, see Sections - Completing the Create or Save as form.
3. When you are finished, click Save as and select an option.

1. In the header of Dev Studio, enter the name of the extension activity rule that is listed in the table in the search field.
2. Click the name of the activity.
3. Check out the rule and save it.
4. On the extension page, add the fields for validation.
   For additional information, see Activities.
5. Save your changes and check in the rule.

   Extension activity rule	Call from this activity rule	Description
   ValidatePrimaryExcelFieldsEXT	ValidatePrimaryExcelField	Use this activity rule to validate the main properties that are required for the PCS import flows.
   ValidateDatesAndStatusEXT	ValidateDatesAndStatus	Use this activity rule to validate the overlapping dates of the consumed entities, for example, a benefit being added to a benefit set. If there is not at least one day overlapping between the benefit and the benefit set, a validation error occurs and the benefit is not accepted. This activity rule also checks for rejected or retired statuses of entities.
   ConvertingDatesForPolicyTermEXT	ConvertingDatesForPolicyTerm	Use this activity rule to validate the dates that you entered for policy terms in the PCS import flows.
   GroupPolicyListEXT	GroupPolicyList	Use this activity rule to group all the rows that are related to one policy into a single list.
   BenefitDataLoadValidationsWrapperEXT	BenefitDataLoadValidationsWrapper	Use this activity rulactivity rule to validate all the business functionality that is related to the PCS import flows for benefits and call all post-activities from the main flows.
   AutoDataLoadGrpValidationEXT	AutoDataLoadGrpValidation	Use this activity activity rule to validate all the business functionality that is related to the PCS import flows for groupers and call all post-activities from the main flows.
   ADLBenefitSetValidationWrapperEXT	ADLBenefitSetValidationWrapper	Use this activity rule to validate all the business functionality that is related to the PCS import flows for benefit sets and call all post-activities from the main flows.
   NetworkValidationsWrapperEXT	NetworkValidationsWrapper	Use this o validate allactivity rule business functionality related to the PCS import flows for networks and call all post-activities from the main flows.
   PolicyTermsValidationsWrapperEXT	PolicyTermsValidationsWrapper	Use this activity rule to validate all the business functionality that is related to the PCS import flows for policy terms and call all post-activities from the main flows.

1. In the navigation panel of Dev Studio, click App and enter the name of the class that corresponds to the entity that you are modifying in the search field.
2. Click User InterfaceSection and select the section that corresponds to the entity that you are modifying.
3. Click Save as to save the section rule to the implementation ruleset.
4. Click Client Configuration to expand the section.
5. Drag the property into the section.
6. Repeat these steps to add new fields to other entities.

1. In the header of Dev Studio, click Launch portalProduct Development.
2. In Pega Product Composer for Healthcare, in the Enter details step of the wizard for plan, product, or product template, select the field, for example, Termination reason and click the Open runtime toolbar in the bottom right corner.
3. Click the Toggle Live UI icon
4. Select the field for which you are configuring options.
5. Click the View properties icon at the right of the field.
6. In the Cell Properties dialog box, at the right of the Property field, click the Open section icon.
7. Check out the rule. For more information about checking out a rule, see Checking out a rule.
8. On the Property page, scroll to the Prompt values section.
9. In the Standard value field, enter text that suits your business, for example, T1-Termination.
10. In the Prompt value field, enter text, such as Obsolete Product.
11. Click Save.