SpringboardThis topic is related to Springboard. | Form Builder | 23.10This feature was updated in 23.10 Retail DAO 4.1This feature was updated in Retail DAO 4.1.
Credit Unions have some unique requirements for opening Retail DAO accounts for new or existing customers. These requirements have been addressed by adding fully configurable options for eligibility requirements, beneficiary, and employment, as well as new logic to automatically add or remove a membership share to the applicant's shopping cart.
Every Credit Union has eligibility requirements unique to them. With the fully configurable Eligibility page, a Credit Union can specify simple to complex eligibility criteria. This page is automatically included for all Credit Unions and is placed early in the workflow to ensure the applicant meets eligibility before proceeding too far.
Moving this page to a different location in the workflow or changing aspects such as the layout or logic is a customization.
Although created with Credit Unions in mind, adding a beneficiary to a deposit account is an optional feature available to all Springboard retail DAO clients implementing retail DAO v4.1 or later.
Moving this page to a different location in the workflow, or changing the layout, content, or logic is a customization.
While gathering employment information may be more common with lending, this page is now available as an optional feature to all Springboard DAO clients implementing retail DAO v4.1 or later. This page gathers employment status, salary, and occupation.
Moving this page to a different location in the workflow, or changing the layout, content, or logic is a customization.
New for Credit Unions with Retail DAO v4.1, membership share accounts will be added to or removed from an applicant's product list automatically as necessary. The membership share needs to be defined in the product catalog. The implementation team needs to know of any previously used membership share to determine if the applicant has an existing membership share. The applicant is advised if a membership share is added to or removed from their product list. The service structure is in place to call core APIs to find an applicant and their account assets. Development work is required by the implementation partner to make the connection and update the logic with the product IDs of all membership share accounts.
Moving the location of the series of core API calls, logic, or advisory is a customization.
Next, learn about the Retail DAO for authenticated customers.