Name the Output Package
Sets the name a finished package is listed under in your workspace.
Overview
A workspace fills up with runs. After a dozen of them the list is the only thing standing between you and opening files to work out which is which — and a run that was never named shows up under a snippet of whatever text was typed when it was started.
This tool gives the run a name. It sets the package's display name, the label the run carries in your workspace list, and reports back the name it set. It is the last thing the agent does before it stops.
What it does not change is the file. The finished PDF is stored and served under a fixed filename, the same one for every package, so a download that has to match your filing convention still has to be renamed. This name lives in the list, not on the file.
What It Does
| Capability | What it means for you |
|---|---|
| Names the run in the list | The package is listed under a name a person can read, instead of a snippet of the text it was started with |
| Shape fixed per workflow | Bid runs are named after the invitation file and the run's date; coating runs after the vessel or spreadsheet and the number of pages created |
| Last step of the run | The agent names the package once, at the end, and stops |
| Overwrites, never appends | Setting a name again replaces the one before it |
| Touches nothing else | No section, attachment or page content changes |
When the Agent Chooses This Tool
Two workflows can call this: contractor-bid packages and coating-QA packages. Appraisal packages cannot — they take their name from the subject property's street address instead, set by the tool that records that address (see Set Subject Property Facts).
In the two workflows that do use it, naming is the closing step and the call is made once. The wording is not left to the agent's judgement: each workflow states the shape of the name it wants.
- Bid runs — after the invitation is in hand. The name is the uploaded invitation file's own name together with the run's date. It is skipped when the run adds no new invitation: a follow-up that attaches only other files leaves the existing name alone.
- Coating runs — after the pages exist. The name is the vessel or spreadsheet name together with how many pages the run created — a count that does not exist until the work is done.
Naming ends the run. Assembling the PDF happens after the agent has stopped.
Inputs and Outputs
Takes: the name the package should carry.
Returns: confirmation, with the name that was set.
Example
A coating inspector uploads one spreadsheet for a barge job. The run reads it, builds the pages, and closes by naming the package after the vessel and the number of pages it made.
In the workspace list that run is now the barge job with its page count, sitting above three others from the same week. Finding it again is reading one line instead of opening four files.
The PDF still downloads under the same fixed filename every package downloads under. What changed is upstream of that: you know which one to download.
Limits
- The finished PDF downloads under a fixed filename, the same one for every package. This sets the name the package is listed under, not the name the file arrives with.
- Two workflows use it: contractor-bid and coating-QA runs. Appraisal packages are named a different way.
- Each workflow fixes the shape of the name. There is no setting for your own convention.
- In bid runs the naming step is skipped when the run adds no new invitation file, so a follow-up run keeps the name it already had.
- Nothing inside the PDF changes. A name printed on the form itself is a field, filled like any other.
- Individual sections and uploaded attachments keep their own identities and are not renamed by this.
- The list shows the name on one line and cuts off whatever does not fit.
FAQ
Can the output follow our existing file naming convention?
No. The finished PDF downloads under a fixed filename that is the same for every package, and the name this tool sets follows a shape the workflow fixes. Renaming a download to match your own convention is still a manual step.
When does the agent decide the name?
The workflow decides, not the agent. Naming is the closing step in both workflows that use it, called once: in bid runs from the invitation file's name and the run's date, in coating runs from the vessel or spreadsheet name and the number of pages created. Assembling the PDF happens after the agent stops.
Does this change anything printed inside the document?
No. It sets the name the package is listed under and changes nothing on the pages. A name printed on the form itself is a field, filled like any other.
Can the name be changed after it's set?
Setting it again replaces it. Neither workflow does that on its own: each names the package once and then stops.
Does naming file the document somewhere?
No. It doesn't create folders or move anything. It changes how the package is listed.