Running Pending Version of Apps in a Station

When an application is validated on a testing instance it will then be imported into a production instance. After it is imported into a production instance the application is immediately published but don’t get released until all approvers approve the new version. Until the app gets approved the application holds a “Pending” state. During that period, controlled test can be conducted with production connectors with actual production data. But apps with pending state cannot be assigned or run on a station. Therefore, having the option of running “Pending” version of apps on a station could facilitate certain testing activities after being published but not approved.

Hey @ecarpena -

I think your underlying need is exactly what we are solving for with the Gated Release feature, which will be available with LTS13, and is available today in standard releases. More information on this feature is here: App Publication Overview.

With this feature, you can also control things like what connector environment will be used during this training phase, grant additional users with training access, etc.

Do you think this will help address your needs?
Pete

2 Likes

Hi @Pete_Hartnett, I think this new feature looks promising. We gave it a try and we observed that we couldn’t execute the pending approval or a pending released version of an app that has not been previously published (Meaning the version 1 of an app has not been released).

More details: We have a station configured with the most recently published version of an app. On the Tulip Player the unreleased app (version 1) does not show up on the list of available apps. Therefore, we can’t select the pending version on the Begin button windows.

We also have two additional questions: 1) Does the pending version of the app creates completion records? 2) Which roles will have the access to execute a non released version of an app?

Thanks for the support.

Hey @ecarpena -

Re: first version - good catch. I have made a ticket to address this behavior.

Re: Completions - Completions are created, but the version name associated with them makes clear that they were created from a version that is pending release

Re: Roles - Account Owners, Workspace Owners, and Admins by default have this permission, but Custom User Roles allow any other custom role to have this accessa as well.

Pete