> For the complete documentation index, see [llms.txt](https://coldbox-orm.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-orm.ortusbooks.com/v5.x/base-orm-service/service-properties.md).

# Service Properties

Service Properties - Configuration options for the Base ORM Service in CBORM.

There are a few properties you can instantiate a base service with or set them afterwards that affect operation. Below you can see a nice chart for them:

| Property           | Type    | Required | Default                   | Description                                                                                                                                  |
| ------------------ | ------- | -------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| `queryCacheRegion` | string  | false    | `ORMService.defaultCache` | The name of the secondary cache region to use when doing queries via this base service                                                       |
| `useQueryCaching`  | boolean | false    | false                     | To enable the caching of queries used by this base service                                                                                   |
| `eventHandling`    | boolean | false    | **true**                  | Announce interception events on *new()* operations and *save()* operations: *ORMPostNew, ORMPreSave, ORMPostSave*                            |
| `useTransactions`  | boolean | false    | **true**                  | Wraps all operations that save, delete or update ORM entities in a BoxLang `transaction{}` (unless one is already running)                   |
| `defaultAsQuery`   | boolean | false    | **false**                 | The bit that determines the default return value for `list()` and `executeQuery()` as query or array of objects                              |
| `datasource`       | string  | false    | System Default            | The default datasource to use for all transactions. If not set, we default it to the `ormSettings` datasource or the application datasource. |

So if I was to base off my services on top of the Base Service, I can do this:

```javascript
class extends="cborm.models.BaseORMService" {

  public UserService function init(){
      super.init( useQueryCaching=true, eventHandling=false );
      return this;
  }

}
```

{% hint style="info" %}
The ORM rides the BoxLang `transaction{}` connection, so the writes of a service call commit and roll back together with any native `queryExecute()` in the same transaction. If a transaction is already active, the service joins it instead of starting a new one.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox-orm.ortusbooks.com/v5.x/base-orm-service/service-properties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.