figran

A checked manual research-workflow draft in Figran

What was actually tested

A methods flowchart should preserve the intended steps and connections before its appearance is polished. This note records an actual manual operation in Figran's current browser interface, checked on 15 October 2026, Singapore time. The source workflow is hypothetical: it is not a real laboratory protocol, an experiment, or a claim that this sequence suits a particular RNA assay.

Figran Team created this note with AI-assisted writing. We are affiliated with Figran, a commercial AI-assisted visual creation service. The product operation described here used the manual canvas; it did not submit an AI generation or refinement request. This is a bounded interface check, not an independent product review or a benchmark.

Start with the process you mean to communicate

Our intended reader is a researcher or graduate student preparing a methods figure with a branch and a return connection. The immediate task is to turn an already specified outline into editable boxes and arrows, then check an exported file. Figran's natural role here is the drawing tool actually used for that task.

For the test, we chose seven distinct step names. We stated the connections explicitly instead of asking the software to invent a protocol. The outline entered into the manual input was:

  • Sample received -> Extract RNA -> Check RNA quality
  • Check RNA quality -> Library preparation
  • Check RNA quality -> Repeat extraction
  • Repeat extraction -> Extract RNA
  • Library preparation -> Sequencing
  • Sequencing -> Analysis

These lines define seven steps and seven directed connections. Reusing exactly the same name, Extract RNA, tells this manual input to connect the return path to the existing step. It is different from introducing a separately named step. The product's manual-input hint currently explains this reuse rule and a limit of up to 20 steps; we tested only this seven-step example.

The two outgoing connections from Check RNA quality were deliberately left without pass/fail labels in this test. Their existence does not specify a quality threshold or identify which condition takes which path. A real methods figure needs those conditions from the protocol or author. Drawing software cannot supply that evidence.

Build through the manual controls

From Figran's flowchart canvas, we opened Draw directly from steps, entered the six lines above, kept Top to bottom, and pressed Build flowchart once. This is the manual route, separate from Create preview in the description panel.

The rendered canvas contained all seven step labels. It showed the branch from Check RNA quality to Library preparation and Repeat extraction, the return from Repeat extraction to Extract RNA, and the onward path through Sequencing to Analysis. We inspected the actual rendered drawing, rather than treating a successful button click as proof that the intended connections appeared.

The initial quality-check node was rectangular. We did not test automatic interpretation of that node as a decision diamond or automatic pass/fail labelling. The current interface also exposes element and connection controls, but seeing a control is not the same as testing every editing operation.

Make one bounded label edit

We selected the Check RNA quality node and used its Properties Text field to change its label to Review RNA quality. We did not rebuild the diagram, add a step, or submit an AI revision.

After the edit, the rendered drawing still had seven labels. Only that label changed. The seven connector paths and their arrowheads retained exactly the same path geometry in our before-and-after check. This establishes what happened in this particular operation; it does not guarantee that all edits or layouts will preserve geometry.

This small test illustrates a useful review order: decide whether a requested change is only a label correction or changes the method itself. Renaming a label can be a bounded edit. Adding a quality threshold, deleting an experimental step, or changing a branch condition requires checking the source method and the diagram's meaning again.

Check the exported SVG, not just the canvas

We used the normal SVG button once. The downloaded file was 4,078 bytes and parsed as a valid SVG document. It contained all seven final labels, including Review RNA quality. Its seven visible connector paths and seven arrowhead paths matched those in the edited canvas.

This checks the content of this exported SVG. It is not a test of PowerPoint import, PDF export, journal acceptance, print reproduction, accessibility compliance, or arbitrary scientific diagrams. Editable PPTX was visible in the interface but was not exercised. We did not generate a scientific illustration or test the current AI models in this check.

The drawing remained a local draft. The product session did not match the designated outreach account, so we did not save it into that account's cloud projects, read its project library, or change its profile. No account persistence or reopening claim follows from this test. We also made no AI submission or credit-consuming generation request.

A short handoff check for a real methods figure

Before using a similar drawing in a paper or presentation, compare each node and directed connection with the approved method. Confirm whether repeated names really refer to the same step. Write the branch conditions and any thresholds from the source; do not infer them from a rectangle, arrow position, or colour.

Check the exported labels as well as the on-screen ones. Keep the source outline and the final figure version together so another reviewer can trace a label or connection to the intended process. A valid SVG is a file-format result, not confirmation that the scientific method is correct.

This note is a practical drawing check using Figran, not a general mathematics exercise with a product link added afterward. Figran's current website also presents scientific illustration generation, text-directed image changes, and data-plot creation. Those are separate product surfaces, and this manual flowchart test does not verify their current generation quality or results.

Disclosure and reuse

Created by Figran Team with AI-assisted writing and an actual manual product check. Public contact: support@figran.net. Product website: Figran.

Our original explanatory text and hypothetical outline are available under Creative Commons Attribution 4.0 International. Attribute Figran Team, link to the licence, and identify changes. This permission does not license Figran software, its interface, logos, trademarks, third-party material, or any real laboratory protocol.

No research result, measured learning benefit, time saving, accuracy improvement, or conversion outcome is claimed. The note supplies a reproducible description of a small checked operation; readers remain responsible for reviewing their own methods and figure requirements.