> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/clients/mobile-clients/miscellaneous.md).

# Miscellaneous

### Field focus

When entering a user step the focus is not set in the first field as that would open the keyboard and cover a big part of the screen.

When moving forward user step, the focus is set in the next editable field.

When using a zebra scanner, or similar, the focus is automatically set in control so the user does not have to click on the screen to scan, see [Scanning](/clients/mobile-clients/scanning.md).

### List selection and list multi-selection

For the new generation clients, the Show Automatically setting in the studio is no longer used but the client will, as a rule, open the list selection and list multi-selection controls inline, ie show the controls opened directly in the user step. This has been changed in order to minimize the number of user clicks.

There are the following exceptions to the rule:

* if the list is too long, it is NOT inline
* if the user step contains other lists, grid, or other complex elements, it is NOT inline
* if the user step has more than one exit button, and none of them is set to default, it is NOT inline
* single select is inlined if the (there is a default button OR the list is <= 15 items) AND it's the only complex element

### Image editor <a href="#image-editor" id="image-editor"></a>

Images fetched into Camera and File Gallery controls can be edited. See Image editor in [Camera ](/development/flow-studio/applications/workflow/user-step/camera-input.md#image-editor)or [File Gallery](/development/flow-studio/applications/workflow/user-step/file-gallery.md#image-editor) control.


---

# 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://help.novacuraflow.com/clients/mobile-clients/miscellaneous.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.