Decision Actions

What is a Decision Action?

Decision Actions are what LendAPI Decision Tree Builder uses to describe the very end of each tree branch. In the simplest decision tree, there might be one decision fork and two branches. For example the tree might say “If Credit Score > 600 then approve, otherwise decline.”

The words “approve” or “decline” are what we call Decision Actions. We in fact have other decision actions defined in our system. We will look at these decision actions and explain their usage below.

Where do we find Decision Actions in the LendAPI platform?

As usual, head on to the left navigation panel. All of our decisioning types of activities are located under Workflow. Underwork flow, you can click on Actions.

Decision Actions are ligaments in our overall design and we systematically defined these decision actions. At the moment, our clients can’t add, delete or edit these actions. These are systematic variables. However we will explain the meaning behind these actions and how to use them.

A. Decision Actions are located from the left navigation panel. Click onto Workflow, then click on Decision Actions.

B. Actions List: actions are defined as follows:

• Approve: Approve action is usually assigned as an End Node of a branch. This usually denotes that an application has been approved systematically.

• Decline: Decline is the counterpart to Approve. This action usually denotes that an application has been systematically declined by the decision rules.

• Review: A Review action links to our Workflow Orchestration system. It means that the End Node of that particular branch requires the application to be reviewed. A few things happen when a Review status is triggered. The applicant will get a webpage that tells them their application is under review. The application will get queues into the Application queue for further review.

• Request Docs: This action is reserved for two actions. First, this action can be assigned in an End Node. When this happens, the application will trigger an upload document request live during the application process. Second, this action can also be assigned to an email template. Meaning that when an email is triggered manually by a staff member to request additional documents, this action is used.

C. System Name: These are names that the decision engine uses. These are system names for these actions. We usually keep the descriptive name and the system name the same to lessen ambiguity.