> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/help-center-index/troubleshooting-index/errors-index/jama-error-solutions/oh-jama-0040.md).

# OH-Jama-0040

### Description

When you encounter error OH-Jama-0040, then following error message will appear:\
**Error message:** OH-Jama-0040: Error occurred while fetching transitions details from Jama. Please provide state transition from external XML file.

Workflow transition is a feature supported by <code class="expression">space.vars.OIM</code> wherein the user can configure <code class="expression">space.vars.OIM</code> to automatically handle workflow transition of an entity as per requirement.

### Cause

Probable cause for this issue is:\
If we have a state transition defined for a field, but related details of Workflow transition are not provided in <code class="expression">space.vars.OIM</code>, then this error occurs.

### Solution

In <code class="expression">space.vars.OIM</code> field mapping configuration, we need to provide the state transition in given format. Refer to [Workflow Transition](/v7.237/integrate/configure-integrations/mapping-configuration.md#workflow-transition) for details.


---

# 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.opshub.com/v7.237/help-center-index/troubleshooting-index/errors-index/jama-error-solutions/oh-jama-0040.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.