> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping/summary.md).

# Summary

We use [**Bookmarks**](https://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping/bookmarks.md) to group **Field Mappings** by category. We compare the [**Source and Target**](https://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping/source-and-targets.md) from the integration framework and change the [**Status**](https://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping/field-mapping-status.md) to indicate that it has been reviewed. [**Comments**](https://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping/field-mapping-comments.md) are used to add further details during the **Pre-Mapping** Process.

**Pre-Mapping** is considered complete when EVERY **Field Mapping Status** has been transitioned from **Not Started** to **Needs Testing, Not Used, Waiting for Support, or Change Requested**

### FAQ

Q: What if the template doesn't have a field mapping for a field I use?\
A: Use your [Help Center](https://alphapack.atlassian.net/servicedesk/customer/portals) to let your Solution Engineer know and they will add it!

Q: Does every Field Mapping need a comment?\
A: No, they don't. But Comments help add context for the **In Progress** and **Waiting for Support** Statuses that will make the Mapping Phase run smoother

Q: How much information should I provide during the Pre-Mapping Stage?\
A: As much as possible! The more information you provide during the Pre-Mapping stage, the quicker your Solution Engineer can go during the Mapping stage. Put any additional information in a Comment on the Field Mapping


---

# 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://glyue.docs.sandboxbanking.com/tutorials/what-is-pre-mapping/summary.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.
