|
|
|
The Save/Continue process is significantly more complex on the web than in client/server because of the ability to insert and/or modify multiple rows.
The behavior of Save/Continue in Costpoint web includes these characteristics:
If no previously existing rows are queried in the top-level Result Set prior to Save, the system will save all new rows. In this circumstance, the system will query only the top-level transaction record at which you currently have context (and its children).
If you are only making changes to previously queried rows in the top-level Result Set, the system will save the changes and re-execute the original query to repopulate the rows. As a result of changes, however, some saved rows may not redisplay in the requeried Result Set. [This is possible even for the row at which you had context at the time of saving].
If the screen contains both existing, queried, and new top-level Result Set rows, the original query will be re-executed if the current context is on a previously-existing, queried, top-level, transaction row. If current context is on a new row, the system will query only the new top-level row if the current context is on a new transaction row.
The system will keep all currently open Result Sets in the tree open after Save/Continue.