> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/getting-started/kinetic-configuration-required.md).

# Kinetic Configuration Required

The following section details the configuration dependencies within Epicor Kinetic. Because EKR is connected directly to the Epicor Kinetic backend, completion of these steps is essential for a successful deployment.

{% stepper %}
{% step %}

## Step 1: Deploy EKR Web Application

**Actioned by:** BISCIT Product Team

The BISCIT product team will provide you with a URL to your pilot and production EKR instance or deployment configured to talk to the relevant EPICOR environment
{% endstep %}

{% step %}

## Step 2: Setup Schema in Kinetic <a href="#step-2-download-cabs" id="step-2-download-cabs"></a>

**Actioned by:** BISCIT Product Team

The BISCIT product team will deploy EKR CAB files in your EPICOR pilot environment initially. On go live, this will be the same for production.

{% hint style="info" %}
Application pool recycles and data model regenerations are required to complete this step.
{% endhint %}
{% endstep %}

{% step %}

## Step 3: Install Business and Functional CABs <a href="#step-4-install-business-and-functional-cabs" id="step-4-install-business-and-functional-cabs"></a>

**Actioned by:** BISCIT Product Team

The BISCIT product team will install some minor CABs, including BAQ, reports and BPMs.
{% endstep %}

{% step %}

## Step 4: Install SSRS Reports <a href="#step-5-install-ssrs-reports" id="step-5-install-ssrs-reports"></a>

**Owner:** Product Consultant&#x20;

1. Request SSRS Reports to be updated to customer specs&#x20;
2. Install BISC\_RMS\_Reports
   {% endstep %}

{% step %}

## Step 5: Configure EKR Login <a href="#step-6-log-into-rms" id="step-6-log-into-rms"></a>

**Owner:** Product Consultant and BISICT Product Team

1. Ensure the users in Kinetic has Allow V1 APIs enabled
2. Authentication options. See options below:

### Authentication Options for EKR

EKR supports two primary methods of integration for user authentication, depending on the configuration of Kinetic.

#### 1. Basic Authentication (Username & Password) <a href="#id-1.-basic-authentication-username-and-password" id="id-1.-basic-authentication-username-and-password"></a>

> If Kinetic supports Basic Authentication, users can log in to **EKR** using their existing username and password.

See here for steps: [<mark style="color:$primary;">EKR Login</mark>](https://app.gitbook.com/o/Ahnq5FWIxn9X9tsNkSHm/s/FuMjREj8WHcxhf8dRWZN/~/changes/10/installation/what-is-needed-to-login-and-how-to-login)

#### 2. SSO or Identity Provider (IdP) Authentication <a href="#id-2.-sso-or-identify-provider-idp-authentication" id="id-2.-sso-or-identify-provider-idp-authentication"></a>

> If Kinetic uses SSO or an Identity Provider, direct login with credentials is now supported. In this case, **EKR** must be embedded within Kinetic’s Home Page.

See here for steps: [Integrated Authentication via Kinetic Home Page](https://app.gitbook.com/o/Ahnq5FWIxn9X9tsNkSHm/s/FuMjREj8WHcxhf8dRWZN/~/changes/10/installation/integrated-authentication-via-kinetic-home-page)  <br>
{% endstep %}

{% step %}

## Step 6: EKR Setup <a href="#step-7-rms-setup" id="step-7-rms-setup"></a>

**Owner:** Product Consultant

1. Setup `Format Mask`
2. Setup `Hire Periods`
3. Setup `Price Groups`
4. Setup `Misc Charges`
5. Setup `Price Lists`
6. Setup `Customers`
   {% endstep %}
   {% endstepper %}


---

# 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://docs.biscit.com/ekr-user-guide/getting-started/kinetic-configuration-required.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.
