It looks like the way Blue Prism populates a number of places in the UI is by making inferences on data that can be queried from the database. I also don't see a stored value for upcoming schedule times, so I'm going to assume here that Blue Prism looks at the ScheduleTrigger table to see active schedule triggers and then does calculations each time you want to look at the Timetables view in the UI. Notice how it takes some time to populate that list? I would imagine this would happen quicker if it were just pulling a list from the database, so I'm thinking it builds that list.
First, try this query, Put the name of a schedule inside the single quotes in the WHERE clause:
SELECT *
FROM BPAScheduleTrigger
WHERE BPAScheduleTrigger.scheduleid = (SELECT BPASchedule.id FROM BPASchedule WHERE BPASchedule.name = 'name of a schedule here')
AND BPAScheduleTrigger.usertrigger = 1It may take a bit of trial and error to determine what some of the numbers mean. I don't think they are foreign keys or at least I don't see a lookup table for them. For example, unittype would indicate hourly, daily, monthly, etc. Also it looks to me that usertrigger being 1 means the Schedule is still active, but I only glanced at this so I'd check to verify this. If you want a similar list as that shown in a Timetable, you may need to calculate the next times that will run based on what comes out of that query. Obviously that's set up for a single schedule so you'll want to write a different query; I just wanted to direct you to where it seems to me that the information is stored.
Hope this helps. I does seem like a view would be useful for this stuff. Maybe someone else can comment with a pre-built query for this to display the resulting table in an already-consumable format.
------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company