Page Comparison

...

“isDeleted“ Policy holder cannot be updated

PolicyHolder Users

...

This page will link interactive (openIMIS) user to PolicyHolder, in order to allow them to access the PolicyHolder’s data on the PolicyHolder portal

...

.

...

PolicyHolder Users search criteria

...

It should be possible to sort the result per column in ASC or DESC order.

PolicyHolder Users create

• A button on

...

• bottom right of the

...

• page. Clicking it results in a popup to add the user.

• Fields:

  • User (User picker, required)

  • Policy Holder (Policy Holder picker, required)

  • Date Valid From (Date picker, required),

  • Date Valid To (Date picker)

PolicyHolder Users replace

...

The material (Save) UI button will save all the changes made on the list.

PolicyHolder Insurees

...

Journal messages

• Create: <UserLabel> is added on <PHlabel>

• Delete: <UserLabel> is removed from<PHlabel>

• Update: <UserLabel> - <PHlabel> is updated

• Replace: <UserLabelNew> is replacing <UserLabelOld> on <PHlabel>

NTG done: PHUser tab in PH

tab showed if the user have the PHuser rights or the PHPortalUser right + link to PH in PHUser

PolicyHolder Insurees

This pages/section will link the PolicyHolder and a given insuree, and will enable the addition of data on that relationship (contribution plan bundle and calculation rules parameters).

...

Same filter As payment, only an addtionnal filter that will be hidden to have only payment with payment details that are linked to PHCPD when a Payment Query $

NTG done: PHPayment tab in PH

tab showed if the user have the PHPayment rights or the PHPortalPayment right + link to PH in PHUser

Solution

Idea to make this additionnal filter within the payment module (i.e the payment tab could be a contribution from payment)

...

Use json_ext

1. When creating payment details, add a section “policyholder” in the json_ext of the payment, this section will have the UUID of the policyholder, add a section “contract” in the json_ext of the payment, this section will have the UUID of the contractholder

2. the payment contribution tab (not sure it is a real contribution_fe, feel more like the tab will be called in PH fe, making it a dependency), will take as hidden parameter the json_ext filter that will be composed of : “nameOfTheToObject“ (policyholder if the tab is show in policyholder) and the UUID of the TOP object

...

.e the payment tab could be a contribution from payment)

1. implement “Dynamic“ parameter in the mutationQuery

   1. adapt the payment payment mutation query to be able take “dynamic“ filters (I hope this is possible), but don’t use it in the mutation payment module BUT enable the “pre_mutation“ query“ signals to add filters in the query set

   2. in PH be module, register a signal on the payment “pre_mutation“query“, check if there is a an PH uuid on the mutation “dynamic“ params, if it is the case if it is the case and if the user have either the Payment right or (the payment portal right + have a link to PH in PH user table ) then add the filters to retrieve only payment with payment details that are linked to CPD link to PH contracts

   3. the Payment module, should block the query if the user have no right or if there is no additional filter on the query

   4. (Nice to have)in the contract be module, register a signal on the payment “pre_mutation“query“, check if there is a contract uuid on the query “dynamic“ params, if it is the case and if the user have either the Payment right or (the payment portal right + have a PH uuid on the mutation “dynamic“ params, if it is the case link to contract PH in PH user table ) then add the filters to retrieve only payment with payment details that are linked to CPD

...

Link to other entities

• place holder for other tab / link to search pages → those should be added by contribution_fe

  • 1 tab from the contract module

    • a simple pre-filtered for the contract search → select/double click will lead to contract pages (in the contract scope)shows the contract for the PH

  • 1 tab form the payment module (should haveNTHD):

    • a simple pre-filtered for shows the payment search → select/double click will lead to contribution pages (made by Bluesquare) TBD

     2

    • related to the contract

  •  3 tab from the policy module (Nice to have):

    • a simple pre-filtered tab for the contribution search → select/double click will lead to contribution pages (made by Bluesquare) TBDa simple pre-filtered for the policy search → select/double click will lead to contribution pages (made by Bluesquare) TBD

    • a tab for the policy search

    • a tab for the insureePolicy

Frontend Configuration

• Get Backend Configuration for the dropdown/enums or duplicate it

• configurable Regex for validation/constraint for the phone and FAX (Nice to haveNTHD)

  • plus message when the constraint is not respected (in different languages)

• configurable Regex for validation/constraint for AccountancyAccount (Nice to have)

  • plus message when the constraint is not respected (in different languages)

• configurable Regex for validation/constraint PaymentReference (Nice to have)

  • plus message when the constraint is not respected (in different languages)

...