dominiquebertrand / coog-fed-planning Goto Github PK

GIE: For a student insurance, the covered element (a student) is different from the subscriber (parent)

Milestone: GIE 1 aout

GOAL

As API user, I want to be able to customize how those informations will be displayed to the
end user, most notably by grouping some data together under a header.

Solution

Add new entry "groups" into "questionnaire / part" to allow question group management.

TODO

• Add this new entry into Coog API RPC (Coog BO) (Blocked by 13077)
• Add this new entry into Coog API REST (Coog Gateway)

The model become:

Questionnaire:

{
   "id":Integer,
   "title":String,
   "mandatory":boolean,
   "sequence":Integer,
   "description":String,
   "questions":[
      Question
   ],
   "groups":[
      Group
   ]
}

Group:

{
   "questions":[
                     {
                             "code":String,
                             "sequence":Integer                  
      }           
   ],
           "title":String,
           "description":String,
           "tooltip":String
}

Exemple de groups:

"groups":[
      {
         "questions":[
            {
               "code":"refund_question",
               "sequence":"1"
            }
         ],
         "title":"Couverture globale",
         "description":""
      },
      {
         "questions":[
            {
               "code":"question_1",
               "sequence":"1"
            },
            {
               "code":"question_2",
               "sequence":"2"
            },
            {
               "code":"question_3",
               "sequence":"3"
            }
         ],
         "title":"Optique",
         "description":"Vos besoins en matiere d'optique"
      }
   ]

Acceptance Criteria

Portal BtoB User should be able to perform an end-to-end sales route as specified in this SFD

Resources:

• Mockups:
  • LOT 1
  • LOT 2
• Functional Specifications:
  • LOT 1
  • LOT 2
• Testing URL:

  • http://poccoog.pegase.lan/portal/salesroutes/

• Staging URL:

  • http://poccoog.pegase.lan/portal/salesroutes/

Todos

• Provide Testing URL
• Provide Staging URL

• Misses the Header:
  

• Misses the Theme:
  

• Drag & drop does not work:
  

• The display of the required documents is not stable:
  Before the refresh of the page:
  
  After the refresh of the page:
  

Web resources should be identified with their code in APIs
[COOG RPC API] Request to get questionnaires failed when using "Web Resources"
=> see https://support.coopengo.com/issues/13003

To Reproduce
Steps to reproduce the behavior:

Request:
URL: [COOG_URL]/[COOG_DB_NAME]
Method: POST
Payload:
{ "id": 1, "method": "model.api.core.list_questionnaires", "params": [ {}, { "user": 4, "dist_network": 3 }, {} ] }

Response:
{ "id": 1, "error": [ "keys must be str, int, float, bool or None, not web.ui.resource.key", "Traceback (most recent call last):\n File \"/trytond/wsgi.py\", line 104, in dispatch_request\n return endpoint(request, **request.view_args)\n File \"/trytond/protocols/dispatcher.py\", line 65, in rpc\n request, database_name, *request.rpc_params)\n File \"/trytond/wsgi.py\", line 72, in auth_required\n return wrapped(*args, **kwargs)\n File \"/trytond/protocols/wrappers.py\", line 148, in wrapper\n return func(request, pool, *args, **kwargs)\n File \"/trytond/protocols/dispatcher.py\", line 318, in _dispatch\n response = app.make_response(request, result)\n File \"/trytond/wsgi.py\", line 123, in make_response\n response = cls.response(data, request)\n File \"/trytond/protocols/jsonrpc.py\", line 173, in response\n response, cls=JSONEncoder, separators=(',', ':')),\n File \"/json/__init__.py\", line 238, in dumps\n **kw).encode(obj)\n File \"/json/encoder.py\", line 199, in encode\n chunks = self.iterencode(o, _one_shot=True)\n File \"/json/encoder.py\", line 257, in iterencode\n return _iterencode(o, 0)\nTypeError: keys must be str, int, float, bool or None, not web.ui.resource.key\n" ] }

1. top header color
2. logo

Milestone: DLPL 17 septembre

public url: /customers/myspace

Description
The request fails with status code 506 when I try to get the documents from a contract.

To Reproduce
Steps to reproduce the behavior:

• Request URL: [GATEWAY_URL]/api/v1/contract/[CONTRACT_ID]/document_request_lines?_fields=document_desc
• Request Method: GET
• Response Status Code: 506 Variant Also Negotiates
• Response Body: ["RPC Error (0): read() missing 1 required positional argument: 'fields_names'"]

Milestone: MGEFI 21 Novembre 2019
=> request more informations to Fred (Galaxie)

Create a react component which allow to visualize and manage a "Questionnaires" form ( ie. Recueil des Besoins).

• see details in the functional specifications

Preview:

Additional context

• This component must be a pure presentational component.
• It must be a part of the package "coog-react-component"
• It must be integrated into the storybook
• The component name is QuestionnaireBlock
• main branch: feature/salesroute/custom-components

Note:

remove branches "feature/custom-component-questionnaire-block" and "feature/custom-component-sales-route" after end sprint.

Create a react component which allow to visualize offers and select at least one in a "Salesroute"
=> see details in the functional specifications

** Preview:

Additional context

• This component must be a pure presentational component.
• It must be a part of the package "coog-react-component"
• The name of this component is "OffersBlock"
• main branch: feature/salesroute/custom-components

Note:

remove branches "feature/custom-component-questionnaire-block" and "feature/custom-component-sales-route" after end sprint.

• "sa commune de naissance"
• "ses données de fonctionnaire"

** "Parcours Professionnel" management / Gestion du parcours professionnel*
Portal user should be able to manage the "Parcours Professionnel" of prospect / adherent

• see details in the related functional specifications

As BtoB user, I would like to be able to make a contract subscription with a Legal Person

Acceptance Criteria

1. If I want to subscribe a insurance contract
2. I should be able to make a subscription with a Legal Person

Resources:

Mockups:

source: https://app.zenhub.com/files/192696512/18b65723-675d-4c4a-944b-c2f69aa08afb/download

The purpose of this feature is to provide to the front-end the list of the action available on a product for a broker / user. The info will allow the frontend to display the related action button only if it is allowed / available.

example: If the subscription is not available, API provide this information to the front end to allow us to hide / disable the button "Subscribe".

transform a calculate offers of a "salesroute" to a calculate offers per product/packages (API 2.0) and aggregate the results.

• Create a multi product description route
• Create or Update calculate-offers action

As Coog 2.6 customer, I would like to be able to create quotation thanks to a dedicated web application
The purpose of this feature is to provide a lighter view dedicated to creating a new quote (one-shot) which consist of:

• login page
• pickup product age
• edit quotation page

Acceptance Criteria

As portal user, I would like to have a theme based on my profile (ie. distribution network)

Resources:

• Mockups: ?
• Testing URL: ?
• Staging URL: ?
• Original Functional Requirement: (see source)

  • logo + couleurS dynamiqueS en fonction du réseau de distribution

Notes: See with Fred

Add information related to a product like:

• Related Commercial Documentations like ipid (PDF)
• Description

The purpose of this library is to create a Boilerplate of React component library that will be used to create custom components for customers. These components should be only at presentational level.

** Improve UX for the Numeric fields *
Currently, in the numeric field "EditQuotation / Loan / duration", if I set a value and then delete it, a "0" appears in the field and I can not delete it.

Solution
Allow to clear the field (do not replace by a 0)

Resources

• See related customer issue #13136

As Portal BtoB user, I want to be able to search an existing party
Ability to search for an existing third party in a quote to avoid duplication / error.

• It must be applied for each entry point with a resource id defined in the URL (GET, PUT, PATCH and DELETE)

The purpose of this library is to create a React component library that will be shared between multiple packages to avoid duplication and improve consistency. These components should be only at presentational level.

• package name: coog-react-components

Building and Deployment of Coog 2.6 in the following environments:

• DLPK
• MGEFI
• Axelliance

Describe the bug
bad label: "Fréquence de paiment" should be "Fréquence de paiement" in edit quotation view > loan > "block.loan.field.payment_frequency.label".

iso perimetre V1.0 :

• Questionnaire
• Save => SalesRoute => Contract

Milestone: Axelliance 1 septembre

TODOs

• Configure coog BO to allow the calculation of the offers
• Modify current MGEFI functional tests to allow testing of the functionality above.
• Update current MGEFI mock server data.

Resources:

• Testing URL: ?
• Staging URL: ?

Notes

Acceptance Criteria

1. If I create a "sales route" for a loan contract insurance with several elements covered
2. I would like to be able to create a contract by covered element

Example:
If I create a loan insurance sales route with:

1. 2 x loans: L-A & L-B
2. 2 x covered elements (party): EL-1 & EL-2
   I would like to create:
3. 1 x contract C-1 with L-A & L-B loans for the EL-1 subscriber.
4. 1 x contract C-2 with L-A & L-B loans for the EL-2 subscriber.

Also, here are a few points that need to be addressed:

1. Constraint 1: contracts C-1 and C-2 must use the same loans (L-A and L-B) and the same elements covered (EL-1 and EL-2). These must not be duplicated in Coog.
2. Constraint 2: It should be done in one transaction.

Resources:

• Mockups: ?

Notes

It must contain all cross code shared between packages, like:

• Coog RPC utils (call & error management)
• Tree shaking

As a Microservice i would like to request a service dedicated to schema construction.

I want to be able to call this service, and he return to me the Mongoose Schema, input Validation, and the Yaml Documentation.

The idea is to have a single entrypoint for the JSONSchema 7.0 parser and this one will have credentials by the event of gateway initialisation.

For now the use of this one is to remove the model schema inside API-B2B server.

This feature will eventually be developped alongside the implmentation of Event Driven Architecture Feature

Milestone: Axelliance 1 septembre

A Sales route consist in (almost):

• profil assuré -> questionnaire tarification
• besoins -> questionnaire DDA
• informations de souscription

TARGET:
Lot 1 MGEFI (1 janvier 2020) :

1. MPD
   1.1 Souscription
   1.2 Avenant
2. Tempo dc
3. Indemuo

Rendre obligatoire la saisie (i.e ne pas pouvoir sortir du bloc et/ou à minima ne pas pouvoir lancer de calcul):

• du montant du prêt
• du taux (si pas taux zéro)
• Durée du prêt
• Paliers si prêt palier
• Toutes les données complémentaires si elles ne sont pas renseignés avec la valeur par défaut
• Quotité
• Date de naissance

Context

I want to calculate offer on a product which have a rule option with get_loan_first_payment_date and get_loan_payment_frequency.

Input

Quotation with loan

Output

No error but calc.

Acceptance test

For the rule function get_loan_payment_frequency return the correct frequency (year or month)

For the rule function get_loan_first_payment_date, with those release date and frequency return:

• 2019-02-28/year => 2020-02-29
• 2020-02-29/month => 2020-03-31
• 2020-03-31/month => 2020-04-30
• 2020-04-30/month => 2020-05-31
• 2019-02-27/month => 2019-03-27

TODO:

• add the new entry into Coog Gateway
• add Swagger documentation related to the new entry
• add functional tests related to the new entry

Dependencies

=> Blocked by 13077

The model become:

Questionnaire:

{
   "id":Integer,
   "title":String,
   "mandatory":boolean,
   "sequence":Integer,
   "description":String,
   "questions":[
      Question
   ],
   "groups":[
      Group
   ]
}

Group:

{
   "questions":[
                     {
                             "code":String,
                             "sequence":Integer                  
      }           
   ],
           "title":String,
           "description":String,
           "tooltip":String
}

Exemple de groups:

"groups":[
      {
         "questions":[
            {
               "code":"refund_question",
               "sequence":"1"
            }
         ],
         "title":"Couverture globale",
         "description":""
      },
      {
         "questions":[
            {
               "code":"question_1",
               "sequence":"1"
            },
            {
               "code":"question_2",
               "sequence":"2"
            },
            {
               "code":"question_3",
               "sequence":"3"
            }
         ],
         "title":"Optique",
         "description":"Vos besoins en matiere d'optique"
      }
   ]