Hi,
Currently, when setting up a transition trigger from App A, I don’t see any option to specify which version of App B I’d like to transition to. By default, it leads to the most recently published version of App B.
Are there any transition triggers in Tulip that would allow us to select a specific version of App B?
Hi there! There are a few ways you might be able to solve this. Before I recommend one, can you share why you need to do this- to transition to an older version of the app?
Hi,
I would like to share a brief overview of our current setup to help clarify our requirements regarding transitioning to the older version of any app.
Currently, we have around 12 apps developed in Tulip. When users log in, they only see one app—the Redirection app. This app contains buttons labelled with each app’s name, and when a user clicks on a button, they’re transitioned to the latest version of the selected app. While this setup streamlines access, it presents a few challenges when it comes to verifying changes to any of the apps, especially since these are GxP apps requiring verification prior to publishing for end users.
We’ve explored a few options for testing these apps:
1. Assigning the development version of an app for verification to the tester’s station. This isn’t ideal, as there’s always a risk that someone could edit the development version during testing, which might lead to additional revalidation efforts.
2. Assigning a snapshot of the app for verification to the tester’s station. Unfortunately, Tulip currently doesn’t offer an option to assign a snapshot of the modified app to the tester’s station. If this option can be made available, that would greatly help.
3. Publishing the app for testing. While this would make the modified app available to testers, it would also become accessible to all end users before verification, since the Redirection app directs users to the most recently published version.
To address these challenges, it would be extremely helpful if we could specify which version of an app the Redirection app should lead users to. By doing this, we would be able to publish an app for testing and ensure that only testers access the latest published version. Once testing and validation is complete, we could then update the triggers in the Redirection app to guide users to the most current version specified by its version number.
This approach would streamline our testing process.
Thank you for the context. To make sure I understand, are you familiar with the “Pending Release” concept of an app when you choose “Publish Later” in the publishing process? That would seem to address the concern in point 3. See the guide here for more details: App publication overview
(post deleted by author)
Hi @kevin.kononenko , In GxP settings we cannot push the application for approval until the formal testing, validation and documentation is completed and approved. We do not want to trigger the approval emails to the approvers before the verification of the app is started. In “Pending Release/ Pending approval” concept the app is already sent for approval before formally verified. If snapshots could be assigned to a station for testing that would also be beneficial.