Name | Value | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NUMBER | 4400 | ||||||||||||
IA # | 4400 | ||||||||||||
DATE CREATED | 2004/04/12 | ||||||||||||
CUSTODIAL PACKAGE | IFCAP | ||||||||||||
CUSTODIAL ISC | Washington | ||||||||||||
USAGE | Controlled Subscription | ||||||||||||
TYPE | Routine | ||||||||||||
ROUTINE | PRCLOP11 | ||||||||||||
NAME | DBIA4400 MODIFY OPTIONS FOR LSSD SHUTDOWN | ||||||||||||
GENERAL DESCRIPTION | At the beginning of a site's conversion to CoreFLS software, the Legacy Software Shut Down (LSSD) program is run to convert the IFCAP, AEMS/MERS, and Equipment/Turn-In Request packages to a read-only state. These packages will be referred to as legacy packages. One of the steps in the program is disabling any options in the legacy systems which could effect an addition, modification, or deletion of data to the site's VistA database. All legacy options are disabled except those in a pre-determined list, which is known as the 'Options to Leave ALone' list. The list is in the LSSD (#449.1) file and will be referred to here as the List. Before a site converts to CoreFLS, the site will continue to install patches as necessary to fix bugs or add functionality to the legacy packages. When adding functionality, a patch may add or enhance or delete an option or group of options. Later on, when the site runs the LSSD shutdown and converts to CoreFLS, the site may need to continue using the functionality provided by those new options. In that case, it will become necessary to prevent those options from being disabled by the shutdown. To do this, the options must have been added to the List before the shutdown was run. Likewise, there may be options in the List that a future patch may remove or enhance such that those options should be disabled by the legacy shutdown. Those options should then be removed from the List before the legacy shutdown is run. This IA describes the API that patch developers should use to add or remove options from the List. The API must be invoked in the post-install executable of a patch. In any patch that uses this API, the patch must also include a patch dependency for the LSSD patch, PRC*5.1*65. |
||||||||||||
STATUS | Withdrawn | ||||||||||||
KEYWORDS |
|
||||||||||||
DURATION | Till Otherwise Agreed | ||||||||||||
ID | PRCLOP11 | ||||||||||||
COMPONENT/ENTRY POINT |
|