This use case defines the sequence of events that occurs when the user exits a session (Editor).
- The "Close All Editors" use case has been removed from this documentation. Each Editor must now be closed individually.
- External User
- Administrator
- The ACME system is running on the user's system
- The user may have one or more ACME sessions running in separate ACME Editor frames
- The user is using ACME, with one Editor frame open
- The user elects to "Close" the ACME Editor
- If there is no job in the Editor
- The system shuts itself down
- Else, if the job in the Editor is clean
- The system closes the ACME Editor frame (without prompting the user)
- The system removes any locks showing that this user had this job open
- The system shuts itself down
- Else, if the job in the Editor is dirty
- The system prompts the user that "The job 'JOBNAME' has been modified, save changes - y/n/cancel?"
- If the user selects "cancel", the shutdown operation will be stopped
- If the user selects "yes"
- The dirty job is saved
- Job module locks are released
- This ACME Editor is closed
- The system removes the database entry showing that this user had this job open
- The system shuts itself down
- If the user selects "no"
- The dirty job is not saved
- Job module locks are released
- This ACME Editor is closed
- The system removes the database entry showing that this user had this job open
- The system shuts itself down
- Job module locks are released (if they had been acquired)
- The informational lock on the job is released
N/A
These are all new
- The option to close a ACME Editor shall be named "Close", and will appear under the "Job" menu
- Any time a job is closed:
- Locks on job modules shall be released
- The informational lock on the Job (proper) shall be released
|
|