> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/v2.3/platform/release-notes/ifix-core-release-notes/ifix-core-build-updates.md).

# iFIX Core Build Updates

With the iFIX v2.3-alpha update, some of the DIGIT core services also need to be deployed. The builds of the same are also listed below. These have been picked from DIGIT-v2.7. 

<table data-header-hidden><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td>Category</td><td>Services</td><td>Docker Artifact ID</td><td><strong>Remarks</strong></td></tr><tr><td><strong>IFIX Domain Services</strong> </td><td>IFIX Master Data Service</td><td><pre data-overflow="wrap"><code>ifix-master-data-service-db:develop-b3f4ff0-3
</code></pre></td><td><ul><li>Removed government master from the service</li><li>Migrated chart of account from MongoDB to PostgreSQL</li></ul></td></tr><tr><td></td><td>Fiscal Event Service</td><td><pre data-overflow="wrap"><code>fiscal-event-service-db:develop-4c14ba4-8
</code></pre></td><td><ul><li>Move to DIGIT architecture</li></ul></td></tr><tr><td></td><td>IFIX ES Pipeline</td><td><pre data-overflow="wrap"><code>ifix-es-pipeline:develop-2dc38e9-4
</code></pre></td><td><ul><li>New kafka stream pipeline to transform data that will be stored in ES. </li></ul></td></tr><tr><td> </td><td>Fiscal Event Post Processor</td><td><pre data-overflow="wrap"><code>fiscal-event-post-processor:develop-4c5c4f8-2
</code></pre></td><td><ul><li>Changes maintain compatibility with other updated services. </li></ul></td></tr><tr><td><strong>Frontend</strong></td><td>DIGIT-UI</td><td><pre data-overflow="wrap"><code>digit-ui:develop-f26305c-1
</code></pre></td><td></td></tr><tr><td><strong>Core Services</strong></td><td>dashboard-analytics</td><td><code>dashboard-analytics:v1.1.7-1ffb5fa2fd-49</code></td><td></td></tr><tr><td></td><td>egov-mdms-service</td><td><code>egov-mdms-service:v1.3.2-72f8a8f87b-12</code></td><td></td></tr><tr><td></td><td>egov-indexer</td><td><code>egov-indexer:v1.1.7-f52184e6ba-25</code></td><td></td></tr><tr><td></td><td>egov-localization</td><td><code>egov-localization:v2.5-log4j-12a9331b-2</code></td><td></td></tr><tr><td></td><td>egov-persister</td><td><code>egov-persister:v1.1.4-72f8a8f87b-6</code></td><td></td></tr></tbody></table>

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*

&#x20;


---

# 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.digit.org/public-finance/v2.3/platform/release-notes/ifix-core-release-notes/ifix-core-build-updates.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.