Skip to main content

How to schedule changes to your app

Learn how to schedule changes to your app

Josh Gare avatar
Written by Josh Gare
Updated over 2 years ago

Thanks to the Venn Apps scheduling feature, you can plan ahead by scheduling updates to your app. The scheduling feature allows you to create as many upcoming schedules as you like and you can also roll back to previous versions of the app.

1. Creating a schedule

In order to create a schedule, all you need to do is follow these simple steps:

  1. Make the changes that you'd like to make to the app.

  2. Click on 'Publish' in the top left-hand corner of the screen.

  3. Click on the clock icon.

  4. Give the schedule a name.

  5. Set the date that you'd like the changes to go live.

  6. Set the date that you'd like the changes to be reverted (if applicable).

2. Managing schedules

Once you have created a schedule, it will appear in 'Scheduling' which can be found on the left-hand navigation side-panel. Within 'Scheduling' you can view and manage all of your upcoming schedules and also restore a previous version from thanks to the archive.

A) Managing upcoming schedules

To edit an upcoming schedule, go to the 'Live & Upcoming' tab and click on the '...' on the schedule you'd like to edit to open the context menu.

From the context menu, you can do the following:

  1. Publish the version now.

  2. Update the date / time of the schedule.

  3. Rename the schedule.

  4. Edit the content of the schedule.

  5. Duplicate the schedule.

  6. Delete the schedule.

B) Restoring a previous version

To restore a previous version, go to the 'Archive' tab and click on the '...' on the version that you'd like to restore to open the context menu.

From the context menu, you can do the following:

  1. Publish the version now.

  2. Schedule the version to be published at a later date.

  3. Rename the version.

  4. Edit the content of the version.

  5. Duplicate the version.

  6. Delete the version from the archives.

πŸ’‘ Pro Tip:

  • There is a maximum capacity of 30 records at which point the oldest record in the archive will be deleted whenever a new version is created.

Did this answer your question?