Running Global Projects
Using Extracts with Global Projects : Extract Sessions
Extract Sessions
When an extract is created, it is created at a particular session number in the parent extract. This is called the linked session. As the owner extract is modified, and new sessions added, the linked session on the child extract will not change until a refresh or flush is made.
Note that ISSUE, DROP and FLUSH cause an automatic refresh.
The following example illustrates how extract session numbers and linked session numbers change as an extract is created and modified:
Extract session no.
Linked session in owner
Comment
1
10
Extract created
2
10
Modification made on extract
3
10
Modification made on extract
4
15
Refreshed from owner (sessions 11 to 15 created by other users).
5
15
Further modification.
6
18
Issued (sessions 16 and 17 created by other users)
7
18
Further modification
8
18
Further modification
9
25
Issued (sessions 19 to 24 created by other users)
While a user is making changes only to the extract, the linked session number in the owner stays the same. On refreshing, the local extract is linked to the most recent version of the parent extract.
The new session number linked to in the owner depends on the number of flushes done by other users. In the example the linked session number goes from 10 to 15, indicating that five flushes have been made by other users in the meantime (assuming that no work is being done directly on the owner).
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo