Action sheet
Each .aia set opened step by step: dialog on, "Save As" with a recorded name, a step inserted via menu item, owner and review date.
Deliverable: ficha_acoes.csv reviewed with designOcto for actions, batch and variables in Illustrator
Illustrator plays actions over whole folders with Batch and turns a spreadsheet into pieces with the Variables panel. Octo inventories the actions, builds and checks the spreadsheet before importing, exports each data set without overwriting anything and checks the folder by content. The artwork, the copy and the release stay with people.
Six possible deliverables, drawn from the assessment. None saves over the original, all check the result by content, and all go to review by whoever is accountable for the piece.
Each .aia set opened step by step: dialog on, "Save As" with a recorded name, a step inserted via menu item, owner and review date.
Deliverable: ficha_acoes.csv reviewed with designHeaders without spaces, "@" for images, "#" for visibility, relative paths, UTF-8 and data set names that become file names.
Deliverable: checked crachas_evento.csvProof PDF, print PDF and screen PNG, with preset, resolution and file size. The script and the check read the same file.
Deliverable: perfis_saida.json with historyDisplays each data set in the template, exports one file per profile with the standard name and logs what came out and what is pending.
Deliverable: exportar_conjuntos.jsx and registro_conjuntos.csvOne file per row and per profile, missing, extra, valid PDF, PNG size, file size and a sha256 manifest.
Deliverable: conferencia.csv and manifesto.csvThe artwork folder is read-only; the queue works on copies with sha256, in parts, each with its own output folder.
Deliverable: fila_lote.sh and fila.csvThe same Octo cycle, applied to actions, Batch and variables. Each arm has a narrow role; the people approve the artwork, the copy and the delivery.
Which pieces go out every month, with which templates and actions, on which Illustrator version and on how many workstations.
Action sheet, output profiles, naming pattern and data sets in versioned files.
Originals read-only, separate output, nothing overwritten, spreadsheets with personal names flagged (LGPD).
Batch on a folder, Batch on data sets, a script or an SVG template, depending on the task and the volume.
Script that walks the data sets, a queue for the artwork folder and a check, with the source of each rule noted.
Missing, extra, format, size, file size and name. "Batch finished" is not a check.
Checked folder and manifest. Sending to the printer or the client is approved by a person.
Templates, actions and versions, profiles, who approved each batch and what changed between versions.
Octo does not save over the original or overwrite files. It does not approve artwork, change a template without the designer or decide the print PDF.
The criteria Octo uses to choose, with the documented limit of each path.
| Task | Path | Note |
|---|---|---|
| Same action on an artwork folder | Batch, Folder source | Destination = Folder; "Save and Close" saves over the file |
| One piece per spreadsheet row | Variables and Batch, Data Sets source | File name from the data set name |
| Several outputs per piece, with a log | Script walking dataSets | Does not overwrite; an existing destination becomes pending |
| Several actions or several folders | Action that records the Batch command | Tip from the Help itself; folders via shortcut |
| Pen, Paintbrush or Effect menu step | Stop with a message or a menu item | Not recorded directly; a person follows along |
| Another system fills in the variables | SVG template with data from Graphics Server | Object names in XML-safe form |
| Check the generated folder | Python, outside Illustrator | Missing, extra, format, size, sha256 |
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Octo opens the actions and checks the folder that already goes out, without changing how you produce.
Spreadsheet checked before importing, a template with locked variables and Batch on data sets.
Script with several profiles per data set and a checked queue for large artwork folders.
Each point below has a source published by the vendor, the project or the responsible body. The sources are in the next section.
6
points with a published source, each with its reference shown alongside.
Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: files, artboards, proofs and reports.
Deliverable: material ready to checkThe client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the approverOcto does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.
Approval: client or art directorIllustrator Help pages, Adobe's developer page and the scripting reference in the community guide that reproduces Adobe's content, consulted on Oct 31, 2026.
The assessment starts with a sheet of the actions already running and a check of an output folder that already exists. You get what was missing, what was extra, what came out off-profile and the questions only your team can answer, and you decide with that in hand.