Script history and notifications

History

If a Violet Script is Live, users can also choose to save the history of script outputs.

This will generate a new output entity after each run, while preserving each of the previous ones. A timeline of historical runs and their outputs can be viewed from inside of a Violet Script. An out-of-date entity will be tagged with This entity is not the latest revision, and cannot be used as a linked entity in parameters or as a Violet Variable. Turning off history will delete all existing history.

Notifications

Subscribing to notifications on a Violet Script can let a user know when a Live script has been automatically run due to a changing Violet Variable, and the output has changed. Notifications will be shown in the notifications panel, as well as through Slack if a Slack notification is set up. Subscriptions are individual to each user.

Click on the eye in the top right corner of a script to subscribe to notifications.

FAQ

Can anyone access a Script I've created?

Currently, all Scripts are accessible to all users, as long as they have permission to all the data within them.

If a script contains a Violet Variable linked to data that a user does not have access to, they will also not have access to that script.

We are working to implement a more tailored and comprehensive permissions model for Scripts - stay tuned!

Why are my runs slow?

Running a script after a period of inactivity may take more time than usual. If your Scripts feature is starting to be heavily used by your team and seems to be running slower than expected, please reach out to us.

Examples

Check out these examples of how to run scripts:

• Calculate a satellite’s orbital period based on input altitude, and write the output to a Violet parameter

• Vary aircraft parameters and observe the effect on calculated mission duration

• Calculate satellite link budget, vary component technical specifications and observe the effect on SNR