Connection Mapping

Connection Mapping to Strategy

Mapping connections to a strategy is a key step in utilizing external APIs or internal decision engines within your workflow. This process ensures that your strategy dynamically consumes the required data or processes from the connections you’ve integrated.

---

Steps to Map Connections to a Strategy

Step 1: Add a Connection to the Strategy

1. Open the Strategy Designer module.
2. Navigate to the workflow area where you want to integrate the connection.
3. Right-Click the desired connection point in the workflow.
4. Select Add Connection and choose the connection type:
   • API: For external services.
   • Engine: For internal Scorport decision engines.

---

Step 2: Configure the Connection

1. Open the Connection Panel:

   • Once the connection icon is added to the workflow, a configuration panel will appear.

2. Select the Connection:

   • Choose the pre-configured API or Engine connection from the available list.

---

Step 3: Map Elements to Request Parameters

1. Locate Parameters:

   • On the left-top panel, you’ll see the data elements available in your strategy (e.g., variables, scores, or calculated fields).

2. Drag and Drop Mapping:

   • Drag the relevant elements from the left-top panel and drop them onto the corresponding request parameters of the connection.
   • Example:
     • Map applicant_ID from the strategy to the connection parameter Applicant.
     • Map income from the strategy to the connection parameter income.

3. Ensure Correct Mapping:

   • Verify that each parameter is mapped to the correct data element to ensure the connection functions as expected.

---

Step 4: Submit and Save

1. Submit the Mapping:
   • Once all parameters are mapped, click the Submit button to finalize the connection mapping.
2. Save the Strategy:
   • Save the updated strategy workflow to ensure the changes are applied.

---

How Connections Work in Strategies

• Once mapped, the strategy will consume the connection dynamically (API or Engine) as part of the workflow.
• The connection will execute in the sequence designed in the strategy:
  • For APIs: The strategy sends a request, receives a response, and processes the data.
  • For Engines: The strategy sends input data to the engine, which returns a processed result for use in subsequent steps.

---

Example: Mapping an API to a Strategy

Scenario:

• Connection: Credit Score API.
• Parameters:
  • credit_score: The applicant's credit score.
  • income: The applicant's annual income.

Steps:

1. Add Connection:
   • Add the Credit Score API to the workflow.
2. Map Parameters:
   • Map credit_score from the strategy’s variables to the API’s score parameter.
   • Map income from the strategy’s variables to the API’s income parameter.
3. Submit and Save:
   • Finalize the mapping and save the strategy.

---

Example: Mapping a Decision Engine to a Strategy

Scenario:

• Connection: Loan Approval Engine.
• Parameters:
  • credit_score: The applicant’s credit score.
  • loan_amount: The requested loan amount.

Steps:

1. Add Connection:
   • Add the Loan Approval Engine to the workflow.
2. Map Parameters:
   • Drag credit_score and map it to the engine’s credit_score parameter.
   • Drag loan_amount and map it to the engine’s loan_amount parameter.
3. Submit and Save:
   • Finalize the mapping and save the strategy.

---

Benefits of Connection Mapping

1. Dynamic Integration:

   • Map and consume external APIs or internal engines seamlessly within your strategies.

2. Flexibility:

   • Design workflows with precise sequence and parameter mapping to achieve desired outcomes.

3. Scalability:

   • Add and map multiple connections to create highly dynamic and data-driven workflows.

---

Mapping connections to a strategy ensures your workflows are robust, adaptable, and capable of leveraging external and internal services for maximum efficiency.