Dashboard for a mortgage intermediary

Availability of functionality depends on the license and may not be available in all deployments.

Assumptions:

• The intermediary sees only the cases he has started himself, even when he is no longer currently assigned to them
• The intermediary can search for cases by case number and customer surname

The dashboard uses data from the projection database, which is fed by events emitted from eximeeBpms. A case started by the intermediary appears on the list after the process (case) is started in eximeeBpms; this is handled by the emitted event RouterProcessStartedEvent

Changes needed to associate the application with the intermediary starting it

• Projection database in the table process_list has been extended with the column startedBy. The column stores the login of the user who started the application.
• The dashboard uses the projection database fed by events, therefore it has been added to KafkaProcessListEventConsumer handling and consuming the **RouterProcessStartedEvent event containing the user's login. This login is stored in the column startedBy.

Defining dashboard functionality visibility

Visibility of functionality is controlled by roles in the application. The mortgage intermediary has permission feature_only_started_processes, which allows him to see:

• inbox (list of cases),
• starting a new mortgage application via the New mortgage button (connected application: simpleMortgage_app),
• filtering applications tailored to the mortgage intermediary.

He should also have the permission feature_process_list - it allows access to the case list.

Filtering cases in the dashboard

• A filter was added when searching for applications on the backend - the intermediary will retrieve only the applications he started himself.

  • in the search above the case list, cases can be filtered by the customer's surname,
  • in the Filter window, in the Case ID field, after entering part of the case number, we should see filtered cases.