Product Hatching Ideas

For the Third Party Pricing XML, tie eligibility to the base product, when custom products are used in the BOS

As it stands now, when a customer has custom products in their BOS, and call for that via third party pricing API, we look at how the custom product is set up for the LTV maximum, instead of looking at the product eligibility for the product to which the custom product is tied.  For example, a client has a custom 7/1 ARM set up, tied to a Conf 7/1 LIBOR ARM in Marksman, but has the max LTV at 110%.  The third party API will look at that, instead of the max LTV for the Conf 7/1 LIBOR ARM.  The LTV can be restricted in the custom product set up.  However, if I price outside of the eligibility for other parameters with lower LTV maximums, such as multiple units, the API will price, Marksman will correctly not price.

  • Dennis Lollman
  • Dec 20 2016
  • Moved to Prioritzation
Workaround Present No
Impact to Existing Customers Multiple
  • Attach files
  • Admin
    Lori Rezac commented
    December 27, 2016 15:08

    Need to tie back to the correct product.  Should this be tied to DNA?  Custom products are not shutting off correctly.  Need more investigation.

    There is an associated BUG ticket with this issue BOB-79.