ERP Technology Considerations

ERP technology attention points

1. Diversified types of members (multiple records, separated by separators)
2. The scope of data authority should be differentiated (data query is performed by recording the scope conditions of this data authority, so that these conditions can be added according to records)
3. People with different roles see and operate the analysis interface differently (by authority classification)
4. Simplify the interface
operation Record the records of the log table (addition, deletion and modification),
6. Diversification of positions (multiple records, separated by separators, and managed together with the organization personnel)
7. The relationship between departments, employees and positions (a single table for such records), Department-related employees, position information
8. Relationship between employees (organizational structure)
9. Accounts and roles, account and authority management methods, not only the way to set permissions by roles
10. Data operation permissions (can be processed through AOP )
11. Permissions should be classified and managed according to large modules and operation types (view/add, etc.),
12. Query content to the front end (can be combined through joint query view, code one by one query,)
13. ERP module management, It can be used with point 11 to determine which modules an account can use (you can associate modules with the account first, and then associate permissions, or you can directly associate permissions, and identify which modules can be used from the permissions)
14. Used 15.
Save the user's operation log (record the content before and after, and save according to actual needs)
16. Product price change record (for some It is used where some data is to be recorded)
17. Serial number grouping management (group by function), serial number format setting management, serial number initial value management, if serial number needs to be restarted every day or for a period of time, then there must be scheduled tasks (unsafe) or every time it is acquired. Determine whether to update the process.
18. Employee information, employee current status (on-the-job, resignation), employee record status (indicates logical deletion)
19. Personnel organization change information management. Organization leader management (change log management).
20. Organizational personnel management (logical deletion is required).
21. Each table must be designed and updated, created and managed by time
22. During the development process, the points that need attention for each function should be recorded, so as to facilitate the functional verification later (the test content of the acceptance table)
23. During the development process Record the problem solving process (the appearance and resolution of bugs).
24. If the management authority is managed at the first level, the table must have the records of the relevant organization (module) to distinguish it.
25. If there are still management authority that can be assigned to the lower level, the authority allocation status should be increased.
26. The design entity is the most important. It is good to explain the role of this entity.
27. Database search includes conditional search, conditional search (fuzzy search)
28. API interface is divided into parameter model, entity model, and view model, which is convenient for parameter processing.
29. Parameters are transmitted in the form of models. , which contains annotations for parameter validation.
30. User display data fields can be dynamically changed (by saving the display order and dynamically generating templates on the front end)
31. Parameter verification, business logic data verification, especially deletion logic verification
32. Operation authority and data authority are handled separately, and operation Permissions can be implemented with annotations, data permissions can be implemented with selectByExample in Mybatis, and jap with Specification
33. There will also be the same function that will be displayed on different pages, according to the business operation context.
34. It is also possible to associate modules with subsystems and associate function pages to achieve the realization of different subsystems displaying different function modules and pages. .
35. Batch modify some related or unrelated content
36. You can manage permissions and accounts, roles and accounts, account and permissions, two-way association display between accounts and roles, and display the source of permissions
37. Money is best represented by an integer, When outputting to the front-end, divide 100 to indicate points
38. The user ID can be generated by saving the last generated user ID in the database,
39. The order ID can be combined with the user ID in time to generate
40. The database access API is related to repetitive work
41. The uniqueness should be set in the database 42. If there is a joint query (view) and a cache needs to be used, then
this joint field must be in the cache key to facilitate Cache cleaning
43. startTime (start time), endTime (end time), pageNum (number of pages), pageSize (page size), these general needs to be determined
44. You can use AOP in the controller to output the log of the parameters, If you want to output the user's information in all logs, you can encapsulate the log, save the user's user information in the request, and save the request in the filter.
45. Don't associate with ID, associate with custom ID
46. Interface parameter detection and verification
47. If you want to support the query between levels, you can use a field to save the level ID to facilitate SQL query, and the level name can be saved in a list of names in another table, which can facilitate the reading of the level name without querying each one. Recombination, but all data update operations should be performed when the level management is modified (the level ID string and level name string should be recorded with their own ID and name)
48. Classification information can be added to the organization ID to manage the classification information of each organization (
48. Commodity information can be added to the organization ID to manage the commodity information of each organization (used under platform management, single function can not be used )