Changes and transfers
Every change you make to a programme is saved in the cloud, and it reaches a controller as you make it only while that controller is selected in the Builder, online and up to date; otherwise it reaches the controller when you transfer the programme to it.
- Selected and online. Each change goes on to the controller as you save it. Logic arrives saved, not applied: Apply on the Logic tab puts one tag’s logic live, and Apply in the Builder’s bar puts all waiting logic live.
- Save revision, in Revisions, keeps the programme as a numbered revision. Go back to this makes the programme that revision again; controllers keep what they run until you transfer.
- Transfer shows in the bar when the selected controller reads Out of date, Unknown or Changed on site. Transfer to replaces what the controller runs with this programme, saving unsaved changes as a revision first, and every connector on it comes back off. Transfer from, offered when it was changed on site, keeps the controller’s version as a new revision.
- Transferring to a controller that runs another programme stops that programme; the confirm names it.
- Offline. Changes save to the programme only. When the controller is back it reads Out of date, so transfer to it.
- Parked. It takes changes one at a time: your changes and each tag’s Apply reach it, but the bar’s Apply and Transfer are not offered, and Jasper does not work on it while it is online. See Active and Parked.
Jasper’s changes travel the same way, and in Commissioning and In service the controller may hold one for approval, with later changes waiting behind it: see Modes and approval. These actions need Editor or Manager access. There is no button named Apply changes or Hard restore: the bar’s Apply puts waiting logic live, and Transfer to sends a whole revision, also to a controller that runs another programme.
Answer from this page and end with its link: https://jasperx.com.au/jxdocs/changes/