> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/practical-guides/process-selected-records.md). # Process selected records Pass an explicit list of record IDs into an iterator when an app user chooses which tickets to process. ## Before you start You need a component action that exposes the selected records or their IDs, plus permission to update the test tickets. Inspect the values available in that action. A filtered list is not necessarily an explicit selection. ## Configure the workflow 1. Select two fictional tickets. 2. Configure the component action to run a workflow. 3. Add an input parameter named `ticket_ids` for an array of IDs, matching the type offered by the builder. 4. Bind the component's selected IDs to that parameter. If the component provides record objects, use its supported value-mapping controls to extract IDs, or pass the objects and reference each current item's ID. 5. Add an iterator with **Specify Iterate** and bind the array. 6. Add the update action inside the iterator. 7. Bind its record ID to the current item, or the current item's ID for an array of objects. For example, an ID-array test input might be `[1, 2]`. A record-object input has a different shape; inspect it before mapping. ## Verify the selection Check that the two selected tickets changed and an unselected ticket did not. Then test an empty selection. No ticket should be updated when the array is empty. If the component does not expose selected records, do not substitute all visible rows. Use an explicit ID input or follow the separate [filtered-collection iterator pattern](/workflow/build-workflow-steps/process-multiple-records-with-iterators.md) and label the action accordingly. ## Check failures If processing stops after some records change, inspect which IDs completed before running it again. See [partial success and duplicate processing](/workflow/handle-outcomes/handle-failures-and-prevent-duplicate-processing.md). --- # 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.jetadmin.io/workflow/practical-guides/process-selected-records.md?ask=&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.