The first data modification process. After receiving the relevant modification application, the person in charge of the problem should fill in the Approval Form for Modification of User-related System Data, clearly describing the cause of the problem, key information items of the data (such as user's fund name, bank card number, mobile phone number and ID number), modification contents and modification results, etc. , submitted to the financial centralized business office manager and in charge of the leadership signature confirmation, and issue a handling opinion. After the director of the Information Center signs and agrees, the project operation and maintenance team will modify and adjust the data. In case of emergency, communicate with the information center orally before data processing. The revised record sheet should be signed later.
The second data modification script. The modified script written by one person must be checked by another person and strictly tested and verified in the test environment before it can be executed in the production environment.
Article 3. Documents. Paper documents are stored in fixed folders after unified signing, and spreadsheet data modification records and corresponding scripts are put on SVN for future reference.
Article 4 naming rules. The data modification record form and the corresponding script should have the same name, and the naming rule is "Data modification change form-date", such as "Data modification change form 201501/kloc-0 _ 3". When modifying the SQL script, we must clearly describe the details of the script modification, and make detailed comments on the modified data at every step in the statement process.
Article 5 It is strictly forbidden to use the identity of business personnel to log in and modify data through the background SMS verification code. If it is really necessary to modify the data, it should be signed by the business personnel, and the administrator should operate the data in a unified way and make records.
User information change specification
In order to strengthen the user information management standard of "user-related system", this standard should be strictly observed in the operation and maintenance process.
Article 1 Download the user registration and change registration form. Business departments need to register and change user information in enterprise-related systems, and need to download the user registration and change table of user-related systems in the download center column of the home page of enterprise-related systems.
Article 2 Define the contents of user registration and change. The change table is divided into investment users and borrowing users. Fill in according to the actual situation, including the user's name, ID number, bank card number, mobile phone number, etc.
Article 3 submission process. The user registration and change information put forward by the business handling office shall be submitted to the information center after being audited by the financial business office and stamped with the official seal, and shall be maintained in the "User Related System" by the operation and maintenance personnel after being confirmed by the information center.
Article 4 Keep the changed contents. The operation and maintenance personnel change the relevant user information according to the paper stamped change order and the system maintenance requirements, and the paper user change order is filed for future reference.