> For the complete documentation index, see [llms.txt](https://docs.timvero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timvero.com/timveroos-admin-panel-documentation/v.-7.10/data-sources-and-bpm-underwriting-setup-for-dynamic-profile-formation/selecting-integrated-data-sources-and-feature-set-management.md).

# Selecting integrated data sources and Feature set management

**Selecting data sources for BPM**

The user is expected to facilitate the necessary data source integration into the underwriting workflow.

Instructions for connecting new data sources can be found [here](https://app.gitbook.com/s/nbcr7S8IIXfIkrmuemOU/timveroos-sdks/v.-7.10/new-data-source-connection-with-bud-financial-example).

**Here is an example of how the integrated data sources look like in the interface:**

![](https://t2574825.p.clickup-attachments.com/t2574825/4aa1b977-2cec-4403-879b-6c835111bc31/Screenshot%202024-09-09%20at%2021.55.05.png)

**Feature set management**

When a new feature is created, the system allows users to validate the scripted logic against a sample response. If the feature is based on a query already used in the system, validation can be done using an existing response.

Users can create as many features as needed, but only those necessary for underwriting, product offers, and document automation are selected. All created features are stored in timveroOS's data warehouse, making them available for future risk assessment, product optimization, and marketing analytics.

**Creating a feature involves transforming data from the response and properly storing the output, which becomes the feature itself:**

![](https://t2574825.p.clickup-attachments.com/t2574825/86bd6bc3-889a-485d-b2a9-8b0dca1fc102/Screenshot%202024-09-09%20at%2021.56.22.png)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.timvero.com/timveroos-admin-panel-documentation/v.-7.10/data-sources-and-bpm-underwriting-setup-for-dynamic-profile-formation/selecting-integrated-data-sources-and-feature-set-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.