What's new

We are back: buying on this site works again, normally. Pick a plan, pay, and your licence is issued straight away — no request, no waitlist, no waiting for anyone to review anything.

Nothing else changed while purchasing was closed. Current customers were never affected and kept receiving system updates throughout, and every licence, download and renewal carried on exactly as before.

If you opened an interaction to ask for a purchase while it was closed, you no longer need to wait for it: you can complete the purchase yourself from the pricing page.

Thank you for your patience.

A workflow that a bundle reinstall used to lose. The ITSM “support this idea” workflow wired a person into a field that had become a reference to the user table, so it no longer validated — and because reinstalling a bundle deletes before it recreates, that workflow was lost instead of simply not being updated. It validates and is recreated correctly again.

Filtering by tag, in workflows and lists alike. A condition on tags now means the same thing wherever you write it: in a list, in a business rule and in a workflow. Tags are not a column of the record — they are rows of their own — so the platform answers questions about which tags a record carries, with the operators that ask exactly that.

A relation only points where it is allowed to. When a relation field carries a condition, linking through it is refused if the target does not match — on save, not only in the picker.

Housekeeping you should not have to think about: many-to-many declarations now travel with the tables they describe, so a copied or synchronised environment arrives with its relations intact instead of two tables that no longer know about each other.

Tags, once for the whole platform. Until now each module stored tags its own way — free text in one place, a fixed list in another — so the same word in two places was not the same thing and could not be counted, renamed or filtered together. There is now a single tag table in Administration, and a tag is a row like any other.

• A new field type, “Tags”, that you can add to any table. A record carries as many as it needs.
• Typing a word that does not exist offers to create it, and anyone can. What you create that way is yours; making a tag for a group or for everyone stays with administrators.
• Lists filter by tag, and the filter understands “has this one”, “does not have it”, “is empty” and “is not empty”. Business rules understand the same thing and mean the same thing in both places.
• Each tag can belong to everyone, a group or one person, and that decides who is offered it.

Join tables are created by the system. When two tables relate many-to-many, the platform now creates the table that joins them — you no longer have to bring one from home to declare the relation. And deleting a table takes its relation with it, leaving nothing behind; what is never touched is the data of the tables it joined.

Three new field types for things that used to be typed into a text box: Entity (pick a table from the list instead of typing its name from memory), Condition (built with the same condition editor the product already uses) and Colour (picked or pasted).

A new record starts with what the package already decided: choice fields open at their initial state instead of blank, and an AGILE record is born inside its own lifecycle.

A relation field can say what it may point at, and it is enforced on save and not only in the picker: the picker offers what fits, and anything else is refused even if it arrives by another route.

Fixes you will notice: a fresh install used to come up missing two of the three approval tables, so approvals did not work until somebody noticed; an ITSM e-mail address was not validated because it was declared as plain text; a duplicate value in a unique field answered with a raw database error instead of telling you, in your language, which value is taken; and right-clicking a cell in a list now filters by what you have in front of you.

Everything new is translated into all thirteen languages. No migration: new tables and columns are added on activation and what was already there is left as it is.

For an internal strategic reason we have disabled public purchasing on this site.

Current customers are not affected: you keep receiving system updates as usual. Your licence, your downloads and your support work exactly as they did before.

New customers can still get the platform: register an account and request the purchase formally by opening an interaction from your account. Each request goes onto a waitlist that our team reviews.

We are sorry for the inconvenience.

Lifecycle actions work again

Pressing an action on an incident, a problem or a demand failed with "Assigned team requires a group id or slug", from any screen. Leaving the assigned team blank was being read as a badly filled field instead of an empty one. A group or a user left blank is a blank field, not a wrong value — and a table with an optional money field can be filled in again for the same reason.

Saving a table keeps the parts you did not mention

A write used to replace the whole definition, so anything the caller did not resend was destroyed: the labels you had translated yourself, the icon, the plural name, whether the table is exposed to the API, whether it runs asynchronously, which field names a record — and the four role lists that decide who gets into the table. That last one was the dangerous one: an empty list is not "nobody", it falls back to the platform's roles, so a table you had restricted quietly opened.

Now silence leaves the stored value alone, and only what a payload actually mentions is written. Clearing something still works — you send the empty value, because that is an answer. The same applies to a field's own attributes: who may read and write it, its configuration, whether it is required, its default and where it sits.

This is enforced where every door writes through, so it covers your integrations, your scripts and your own API calls, not only the screen.

"Me" is offered again in a filter

Building a filter on a field that holds a person no longer leaves out Me, so "assigned to me" can be asked for from the screen again and one saved view serves everybody. Filters you had already saved kept working throughout: what was missing was the offer, not the answer.

An upgrade keeps what you arranged

Three seeded buttons and a UI policy still wrote themselves back over yours on update — restoring the label, moving them to the seeded position and switching back on anything you had switched off. They now follow the rule everything else follows: what exists is yours, and what you deleted stays deleted.

Also fixed

A record write no longer takes the whole request down when the approval check cannot run. That check sits on every write; it now refuses that one write and says the record could not be checked.

If your chat stopped being able to start a conversation, this is the fix

On a site that had been running WP-PFAgent™ for a while, opening a new conversation answered "Chat session not found after creation" and nothing else worked from there. The conversation was written and then could not be found — and whether any given attempt worked at all depended on chance.

The cause is one every product meets once: the table that holds your conversations moved to a new kind of identifier, and that move ran when the plugin was activated. A site that updates never activates. So the installs that had been running the longest — the ones with the most conversations — were exactly the ones left behind.

The schema now catches up when you update, once, and only marks itself done after it has finished. Your existing conversations are carried across; nothing is deleted and nothing needs reinstalling.

Approvals

A record can now require approval before it moves. You declare when an approval is needed and who approves it — everyone on the list, or any one of them.

While an approval is open the record is read-only. Everyone can still read it, an administrator is never blocked, and a journal entry can always be added.

Each approver finds their own task — and only their own — in a new Self service area, and answers it from there. A rejection asks why, and the reason is kept with the task. Once the approval is decided the record is free again, and the tasks nobody got to answer stop asking for a decision that has already been made.

Relating two tables

A new Many to many module relates two tables through an intermediate one, declared like any other relation. On a record it appears as a related list showing the columns of the table it points at. The + creates a record there with this one already linked, and the button beside it links and unlinks records that already exist.

Your records show their names

A table now declares which of its fields names its records. Relation labels, pickers, filter values and board cards all read that declaration instead of guessing what looks like a name — so renaming a field is enough to change what everyone sees.

And no screen shows an internal identifier where a name belongs. When there is no name to show, it says so instead of printing a key.

Screens tell you what happened

An action now answers what it did, not just that it was fired: when a rule blocks it, you get the rule's message instead of a tick and a record that did not move.

An action can also ask for what it needs before running.

A list that could not load no longer claims a reason it cannot know. Dialogs take the keyboard and close with Escape. Board cards show the first three columns you chose. And a board embedded in a public page renders as a board.

Views of your own work

My incidents, My changes to approve, My demands and My problems find your records again.

Also fixed

Reading a stored value that cannot be decrypted now answers with an error instead of taking the page down with it.

Your data is safer than it was

• Removing a field takes its column and its data, or nothing happens at all. A removal could previously report success while leaving the data behind — or take more than you asked.
• A write no longer deletes what nobody asked it to delete.
• Deleting a journal entry means it is gone, and deleting is governed by the same permissions as writing.
• An update never removes records it did not create.

Screens

• A list opened from the customer area could come up blank, showing "this screen could not be displayed". It opens normally again.
• A field that points at another record shows that record's name, and when it cannot resolve it, it says so plainly instead of showing an identifier.
• The planner is readable, and several screens that reported the wrong thing now report what actually happened.
• Adding a task where you clicked puts it there.

People and language

• An account hidden behind a duplicate login is named instead of disappearing from the people list.
• The thirteen translations reach full coverage, and the labels stored in your own configuration are translated too — not only the ones we ship in code.
• The API answers in the caller's language.

Working with your data

• Your tables are reachable through the Table API unless you say otherwise, instead of the other way round.
• Numbering arrives when you ask for it.
• A query the server cannot understand answers with an error that tells you what is wrong.
• Execution history names who did what again.

Copying a site between environments

Records and configuration now carry identifiers that stay the same wherever the site is copied. A staging copy, a restored backup and the original recognise each other, which was not true before.

Webhooks

• Replaying a captured sample reaches the workflow that listens for it. Samples were being filed under a trigger name no workflow answers to, so a replay went nowhere.
• The samples you already captured are corrected when you update — nothing to capture again.

Day to day

• The approvals inbox is readable again.
• Listings tell you how many there are and can be walked page by page, instead of stopping at a hidden ceiling.
• The API stops answering "done" for work that never happened.
• An OAuth error lands you on a real page, and the links to the runner point where the project actually lives.

Copying a site between environments

Workflows, executions and history carry identifiers that survive a copy, so a workflow moved to another environment is still the same workflow.

• A chat survives a confirmation you never answered, and a conversation can be picked up where it was left.
• "How many" is answered by looking, or not answered at all — no more confident guesses.
• A workflow variable can finally be created from the chat.
• The assistant is given a map and one entity at a time instead of the whole data model on every turn: faster answers, and fewer of them invented.
• A conversation keeps its identity when the site is copied to another environment.

Integrators first: five parameters of the record API were renamed, and the old names no longer work. Everything else in this release is yours to enjoy without doing anything.

This update brings the 1.2.0, 1.2.1 and 1.2.2 releases together, so what lands on your site is bigger than a single version.

If you call our API from your own code

Five parameters were renamed, and there are no aliases. An integration written against the old names has to be updated with this release:

• sysparm_query is now filter
• sysparm_limit is now limit
• sysparm_offset is now offset
• sysparm_orderby is now sort
• sysparm_fields is now fields

Free-text search has a parameter of its own now, search, separate from the structured filter. Everything we ship moved with it, and the documentation describes the new names.

Two more changes you will want to know about before they surprise you:

• A filter the server cannot parse is answered with an error instead of an empty result. A typo in your query used to look exactly like "no records match".
• Writes now have a speed limit: 120 changes a minute per caller. Go over it and the next request comes back as 429 with a Retry-After header, and a minute later you are clear again. Normal use never comes near it — a person working, or a workflow reacting to records; a bulk import that writes in bursts can. Writes are counted on their own, separate from the 240-a-minute ceiling that already applied to the administrative endpoints, and scheduled tasks and command-line runs are not counted at all. An administrator can raise the limit or switch it off with the pfm_write_rate_limit_per_minute filter.

What you gain

• The admin works on a phone. On a narrow screen the sidebar becomes a drawer over the content and record forms drop to a single column: navigating, opening a record and editing it all work at 375 px wide with no sideways scrolling. Wider screens look exactly as they did.
• Scheduled maintenance windows. Schedule one and your users are warned about an hour ahead; while it runs they see a maintenance page across the three plugins, administrators keep working, and the WordPress login is never touched. Installing or updating creates no window — nothing changes until you schedule one yourself.
• Lists tell you how many there are. A list now reports the total as well as the rows, and can be read a page at a time. Asking without pagination parameters returns exactly what it always did.
• Your workflows come across on their own. The update migrates them for you on the first request after it lands, tells you while it is under way, and nothing is deleted or needs reinstalling. A workflow also keeps the same identity when you copy it to another site, so the same automation is recognisably the same in every one of your environments.

What is fixed

• The screen no longer goes blank without saying why: if a response cannot be read, the page loads with an explanation and stays navigable.
• Reading WooCommerce orders through the agent no longer fails on shops that have issued refunds.
• When the AI provider rejects a request, the chat says what happened and what to do — a rejected key, an exhausted quota or a rate limit each read as themselves instead of as a failure of the plugin.
• Deleting something that is not there answers "not found" instead of reporting success, and a request the plugin cannot read is refused instead of guessed.
• Accessibility and contrast fixes across the admin, and the full-screen view now carries the same browser protections as every other page of your WordPress admin.
• Your customisations survive an update: the order of your applications and modules, your names and icons, what you hid, and the pieces of ours you deleted all stay as you left them.

How to get it

The update reaches sites with automatic updates enabled in batches over the coming days. If you would rather not wait, the current version is in your account's Downloads at any time.

Update-channel support: from this version, updates arrive directly in your WordPress dashboard.

Update-channel support: from this version, updates arrive directly in your WordPress dashboard. Includes a plugin load-order fix so Workflow runs cleanly alongside Setyenv Management 1.1.2.

Planning Gantt — visible date range. The visible date range is now set with a two-pin slider below the chart (default −1 / +2 months, up to ±2 years around today). The whole plan stays loaded; anything beyond the window is flagged at the edge.

Axis framing fix. Fixed a sprint carrying placeholder dates (e.g. 1979→2030) from dragging the timeline decades off and pushing real task bars off-screen.

PF Manage gets a more consistent interface and friendlier data on screen:

• Consistent themes. Your chosen theme now applies uniformly across every admin page.
• Branding on embedded views. Your branding — theme, logo and product name — now also appears when you embed PF Manage inside your own WordPress pages.
• Friendlier data. References show readable names instead of raw identifiers, and dates follow your language.
• Edit many rows at once. Set a value across several selected records in a single step.
• Quick jump to workflows. Go straight from an action or a rule to the workflows it triggers.

This release makes your automations more dependable and the editor quicker to work in:

• Loop steps now process every item in a collection — not just the first one — so a step that runs over a list completes the whole list.
• Entity references chain effortlessly. A relation from one step drops straight into later steps in the editor, so linked records flow through your workflow without extra wiring.
• Find and reach workflows faster. Search the library for the workflows that respond to an action with action:<event>, and jump straight from an action or a business rule to the workflow it runs.

A big visual refresh, plus practical additions to how you work with your records.

• Redesigned interface — a cleaner, more modern look across lists, records and boards, in both light and dark themes.
• Private attachments — attach files to a record with per-field and per-row access control, stored privately (not in the public uploads folder).
• Activity log with filters — see what happened and when, filtered by time range and actor.
• Smarter dates — dynamic date values in filters (Today, Last week, This quarter…), one consistent date picker everywhere, and your WordPress date/time format respected throughout.

PF Manage now sends and receives email, and can notify people automatically from your records.

• Outbox & Inbox accounts — configure one or more sending (SMTP) and receiving (IMAP) email accounts. Incoming messages land in a manageable inbox inside PF Manage.
• Notifications — a new section to send templated emails: choose recipients (email addresses and users), write a subject and a rich body with {{field}} placeholders that fill in from the record, and pick which outbox sends it.

Workflows can now send email through your configured accounts.

• Email node — send a notification from any workflow using the outbox accounts you set up in PF Manage, with the same templated subject and body.

WP-PFWorkflow 1.0.38 rounds out WooCommerce automation, lets Woo actions chain into other workflows, and makes execution more reliable.

• Full WooCommerce coverage — new triggers and actions across orders (update, delete, remove a line, remove a coupon — alongside the existing ones), products (create, update, delete, and a "Product created" trigger), customers (create, update, delete, with optional reassignment), coupons (update, delete, get by id or code), stock (an "Out of stock" trigger and a "Set stock status" action), and subscriptions — get, status change, and created / status / renewal triggers (requires WooCommerce Subscriptions).
• Automation chaining in WooCommerce — when a workflow writes to WooCommerce, those writes now fire their WooCommerce triggers, so other workflows react to the change just as they would to any external one.
• More reliable execution — duplicate jobs are dropped at enqueue, each node's output is checkpointed (encrypted at rest), and retries are on by default with a status-aware policy: a transient failure retries with backoff, a 4xx does not.
• Translations updated across all 13 languages.

WP-PFWorkflow 1.0.37 makes it easy to move a workflow between sites — or restore one you exported as a backup.

• Import a workflow from JSON, right from the dashboard. When you choose a file, you pick how it lands:
  • Clone — create a new workflow (draft); it never touches your existing ones.
  • Overwrite — update the matching workflow in place, with no duplicate (matched by the export's origin id).
  • Import quietly — write the definition without re-registering its triggers or sending notifications.
• A compact import card shows the workflow's name, its size, and exactly what will happen — at a glance.
• The import experience is translated across our languages.

Thanks to Zekiye and Savaş Elcüman from Product Hunt for requesting workflow import/export.

WP-PFManagement 1.0.53 improves list filtering, clears a stray notice, and lays the groundwork for record export/import.

• Clearer default list filters — when a list opens with a default filter on a yes/no field (for example "active only"), the filter now shows its value in the filter panel instead of looking empty. You can always see what a list is filtered by — and clear it.
• Fixed — creating a record no longer produces an internal "Array to string conversion" notice.
• New engine (backend) — a record export/import engine can serialise any record together with its full relation graph to a self-contained JSON and rebuild it: a lossless round-trip, with either a fresh copy (new ids) or restore-in-place by id, plus an option to restore data without re-firing automations. It ships as a foundation in this release.

The update applies additively — no destructive schema change.

• Synchronous-by-default execution engine. Automations run predictably in order, with fault-isolated steps and an async queue that drains reliably.
• Native per-action triggers. Start a workflow directly from any entity action.
• Safer outbound requests. The SSRF guard is always on, with an egress allowlist for the private-network exceptions you approve.

• New “WordPress” tab. A live view of your WordPress admin that follows the agent’s actions as they happen.
• Chat improvements. A smoother, more reliable conversation experience.
• Refined capabilities. Sharper, more dependable agent actions.
• Full interface localization across all supported languages.

• Row-level visibility controls for your entity data. Decide, per entity, exactly which rows each audience can list and open — with an optional row filter for fine-grained control.
• Full interface localization. The admin interface is now fully translated across 14 languages.

You can now try the full Setyenv suite — Manage, Workflow and Agent — in a real, temporary sandbox, straight from your browser. One click launches a private WordPress preloaded with a realistic “Bookings Platform” IT-service scenario: live tickets across every state, a change awaiting approval, a CMDB, and an agile project with a Gantt — a system with real data, not an empty shell. No install, no commitment; it resets after about two hours. Open the Demo page to start. And if you buy, you still get 14 days with a full refund if it’s not for you.

Also shipping — Workflow reliability and editor improvements: automations no longer stall when background processing isn’t reachable, and you can now wire a dynamic value (such as a field from an incoming webhook) straight into a text input.

Integrations you define in Management, run in Workflow.

Workflow now runs the integrations you configure in WP-PFManagement as native nodes — while the engine, security and credential handling stay in Workflow.

• Management integration nodes — REST Message calls, Scripted REST routes, and per-entity Table nodes (Get / Create / Update / …) read their definition from Management (Management-first, with a local fallback so a workflow keeps running while you adopt the platform).
• OAuth outbound — authorization code and client credentials grants, automatic refresh, SSRF-guarded. Tokens live only in Management (written back after each exchange; Workflow keeps no local copy).
• The inherited moat (run-as-caller) — a workflow runs as the user or API client that triggered it. Row visibility, field projection and the verb guard all apply — even when the entity and its rules were defined in Management.
• Every outbound call rides the same hardened HTTP stack (retry with Retry-After, SSRF protection, redacted logging).
• 13-language coverage.

The certified engine, moat, SSRF guard and credential encryption are unchanged — only where the definition is read from moved to Management.

A full integration layer — defined in Management.

This release brings the integration surface into WP-PFManagement, where you configure it once and reuse it everywhere, with its own admin pages, tables and tests.

• OAuth 2 — client and provider.
  • Client (outbound): register connections to third-party APIs (authorization code and client credentials), with their endpoints, scopes and credentials. Test a connection from the admin.
  • Provider (inbound): register the consumers that integrate with you over OAuth. Configure allowed grants (including client credentials), scopes, token lifetimes and — for server-to-server — the least-privilege service user the issued tokens act as.
• API keys — mint scoped, least-privilege keys for machine callers (never for admins).
• REST Messages — define an outbound HTTP call once (URL, headers, body template, auth), with keywords, and reuse it as a Workflow node.
• Scripted REST routes — define inbound endpoints that run a workflow or return entity data, under the caller’s own permissions.
• Table REST API — auto-documented (OpenAPI) surface over your opt-in entities.
• Tokens — a dedicated module: every token PFM holds, in one native table, with view / revoke / delete. Secrets are encrypted at rest with an install-only key and never leave the server.
• Dialogs — a multilingual message with branching action paths, auto-translated via your configured LLM; usable from a UI Policy or a form Action.
• Theme-aware throughout — the whole admin, including native controls, adapts to your theme.
• Themes & branding — pick a theme and set your logo/product name.
• 13-language coverage — the admin is fully localized.

All record access stays governed by the same row-visibility, field-projection and permission model — the integration layer can never be used to bypass it.

The whole admin UI is now translated across 14 languages and fully theme-aware — every surface, including the new integration and dialog screens, renders correctly under the dark theme.

A single Setyenv PF Pack subscription now activates both WP-PFManagement and WP-PFWorkflow across your sites. One licence, one renewal, both plugins — with a combined discount over buying them apart.

A new first-class Dialogs feature: a multilingual message with a set of action buttons, each running an existing action on the current record. Launch a dialog from a UI policy or a form action; scope it to one entity or reuse it everywhere.

Expose your entities to machine callers through the Table API, authenticate with API keys or OAuth2 (PFM as provider and as client), and reach external services with the new REST Message action and custom REST endpoints — all gated by the same field and row permissions as the UI.

We have shipped a round of security and self-service improvements to your Setyenv account. Nothing you have to do — it is already live.

• Two-factor on every sign-in. Every account now confirms a one-time code at login. A code sent to your email is always available; for something stronger and faster, add an authenticator app (Google Authenticator, Aegis, 1Password or any TOTP app) from My Account → Security, and keep the recovery codes it gives you.
• Verified email from the start. New sign-ups confirm their email with a one-time code before the account is usable, so the address on file is always one you control.
• Clear, minimal cookies. A short notice spells out exactly what we store: a session cookie and, when you sign in, your login cookies. No tracking, no third parties.
• Safer downloads. Download links are single-use and watermarked to your account. WP-PFAgent — our AI agent — now shows a short responsibility notice you accept once before your first download, so you know what you are running before you run it.
• A smoother account area. “My Account” resolves straight to your own record and your licences, and the store sends you to register or sign in before checkout so every purchase lands on your account cleanly.

Your data, your control — with a lighter touch. Sign in and take a look at My Account → Security.

Project Flash is now Setyenv. Same suite, same licenses, new name and home: setyenv.com.

• Maintenance releases WP-PFManagement 1.0.23, WP-PFWorkflow 1.0.20 and WP-PFAgent 1.0.3 update all product surfaces and point license validation and updates at the new portal.
• Existing license keys keep working unchanged — no action needed.
• project-flash.com now redirects here.

Maintenance release — stability and correctness fixes from the agent debugging cycle.

• Completes the agent's record CRUD (adds delete) and wires row-visibility into the tool set.
• Tool-bridge argument errors now return a clean, labelled validation failure instead of a generic bridge error.
• Longer agent turns no longer hit the time limit; transparent auto-continue for multi-step chats.
• Workflow activation is confirmed by read-back rather than reported blindly.
• Licensing drop-in synced to PFL3 v1.4.0 (pure-PHP crypto).

Project management just became a first-class citizen of PF Manage. This release ships the complete Agile package — not a plugin bolted on the side, but agile built into the platform you already run.

• A visual Gantt that thinks the way you do. A task's width is its duration — drag to reschedule, grab the handle to resize, and wire typed dependencies (Finish→Start, Start→Start, Finish→Finish, Start→Finish) with a click. Drop milestones on the timeline and watch the whole schedule cascade in real time. Right-click for everything; the canvas stays clean.
• The whole agile flow, native. Epics, stories, sprints and tasks; a drag-and-drop Kanban board for the active sprint; a groomable backlog; assignments, timesheets, absences and capacity.
• Read the story at a glance. Burndown, velocity, planned-vs-real, workload and a project dashboard — built in, always current.
• Speaks your language, wears your theme. The entire interface — Agile included — is localized in 14 languages, and every surface honours your branding theme, including the new Midnight dark mode.

Agile in PF Manage. All of it. Ship it.

• More reliable account and purchase flows. A permissions fix ensures the plan catalog and purchase page always show what is available to buy, for every customer account.
• Minor robustness fixes. Coupon handling and background services recover more gracefully and report clearer errors.

• A new Branding page puts the look of PF Manage™ under your control. Pick a theme, set your own logo and even rename the product in the top bar — all from Administration → Branding.
• Your interface stays exactly as it was — until you decide otherwise. The default theme is the standard PF Manage™ look, untouched: sites that never open the Branding page render pixel-for-pixel as before.
• Create your own themes. Start from the standard palette or duplicate a factory theme (Midnight, Slate) and adjust twelve color tokens. Themes change colors only — layouts never move, so nothing can break.
• Coherent on every screen. An applied theme paints the whole interface — lists, kanban boards, forms, journal, audit trail, navigation and every administration page — and the factory palettes meet WCAG AA contrast.
• Speaks your language. The Branding page ships in all 13 supported languages.

We are working on an AGILE module for WP-PFManagement™: agile project management inside your PF Manage workspace, with Scrum, Kanban and hybrid boards, time tracking on work items, and an interactive Gantt view for planning.

It will be distributed shortly as a module patch — no reinstall, no migration. Alongside it we are preparing a substantial upgrade of WP-PFAgent™, the assistant that operates the platform with you.

More details here on News as the work lands.

• The engine is shielded from failing steps. A step that crashes now fails that step cleanly — with a clear timeline entry — instead of ever affecting the page, checkout or signup that triggered the workflow.
• Triggers run in the background by default. Site events (registrations, orders, record changes) enqueue their workflows instead of running them inside the visitor's request — pages stay fast even with heavy automations.
• Automation chains are reliable. A workflow that creates a record now correctly triggers the workflows watching that record — chained automations fire in order, with a built-in guard against accidental loops.
• No more lost edits while saving. Changes made while a save was still in flight are preserved — the editor keeps your latest work, always.
• A lighter, steadier editor. The workflow studio loads leaner and behaves more predictably across dashboard, canvas and inspector.
• Consistent pin connections. Approval, retry, loop and error branches classify and validate their wires the same way in the editor and the engine.
• Webhooks are safer by default. Incoming webhooks require a signature unless you explicitly allow unsigned calls, with secret rotation supported; remote workers verify signatures by default too.
• Honest connectors. LLM provider defaults corrected, admin notices persist for real, and SEO analysis scores with a genuine rubric.

• Hardened permissions across every surface. Entity, field, row and journal access checks are now enforced consistently on lists, forms, actions, imports and the automation surface — what a role can see and touch is the same everywhere.
• One filter language, everywhere. Conditions behave identically in list filters, business rules and form policies — including relative dates, field-to-field comparisons, choices and accent/case handling. What you test in the list is exactly what your rules do.
• Currency that sorts and compares as money. Amount columns now order and filter numerically (no more "999 > 1000" surprises), while keeping the currency code intact.
• Business rules guard every write. Abort rules and rule-triggered automations now apply to all ways of writing records — forms, imports and integrations alike.
• Sturdier upgrades. Schema and data migrations verify themselves before switching over, and currency data backfills automatically when a field changes type.

WP-PFManagement 1.0.19 makes everyday record editing cleaner: working file attachments, tidier inline editing and forms that fit their content.

• Attachment fields now work end to end — a real media picker opens, and the field shows the file’s thumbnail and name instead of a raw number.
• Inline editing is calmer: double-click a cell to edit (the per-cell pencils are gone), and the transient “saved” tick stays.
• More field types edit in place from the list — multi-line text and currency now join the rest.
• Record forms are proportional: a short record no longer sprawls across several near-empty section headers; only large records keep the grouped layout.
• The unified activity Journal now appears on more ITSM records — ideas, issues, assets and CIs — alongside incidents, changes, problems and the rest.

WP-PFWorkflow 1.0.15 is a large workflow-editor polish release, plus offline licensing.

• Descriptive, automatic node titles and a type icon on every node.
• The socket itself is now the type symbol, with a per-type glyph legend on the pins; sockets dim or light up according to what is wired.
• The field picker stays inside the viewport, the mouse wheel no longer zooms the canvas, and the +/- controls behave deterministically.
• Cleaner pin labels (internal ids now read as “Record ID”); the trigger’s +RECORD offers the full entity schema.
• A business rule’s linked workflow is now active from the moment it is created.
• Offline license activation (shared drop-in).

WP-PFAgent 1.0.1 goes open source, moves to an English-base interface and adds offline licensing.

• Now open source under the GPL-2.0 license.
• English-base interface throughout, fixing the earlier mixed-language drift.
• Offline license activation with an enforcement gate (shared drop-in).
• Refreshed DeepSeek model catalog.
• Console polish: a skeleton loader while a conversation opens, aligned diagnostics, and clearer confirmation prompts that name the workflow on file write/edit.

WP-PFManagement 1.0.18 introduces offline license activation, per-role form layouts and a batch of reliability and SEO fixes.

• Offline license activation with a self-contained key — activation no longer needs the portal to be reachable; it re-validates online whenever it can.
• View Rules: route each role to the form layout it should see.
• Multi-layout Form Designer: keep several saved layouts per table and switch between them.
• Inline editing extended to choice, reference, user and group fields, right from the list.
• ITSM bundle: de-duplicated navigation and clearer per-type icons.
• Record sub-sitemaps now serve valid XML so search engines can index your public records.
• Reliability: deleting an entity now removes all of its configuration, leaving nothing orphaned behind.

Setyenv is now open for registration. Create your free account today to set up your profile and be ready for launch.

Purchases aren't available just yet — we're putting the final touches on checkout. The moment buying goes live, registered users will be the first to know by email.

Setyenv 1.0 is here. The whole suite is production-ready and ships together — self-hosted, source-available to licensees:

• WP-PFManagement — the low-code data & ITSM platform: entities, fields, forms, lists, a native event catalog and a restrictive schema reconciler that never destroys your data.
• WP-PFWorkflow — the visual workflow engine: build automations that really run (queue, retries, timeline) off native record events.
• WP-PFAgent — an AI agent that asks before it acts: it drafts, then stops at a confirmation gate. Bring your own LLM — your keys, your bills.
• WP-Executor — the open-source runner that reaches beyond WordPress onto your own machine.

Also in 1.0: a silent license lifecycle, a 14-language interface, a 14-day risk-free refund, and the full end-to-end use case — a defective order resolved from WooCommerce through support, workflow, agent and executor, all inside your own WordPress.

The three plugins and the runner reached feature-complete and opened for public beta. This release focused on hardening, the 14-language rollout and the commercial portal ahead of the 1.0 stable release.