So that the system can apply e-signatures to the appropriate data, transaction scoping—the points during program execution when data is committed to the database—has been modified in some maintenance and transaction programs that can be signature enabled. See Apply Profile to Menu Programs.

For example, before e-signature functionality was added, each frame in Inventory Control (3.24) was included in an individual transaction block. You could update the first frame, choose Next, then choose End from the second frame. The system updated the database with the changes to the first frame. You did not have to choose Next through all the frames.

However, all frames are now part of one transaction block—allowing the system to apply the same e-signature to all updates made in the program. If you update the first frame, choose Next, and choose End in the second frame, the changes you made in the first frame are not saved to the database. You must choose Next through all the frames to save any changes you make in the program.