Thoughts on the way resources are organized in BPMs

Resources are indispensable in the BPMs system. For the basic elements of BPMs, refer to my other article. The way resources are organized is the basis for processing resources. Currently, most systems use tables as units for user operations. Generally, these systems integrate SQL operations, this allows you to easily manipulate resources. So what is the problem with this method? 1. SQL is a simple language, but it is generally only available to developers or IT personnel who need to be familiar with this language, but not to general business personnel. In this way, the system usage will be discounted; 2. SQL is based on data tables. In this way, data can only be analyzed quantitatively, such as quantity, size, and quantity. It is difficult to directly perform qualitative analysis, for example: positions, organizational structures, quality, and so on. In this way, the direct use of data has certain limitations. How can we change this? My idea is very simple. I organize a group of meaningful data into a whole, and a single data is no longer meaningful. For example, in the order system, the data of order name is meaningless, the order name is only a part of the overall order. At the same time, there are some relations between each other, such as the high-low relationship between departments. In this way, resources can be designed with some qualitative analysis. At the same time, it is more advantageous for business personnel to understand the system because the data is expressed as a whole. So how to design such an idea under. net should be left to the readers... ^_^