Allow asset views to run now and on a schedule
I need to create asset views that perform daily aggregation at midnight. Currently once I create an asset view I must wait until after the following midnight to see the output. It would be very useful to have the option to publish once and thereafter on a schedule so there is data to work from immediately.
Alternatively if it was possible to upgrade an existing single published asset view to running on a schedule this would solve the problem.
Since the 2018 release, it is possible to select Run Once to work with the data now. If it’s acceptable, a user has the ability to modify the view to Run on a Schedule and schedule the first run time in the future (midnight tonight for every month etc.) Therefore, we consider the idea of “upgrade an existing single published asset view to running on a schedule” to be solved and completed. Please let me know if you have another idea or use case related to this idea that is not addressed by the 2018 release! Thank you!
AdminJoy Wang (Product Manager, OSIsoft) commented
1. Create a RunOnce test view. Verify it works. And then import the shape from the RunOnce view to create a production view that is scheduled.
2. Another option is to create a continuous view, and then modify the runtime afterwards to start one cycle later (Lok's suggestion below).
3. One more option is to create a RunOnce view and run it. Then modify it and make it a Scheduled view.
**Make sure to pay attention to the start and end times of the view on the Modify View page so that you get the right timestamps for your datasets!
Lok Shun Ko commented
Since the release of the PI Integrator for Business Analytics 2018, it has been possible to modify published views. So it has become possible first publish a scheduled view send the data immediately, then to change it so that it's scheduled to run in the future. For example, assuming the daily aggregation at midnight as described in the enhancement request above, use the following configuration:
start time: as desired
end time: The end time of the last scheduled run. In the example above, t (today at midnight)
first run time: *
recur every: 1 day
Once the initial publication has finished, you can edit the view and use the following parameters:
end time: *
first run time: the time of the next desired run, t+1d
It would be great to know if this enhancement has the potential to be included in the next release! I'm in a similar boat as some of the views I create only publish once every 31 days...