What's New

Stay up to date with the latest improvements to AseptSoft. This page highlights recent changes, with links to the full documentation for each feature.

🗓️ June 2026

This update rolls up a large batch of capabilities across version control, equipment modules, process design, annotation, fluid mapping, and platform support.

🔁 Version Control & Merge

📋 Saving a version used to mean three different things. The module gallery's Create Commit button made a loose, history-less file copy into a flat folder; bumping a version number in an export window made another loose copy; and the only real history lived in a separate browser. None of these talked to each other, and a "commit" carried no author, description, diff, or way to restore.

✅ Now they are one thing. Every checkpoint — whether you create a commit from the module gallery, or AseptSoft records one automatically when you raise a version number during a PDF/Word/Processes export — lands in a single, real commit timeline for that module. Each commit carries who made it, when, your description, and a summary of what changed (+added ~modified −removed) compared to the commit before it.

🕑 The new Version Control browser is one click away from the module ribbon's Data split button or the module gallery's Version History… menu. From it you can read the full history, see exactly what any commit changed, compare any two versions, and restore an earlier state safely — restore always produces a brand-new module, so your current work is never overwritten. Big diffs stay navigable with filters by change kind and entity category, and grouping by PID or Process. Changes read in plain domain terms — coloured state bullets, valve/instrument chips with their PID, percent bars, fluid names, "the version went 1.1 → 1.2" — with no raw identifiers, and can be copied to the clipboard (readable or raw) for a change record.

➡️ Full details: Version History & Comparison and Commits and Branches.

Visual merge-conflict review

🔀 Resolving a merge used to mean reading a flat grid where each record was dumped as key: value text — a phase showed as a name with no idea which Process it belonged to, a valve state read State: Open / Percent: 50 with no sense of what colour "Open" was or whose step it referred to, and you had to scroll the whole list even when only a couple of fields actually differed.

✅ Now conflicts are reviewed visually. Each conflict is a compact card that leads with only the fields that differ, shown as click-to-pick Incoming and Current panels (plus a neutral Base column for a true three-way view). Values render richly — state colour bullets, valve/instrument chips with their PID, percent gradient bars, named references — and a "Full record" toggle expands the whole thing on demand.

🧹 Far fewer conflicts reach you. Identical changes, purely-additive changes, cosmetic colour differences, and knock-on (transient) conflicts are resolved automatically and hidden — you only decide the genuine disagreements. A side rail lets you group and filter conflicts by Process/Step/Item, PID, table, or kind, and reordered sequences are reconciled as one Order conflict with a single drag-and-drop final-order list instead of fighting over each step's slot. Every conflict — or all of them at once — can be copied to the clipboard, readable or raw.

➡️ Full details: Merging.

🔗 Manual cross-sheet OPC connections

Before: Off-Page Connectors could only pair automatically, using their Tag/Bind matching rules across sibling sheets. If the naming didn't line up, there was no way to express the link by hand — and if the rules inferred a link you didn't want, there was no way to suppress it.

Now: you can author or cut a specific cross-sheet OPC link directly from the connector's hover popup. Click Connect to another OPC…, choose a sheet (your active sheet is listed first and highlighted; open siblings follow), and point at the partner connector on the drawing — the green bullet lights up and fluid flows across the sheets on the same gesture. When a connector already has links, you choose Keep to add the new partner alongside the existing ones or Replace to make it the sole route. The Connected to list now shows every partner an OPC holds, each with its own Navigate and Disconnect buttons; Disconnect is origin-aware — it bans an automatic link or clears a hand-made one. Manual connections and bans are saved against each sheet's durable identity, so they survive drawing re-versioning and are shared with everyone working in the module.

See Off-Page Connector for the full workflow.

🪜 Sub-steps now export to PDF and Excel

Before: Exporting stopped at top-level steps. Composite steps that hosted their own sub-process showed nothing of their sub-steps in the PDF or the Excel matrix — the detail you built was invisible in the deliverable.

Now: Both the PDF and the Tabular Excel export carry a Sub-steps choice — Only the step, Only the sub-steps, or The step and its sub-steps — applied consistently across the whole export and remembered per module. In PDF, composite steps emit their sub-step pages with path-qualified bookmarks (e.g. Caustic Wash ▸ Recirculate), continuous page numbering, and a preview tree that mirrors exactly what you’ll get; multi-P&ID page correspondence stays intact even as sub-steps add or drop pages. In Excel, sub-steps become path-qualified columns headed “Step ▸ Sub-step” inserted after their parent step, fully round-trippable on re-import (plain step headers are unchanged).

Read more: Export Processes to PDF and Export Processes to Excel - Tabular.

📈 One PDF export now also produces GRAFCET and EM SFC decks

Before: Each kind of PDF lived behind a different button — process P&ID PDFs on the Module ribbon, GRAFCET PDFs inside the GRAFCET window, and Equipment Module SFC PDFs on the Equipment Modules ribbon. You had to remember and visit each one.

Now: The main Export-PDF window has an SFC group with two checkboxes — Phases SFC and Equipment Modules SFC. Tick either and, after the normal P&ID PDFs finish, AseptSoft automatically runs the matching dedicated export into Processes/GRAFCET/ and Equipment Modules/PDF/. The settings persist per module, so teams who deliver all three kinds tick once. The original dedicated buttons remain for one-off use.

Read more: Export Processes to PDF.

🧭 Header blocks gain breadcrumbs and an Equipment Modules summary

Before: A title block could show the process and step, but had no way to say which sub-step a drawing belonged to, and no at-a-glance view of how each Equipment Module was set on the current step — you had to open the matrix. After editing a preset, surfacing a newly added field usually meant deleting and re-inserting the block.

Now: A one-click Breadcrumb (Process › Step › Sub-step) field shows the full path and grows its sub-step segment automatically only when you drill in — with a separator you choose. A new Equipment Modules field lists one line per module (Module: assignment) for the current step, skipping idle modules and marking gaps with an em-dash; it ships as its own default preset. And every Save & Apply now refreshes every existing block in place (full ATTSYNC of geometry and new fields) and always offers a placement prompt — no more delete-and-reinsert to see changes.

Read more: Header Block.

Cross-Tag Valve Function Migration — reuse a P&ID's behaviour on a differently-tagged twin

Cloning a near-duplicate P&ID used to mean re-authoring every per-step valve state, control relation, equipment module and interlock by hand on the second drawing, because its valves carried different tags from the original. Cross-Tag Valve Function Migration removes that duplicate work: you describe the tag correspondence once with a simple pattern, and AseptSoft clones each valve's full function from the source P&ID onto the matching valves of the destination P&ID.

Full documentation: Cross-Tag Valve Function Migration.

Valve Traceability — behaviour now stays glued to the valve through every drawing change

Valves used to lose their per-step open/closed states during routine drawing hygiene — a copy/paste, a file rename, an offline edit, or a tag change could silently drop or transpose the configured behaviour, with the only recovery being a first-come-first-served tag fallback that missed most cases.

Full documentation: Valve Traceability.

Equipment Module configuration cells now carry full operating detail — and modules can be built with their instruments

An Equipment Module Configuration used to record only a state name per cell. Each cell now carries the complete operating specification of an item in that configuration: the state, an opening percent, typed in-state attributes (checkboxes, numbers, and pick-lists), or an instrument-control relationship — a cell is either a fixed state or under instrument control, never both. The template matrix shows each cell as a scannable summary (coloured bullet, state, percent, a tag pill for attribute count, a gear pill for the controlling instrument), and a single click opens the Configuration Cell Editor with a Set-state / Under-instrument-control mode toggle.

Creating a module from a drawing selection also brings instruments along, not just valves — each detected instrument gets an editable nickname in the same creation window, so its template slot is named the way you want from the start.

See Equipment Module Configurations & Phases for the full anatomy of a rich cell and the cell editor.

Equipment Module Workspace — Overview and per-phase SFC side by side

Editing an Equipment Module graphically previously meant bouncing between two separate top-level windows — open the Overview, click into a phase, get a second window, close it, repeat. These are now one combined Workspace: the Overview (all Configurations and Equipment Phases as a sequential function chart) on the left and the per-phase control-step editor on the right, with a draggable splitter and collapsible panes whose expand button always lives on the pane that stays visible. A change on one side reflects on the other instantly. The canvases gained snap-to-grid dragging, clean orthogonal edge routing, distinct START/END configuration cards bracketing each phase's steps, inline edge-condition editing with intellisense, and working one-click vector PDF export (per phase, combined, or batched for every module).

See Equipment Module Workspace & SFC Editors.

Process steps can be driven by an Equipment Phase (a trajectory), not only a Configuration (a snapshot)

Assigning an Equipment Module into a process step used to mean picking a static Configuration only. A step can now be driven by either a Configuration (a resting snapshot) or an Equipment Phase (a trajectory of control steps that ends in a configuration, or in a designated end step for looping phases). The Valve Phase Matrix cell dropdown interleaves each Configuration with the Phases that end in it — so you read snapshot-versus-trajectory at a glance — previews the choice live on hover before you commit, and flips the cell's header icon to a play marker when a Phase is in control. Phases mirror their destination configuration's colour unless you override it, and the whole picture round-trips through Excel by name with no loss.

See Equipment Module Configurations & Phases.

Processes Workspace — a single five-column window for the whole process design

📊 Process and step management used to be split between the ribbon's separate Processes and Steps panels, with no single place to see how a process, its steps and their conditions fit together. They are now unified in the Processes Workspace: five linked columns that read left to right — Processes → Steps → Conditions → Sub-steps → Sub-conditions — where selecting an item in one column reveals its contents in the next. Where you previously navigated steps one at a time and re-checked the drawing to see which was live, the workspace now tracks two paths at once: the active path (bold coloured stripe, live on the P&ID) and the selected path you are inspecting (neutral highlight), dimming the columns past any branch point so a parallel branch is obvious at a glance. The old text-only "active cascade" line is now an interactive breadcrumb of clickable chips that jump the live state to any sibling step. Column visibility, column widths and the window size are remembered between sessions, and you can dock the window as a narrow vertical strip or stretch it wide. Drag-drop reorder now shows a blue insertion line, step codes are editable inline from a badge, and a single Refresh button rebuilds everything from scratch. Full details: Processes Workspace.

Auto-Naming Rules — consistent step names and codes generated for you

🏷️ Step names and codes previously had to be typed in by hand for every step. You can now define naming rules once per module and have AseptSoft generate names and codes automatically whenever a step is created or duplicated. Patterns mix fixed text with tokens — sequential numbers ({N}, padded {NN}, stepped {N,10}, offset {NNNN,10,1000}), {PROCESS}, {PROCESS_CODE}, {MODULE}, {NAME}, {INITIAL} — refined by modifiers such as :UPPER, :VOWELLESS and :FIRST3. Generated numbers are collision-safe, so duplicating a step never produces a clashing code. Beyond the original engine, you can now switch code generation on or off independently for steps, sub-steps and processes, choose separate patterns for sub-steps, and pick whether cards lead with the Name or the Code. A click-to-insert token palette and a live three-row preview show the numbering before you save. Leaving every pattern blank keeps naming fully manual. Full details: Process Design — Auto-Naming Rules.

Composite Steps — nest a sub-process inside a step

🧬 A step used to be a single point in time. A step can now be marked composite, containing its own internal sequence of sub-steps (a sub-process) — aligning with the ISA-88 idea of nested procedures. A Caustic Wash step, for example, can expand into Fill caustic → Circulate → Drain caustic, each sub-step with its own valve states and transition logic. In the column view, two extra columns (Sub-steps and Sub-conditions) appear for composite steps and a Make composite + add first sub-step button converts a leaf step in place. In the SFC Editor, composite steps are drawn with an indigo double border and you double-click to drill in; a breadcrumb bar shows your depth and lets you navigate back up. PDF export can summarise a composite step to one resolved colouring or expand it to show every sub-step. Full details: Composite Steps and Sub-Processes.

Highlighter Designer: real shapes, an intelligent inspector, and span-fit text

The Highlighter Designer now renders every shape kind exactly as AutoCAD will plot it and adapts its editor to the shape you pick.

• Before: six shape kinds (polygon, hatch, split panel, polyline, path, icon) fell back to a plain bounding rectangle; the icon shape could not actually pick a glyph; dynamic colours were lost the moment a colour was re-picked; and the inspector showed every field for every shape regardless of relevance.

• Now: all ten shape kinds render faithfully in both the live preview and the drawing — including FontAwesome icons drawn as real geometry so they print without the font installed. The inspector shows only the fields that matter for the selected shape, the shape and catalog rows carry recognisable icons, the icon picker is a searchable list with a glyph beside every name, and colour fields are mode-aware (Fixed, item-state, active-fluid, or token) so dynamic colours round-trip instead of collapsing to a fixed colour. Per-part visibility, line weight, line type, and rotation are all editable, with inline validation on expression fields.

Text parts can also be spanned between two points to fit a wall or box: text that is too long is always condensed to fit, while shorter text keeps its natural proportions and is aligned (or, with Longer to fill, stretched to touch both ends), and Auto-break wraps long notes instead of squeezing them.

Read more: Highlighters.

Placed highlights now scope to a step, a process, or the whole module

Placing a free-form highlight now offers three visibility buckets instead of the old step-only / all-steps pair.

• Before: a placed highlight could only be visible on its own step or on every step — a drawing-wide note had to accept step-only visibility or be re-placed on each step, and there was no way to make a note follow one process.

• Now: choose This step (visible only while its step is active), This process (rides along through every step of its process), or Whole module (always on screen). The Manage Placed Highlights window shows each placement's bucket as a coloured scope pill, its Locate action activates the correct PID and step/process before zooming (and respects modelspace vs. layout viewports), and the list refreshes live as you switch drawings or steps. PDF export honours the scope automatically — module notes print on every page, process notes on their process's pages, step notes on their step's page.

Read more: Highlighters.

Instrument-alarm highlights on the drawing

Instruments that participate in alarms can now be marked directly on the P&ID.

• Before: the instrument hover popup listed each instrument's alarms, but a reviewer scanning the drawing had no visual signal for which instruments carried alarms — and no way to ship that information in a PDF.

• Now: a Show Instrument Alarms toggle on the Module ribbon's Highlight dropdown marks every alarm-referenced instrument with a red diamond, a ⚠ ALARM banner, and its alarm names. The diamond shape is distinct from the square instrument frames, so it stacks on top without confusion (an alarm-tagged controlling instrument shows both its magenta square and its red diamond). The overlay refreshes the instant an alarm is created, edited, or deleted, and the PDF export has an Instruments used in Alarms checkbox so an alarm review can be shipped as a one-click deliverable. The same Highlight dropdown also mirrors the Equipment Module overlay toggle, and Equipment Module configuration cells that name a controlling instrument paint control highlights on their own.

Read more: Equipment Module Highlighting and Highlighters.

Hover popups you can move, sort, search, and pin

The valve and instrument hover popups gained a layer of control they never had before.

Before: popups appeared in a fixed position you couldn't influence, the valve states gallery was always sorted by creation order with no way to find a state by name in long lists, and any adjacent hover area would steal the popup before you could reach it.

Now:

• 🖱️ Drag to reposition. A grip handle on each popup header lets you move it; the corner nearest the item stays glued to the item, and the placement is remembered per popup type.

• 🔍 Sort, search, and Most Used. The valve states gallery now sorts by name or by colour, offers a live search box on valves with many states, and surfaces your recently-applied states in a Most Used row for one-click recall.

• 🔒 Sticky & lost-interest. Holding Ctrl/Alt locks a popup on the item you pointed at so you can reach it through busy areas; once you leave the popup, it dismisses itself instantly instead of lingering.

See Valve Hover Inspector and Instrument Hover Inspector.

A real settings window for valve hover popups

Configuring when valve popups appear is now a proper dialog instead of a command-line prompt.

Before: choosing the popup mode meant answering an AutoCAD keyword prompt on the command line, and there was no way to silence specific valve types — popups were all-or-nothing.

Now: AseptSoft Settings → Interactive Hover → Valve Hover Popups opens a window with three selectable mode cards — Off, Always on hover, and Ctrl + Hover, each stating what it does at a glance — and an Excluded valve types checklist. Any usage type you check there never shows a popup, even when popups are turned on, so you can keep popups for the valves you actually inspect (CV-202, XV-101) and silence noise like plain fittings.

See Valve Hover Inspector.

♻️ Reusable Alarm Templates

Authoring a fresh alarm in an empty form for every new tank, pump, or reactor used to mean re-typing the same rationalization — priority, severity, classification, acknowledgement and shelving rules, routing, return-to-normal behaviour, and operator guidance — over and over, when in practice only the tag, setpoints, and units change between instances.

Before: Every alarm had to be built from scratch (or copied one row at a time), and there was no project-wide place to keep a well-reasoned alarm shape for reuse across modules.

Now: You can capture a fully rationalized alarm once as a project-wide template and stamp it out per instance. Right-click any alarm (or use the button in the alarm editor) to Save as Template…; use the split "+" button's chevron to add From Template…; pick from a searchable, keyboard-driven picker; refine templates in a dedicated Manage Templates window with a full snapshot preview; and browse/apply templates from a collapsible Templates panel inside the alarm editor itself. Templates live with the project — available in every module — and act as seeds: editing or deleting a template never touches alarms already created from it.

See the full documentation: Alarm.

Valve drive mode: a valve is either manual or under control — never both

📊 Valve drive mode is now an explicit per-step discriminator. Previously a valve could carry a hand-picked state (Open / Closed) and be shown as driven by an instrument at the same time, which produced contradictory highlights and ghost control relationships. Now, for any given step, a valve is in exactly one of two situations: a manual state (Open / Closed you assign by hand) or under instrument control. The moment an instrument takes the Controlling role over a valve in a step, that valve's state for that step becomes one of two named control states — Under control for ordinary on/off valves, or PID control for intrinsic control valves — and a hand-picked Open/Closed for that step releases the control link instead of coexisting with it.

Both control-state names, the separator character (⚙ by default), and whether the controlling instrument's tag and its linked variable/parameter (XX source) appear are configurable for the whole environment, so each site can use its own vocabulary (AUTO, PID, CV control, Under PLC control). The role an instrument plays is also explicit per step: Controlling drives the valves, while Monitoring only reads the process and claims no valve.

See the full documentation on Control Loop.

Control cells in the matrix and Excel — round-trippable

🔄 Controlled valve cells now compose the control state together with the controller, and survive a round trip through Excel. Where the matrix previously showed only plain state text, a valve driven by an instrument in a step now reads as a single composed identifier — for example PID control ⚙ FIT-203 — naming the control state, the separator, and the controlling instrument (optionally with the XX source). Exporting the process writes that exact text to the spreadsheet step by step, and importing it back parses the cell, matches the instrument by tag, and restores the per-step control relationship automatically; if the named instrument is missing, the valve keeps the plain control state so visuals stay correct until it reappears.

Because the composed text is identical end to end, a process reviewed and edited in Excel returns to AseptSoft with its per-step control configuration intact. The same instrument can also drive a completely different valve set in each step — control one pair during Pre-Rinse, only monitor during Caustic Wash, and trim a different valve during Acid Wash — and the matrix and Excel both reflect that step-by-step.

See the full documentation on Valve Phase Matrix.

Ignored Entity Types: per-project, type-level fluid control

📋 Fluid-map inclusion can now be controlled by entity type, per P&ID, instead of only entity-by-entity. Previously, keeping a whole category of objects out of the fluid stream meant picking each one in the Override Fluid Map editor; a drawing full of border polylines or label splines was tedious to clean up.

The Ignored Entity Types setting (Settings window) lists AutoCAD entity types with a per-type checkbox and a finer sub-option. Each type can now be in one of three states:

Both checked variants gray out during fluid-stream visualization, matching how other non-fluid entities already appear.

👉 See Fluid Map Overrides for the full workflow.

Controlled-Valve Linetype Override (resilient across drawings)

🧵 Fluid that flows past valves under instrument control can now be drawn with a distinct linetype automatically. Previously, making regulated fluid look different meant manually setting a fluid linetype override on each controlled-valve state, every time.

The new environment-scope Controlled-Valve Linetype setting does it with one checkbox and a linetype choice: tick it, pick a linetype, and fluid travelling past any binary- or modulating-controlled valve adopts that linetype from the valve onward — applied to every controlled valve at once, taking effect immediately without reopening the module.

👉 See Fluid Map Overrides.

Intermittent marks are now phase-scoped

🔄 Intermittent marks now belong to a phase instead of being a single drawing-wide flag. Previously, marking an entity intermittent applied it to every phase, which made it unusable when the same drawing took part in several phases that needed different intermittent behaviour.

Now each (phase, P&ID) pair owns its own intermittent set:

• Before: one universal list — an entity was either intermittent everywhere or nowhere.

• Now: a drain valve can pulse intermittent during Pre-Rinse and Final Rinse yet run continuously during Caustic Wash, each phase keeping its own list.

The Toggle Intermittent loop names the active phase and its count, follows you automatically if you switch phases mid-session, and offers a three-scope WipeAll (this phase / this phase across all P&IDs / all phases on this P&ID). Duplicating a phase carries its intermittent set forward as a starting point.

👉 See Fluid Map Overrides.

🧩 AutoCAD & Plant 3D 2027 now supported

AseptSoft now installs and runs on the AutoCAD 2027 and AutoCAD Plant 3D 2027 release lines. Previously the bundle covered releases up to 2026; it now extends through 2027 while continuing to support every earlier year (2018 onward). As before, a single installation covers every supported AutoCAD and Plant 3D version on the machine at once — installing on a 2027 workstation needs no special steps, and the correct module loads automatically with the same ribbon, commands, and behaviour as on previous releases.

See Software Updates for the full list of supported releases and how the matching module is chosen.

🔄 One master switch for auto-activation

The Activation Settings now centre on a single master switch — Automatically activate AseptSoft when opening drawings — that decides whether AseptSoft starts up at all. Previously there were two separate global checkboxes (one for never-before-seen drawings and one for drawings used with AseptSoft before). They are replaced by this one switch, which can be set the instant AutoCAD opens, before any project or drawing is loaded. When it is off, nothing AseptSoft-related runs in the background — no ribbon, no scanning, no automatic update checks — until you activate it by hand for the drawing you actually want to work on. The per-project and per-drawing refinements remain, and now appear only while a project is open.

See Activation Settings for the master switch, the refinements, and the manual-activation workflow.

🗓️ May 2026

🖍️ Annotation overhaul — Highlighters and Descriptions

Previously, the highlight system was a thin "draw geometry, mark as highlight" tool, and there was no first-class way to attach a description to an entity that travelled with it across surfaces. State-driven visual feedback was hard-coded; per-step values like Open delay on a Pulsating valve had to live in custom tracker text.

Now, two coordinated systems give you a full annotation layer over the P&ID.

👉 Full documentation: Highlighters · Descriptions · State

🛠️ Fluid Map Overrides — per-drawing manual control

Previously, when the automatic fluid map disagreed with how a drawing actually flowed, the only options were to edit the drawing to match the heuristics or live with the result. There was no way to force-include a specific entity, ban a phantom edge, or mark a single entity as intermittent.

Now, Override Fluid Map opens an interactive editor that lets you author drawing-specific exceptions on top of the automatic mapping. Overrides are saved with the drawing, never modify the drawing itself, and stay synced with the project's normal save/load lifecycle.

👉 Full documentation: Fluid Map Overrides · Fluidstream Simulations

🪪 Licensing experience overhaul

Previously, browser-based PKCE login was the only option, AutoCAD reserved a seat eagerly at startup whether you used AseptSoft or not, server-side seat revocations left you in a silent limp-mode where commands just stopped working, and the "Too Many Devices" dialog gave a generic message that made resolution a guessing game.

Now, the licensing layer is significantly more honest about state and friendlier to recovery.

👉 Full documentation: Login and Subscription

📤 Word + Excel from one configuration

Previously, the Export to Word ribbon button produced a Word document; getting the same content as a spreadsheet meant re-running a different export with separate configuration.

Now, the same window — renamed Export Module Data — has a Format selector at the bottom: Word (default ON), Excel (default OFF). Tick either, both, or neither.

👉 Full documentation: Export Module Data to Word and Excel

📄 PDF Export auto-switches from Model

Previously, exporting a P&ID currently on the Model tab produced an unusable model-space plot. You had to manually switch to a paper-space layout before clicking Export.

Now, AseptSoft auto-switches to the right paper-space layout. Resolution order: single layout → per-PID override → match against the global preferred-layouts list (seeded with AseptSoft) → optional one-time prompt with an "Add to preferred" checkbox.

👉 Full documentation: Export Processes to PDF

☁️ Environment Updates: always-visible push button + Cloud Scope pill

Previously, the per-row push-to-cloud icon was hidden whenever you didn't have permission to push — leaving you wondering whether the feature was missing or your role was. There was also no on-screen indication of which cloud organization (tenant) the window was operating against.

Now, the push icon is always shown when a cloud manifest exists. When you can't push, the icon is greyed with a small red ! badge — hover for the precise reason (no role, not logged in, server unreachable, etc.). Manually-assigned roles via the 10Duke admin UI are recognised, not just programmatically created ones.

The Environments section header carries a new indigo pill — for example, ☁ Cloud scope: Jacobs — derived from your local manifest. On a machine configured for Jacobs vs Abcd, you can visually confirm the target before clicking, and support can ask "what does the scope pill say?" instead of hunting through manifests.

👉 Full documentation: Environment Updates

📦 Auto-update recognises both deployment formats

Previously, AseptSoft installed via the Autodesk bundle.exe (per-user, no admin) was reported as "not managed by auto-update" even when a valid version.json was present on disk — the updater simply didn't know to look there.

Now, both MSI (Program Files, admin rights, Add/Remove Programs entry) and bundle.exe (per-user under %APPDATA%\Autodesk\ApplicationPlugins, no admin rights) installations are recognised as managed. When neither is recognised, the Software Updates window offers a side-by-side switch panel — pick MSI for IT-managed fleet deployments or bundle.exe for individual users without admin rights. Each option is explained in one line so the trade-off is visible without reading documentation.

👉 Full documentation: Software Updates

✨ Smaller polish

🗓️ April 2026

🧩 Interactive Create Equipment Module

Previously, the Create Equipment Module command was a one-shot flow: select some valves, type a name, and the module was created immediately with a 1:1 valve-to-item template. There was no review step, no way to add a second module without restarting, no conflict checking against existing modules, and no way to adjust the template or item names before committing.

Now, the command opens the same rich review window used for Excel imports, letting you configure and confirm multiple Equipment Modules in a single interactive session.

The Excel import window gained the same editable-name behavior: worksheet names are now editable before committing, and press-Enter-to-import works anywhere.

Valve exclusivity is now enforced project-wide and across all entry points — Create from Selection, Add another EM, and Excel Import all refuse to assign a valve that already belongs to another module, with a clear dialog explaining which module owns which valve.

👉 Full documentation: Equipment Module · Import Equipment Modules from Excel

☁️ Environment Updates with Backup, Rollback & Cloud Push

Previously, when you opened a project, AseptSoft silently overwrote your local environment files if newer versions were found — either in the project's portability folder or (in a recent change) from the cloud. You had no control, no notification, and no rollback path. Environment push to the cloud required FTP credentials and manual file management.

Now, the Environment Update Options window gives you full control over both update sources and the complete history of every environment on your machine. Every overwrite is backed up. Every cloud push goes through secure, role-based authentication — no FTP credentials required.

Prepare for Portability now integrates fully with cloud push: in one command, it bumps every used environment, backs up each, copies to the portability folder, and pushes to the cloud — guaranteeing local, project, and cloud all end at the same version number. The AutoCAD command line reports each step with ✅/⚠/❌ status.

👉 Full documentation: Environment Updates

🤖 AI Assistant (Beta)

AseptSoft now includes an AI-powered copilot that lets you work through natural language conversation. Instead of navigating ribbons and dialogs, you can ask the assistant to create processes, configure equipment, manage automation data, export documents, and more — all from a chat window.

The assistant shows each action as a collapsible tool card with human-readable descriptions (valve names, step names — not database IDs). Read operations execute automatically; delete operations require confirmation. Choose between multiple AI models from the header dropdown.

⚠️ Beta — The AI Assistant is actively being expanded. Further capabilities will be added in future updates.

👉 Full documentation: AI Assistant

🔒 Valve Interlocks with Conditional Rules

Previously, interlocks were defined as ISA-88 cause-and-effect logic (cause condition → protective effect → safe actions). This approach focused on runtime behavior but did not capture which physical valve combinations are permitted or forbidden.

Now, valve interlocks define which combinations of valve positions are allowed or forbidden in the plant — directly from the P&ID. Two rule types are available:

Creating interlocks is straightforward: select 2 or more valves in the drawing, choose Forbidden or OnlyAllowed, set each valve's state — done. The Module Data window provides a full master-detail panel for managing all interlock sets, with valve filtering, grouping, and inline editing.

Conditional interlocks let you attach reusable conditions (e.g., "CIP Active", "Temperature > 70°C") to individual configurations — so a rule is only enforced when its condition is true. Conditions are created with syntax-highlighted expressions, shared across configurations, and editable from multiple places.

Additional capabilities include:

• 🔍 Interlock overlay — visualize interlocked valves on the drawing with colored circles and connecting lines.

• 🧭 Configuration path finder — find the shortest step-by-step transition between two valve configurations, never passing through a forbidden state.

• ⚠️ Reachability analysis — detect disconnected configuration "islands" and process violations.

• 🔧 Mechanical interlock designer — generate physical key/lock/hub specifications.

• 📤 Export — four modes (Raw, All Forbidden, All Allowed, Mechanical Design) to Excel and Word.

👉 Full documentation: Valve Interlocks

🎨 Header Block Designer

Previously, displaying project data in the drawing title block required placing individual Targeted Trackers one by one, with no way to track algorithm conditions or store custom per-step annotations.

Now, the Header Block Designer lets you build a complete, auto-updating title block as a single AutoCAD block — with a visual designer, live preview, and reusable presets. The block automatically populates with project data and updates as you navigate between steps and conditions.

The block uses a two-zone layout: a main zone for project information (process, step, user, date, custom fields) and a separate algorithm zone below for dynamic condition tracking with GRAFCET symbols.

👉 Full documentation: Header Block

📤 Export Enhancements

Word Export: Process Matrix, Equipment Modules & Algorithm

Previously, the Word export included module-level data (States, Fluids, Parameters, Variables, Alarms, Interlocks, Control Loops, Dialogs). Process-specific data like the valve phase matrix or algorithm conditions required separate Excel exports.

Now, the Word export dialog includes three additional data types for a more complete Functional Design Specification (FDS):

A shared left sidebar centralizes process and PID selection — choose once, and all relevant data types follow those selections.

👉 Full documentation: Export Module Data to Word and Excel

PDF Export: Cover Pages

Previously, adding cover pages or appendices to exported PDFs required manual post-processing in an external PDF editor.

Now, the PDF Export dialog includes a Cover Pages section where you can attach a prefix PDF (prepended before the export) and a suffix PDF (appended after). Page counts are displayed, and an option lets page number trackers account for prefix pages in their numbering.

👉 Full documentation: Export Processes to PDF

🗓️ March 2026

Export Module Data to Word (.docx)

Previously, module data (States, Fluids, Parameters, Variables, Alarms, Interlocks, Control Loops, Dialogs) could only be exported to Excel or shared via templates. To create a formatted functional specification document, you had to manually copy data from Excel into Word.

Now, AseptSoft includes a dedicated Word export that generates a professional, ready-to-share .docx document directly from the Module Ribbon. The export dialog lets you:

• Choose which data types to include or exclude.

• Reorder and filter individual fields per table by dragging them.

• Transpose tables (swap rows and columns).

• Group data by category (e.g., group Parameters by Phenomenon).

• Add an export comment embedded in the document properties.

The exported document includes a title page, document metadata, and one formatted table per data type — with blue headers, clean borders, and actual color previews in color columns. Like all AseptSoft exports, it is cumulative — re-exporting updates the data while preserving your manual edits and formatting.

👉 Full documentation: Export Module Data to Word and Excel

🖱️ Valve Hover Inspector

Previously, inspecting a valve's state required selecting it and opening the Status Editor or Live Edit panel. Checking how a valve behaves across multiple process steps meant navigating step by step.

Now, simply hover your mouse over any valve on the P&ID drawing to see a rich, interactive popup showing:

The feature supports three modes: Auto (always on), Ctrl+Hover (shows only when holding Ctrl/Alt), or Disabled. Colored bullet overlays appear at each valve position, giving a bird's-eye view of all valve states across the drawing.

👉 Full documentation: Valve Hover Inspector

🔀 Off-Page Connector Hover and Connectivity Bullets

Previously, checking whether Off-Page Connectors were correctly paired required running a simulation or manually comparing Tag/Bind values across drawings. There was no visual indicator of connection status.

Now, AseptSoft displays colored connectivity bullets at each OPC's position:

Hovering over any OPC bullet shows a popup with full connectivity details — the current OPC's Tag, Bind, and PID, plus the partner's information if connected. For connected OPCs, a Navigate to Pair button lets you jump directly to the paired connector on the destination P&ID in one click.

For unconnected OPCs, the popup lists all other unconnected OPCs across open PIDs, helping you identify potential matches or spot misspelled Tag/Bind values.

The feature uses the same three modes as the Valve Hover Inspector: Auto, Ctrl+Hover, or Disabled.

👉 Full documentation: Off-Page Connector