ADD A NEW IDEA

Automation

    Showing 6

    Allow synchronization profile of an Application Workspace connector to be configured using powershell

    It is possible to create an Application Workspace connector using powershell but you cannot configure the synchronization profile settings. The default values are not desirable because they cause certain data to be not migrated (like package tags)...
    Kid Kooijmans about 1 month ago in Automation 0 Future consideration

    More granular Connector and IdentitySource settings through Powershell

    We want to be able to go to Connectors -> Setup Store Connector -> Release: Publish to Production. By Default it's set to Development when we create this connector through Powershell. Also we want to be able to go to IdentitySource -> Con...
    Glenn Eriksen 4 months ago in Automation 0 Future consideration

    Automate Certificate Import through Powershell

    We want to import certificate with password (.pfx) and assign it the correct zone through your Powershell module. We use our own wildcard certificate for every customer zone, and updating all of them manually are taking a lot of time. Should be qu...
    Glenn Eriksen 4 months ago in Automation 0 Future consideration

    Support automated patching for versioned app names to reduce manual maintenance overhead

    When products use versioned app names (e.g. Postman 9, Postman 10, Postman 11) the patch and release management sort of breaks. Within the same version (e.g. Postman 10) automatic setup store updates work well and update to the latest versions pub...
    Jan Beese 4 months ago in Automation 0 Future consideration

    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

    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