> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/configuration/projection-administration.md).

# Projection administration

## Projection updates 

Projections may change during

* version upgrade (from version 21 -> 22) delivered by IFS,
* service update (SU) delivered by IFS twice a year, 
* patching provided by IFS between SUs,
* customized standard projections and custom projections updated during delivery updates 
* custom projections updates via Application Configuration Packages.

If in/out parameters are changed, each flow steps that using updated projection must be manually checked and refreshed.

## How do we know when projection is updated in IFS?

Depending on type of installation (SU, delivery update) different documents are produced. Below are examples of some documents produced.

### Service update

IFS can/should provide high level list of fixed issues to supplier.

<figure><img src="/files/CrmvltNnOlvoggJKJtMb" alt=""><figcaption><p>Service Update contents examples</p></figcaption></figure>

### Delivery Notes

Each installation will produce more specific list of changed projections.&#x20;

<figure><img src="/files/PWsSbBM3lOYSTXchn3FC" alt=""><figcaption><p>Example of projection change generated during delivery updtae</p></figcaption></figure>

## Documenting used projections in flow

{% hint style="info" %}
For the time being, before and if we have some other means of mining Projections used in flows, it could be a good idea to add an Annotation to each flow which lists the used projections.&#x20;
{% endhint %}

{% hint style="info" %}
Listing projections used in flows is also needed to grant projections to users in IFS&#x20;
{% endhint %}

## Locating used projection and operations in flow

Use Find functionality in Flow to identify:&#x20;

* Projection
* Operations

<figure><img src="/files/mjYzpupKdZCtwgHhchR4" alt=""><figcaption></figcaption></figure>


---

# 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.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/configuration/projection-administration.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.