OnePager Project View Custom Update Feature

From OnePager Documentation
Revision as of 17:37, 1 March 2016 by Rfeingold (Talk | contribs) (Selected file(s))

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

OnePager Pull Operations

1) In the past, to update a project view by creating a new snapshot or updating an existing snapshot, you sometimes had to go back to the source application and relaunch OnePager. In effect, you were pushing changes to OnePager from the source application. You can still work this way in version 5.3, but now there is a more natural way to make updates.

2) With OPP and OPX version 5.3, you now have the option to pull source file data into the OnePager Project View Editor (PVE) directly without the back and forth transitions. Behind the scenes, OnePager version 5.3 will locate your source files, open them in the Microsoft source application, and update the project view.

3) To implement this more efficient method for replacing or adding snapshots, we’ve added a new tab to the OnePager ribbon: the Data tab:

P53-0 2-(7)-10272015.png

Replace Snapshot

4) Replace Snapshot The Replace Snapshot button allows you to replace the current snapshot with data from the modified application source file.

a) With the desired snapshot showing in the PVE, OnePager goes to the application source file, imports that application’s source data, and replaces the snapshot.
b) Of course, the implication is that you’ve previously updated the application’s source data.
c) Since OnePager knows the file name and the path name to get to the application’s source data, there is no need to have the Microsoft application itself up and running with the source data loaded. All of this is done for you behind the scenes.

Add snapshot

5) Add Snapshot As with the Replace Snapshot, the Add Snapshot function allows you to add a new snapshot to the project view’s set with data from the modified application source file.

a) With the application source data previously updated to reflect the snapshot you want to add, click the Add Snapshot button and OnePager will retrieve the source data and produce the new snapshot.
b) Again, since OnePager knows the file name and the path name, there is no need to have the application itself running and the source data loaded.

Custom Update...

6) Custom Update… The Custom Update… button works in the same way as the UPDATE button found on the OnePager Start form. As such, the Custom Update… function allows you greater control than the simple Replace Snapshot and Add Snapshot buttons just discussed.

a) With the application source data previously updated to reflect the snapshot you want to add or replace, click the Custom Update… button and OnePager will retrieve the source file and add or update the snapshot.
b) Again, since OnePager knows the file name and the path name, there is no need to have the application itself running and the source data loaded.
c) At this point in the process, OnePager will display the OPC form to give you additional control over how the update is performed.
d) Additionally, you can do a custom pull with the Update… button located on the File tab of the ribbon.

Selected file(s)

7) Selected file(s) The Selected file(s) button gives you additional options for managing the source file or files that provide the data for the pull updates:

a) If you are using a project view (i.e., .TAM file) that was produced with a version of OnePager prior to version 5.3, the .TAM file will not contain the path name for the source file. When you click on the Selected file(s) button, a Data source selection form will appear which gives you several options to associate the project view being displayed with the correct application source data.
b) If the project view being displayed was produced by OnePager version 5.3, the .TAM file will contain an associated application source file name and path name. Using the Selected file(s) button allows you to change the source file(s) before you do a pull update.

(0.2.1.2-53)