Create One Page per Workbook Tab
Creates one page of the package for each workbook tab the agent names, in a single call.
Overview
A filled inspection workbook is a stack of inspections, one per tab. Each of those tabs is one page of the document you get back, and this is the step that turns the tabs the agent identified into those pages, still empty.
Running it again is safe by design: a page is keyed by the tab it came from, so declaring the same set of tabs twice creates nothing twice.
What It Does
| Capability | What it means for you |
|---|---|
| One page per tab, one call | Every tab of the workbook that is a page is declared together |
| Different appendices in the same call | Each tab carries the appendix it is a page of, so a mixed workbook needs no second pass |
| Declaring the same tab twice is harmless | A tab that already has a page comes back as already there, and no second page appears |
| Your order is the package's order | The pages come out in the order the tabs are listed |
| One tab's failure is its own | Every tab gets its own result, and one that fails leaves the others created |
| The tab name is matched, not guessed | A name that matches no tab in the workbook is reported as not found by name |
When the Agent Chooses This Tool
Available in the Coating QA workflow. The Fill Any Form, appraisal-report and pre-bid workflows do not have it.
The instructions call it once, after the tabs have been matched to the appendices the package can fill, and require the tabs to be listed in workbook order.
- Only form tabs go in. A tab of instructions, pick-lists, configuration or a worked example is not a page and is left out.
- Every tab carries the appendix it was matched to, so tabs of different appendices go in the same call.
- Creating a page does not fill it. The values are copied in by the next step.
Inputs and Outputs
Takes: one entry per tab, each naming the workbook, the tab, and the appendix that tab is a page of.
Returns: how many pages were created, and one result per entry saying whether it was created, was already there, or could not be.
Example
The agent has matched five tabs of a vessel's workbook to three appendices.
One call lists all five in workbook order. Five pages appear in the package, in that order, each stamped with the tab it came from and still empty. A sixth tab the inspector added after the run is picked up on the next one, and the five that already have pages are reported as already there.
Limits
- A tab name is matched against the workbook, ignoring case and extra spaces, and a name that matches nothing comes back as not found while the rest are still created.
- Pages are keyed by tab name across the whole package. That is what lets you re-upload a corrected workbook and have it refill the same pages. It also means a package works from one workbook: a second one whose tabs repeat those names takes those pages over rather than adding its own.
- An attachment that is not a workbook, or one this package does not hold, is refused for every tab naming it, with the other workbooks in the call unaffected.
- A page created here is empty. What it holds comes from the fill that follows, and a page whose fill never runs stays blank in the finished document.
FAQ
I re-ran the agent after adding a tab. Do I get duplicate pages?
No. Pages are keyed by the tab they came from, so the tabs that already have pages are reported as already there and only the new tab gets one.
Can one workbook hold more than one kind of appendix?
Yes. Each tab is declared with the appendix it is a page of, and tabs of different appendices go in the same call.
What happens if I rename a tab between runs?
The old name no longer matches anything in the workbook, and the new name has no page yet, so the renamed tab gets a page of its own and the earlier one stays where it was.