Number generation method and system and electronic equipment

Abstract

The invention relates to the technical field of computers, in particular to a number generation method and system and electronic equipment. According to the number generation method provided by the embodiment of the invention, when the number rule is configured, the plurality of attributes of the entity can be obtained from the entity metadata information, and the attribute list is generated. In the embodiment of the invention, a user only needs to select one attribute from the plurality of attributes of the entity in the attribute list through the rule configuration interface without manual input, so that the number rule configuration accuracy can be improved, and the number configuration efficiency and the number generation efficiency can be improved.

Description

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on March 30, 2024, with application number 202410389412.2 and application name “A method for automatically generating numbers according to rules based on metadata configuration”. The entire contents of the above application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a number generation method, system and electronic device. Background Art

[0003] Number generators are usually used in industry software systems such as enterprise resource planning (ERP) and customer relationship management (CRM) to automatically generate numbers. System administrators can configure the numbering rules for generating numbers through the relevant pages in the above industry software systems. The above industry software systems can be used in service systems such as shopping systems and payment systems. Figure 1 Taking the shopping system shown above as an example, consumers can purchase items through the shopping system, merchants can add product information through the shopping system, and system administrators can configure numbering rules for the entities that are numbered through the shopping system. After the consumer purchases the item, the shopping system can obtain relevant information about the item purchased (such as payment time and item number), generate an order corresponding to the item purchased, and generate the corresponding order number based on the numbering rules configured by the system administrator.

[0004] In the actual numbering scenarios of industry software systems, multiple fields and products require entities to be numbered according to specific rules. Industry software system developers typically set up a numbering rule framework for the system based on the common numbering requirements in each field. System administrators can use this numbering rule framework to configure the text of the numbering rule for each entity, thereby generating numbers that meet these requirements.

[0005] The number usually includes a unique part corresponding to the entity characteristics (i.e., entity attributes) and a common part that is unrelated to the entity's characteristics. The common parts in the numbers corresponding to different entities may be the same. For example, the common parts may include fixed characters, dates, serial numbers, etc. The unique parts in the numbers corresponding to different entities are different. For example, when the entity is an order, the unique part of the number may correspond to the attributes of the order, including the order region, order line number, item number, product category, etc. For example, for the number "LS20201225BJ001", the common part of the number "LS" represents fixed characters, "20221225" represents the date, and "001" represents the serial number. The unique part of the number "BJ" corresponds to the attributes of the order, indicating the order region.

[0006] Currently, when configuring numbering rules, system administrators need to consult system developers to obtain multiple attribute texts of the entity for the unique part of the number. Then, based on actual needs, they need to determine one attribute text from the multiple attribute texts and manually enter the attribute text. This affects the efficiency of rule configuration, and manual entry is prone to errors, resulting in incorrect number generation, which in turn affects number generation efficiency. Summary of the Invention

[0007] In order to solve the above technical problems, the embodiments of the present application provide a number generation method, system and electronic device.

[0008] In a first aspect, an embodiment of the present application provides a numbering method, comprising: displaying a numbering rule generation interface; displaying an attribute list of a first entity in response to a first operation of a user, the attribute list including multiple attributes of the first entity; and generating a numbering rule based on the first attribute in response to a user selecting a first attribute among the above multiple attributes.

[0009] In the embodiments of the present application, the numbering rule generation interface is the numbering configuration interface mentioned in this application. When configuring a numbering rule, a user can select an attribute, such as a first attribute, from the attribute list of the first entity displayed on the numbering configuration interface. Based on the first attribute, a numbering rule corresponding to the first entity can be generated. This eliminates the need for the user to manually enter the attribute text of the first entity, thereby avoiding the problem of incorrect rule configuration caused by input errors, which in turn leads to incorrect number generation. This improves the efficiency of rule configuration and number generation.

[0010] In a possible implementation of the first aspect above, the displaying of the attribute list of the first entity corresponding to the first operation of the user includes: in response to the first operation of the user, obtaining metadata information of the first entity, the metadata information of the first entity including attribute information of multiple attributes of the first entity, the attribute information of the multiple attributes of the first entity including attribute names of the multiple attributes of the first entity; based on the attribute names of the multiple attributes of the first entity, generating an attribute list and displaying the attribute list.

[0011] It is understood that the user's first operation may be, for example, clicking Figure 8 Control 001 in .

[0012] In an embodiment of the present application, in response to a first user operation, metadata information of a first entity can be obtained, and attribute information of the first entity, such as attribute names, can be obtained from the metadata of the first entity, thereby generating an attribute list. In this way, the user can see the attribute names of multiple attributes of the first entity in the attribute list without having to inquire about the attribute information of the first entity from the query or system developer, thereby improving the accuracy and efficiency of rule configuration.

[0013] In a possible implementation of the first aspect above, corresponding to the user selecting the first attribute among multiple attributes, generating a numbering rule based on the first attribute includes: corresponding to the user selecting the first attribute among multiple attributes, generating a first numbering sub-rule based on the first attribute, and generating a numbering rule based on the first numbering sub-rule.

[0014] In the embodiment of the present application, the user can directly select the first attribute to complete the configuration of the first numbering sub-rule without manual input, which can avoid input errors that lead to rule configuration errors and other problems.

[0015] In a possible implementation of the first aspect above, the method further includes: detecting a number generation instruction corresponding to the first entity, and generating a number corresponding to the first entity based on a numbering rule.

[0016] It can be understood that when the first entity is generated, a number generation instruction corresponding to the first entity can be detected, instructing to generate a number corresponding to the first entity.

[0017] In a possible implementation of the first aspect above, the numbering rule also includes a second numbering sub-rule; a numbering generation instruction corresponding to the first entity is detected, and a number corresponding to the first entity is generated based on the numbering rule, including: detecting the numbering generation instruction corresponding to the first entity, obtaining the running data of the numbering rule and the first entity, wherein the running data includes data generated during the generation process of the first entity; obtaining a data value corresponding to the first attribute and a data value corresponding to the second numbering sub-rule from the running data; determining the data value corresponding to the first attribute as a first numbering segment, and determining the data value corresponding to the second numbering sub-rule as a second numbering segment; and determining the number corresponding to the first entity based on the first numbering segment and the second numbering segment.

[0018] It can be understood that the numbering rule including the second numbering sub-rule is only an example, and the numbering rule may also include a third numbering sub-rule, a fourth numbering sub-rule, and so on.

[0019] In a second aspect, an embodiment of the present application provides a numbering system, which includes a metadata information management unit and a rule configuration unit, wherein the metadata information management unit is used to store metadata information of a first entity, and the metadata information of the first entity includes attribute information of multiple attributes of the first entity; the rule configuration unit is used to display a numbering rule generation interface, and display an attribute list of the first entity corresponding to a first operation of the user, the attribute list includes multiple attributes of the first entity, and, corresponding to the user selecting a first attribute among the multiple attributes of the first entity, generate a numbering rule based on the first attribute.

[0020] In a possible implementation of the second aspect above, the system further includes a number generation unit, which detects a number generation instruction corresponding to the first entity, obtains a numbering rule, and generates a number corresponding to the first entity based on the numbering rule.

[0021] In a third aspect, an embodiment of the present application provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and runnable on the processor. When the processor executes the computer program, the numbering generation method in the first aspect and any possible implementation of the first aspect is implemented.

[0022] In a fourth aspect, an embodiment of the present application provides an electronic device, which includes the numbering generation system in the above-mentioned second aspect and any possible implementation of the second aspect.

[0023] In a fifth aspect, an embodiment of the present application provides a readable storage medium, on which instructions are stored. When the instructions are executed on an electronic device, the electronic device executes the numbering method mentioned in the present application.

[0024] The beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions of the first aspect and various possible implementations of the first aspect, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 According to some embodiments of the present application, an application scenario is shown;

[0026] Figure 2 According to some embodiments of the present application, a numbering rule configuration interface is shown;

[0027] Figure 3 According to some embodiments of the present application, a number generation system architecture is shown;

[0028] Figure 4 According to some embodiments of the present application, a metadata information management interface is shown;

[0029] Figure 5According to some embodiments of the present application, another number generation system architecture is shown;

[0030] Figure 6 According to some embodiments of the present application, a flowchart of a number generation method is shown;

[0031] Figure 7 According to some embodiments of the present application, a schematic diagram of an attribute list is shown;

[0032] Figure 8 According to some embodiments of the present application, another numbering rule configuration interface is shown;

[0033] Figure 9 According to some embodiments of the present application, a schematic diagram of a rule matching condition is shown;

[0034] Figure 10 According to some embodiments of the present application, a schematic diagram of a numbering rule list is shown;

[0035] Figure 11 According to some embodiments of the present application, a flowchart of another number generation method is shown;

[0036] Figure 12 According to some embodiments of the present application, a hardware structure diagram of an electronic device is shown. DETAILED DESCRIPTION

[0037] The illustrative embodiments of the present application include, but are not limited to, a number generation method, system, and electronic device.

[0038] In order to more clearly understand the solution of this application, the relevant field terms involved in this application are first explained.

[0039] (1) Entity

[0040] As previously mentioned, in the embodiments of the present application, the entity is a numbered object, and the entity generally has multiple attributes. If the number involves entity attributes, the unique portion of the number corresponds to at least one attribute of the entity. For example, in a shopping system, the entity may be an order, and the attributes of the entity may include the order region, order line number, item number, product category, etc. The unique portion of the order number may be determined based on at least one of the attributes such as the order region, order line number, item number, product category, etc. For another example, in a payment system, the entity is an invoice, and the attributes of the entity may include the billing region, billing unit, invoice type, etc. The unique portion of the invoice number may be determined based on at least one of the attributes such as the billing region, billing unit, invoice type, etc.

[0041] For example, when the administrator of the shopping system configures the order numbering rule, if it is necessary to enter the attribute text of the order in the rule configuration interface, it is necessary to enter the attribute name recorded in the metadata corresponding to the order.

[0042] (2) Metadata

[0043] Metadata is data that describes the characteristics of data and does not include the substantive information of the data, such as the content of an image or a text message. Data characteristics may include the structure, meaning, and rules of the data. Specifically, in the aforementioned industry software system, when developing the system, system developers will configure the attribute name, attribute alias, attribute type, attribute value type, etc. for each entity attribute to ensure consistency in the description of entity attributes during system development and use. This generates metadata for each entity that includes each attribute of the entity, allowing subsequent system administrators to configure numbering rules based on the entity attributes in the metadata. For example, if the entity is an order, the entity's metadata information may include information such as the attribute name being orderarea, the attribute value type being text, and the attribute type being standard attribute.

[0044] As mentioned previously, numbers typically consist of a unique portion and a common portion. Because the unique portion of a number corresponds to an entity's attributes and needs to be configured for each entity, system developers can set the location corresponding to the unique portion of the number in the numbering rule framework as a text input box. When configuring numbering rules for different entities, system administrators will need to manually enter the entity's attribute text in this text input box.

[0045] For example, a numbering requirement might be "automatically generate business numbers based on four components: character prefix, date, custom field, and serial number." Custom fields correspond to entity attributes. System developers can then configure a numbering rule framework of character prefix + date + custom field + serial number, which includes four sub-rules: sub-rule 1 for character prefix, sub-rule 2 for date, sub-rule 3 for custom field, and sub-rule 4 for serial number. In the supplier document numbering scenario shown in Table 1 below, products can include supplier management, product entities can include supplier changes, and the application field for numbering (i.e., the name of the number) can be the change process number. System administrators can configure numbering rules based on the above numbering rule framework. For example, sub-rule 1 can be "GYS"; sub-rule 2 can be "year and month" (e.g., 202206); and sub-rule 4 can be "incremental natural number" (e.g., 00001). It is understood that a numbering rule includes a sub-rule to ensure number uniqueness, such as the serial number. This sub-rule can be configured to increment by a natural number, increment by a natural number every day, and so on, and the number of digits in the natural number can also be configured.

[0046] Because Sub-Rule 3 corresponds to the supplier's changed attributes, which are also attributes of the entity, the system administrator needs to manually enter the entity's attribute text in the text input box. Specifically, since entities typically include multiple attributes, the system administrator needs to select an attribute from the entity metadata information set during system development based on actual numbering requirements. For example, if the system administrator selects "Business Type," the text "Business Type" must be manually entered as Sub-Rule 3.

[0047] When generating a change process number based on this numbering rule, obtain the data values ​​corresponding to each sub-rule, namely the numbering segments, and then arrange the numbering segments in the order of their corresponding sub-rules. For example, if the numbering segment corresponding to sub-rule 1 is "GYS", the numbering segment corresponding to sub-rule 2 is "202206", the numbering segment corresponding to sub-rule 3 is "YWLX", and the numbering segment corresponding to sub-rule 4 is "00001", the generated change process number is GYS202206YWLX00001.

[0048] Table 1:

[0049] product entity Application Fields Numbering Example Supplier Management Supplier Change Change process number GYS202206YWLX00001

[0050] In some embodiments, the numbering rule configuration interface can refer to Figure 2 ,like Figure 2 As shown, the table header is the numbering rule framework set by the system developer. The prefix corresponds to sub-rule 1, the second segment corresponds to sub-rule 2, the third segment corresponds to sub-rule 3, and the suffix corresponds to sub-rule 4. Because sub-rule 3 corresponds to an entity attribute, when configuring the numbering rule, the system administrator needs to select an entity attribute from multiple attributes based on actual needs and manually enter the text corresponding to the entity attribute. For example, for an entity supplier change, the application field of the number is the change process number corresponding to sequence number 4. When configuring the numbering rule, the system administrator needs to manually enter the entity attribute text "Business Type" in the column where the third segment is located.

[0051] In addition to the above-mentioned numbering involving entity attributes, there is also a type of numbering that does not involve entity attributes. In some embodiments, when the numbering requirement does not involve entity attributes, the configured numbering rules do not involve entity attributes, and the numbers generated according to the numbering rules only include the general part. Since the general part of the number does not need to be set for the entity, the system developer can directly set the text required for the configuration of each sub-rule in the numbering rule framework according to common application requirements. For example, for dates, system developers can directly set a text list that can include "year", "year-month", "year-month-day", etc. When configuring the numbering rules, the system administrator can directly select the existing text in the text list without manual input.

[0052] For example, if the numbering requirement is "Automatically generate numbers based on a character prefix, date, and serial number through configuration," the system developer sets the numbering rule framework as character prefix + date + serial number, which includes three sub-rules: sub-rule 1 for the character prefix, sub-rule 2 for the date, and sub-rule 3 for the serial number. When configuring the numbering rule, the system administrator can directly select the text corresponding to the character prefix, date, and serial number from the existing text list, eliminating the need for manual entry. For example, in the accounts receivable document numbering scenario shown in Table 2 below, products can include accounts receivable (i.e., sales), product entities can include invoices, and the application field for the numbering can be the invoice number. When configuring the numbering rule, the system administrator can select the text for each sub-rule based on the above numbering rule framework. For example, if sub-rule 1 is selected as "FP," sub-rule 2 is selected as "Year and Month" (e.g., 202212), and sub-rule 3 is selected as "Incremental natural number" (e.g., 99), the invoice number generated according to this numbering rule might be FP20221299.

[0053] Table 2:

[0054] product entity Application Fields Numbering Example accounts receivable bill Invoice number FP20221299

[0055] However, for numbering involving entity attributes, as shown in Table 1, system administrators need to manually enter the entity attribute text in the numbering rule configuration interface when configuring numbering rules, which affects rule configuration efficiency. Manual input is also prone to errors, which can lead to incorrect number generation and affect numbering efficiency.

[0056] To solve the above problems, an embodiment of the present application provides a numbering generation method, which may include: if the numbering rule involves the attributes of an entity, for example, the numbering rule of the entity includes a first sub-rule, and the first sub-rule is related to the attributes of the first entity. When configuring the numbering rule corresponding to the entity, a numbering configuration interface (i.e., the numbering rule generation interface mentioned in this application) can be displayed. Corresponding to the first operation of the user (i.e., the system administrator mentioned in this application), the metadata information of the first entity can be obtained and multiple attributes of the first entity can be displayed on the rule configuration interface, for example, it can be displayed on the rule configuration interface in the form of an attribute list. The first attribute selected by the user in the attribute list can then be determined as the attribute text required when configuring the numbering rule, and the numbering rule is generated based on the first attribute. In this way, when configuring the numbering rule, it is only necessary to obtain the first attribute through the entity metadata information, without the need for manual entry, which reduces the possibility of numbering rule configuration errors and can improve the rule configuration efficiency and numbering generation efficiency.

[0057] For example, for the above-mentioned supplier document numbering scenario and the numbering request "automatically generate business numbers according to the four parts of character prefix, date, custom field, and serial number through configuration", the numbering rule framework set by the system developer can be character prefix + date + custom field + serial number, which includes four sub-rules, sub-rule 1 for character prefix, sub-rule 2 for date, sub-rule 3 for custom field, and sub-rule 4 for serial number. When configuring the numbering rules corresponding to the entity "supplier change", for sub-rule 3 involving entity attributes, first obtain the metadata information of the supplier change and display the attribute list of the supplier change on the rule configuration interface. The attribute list includes multiple attributes of the supplier change. The first attribute selected by the user in the attribute list (such as business type) can then be used as the text of sub-rule 3.

[0058] In some embodiments, in response to a first user operation, metadata information of a first entity is obtained. The metadata information of the first entity may include attribute information of multiple attributes of the first entity, and the attribute information may include attribute names of the multiple attributes of the first entity. Then, an attribute list is generated based on the attribute names of the multiple attributes of the first entity.

[0059] It is understood that when the first numbering sub-rule in the numbering rule corresponds to an entity attribute, the user's first operation may be clicking a control corresponding to configuring the first numbering sub-rule in the rule configuration interface, for example, clicking a control corresponding to the first numbering sub-rule. The multiple attributes of the first entity may include all attributes of the first entity, and the generated attribute list may include the attribute names of all attributes of the first entity.

[0060] In some embodiments, corresponding to a user selecting a first attribute among a plurality of attributes of a first entity, a first numbering sub-rule is generated based on the first attribute, and a numbering rule is generated based on the first numbering sub-rule.

[0061] It can be understood that the first numbering sub-rule can be the part of the numbering rule corresponding to the entity attribute. After the user selects the first attribute, the first numbering sub-rule can be generated, that is, the configuration of the first numbering sub-rule is completed.

[0062] In some embodiments, when a first entity is generated, a number corresponding to the first entity needs to be generated. When the first entity is generated, a number generation instruction corresponding to the first entity can be detected, where the number generation instruction is used to instruct the generation of a number corresponding to the first entity. Then, a number corresponding to the first entity can be generated based on a numbering rule.

[0063] It is understood that during the generation of the first entity, operational data of the first entity is generated, and the operational data includes attribute values ​​corresponding to various attributes of the first entity. For example, when the first entity is an order, when the order is generated, order information (i.e., operational data) is generated, including attribute values ​​corresponding to attributes such as the order region, order time, order line number, item number, and product category. Based on the numbering rule, the data value corresponding to the numbering rule can be determined from the operational data of the first entity, thereby determining the number corresponding to the first entity.

[0064] During the numbering process, a configured numbering rule can be obtained. Then, the operating data of the first entity is obtained, and the data values ​​corresponding to each sub-rule of the numbering rule are obtained from the operating data of the first entity, and the numbering fragments corresponding to each sub-rule are determined. Among them, for the sub-rules in the numbering rule involving entity attributes, such as the first numbering sub-rule mentioned above, the attribute value corresponding to the first attribute can be obtained from the operating data of the first entity based on the first attribute corresponding to the first numbering sub-rule, and the first numbering fragment can be determined. And based on other numbering sub-rules, the data values ​​corresponding to other numbering sub-rules can be obtained from the operating data of the first entity to determine the second numbering fragment. Finally, the first numbering fragment and the second numbering fragment are arranged in the order of the corresponding numbering sub-rules to generate a complete number.

[0065] In other embodiments, during the number generation process, after detecting the number generation instruction corresponding to the first entity, the operation data of the first entity may be obtained first, and then the numbering rule may be obtained. This application does not limit this.

[0066] For example, Figure 1 Taking the shopping system shown as an example, the first entity is an order. When a consumer purchases an item through the client of the shopping system (such as a shopping application), the server side of the shopping system can obtain relevant information about the consumer's purchase of the item (i.e., the operation data of the order) and generate an order and order number corresponding to the consumer's purchase of the item. Specifically, the server side can detect the order number generation instruction corresponding to the order and obtain the numbering rule corresponding to the order. If the first numbering sub-rule in the numbering rule corresponds to the attribute of the order, the server side will obtain the attribute value of the first attribute from the operation data of the order according to the first numbering sub-rule to determine the first numbering fragment. And according to other numbering sub-rules, the data values ​​corresponding to other numbering sub-rules are obtained from the operation data of the order to determine the second numbering rule fragment. Finally, the server side arranges the first numbering fragment and the second numbering fragment in the order of the corresponding numbering sub-rules to generate a complete order number.

[0067] The value of the first numbering segment corresponding to the first attribute (i.e., the first sub-rule) in the numbering can be obtained by obtaining the attribute value of the first attribute from the operational data of the first entity based on the first attribute name determined in the metadata information of the first entity. For example, when the first entity is an order and the first attribute name is region, during the order generation process, the value corresponding to the region can be obtained from the operational data of the order (for example, the corresponding value for Beijing is bj), and the resulting first numbering segment is bj.

[0068] In some embodiments, metadata information may include standard attributes and extended attributes. The information of standard attributes is the system default configuration information, which cannot be changed by the user, and the standard attribute information of different entities is consistent; the relevant information of extended attributes can be configured by the user, for example, it can be added, changed or deleted according to actual needs, and the extended attribute information of different entities may be inconsistent.

[0069] Exemplarily, for the order document number scenario, when the product is a sales order, its corresponding entity may be an order. Taking the first entity as an order as an example, the metadata information of the order may include the attribute information shown in Table 3 below. As shown in Table 3, in the attribute information of the order, for each attribute, information such as the attribute name, alias, attribute value type, table field name and type are recorded. For example, for the standard attribute "lineNumber", the alias "Order Line Number", the attribute value type "Text (String)" and the type "Standard" are recorded. The attributes of an order include standard attributes and extended attributes, among which the standard attributes are fixed attributes of each type of entity (such as an order), such as the order line number in Table 3, which cannot be changed or deleted by the user. Extended attributes are additional attributes of an entity. Users can manage the extended attributes of an entity (including adding, changing or deleting) by clicking "Change / Delete" in the operation column on the left.

[0070] Table 3:

[0071]

[0072] First, combine Figure 3-Figure 5 , the numbering generation system 10 provided in an embodiment of the present application is described.

[0073] Reference Figure 3 , Figure 3 FIG. 1 shows a number generation system architecture provided by an embodiment of the present application. Figure 3 As shown, a number generation system 10 provided in an embodiment of the present application includes a metadata information management unit 101, a rule configuration unit 102 and a number generation unit 103.

[0074] The metadata information management unit 101 is used to store entity metadata information, system page data information, system rule data information, system process data information, etc. The attribute information in the entity metadata information can refer to Table 3 above, including the entity's standard attribute information and extended attribute information. The entity metadata information is pre-configured by the system developer, and users can view and manage the stored metadata information. For example, users can add, modify, or delete information related to extended attributes based on actual needs.

[0075] For example, Figure 4 An entity metadata information management interface is shown, such as Figure 4 As shown, when the first entity is an OrderLine, its metadata information may include the attribute information shown in Table 3 above, as well as basic entity information, validation rules, data services, data events, and preset extension points. Users can click the New Attribute control 041 to add an extended attribute, click the Add Index control 042 to add an index to an attribute, click the Index Initialization control 043 to clear an attribute index, and click the Search box 045 to search for attribute information. Each extended attribute has a selection control A, an edit control B, and a delete control C. Clicking the Select control A and then the Batch Delete control 044 deletes multiple selected extended attributes. Clicking the Edit control B allows editing of the corresponding extended attribute information. Clicking the Delete control C allows individual deletion of the corresponding extended attribute.

[0076] The rule configuration unit 102 is used to store numbering rules and numbering rule matching conditions, and provides a rule configuration interface and numbering rule management services. Users can use the numbering rule management services in the rule configuration interface to configure and maintain numbering rules (i.e., modify numbering rules based on numbering requirements). When users configure and maintain numbering rules, the rule configuration unit 102 can obtain metadata information provided by the metadata information management unit 101 through remote services.

[0077] The number generating unit 103 includes a number generator software development kit (SDK). The number generator SDK can obtain the required numbering rules from the rule configuring unit 102 to generate corresponding numbers.

[0078] Reference Figure 5 , Figure 5 Another number generation system architecture provided by an embodiment of the present application is shown.

[0079] like Figure 5As shown, the rule configuration unit 102 may include a management terminal, which provides a rule configuration interface. Users can configure numbering rules in the rule configuration interface. After the numbering rule configuration is completed, rule matching conditions can be generated. The rule matching conditions refer to the correspondence between entities and numbering rules. For example, the entity name A may correspond to numbering rule 1. After the user completes the numbering rule configuration, the management terminal stores the rule matching conditions, numbering rules, and numbering rule fragments in a database.

[0080] The number generator SDK in number generation unit 103 also stores business code. When generating a number, number generation unit 103 needs to obtain a rule interface, then call the SDK interface method using the business code and determine the numbering rule corresponding to the entity based on the method input parameters. When an entity is generated, the database can store the entity's operational data, and the number generator can retrieve the entity's operational data from the database to generate the corresponding number for the entity.

[0081] The following is based on Figure 5 The system architecture shown, combined with Figure 6-Figure 9 , describes the numbering method provided in the embodiment of the present application.

[0082] Figure 6 FIG. 1 shows a flow chart of a number generation method provided in an embodiment of the present application; FIG. Figure 6 As shown, the method includes the following steps:

[0083] S101 , the rule configuration unit 102 obtains metadata information of a first entity from the metadata information management unit 101 .

[0084] In some embodiments, when configuring the numbering rule corresponding to the first entity, the user can perform a first operation, for example, the user can Figure 8 In the rule configuration interface shown, click on the selection control 001. The rule configuration unit 102 can respond to the user's first operation, obtain metadata information of the first entity from the metadata information management unit 101, and display multiple attributes of the first entity on the rule configuration interface.

[0085] It can be understood that the numbering rule corresponding to the first entity includes numbering sub-rules related to the attributes of the first entity.

[0086] Specifically, the rule configuration unit 102 can Figure 4 The metadata information shown in the figure obtains information about multiple attributes of the first entity and generates an attribute list, which is displayed on the rule configuration interface. The attribute list may only include Figure 4 The attribute name in the Figure 4 The alias in , or you can also include Figure 4For example, when the first entity is an order, you can generate the following Figure 7 The attribute list of the order shown includes aliases for standard attributes such as item number and aliases for extended attributes such as order line number.

[0087] S102: The rule configuration unit 102 determines a first numbering sub-rule according to the entity metadata information, and completes the numbering rule configuration.

[0088] In some embodiments, when configuring a first numbering sub-rule related to an attribute of a first entity, a user can select an attribute (i.e., a first attribute) from the entity metadata information displayed on the rule configuration interface, and the rule configuration unit 102 can determine the first attribute as the first numbering sub-rule, thereby completing the configuration of the first numbering sub-rule. Numbering sub-rules that do not involve entity attributes also need to be configured. For example, when the numbering sub-rule is a time series, it can be configured as "year-month" or "year-month-day", etc.; when the numbering sub-rule is a serial number, it can be configured as "natural number increment every day" or "overall natural number increment"; when the numbering sub-rule is a fixed value, it can be configured as a fixed character "V" or "LS", etc. In addition, the maximum character length of each numbering sub-rule in the numbering rule can also be configured, for example, it can be 10 bits or 20 bits. After configuring each numbering sub-rule in the numbering rule, the numbering rule can be generated.

[0089] It is understood that the rule configuration interface can refer to Figure 8 The three columns in the figure correspond to the attributes of the entity. Each row of numbered sub-rules does not require manual entry. Instead, a selection control 001 is included. When the user clicks this selection control 001, a list of attributes for the first entity is displayed in the rule configuration interface. The user can select an attribute from the list based on actual needs. In some embodiments, the list of attributes for the first entity can be displayed in a new interface or as a drop-down list, which is not limited in this application.

[0090] In some existing implementations, configuring numbering rules requires manual entry of text related to entity attributes. When the numbering rule corresponding to a particular entity needs to be distinguished from other entities in the first numbering sub-rule section, the numbering rule corresponding to that entity involves the entity's extended attributes. In this case, the user may be unable to access the entity's extended attributes, thus failing to complete the numbering rule configuration. However, when configuring numbering rules, the numbering generation method provided in the embodiments of the present application allows the user to directly select extended attributes from the entity's attribute list displayed in the rule configuration interface, thus avoiding this technical issue.

[0091] In some embodiments, when the numbering rule configuration of multiple entities is completed, the rule configuration unit 102 may further generate a rule matching condition. The rule matching condition may be that the entity named A matches the first numbering rule. For example, Figure 9 As shown, the rule matching condition may be that the first entity corresponds to a numbered rule with a rule number of 1001, and the second entity corresponds to a numbered rule with a rule number of 1002.

[0092] It is understood that in actual numbering scenarios, multiple products may be included, and each product may include multiple entities. Therefore, it is necessary to configure numbering rules for each entity corresponding to each product in the scenario. For example, when the numbering rule only involves the standard attributes of the entity, since the standard attributes are system default configuration information and cannot be modified by the user, the user can select the same attribute when configuring the numbering rule corresponding to each entity, resulting in the same first numbering sub-rule. For another example, when the numbering rule involves the extended attributes of the entity, since the extended attributes are user-configurable information, the user can select different attributes when configuring the numbering rule corresponding to each entity, resulting in different first numbering sub-rules.

[0093] In some embodiments, after the numbering rule configuration is completed, the rule configuration unit 102 can store the numbering rule and rule matching conditions of each entity in the database. For example, when the first entity is an order, the order numbering rule stored in the database can refer to Figure 10 The numbering rule list shown may include the rule number, sub-rule number, type, configuration value (i.e., numbering rule text), parameter number, maximum length, sequence number starting value, sequence number maximum value, and current time series value. Each numbering sub-rule corresponds to a sub-rule number. The numbering sub-rule associated with an order attribute has a sequence number of 2, a configuration value of the first attribute (e.g., project number), a corresponding parameter number of 1, and a maximum length of 20 bits, indicating that this numbering sub-rule corresponds to the first attribute in the order metadata (i.e., the attribute in the first row of Table 3). The character configuration value for sub-rule number 1 is a fixed value of "LS," corresponding to a maximum length of 10 bits. The time series configuration value for sub-rule number 3 is "year-month-day" (i.e., "YYMMDD"), corresponding to a maximum length of 20 bits, and the current time series value is "20221223." The numeric sequence for sub-rule number 4 corresponds to a sequence number starting value (e.g., 1), a maximum sequence number (e.g., 999999), and a maximum length of 10 bits. The maximum length corresponding to each numbering sub-rule is the maximum character length configured when the rule is configured.

[0094] It's understood that the type of each sub-rule corresponds to the numbering rule framework set by the system developer. For example, if the numbering sub-rule framework is character prefix + custom field + date + serial number, the type of the sub-rule with sub-rule sequence number 1 is character prefix, the type of the sub-rule with sub-rule sequence number 2 is custom field, the type of the sub-rule with sub-rule sequence number 3 is date, and the type of the sub-rule with sub-rule sequence number 4 is serial number.

[0095] S103: The numbering generating unit 103 obtains a numbering rule.

[0096] When the first entity is generated, the number generation system 103 can detect the number generation instruction corresponding to the first entity and enter the number generation process. During the number generation process, the number generation unit 103 can obtain the numbering rule from the rule configuration unit 102. Specifically, when generating the number corresponding to the first entity, the number generation unit 103 can use the numbering rule management service of the rule configuration unit 102 to determine and obtain a numbering rule that matches the first entity based on the rule matching conditions.

[0097] For details, please refer to Figure 5 , the number generation unit 103 first needs to obtain the rule interface to obtain the numbering rule corresponding to the first entity. Then, in the business code, the numbering rule corresponding to the first entity can be determined according to the method parameters (i.e., the parameters passed into the method statement) by calling the SDK interface method statement. Exemplarily, the statement for calling the SDK interface method can be "genegrateNumber(bizCode: String, condition: String, orderLine: OrderLine)". After the method is passed in, the statement for determining the numbering rule corresponding to the first entity can be "genegrateNumber("OrderNumber", "Order", orderLine)". According to this statement, it can be determined that the current application scenario is the order document numbering scenario, the operating environment is the order generation environment, and the first entity can be determined to be an order, so that the numbering rule corresponding to the order can be obtained.

[0098] S104: The number generating unit 103 generates a number corresponding to the first entity according to a numbering rule.

[0099] During the process of generating a number corresponding to the first entity, after obtaining the numbering rule, the numbering generation unit 103 can determine the data value corresponding to each sub-rule in the numbering rule based on the numbering rule, that is, determine the numbering fragment corresponding to each sub-rule, and then arrange the numbering fragments in the order of the corresponding sub-rules to generate a complete number. The value of the numbering fragment corresponding to the first attribute in the number is obtained by obtaining the attribute value corresponding to the first attribute from the first entity's operational data based on the first attribute determined in the metadata information of the first entity.

[0100] If the numbering rule corresponding to the first entity includes at least two numbering sub-rules, and the first numbering sub-rule corresponds to the first attribute of the first entity, the numbering generation unit 103 can obtain the operating data of the first entity from the database, determine the attribute value corresponding to the first sub-rule (i.e., the first attribute), and thus determine the numbering segment corresponding to the first attribute in the numbering.

[0101] For example, in some embodiments, during the number generation process corresponding to the first entity, the number generation unit 103 may obtain the following information: Figure 10 In the numbering rule list shown, the attribute corresponding to the first entity is determined for the numbering sub-rule with the custom field type. Based on the parameter sequence number being 1, the first attribute in the entity order metadata information corresponding to the numbering sub-rule is determined to be the item number. Numbering generation unit 103 can obtain the attribute value corresponding to the item number from the order's operational data.

[0102] It is understood that when the first attribute is a standard attribute, the attribute value of the first attribute can be obtained from the database through Java reflection technology; when the first attribute is an extended attribute, the attribute value of the first attribute can be obtained from a dynamically created data set (Map). Among them, Java reflection technology is a method that can obtain all attributes of any entity in the runtime state.

[0103] For other numbering sub-rules, the numbering generation unit 103 can obtain the data value corresponding to the other numbering sub-rule, i.e., the numbering fragment, from the cache. For example, when the other numbering sub-rule is a sequence number, the numbering generation unit 103 can obtain the sequence number value from the cache. It will be understood that the sequence number can ensure the uniqueness of the ultimately generated number. The sequence number value can be a randomly generated value or a value generated according to the "daily natural number increase" or "overall natural number increase" rule.

[0104] Optionally, the numbering unit 103 may obtain the operating data of the first entity from a database and determine the data values ​​corresponding to the other numbering sub-rules from the operating data of the first entity. For example, when the type of the other numbering sub-rule is time series and the configuration value is "year, month, and day", the numbering unit 103 may obtain the generation time of the first entity from the operating data of the first entity to determine the data value corresponding to the numbering sub-rule.

[0105] Once the numbering segments corresponding to each numbering sub-rule in the numbering rule are determined, the numbering generation unit 103 can arrange these numbering segments in the order of their corresponding numbering sub-rules, for example, by sub-rule sequence number, to obtain a complete number. In this way, when multiple entities are generated sequentially, the numbering generation unit 103 can determine the data values ​​corresponding to each numbering sub-rule from the operating data of each entity based on the obtained numbering rule corresponding to the entity, thereby automatically generating a number for each entity. For example, if the entity is an order, when multiple orders are generated sequentially, the numbering generation unit 103 can automatically generate multiple order numbers in sequence.

[0106] Figure 11 FIG. 1 shows another flow chart of a number generation method provided in an embodiment of the present application; FIG. Figure 11 As shown, the method includes the following steps:

[0107] S201, displaying a rule configuration interface.

[0108] In this step, the numbering system 10 may display a rule configuration interface, and the user may configure the numbering rule in the rule configuration interface.

[0109] S202 : In response to a first operation by the user, display an attribute list of the first entity, where the attribute list includes a plurality of attributes of the first entity.

[0110] In this step, for a first numbering sub-rule related to an attribute of the first entity within the numbering rule, the user can perform a first operation to configure the first numbering sub-rule. In response to the user's first operation, the numbering generation system 10 can display an attribute list of the first entity in the rule configuration interface. This attribute list includes multiple attributes of the first entity. The user can select an attribute from the multiple attributes in this attribute list to complete the configuration of the first numbering sub-rule.

[0111] S203 : In response to the user selecting a first attribute from among the multiple attributes, a numbering rule is generated based on the first attribute.

[0112] In this step, when the user selects the first attribute among multiple attributes, a first numbering sub-rule is generated based on the first attribute, that is, the configuration of the first numbering sub-rule is completed. When all numbering sub-rules in the numbering rule are configured, a numbering rule corresponding to the first entity is generated. When the first entity is generated, the numbering generation instruction corresponding to the first entity is detected, and the number corresponding to the first entity can be generated based on the numbering rule corresponding to the first entity. For details, please refer to the aforementioned Figure 10 The relevant description will not be repeated here.

[0113] For example, the number generation system 10 can be applied to Figure 1 On the server side of the shopping system shown, users can configure numbering rules on the server side. If the numbering requirement is "to generate business numbers according to the four parts of character, time sequence, custom field, and digital sequence through configuration", where the custom field corresponds to the attribute of the first entity. Then, the numbering rule framework set by the system developer is character + time sequence + custom field + digital sequence, where sub-rule 1 is character, sub-rule 2 is time sequence, sub-rule 3 is custom field, and sub-rule 4 is digital sequence. In the order numbering scenario, if the first entity is an order, when configuring the order numbering rule, the user can select an attribute from the attribute list of the order displayed in the rule configuration interface. For example, the user can directly select the text "order line number" or "lineNumber", and the rule configuration unit 102 can determine sub-rule 3 as "order line number" or "lineNumber". After the configuration of each sub-rule in the numbering rule framework is completed, the order numbering rule can be generated.

[0114] When a consumer purchases an item in the client, the order generation unit in the server can obtain the consumer's order information and generate an order. When the order is generated, the order production unit can also send an order number generation instruction to the number generation unit 103. The number generation unit 103 responds to the number generation instruction and enters the number generation process. During the order number generation process, the number generation unit 103 obtains the order number rule from the rule configuration unit 102, and then obtains the attribute value corresponding to the order line number from the operation data of the order, that is, determines the number segment corresponding to sub-rule 3 in the number rule. In addition, the number generation unit 103 can also obtain the number segments corresponding to sub-rule 1, sub-rule 2 and sub-rule 4 from the operation data of the order. Finally, the number generation unit 103 can arrange the number segments corresponding to each sub-rule in the order of the sub-rules, for example, in the order of sub-rule 1, sub-rule 2, sub-rule 3 and sub-rule 4, thereby generating a complete order number.

[0115] For example, as shown in Table 4 below, if the first entity is an order, when the numbering segment corresponding to sub-rule 1 is LS (i.e., a pre-set fixed value), the numbering segment corresponding to sub-rule 2 is 20220923 (i.e., the year, month, and day when the order was generated), the numbering segment corresponding to sub-rule 3 is 003 (i.e., the order line number), and the numbering segment corresponding to sub-rule 4 is 00001 (i.e., a value generated according to the rule of increasing overall natural numbers), the generated order number can be LS-20220923-003-00001.

[0116] Table 4:

[0117] product entity Application Fields Numbering Example Sales Order Order Order number LS-20220923-003-00001

[0118] It can be understood that the number generation method provided in the embodiment of the present application can be applied to the accounts receivable document numbering scenario shown in Table 1 above, for example, it can generate invoice numbers, etc.; it can be applied to the supplier document numbering scenario shown in Table 2 above, for example, it can generate change process numbers, etc.; it can be applied to the sales order numbering scenario shown in Table 4 above, for example, it can generate order numbers, etc.; it can be applied to the inventory document numbering scenario shown in Table 5 below, and it can generate transaction order numbers.

[0119] Table 5:

[0120] product entity Application Fields Numbering Example in stock in stock Transaction number KC-20220923-BJ-00001

[0121] The numbering generation method provided in the embodiment of the present application combines the automatic numbering technology with the metadata-driven technology. When configuring the numbering rules, multiple attributes of the entity (including standard attributes and extended attributes) can be obtained from the entity metadata information, and an attribute list can be generated. The user only needs to select an attribute from the multiple attributes of the entity in the attribute list through the rule configuration interface without manual input. In this way, the accuracy of the numbering rule configuration can be improved, and the efficiency of the numbering configuration and the numbering generation efficiency can be improved. Among them, metadata-driven technology can be considered as a way of software design and implementation. By adding different types of metadata records, the definition of system interface, functions, services, and underlying data can be realized. When the software application is running, the corresponding functions can be realized by reading these metadata, such as realizing the application upgrade of the software in the running state.

[0122] An embodiment of the present application also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the above-mentioned numbering method is implemented.

[0123] An embodiment of the present application further provides an electronic device, which includes the above-mentioned numbering system.

[0124] An embodiment of the present application further provides a readable storage medium, on which instructions are stored. When the instructions are executed on an electronic device, the electronic device executes the numbering method mentioned in the present application.

[0125] It can be understood that the electronic device in the embodiment of the present application can be any electronic device such as a server that can implement the above-mentioned number generation method.

[0126] The following takes the electronic device 100 as an example to illustrate a hardware structure diagram of an electronic device according to an embodiment of the present application.

[0127] like Figure 12 As shown, the electronic device 100 includes one or more processors 201, a system memory 202, a non-volatile memory (NVM) 203, a communication interface 204, an input / output (I / O) device 205, and a system control logic 206 for coupling the processor 201, the system memory 202, the non-volatile memory 203, the communication interface 204, and the input / output (I / O) device 205. Among them:

[0128] The processor 201 may include one or more processing units, such as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a micro-programmed control unit (MCU), an AI (artificial intelligence) processor or a programmable logic device (FPGA) or a neural network processing unit (NPU). The data processing unit or processing circuit may include one or more single-core or multi-core processors. In some embodiments, the processor 201 may be used to execute instructions to implement the relevant functions of the metadata information management unit 101, the rule configuration unit 102, and the number generation unit 103.

[0129] System memory 202 is a volatile memory, such as random-access memory (RAM) or double data rate synchronous dynamic random access memory (DDR SDRAM). System memory is used to temporarily store data and / or instructions. For example, in some embodiments, system memory 202 can be used to store metadata information or numbering rules.

[0130] The non-volatile memory 203 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. In some embodiments, the non-volatile memory 203 may include any suitable non-volatile memory such as flash memory and / or any suitable non-volatile storage device, such as a hard disk drive (HDD), a compact disc (CD), a digital versatile disc (DVD), a solid-state drive (SSD), etc. In some embodiments, the non-volatile memory 203 may also be a removable storage medium, such as a secure digital (SD) memory card. In other embodiments, the non-volatile memory 203 may be used to store metadata information or to store numbering rules.

[0131] In particular, the system memory 202 and the non-volatile memory 203 may respectively include a temporary copy and a permanent copy of the instruction 207. The instruction 207 may include: when executed by at least one of the processors 201, enabling the electronic device 100 to implement the number generation method provided in various embodiments of the present application.

[0132] The communication interface 204 may include a transceiver for providing a wired or wireless communication interface for the electronic device 100, thereby communicating with any other suitable device through one or more networks. In some embodiments, the communication interface 204 may be integrated into other components of the electronic device 100, for example, the communication interface 204 may be integrated into the processor 201.

[0133] The input / output (I / O) device 205 may include input devices such as a keyboard, a mouse, etc., and output devices such as a display, etc. Users can interact with the electronic device 100 through the input / output (I / O) device 205. For example, business personnel can select the attributes of an entity through the input / output (I / O) device 205.

[0134] System control logic 206 may include any suitable interface controller to provide any suitable interface with other modules of electronic device 100. For example, in some embodiments, system control logic 206 may include one or more memory controllers to provide interfaces to system memory 202 and non-volatile memory 203.

[0135] In some embodiments, at least one of the processors 201 may be packaged together with the logic of one or more controllers for the system control logic 206 to form a system in package (SiP). In other embodiments, at least one of the processors 201 may be integrated with the logic of one or more controllers for the system control logic 206 on the same chip to form a system-on-chip (SoC).

[0136] I understand. Figure 12 The structure of the electronic device 100 shown is only an example. In other embodiments, the electronic device 100 may include more or fewer components than shown, or may combine or separate some components, or arrange the components differently. The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0137] The various embodiments disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0138] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor, a microcontroller, an application processor, or a microprocessor.

[0139] Program code can be implemented with a high-level programming language or an object-oriented programming language to communicate with the processing system. Where necessary, program code can also be implemented in assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0140] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable storage media (e.g., computer-readable storage media), which may be read and executed by one or more processors. For example, instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to a floppy disk, an optical disk, an optical disc, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), a magnetic card or an optical card, or a tangible machine-readable memory for transmitting information (e.g., a carrier wave, an infrared signal, a digital signal, etc.) using the Internet in an electrical, optical, acoustic, or other form of propagation signal. Therefore, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0141] In the accompanying drawings, some structural or method features may be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or order may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of a structural or method feature in a particular figure does not imply that such a feature is required in all embodiments, and in some embodiments, such features may not be included or may be combined with other features.

[0142] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems raised by this application. In addition, in order to highlight the innovative part of this application, the above-mentioned device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems raised by this application. This does not mean that other units / modules do not exist in the above-mentioned device embodiments.

[0143] It should be noted that, in the examples and description of the present application, relational terms such as first and second, etc. are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further qualifications, an element defined by the statement "comprises a" does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0144] While the present application has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the present application.

Claims

1. A number generation method, characterized in that: include: Display the numbering rule generation interface; In response to a first operation by the user, displaying an attribute list of a first entity, the attribute list including a plurality of attributes of the first entity; In response to a user selecting a first attribute among the plurality of attributes, a numbering rule is generated based on the first attribute.

2. The numbering method according to claim 1, wherein: The displaying of the attribute list of the first entity in response to the first operation of the user includes: In response to a first operation by the user, metadata information of the first entity is acquired, where the metadata information of the first entity includes attribute information of a plurality of attributes of the first entity, and the attribute information of the plurality of attributes of the first entity includes attribute names of the plurality of attributes of the first entity; Based on the attribute names of the plurality of attributes of the first entity, the attribute list is generated and displayed.

3. The numbering method according to claim 1, wherein: In response to a user selecting a first attribute from the plurality of attributes, generating a numbering rule based on the first attribute includes: In response to a user selecting a first attribute among the multiple attributes, a first numbering sub-rule is generated based on the first attribute, and the numbering rule is generated based on the first numbering sub-rule.

4. The numbering method according to claim 3, wherein: Also includes: A number generation instruction corresponding to the first entity is detected, and a number corresponding to the first entity is generated based on the numbering rule.

5. The numbering method according to claim 4, wherein: The numbering rule also includes a second numbering sub-rule; The detecting a number generation instruction corresponding to the first entity and generating a number corresponding to the first entity based on the numbering rule includes: detecting a numbering generation instruction corresponding to the first entity, and acquiring the numbering rule and operation data of the first entity, wherein the operation data includes data generated during the generation of the first entity; Acquire a data value corresponding to the first attribute and a data value corresponding to the second numbering sub-rule from the operating data; Determine the data value corresponding to the first attribute as a first numbering segment, and determine the data value corresponding to the second numbering sub-rule as a second numbering segment; A number corresponding to the first entity is determined according to the first numbering segment and the second numbering segment.

6. A numbering system, characterized in that: It includes a metadata information management unit and a rule configuration unit, wherein: The metadata information management unit is configured to store metadata information of a first entity, where the metadata information of the first entity includes attribute information of a plurality of attributes of the first entity; The rule configuration unit is used to display a numbering rule generation interface, and in response to a first operation of the user, display an attribute list of the first entity, the attribute list including multiple attributes of the first entity, and, In response to a user selecting a first attribute among the plurality of attributes, a numbering rule is generated based on the first attribute.

7. The numbering system according to claim 6, wherein: Also includes a number generation unit, The number generation unit detects a number generation instruction corresponding to the first entity, obtains the numbering rule, and generates a number corresponding to the first entity based on the numbering rule.

8. An electronic device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the numbering method according to any one of claims 1 to 5 when executing the computer program.

9. An electronic device, characterized in that: The invention comprises the numbering system as claimed in claim 6 or 7.

10. A readable storage medium, characterized in that: The readable storage medium stores instructions, which, when executed on an electronic device, enable the electronic device to execute the numbering method according to any one of claims 1 to 5.

Images