Tag: Automation

  • From building to proving

    From building to proving

    Automation has become an integral part of our work. Many of our daily tasks are now largely automated.

    In the application domain: manual installation of applications? That’s long gone. Software packaging is often automatically triggered as well. With solutions like Winget, Chocolatey, and Evergreen, you hardly need to worry about it anymore. Installations and updates run fully automated.

    But in the end, it all comes down to one thing:
    does the application truly function as intended?

    From technology to user experience

    After installing or updating, there’s a step we simply cannot skip: testing. And that’s often where the biggest challenge lies. Testing has two dimensions:

    • Technical testing: Does the installation work as expected? Are all files present, does the application start correctly, and are there no error messages?
    • Functional testing: Does the application deliver what the user expects? Can you open documents, process data, or perform specific business tasks?

    In practice, we often see that testing:

    • is performed too little or not at all
    • is repeated in the same way without variation
    • frequently ends up with end users.


    These points are closely connected. Because tests often follow fixed patterns, they are perfectly suited for automation. By automating this process, tests can be repeated as often as needed, with consistent quality and without extra effort. Testing then becomes less of a burden for end users, transforming into an automated process that provides certainty and frees them up to focus on the work that truly matters.

    Taking testing to the next level

    Fortunately, there are solutions that make this process smarter. Login Enterprise by LoginVSI offers a powerful way to not only automate application testing but also elevate it to the next level.


    With scripts, you can simulate user actions. From opening Microsoft Edge or working in PowerBI, to performing complex tasks in business critical applications. To create these scripts, LoginVSI developed a recorder. It was already available for Windows applications, and now there’s also a browser variant. This allows user actions to be easily recorded and automatically converted into a script. Where needed, a bit of fine-tuning can further perfect the scenarios.


    These scripts can then be executed automatically, whenever you choose. This way, you don’t just know that an application is installed, you know it actually works as intended. Even more importantly, you immediately see when something breaks after an update, slows down, or throws errors. All of this is presented in clear, functional reporting. Testing thus shifts from a manual, time consuming task to an automated process that continuously provides insight and certainty.


    In this blog, I mainly highlighted the value of automated testing. In a later blog, I will dive deeper into the features and possibilities of application testing in Login Enterprise itself.

    If you’d like to learn more already, feel free to reach out or visit Login Enterprise.

  • The shortcut that broke the flow

    The shortcut that broke the flow

    At one of our hospital clients, we deployed a new digital workspace built on Omnissa products like Horizon, App Volumes, and DEM. Ivanti Automation Manager was already in use. The EHR system receives multiple updates each month, including hotfixes. Previously, every update required a new image, a time-consuming and error-prone process.

    With App Volumes as our Application Layering solution, we gained flexibility. And we went a step further: we fully automated the packaging process.

    What we automated

    Using PowerShell scripts and an Ivanti Automation Runbook, we automated:

    • Creation of Ivanti Automation resources and modules
    • Creation of App Volumes Applications and Packages
    • Booting the Package VM
    • Installing the application into the App Volumes package
    • Reverting the Package VM to snapshot
    • Marking the package as ‘Current’
    • Assigning the package to users

    The only manual steps left are entering the HF number and providing the necessary credentials to execute tasks and link them to logging. Everything else runs automatically.

    Smart versioning with DEM integration

    To stay flexible, we place each application in a folder named after its version. This allows multiple versions to coexist across Test, Acceptance, and Production environments. The correct version is launched via a DEM shortcut using a variable:

    C:\Program Files (x86)\Chipsoft\Hix\%HiXPrd%\Chipsoft.hix.exe
    C:\Program Files (x86)\Chipsoft\Hix\%HiXAcc%\Chipsoft.hix.exe
    C:\Program Files (x86)\Chipsoft\Hix\%HiXTst%\Chipsoft.hix.exe

    In DEM, it’s easy to see which environment runs which version. Updating the variable is the only manual step, intentionally kept that way.

    And then it broke…

    Everything worked as expected. Until after an update, the service desk started receiving calls: the shortcut no longer worked.

    Turns out some users had dragged the shortcut from the desktop to the taskbar. DEM translates variables into static paths. Once copied, the shortcut becomes fixed to a specific version. After an update, that path is no longer valid resulting in errors, frustration, and no access to the EHR.

    The fix: Files and Folders

    We solved this by no longer using DEM shortcuts. Instead, we use a Files and Folders action to place a file with the correct reference on the desktop and in the start menu. This preserves the variable and ensures the shortcut keeps working after updates.

    Conclusion

    Technical automation is incredibly valuable. It saves time and boosts reliability. But in the end, it’s all about the end-user experience. For them, it just has to work. That’s where the real value lies.

    I’m curious to hear if others have found a more elegant solution to this. Have you tackled similar shortcut issues in a smarter way? I’d love to learn from your approach.