ADD A NEW IDEA

Automation

    Showing 68

    The Deployment under automation is always deploying the production version but i want to be able to choose a different fase like development or test

    The Deployment under automation is always deploying the production version but i want to be able to choose a different fase like development or test. Sometimes we want to test an entire deployment with new version before changing the packages to p...
    Johan Kamping 5 months ago in Automation 2 Will not implement in the near future

    Set file type associations

    For file associations like PDF you not able to set it as default. And in programs like Ivanti is do have this feature.
    Vembrechts 6 months ago in Automation 0 Planned

    Deployment approval email recipients

    Allow also to define email recipients for available type of deployment processes steps that require approval
    Juha Haapsaari about 2 years ago in Automation / Roles and Permissions / Security 0

    Update the Uninstall MSI action

    I would to suggest to add a 'Product Code' text field between 'File' and 'Arguments'. This gives the option to bypass selecting an MSI, when the Product Code is already known. And also clarifies that using the 'File' select option (...) is just an...
    Roel van Bueren 7 months ago in Automation 0 Future consideration

    API for Builder Automation

    Builder is awesome. What would make it even better is if I could initiate automation from other systems using an API. Think Azure Automation calling an RMS API to add devices to collections, or install missing software updates, or whatever else we...
    Scott Erickson over 3 years ago in Automation 0 Future consideration

    Builder: Pass information from Powershell step to other steps

    Allow output from a PowerShell step to be used as input in future steps. This could just be a single variable, or customizable list (similar to input param for script blocks). This would allow for a lot more customization in builder actions.
    Guest about 4 years ago in Automation 1 Future consideration

    Liquit PowerShell Support for .NET CORE

    Currently Liquit PowerShell .NET library is based on .NET Framework but doesn't support .NET CORE environments. This limits the ability for customers to manage Liquit in cloud environments that support .NET CORE only.
    David Herfurth 7 months ago in Automation 0 Future consideration

    Uninstallation of application for MECM

    Allow creating uninstallation deployments for MECM
    Prudvee Raj over 2 years ago in Automation / Efficiency / User Experience 0 In Progress

    Specify supersedence relationship for new applications

    First time creating applications in MECM or Intune and creating supersedence relationships to the application I created previously
    Prudvee Raj over 2 years ago in Automation / Special Configuration needs 0

    Support MECM Implicit Uninstallation feature

    Allow to configure implicit uninstallation settings (MS docs) for any deployment targeting to MECM collection
    Prudvee Raj almost 3 years ago in Automation / User Experience 0 Future consideration