Mugnsoft logo Mugnsoft
Changelog

Pulse release notes

Detailed information about every release of Mugnsoft Pulse — the portable Linux and Windows application that builds, runs and schedules user journeys without a line of code. Pulse succeeds Mugnsoft IDE. Looking for the monitoring platform? See the Core release notes.

v1.2.1

latest

v1.2.1 is provides minor UX Improvements.

▲ Improvements

  • Step suggestions fix have been introduced.

v1.2.0

v1.2.0 is a reliability and security release. Licensing is more robust — a network outage no longer puts your license at risk — the application behaves predictably when started twice or closed during work, and scheduled journeys run more reliably over long sessions. Recommended for every Pulse user.

＋ New features

  • Pulse for Linux. Pulse now also ships as a portable Linux archive (64 bit), next to the Windows one: extract mugnsoft-pulse-1.2.0.linux-amd64.tar.gz and run mugnsoft-pulse. Pick the operating system on the download page.

▲ Improvements

  • Offline tolerance for paid licenses. A paid license keeps working for 14 days without reaching the license server. After that, Pulse clearly explains that it could not reach the server and asks you to reconnect, instead of reporting a generic validation failure. Free licenses keep working offline once activated.
  • Stronger license protection. The connection to the license server is now fully certificate-verified, and the license is checked against its server signature and the computer it was issued for every time Pulse starts.
  • Safer links. Links opened from Pulse are limited to web pages and email addresses.
  • Free tier limit shown consistently. The free tier allows 3 tests, and Pulse now says so everywhere it describes the tier.
  • Correct version number. The start screen and the About window display the actual version of Pulse.

✕ Bug fixes

  • A temporary network or license-server problem could leave a valid paid license reported as invalid at the next start, until it was activated again. Licenses affected by this recover automatically with v1.2.0.
  • Starting Pulse a second time could interrupt the instance already running. The second start now simply brings the existing window to the front.
  • Cancelling the exit — for instance to save unsaved changes — stopped scheduled journeys until Pulse was restarted.
  • An error while closing could leave Pulse running in the background and impossible to quit.
  • Changing schedules many times during a long session gradually consumed resources, and a schedule saved while recording could start running before the recording ended.
  • Uploading a journey to Mugnsoft could wait indefinitely when the server stopped responding; it now stops after two minutes with an error.

⬢ Upgrading

  • Close Pulse, replace the mugnsoft-pulse folder with the one from the new archive, and start it again. Projects, settings and your license are stored outside the application folder and are kept.
  • On Windows, extract the archive into a folder with a short path, such as C:\Mugnsoft, and unblock it first to avoid a Windows warning at start-up — see the installation guide.

v1.1.0

v1.1.0 improves interface clarity and consistency, making navigation and data analysis easier in everyday use.

v1.0.0

The first release of Mugnsoft Pulse, and the successor of Mugnsoft IDE. What used to be a browser extension for Firefox and Chrome is now a standalone portable application for Windows: nothing to install, no extension store in the loop, and no dependency on a third-party platform to keep working. Pulse also goes well beyond what the IDE did — it does not only record a user journey, it runs and schedules it on its own.

＋ New features

  • A portable application instead of a browser extension. Pulse ships as a single Windows archive: unzip it and run it. It no longer depends on Firefox or Chrome extension stores, their review cycles or their APIs — a sovereignty and continuity choice, so that the tool you build your journeys with stays under your control.
  • No-code journey building. Click and fill: a user journey is assembled step by step from the interface, with no script to write.
  • Run journeys on your own machine. A journey can be replayed directly from Pulse, without a monitoring platform behind it.
  • Schedule journeys from Pulse. Recurring replays can be planned inside the application, within the options, metrics and concurrency limits of the tier in use.

⬢ Migrating from Mugnsoft IDE

  • Mugnsoft IDE is superseded by Pulse and is no longer the recommended way to build journeys. The Pulse documentation is available at doc-pulse.mugnsoft.com.
  • Journeys built with Pulse feed Mugnsoft Core when an organisation needs more than a workstation can offer: full metrics, unrestricted replay frequency, concurrency, alerting, reporting and SLA.
  • Pulse runs on a license. A free tier is available on request, with a limited scope and replay frequency; contact sales for the full feature set.