Sample Onboarding application

The sample Onboarding application is an example application for the onboarding scenario that deals with opening a bank account. The application uses building blocks of the toolkit and out-of-the-box Power Platform components to demonstrate the recommended use of the different components and the integration between them. The example application demonstrates best practices with the help of data model setup, user experience, and automated flows.

Constituents of the sample Onboarding application

The kit includes the following components:

Sample Onboarding model-driven application: Includes the following recommended toolkit components:

  • Application queue user interface control

  • Application progress user interface control

  • Customer snapshot user interface control

  • Tasks component (user interface control and out-of-the-box workflow)

  • Document intelligence (user interface control and out-of-the box core flows)

  • Out-of-the-box platform components (Main application form, Business Process Flow, Additional applicants view based on the Grid view).

Extended data model for a sample business scenario (the Open a bank account scenario): Shows how to use the basic data model entities in the best manner; for example, in the Open a bank account scenario, the link between the Application table and the Account application table.

Sample data: The sample data for the Open a bank account onboarding application scenario:

  • Configuration of a form that is linked to a task definition.

  • Reference data configuration: The business scenario (account onboarding), the business scenario subcategories (saving and checking account opening), the roles relevant for the scenario (owner role), the task groups, and the task definition setup data.

  • Sample application data: A list of applications where each application includes information about the primary applicant, the additional parties, and their roles.

Sample Document intelligence workflows: A custom pipeline built for Identity document definition. This pipeline holds three steps outlined in the Pipeline step definition entity. Each step has a corresponding custom pipeline step flow defined, except the AI Builder automatic extraction step, which does not require a flow configuration.

The sample Identification document custom sub-workflow includes the following steps:

  • Extraction step: Information is extracted from the document using the Identity document pre-built AI model within the Power Platform. This step is not considered a custom pipeline step because the first step definition, designated as an extract type step, is automatically generated by the process without the need for flow definition.

  • Supporting information step: Includes additional supporting information on top of the extraction output. This information is additional data from the data model. In the example workflow, the additional information is the applicant's credit score that is relevant for future process use such as shipping the data to a third party along with the extracted data. This step is defined as a custom pipeline step in the workflow.

  • Verification step: This step uses the extraction step output to check whether the document is an identity document. This step is defined as a custom pipeline step in the workflow.

See also