Business process attribute configuration method and device, electronic equipment and storage medium

Abstract

The application provides a business process attribute configuration method, device, equipment, medium and product, including: in response to a first selection operation on any target attribute directory of a business process on a first configuration page, displaying a plurality of attribute labels under the target attribute directory on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process; in response to a second selection operation on any target attribute label in the plurality of attribute labels, displaying a second configuration page, wherein the second configuration page displays a plurality of attribute fields under the target attribute label; in response to a configuration operation on the plurality of attribute fields on the second configuration page, obtaining field configuration data; and generating process attribute information of the business process according to the field configuration data. The application can improve the configuration efficiency of the business process attribute and reduce the cost.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, electronic device, storage medium, and program product for configuring business process attributes. Background Technology

[0002] In the corporate lending business processes of banks and other financial institutions, there are business label attributes in core stages such as business approval and contract disbursement. These business label attributes are characterized by multiple stages, multiple granularities, and multiple types, and they need to respond to regulatory requirements in a timely manner.

[0003] Existing technologies typically configure business tag attributes directly in the code. This not only places higher demands on the technical skills of operators, but also inevitably requires a series of operations by technical personnel to take effect in actual business operations since the rules are configured at the code level. Therefore, it cannot meet the need for timely response to business processes. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, storage medium, and program product for configuring business process attributes, in order to solve the problems of low efficiency and high cost in configuring business process attributes in the prior art.

[0005] Firstly, this application provides a method for configuring business process attributes, including:

[0006] In response to a first selection operation on any target attribute directory of a business process on a first configuration page, multiple attribute tags under the target attribute directory are displayed on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process.

[0007] In response to a second selection operation on any target attribute tag among the plurality of attribute tags, a second configuration page is displayed, wherein the second configuration page displays a plurality of attribute fields under the target attribute tag;

[0008] In response to configuration operations on the plurality of attribute fields on the second configuration page, obtain field configuration data;

[0009] The process attribute information of the business process is generated based on the data configured in the fields.

[0010] Secondly, this application provides a configuration device for business process attributes, comprising:

[0011] The attribute label display module is used to display multiple attribute labels under the target attribute directory on the first configuration page in response to a first selection operation of any target attribute directory of the business process on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process.

[0012] The attribute field display module is used to display a second configuration page in response to a second selection operation on any target attribute tag among the plurality of attribute tags, wherein the second configuration page displays a plurality of attribute fields under the target attribute tag;

[0013] The field configuration data acquisition module is used to acquire field configuration data in response to configuration operations on the multiple attribute fields on the second configuration page;

[0014] The process attribute information generation module is used to generate process attribute information of the business process based on the field configuration data.

[0015] Thirdly, embodiments of this application also provide an electronic device, including a processor and a memory communicatively connected to the processor;

[0016] The memory stores computer-executed instructions;

[0017] The processor executes computer execution instructions stored in the memory to implement some or all of the steps in the method for configuring business process attributes as disclosed in the first aspect of the present application.

[0018] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement some or all of the steps in the configuration method for business process attributes as disclosed in the first aspect of this application.

[0019] Fifthly, embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements some or all of the steps in the configuration method for business process attributes as disclosed in the first aspect of this application.

[0020] The business process attribute configuration method, apparatus, device, medium, and product provided in this application, in response to a first selection operation on a first configuration page for any target attribute directory of the business process, displays multiple attribute tags under the target attribute directory on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process; in response to a second selection operation on any target attribute tag among the multiple attribute tags, displays a second configuration page, wherein the second configuration page displays multiple attribute fields under the target attribute tag; in response to a configuration operation on the multiple attribute fields on the second configuration page, obtains field configuration data; and generates process attribute information of the business process based on the field configuration data. This application modifies the entry point to achieve visual and adaptive page configuration. In most business scenarios, no code changes are required; instead, the configuration page expands hierarchically, supporting configuration at three granularities: attribute directory, attribute tag, and attribute field. It generates tag attribute information for the corresponding business scenario process, requiring low operator skill, featuring a user-friendly interface, and allowing real-time application of tag attribute configuration. Attached Figure Description

[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0022] Figure 1 A flowchart illustrating the method for configuring business process attributes provided in this application embodiment;

[0023] Figure 2 A flowchart illustrating yet another method for configuring business process attributes provided in an embodiment of this application;

[0024] Figure 3a This is a rendering of a first configuration page shown in an embodiment of this application;

[0025] Figure 3b This is a rendering of another first configuration page shown in an embodiment of this application;

[0026] Figure 4a This is a rendering of a second configuration page shown in an embodiment of this application;

[0027] Figure 4b This is a rendering of another second configuration page shown in an embodiment of this application;

[0028] Figure 5 A schematic diagram of the structure of the configuration device for business process attributes provided in the embodiments of this application;

[0029] Figure 6This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0030] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0031] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present application, not the entire structure.

[0032] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first" and "second" are used only to distinguish descriptions and should not be construed as indicating or implying relative importance. The acquisition, storage, use, and processing of data in the technical solution of this application all comply with the relevant provisions of national laws and regulations.

[0033] Figure 1 This is a flowchart illustrating a method for configuring business process attributes according to an embodiment of this application. This embodiment is applicable to situations requiring visual configuration of business process attributes. The method can be executed by a business process attribute configuration device, which can be implemented in software and / or hardware, preferably configured in an electronic device, such as a computer or server. Figure 1 As shown in the embodiments of this application, the method for configuring business process attributes specifically includes:

[0034] Step 101: In response to the first selection operation of any target attribute directory of the business process on the first configuration page, display multiple attribute labels under the target attribute directory on the first configuration page.

[0035] Specifically, the first configuration page is a visual page that can be displayed on an electronic terminal device with a display screen, such as a computer, tablet, or mobile phone. This electronic terminal device has communication capabilities and is connected to a server or server cluster via a network. This network can include various types, such as wired and / or wireless communication links, etc.

[0036] The electronic terminal device sends or receives messages with a server or server cluster via a network. The server or server cluster can provide various services, such as providing backend support for users through the electronic terminal device. The server or server cluster can receive user requests, parse the requests, and return processing results to the electronic terminal device, such as web pages or data generated based on user requests.

[0037] Optionally, the method for configuring business process attributes provided in this application embodiment can be executed by the server or server cluster, and correspondingly, the device for configuring business process attributes provided in this application embodiment is also configured in the server or server cluster. Alternatively, the method for configuring business process attributes provided in this application embodiment can be executed by the electronic terminal device, and correspondingly, the device for configuring business process attributes provided in this application embodiment is also configured in the electronic terminal device.

[0038] Specifically, a user sends a configuration request for a certain business process attribute. The server or server cluster, or the electronic terminal device, executes the business process attribute configuration method provided in this application embodiment and returns processing data. This processing data is used to generate a configuration page for the business process, such as a first configuration page and a second configuration page. It should be understood that, depending on actual needs, there can be any number of electronic terminal devices, servers or server clusters, and networks.

[0039] In this embodiment of the application, the first configuration page displays at least one attribute directory of the business process. The business process is designed to meet specific business scenarios and consists of a series of business nodes. The attribute directory is used to display the series of business nodes. Furthermore, any business node supports calling sub-business nodes, and the sub-business nodes are displayed through the sub-attribute directory.

[0040] Typically, the business process described in this application embodiment is a corporate credit business process. In this application embodiment, the business process may include one or more business nodes, the business nodes form an attribute directory, each business node has one or more sub-business nodes, the one or more sub-business nodes may be attribute tags used to describe the business node, and the one or more of these business nodes form a target attribute directory.

[0041] For example, the first selection operation may be that the user selects any business node in the attribute directory on the first configuration page. In response to the user's selection operation, the first configuration page displays the target attribute directory corresponding to the business node, and the target attribute directory includes one or more target attribute tags of the business node.

[0042] Step 102: In response to a second selection operation on any target attribute tag among the plurality of attribute tags, display the second configuration page.

[0043] In this embodiment of the application, the target attribute tags are preferably multiple. For example, the second selection operation may be that the user selects any attribute tag from the target attribute directory on the first configuration page, and this arbitrary attribute tag serves as the target attribute tag for the user's operation. In response to the user's selection operation, the second configuration page is displayed.

[0044] The second configuration page displays multiple attribute fields under the target attribute tag, and these attribute fields are used to configure the attribute tag. It is understood that there can be only one attribute field under the target attribute tag, and different target attribute tags can have the same attribute field.

[0045] Optionally, in this embodiment, the first configuration page and the second configuration page can represent different areas of the same page or different pages. The attribute tags in the target attribute directory of the first configuration page can be set as visual hyperlinks. When a user selects an attribute tag and clicks it, they can enter the second configuration page corresponding to the selected attribute tag from the first configuration page. Alternatively, when a user selects an attribute tag and performs other operations, such as long-pressing, swiping left, or swiping right, they can perform preset configuration operations on the attribute tag, such as deleting or viewing editing history. Each attribute tag in the directory attribute directory of the first configuration page can also have a corresponding operation control, such as edit. When a user clicks the operation control, they can enter the second configuration page corresponding to the selected attribute tag from the first configuration page. Alternatively, the operation control can also include history and delete. When a user clicks the corresponding operation control, they can perform the configuration operation of viewing editing history or deleting the attribute tag. For example, when performing a delete operation, the user directly clicks the delete control and calls the template / delete interface to complete the deletion.

[0046] Step 103: In response to configuration operations on multiple attribute fields on the second configuration page, obtain the field configuration data.

[0047] Optionally, in this embodiment of the application, the attribute fields under the target attribute tag are typically multiple, and each attribute field can be configured individually. For example, the configuration operation may include basic information of the attribute field, whether it is required, and whether to enable prompts, etc.

[0048] The configuration operations for basic information of attribute fields can include formatting text, tables, graphics, etc. on the page, configuring one of the following: font, font size, orientation, margins, width, etc.; or setting the attribute information of input boxes, configuring one of the following: font, font size, color, input data type, data filtering length, etc. For example, the input numeric data can be configured to retain two decimal places. The configuration operation for whether an attribute field is mandatory can be configured to allow the user to submit or fill in the next attribute field. The configuration operation for enabling suggestions for attribute fields can be configured to allow users to input suggestions for that attribute field. When suggestions are enabled, the input box of the attribute field can display characters suggesting what data the user should enter or other characters assisting the user in inputting the data.

[0049] For example, configuration data can be predefined for each attribute field. This configuration data has multiple selectable controls, such as whether input is allowed and whether hints are enabled. Users can select the target selectable from these controls for configuration. Optionally, the configuration data also has input boxes that allow users to supplement their input, such as a hint box for entering informational messages or an input box for modifying the logical rules of the entire configuration data. For example, when a user edits the logical rules and enters `this.pvtAlvetLnTypeCode == 1`, it indicates that the user's input in that field is hidden.

[0050] In this embodiment, the configuration operations for attribute fields described above can be configured through a preset attribute information interface, and the corresponding field configuration data can be obtained. For example, the fields and their corresponding configuration rules can be saved through the create interface, stored in a database, and the keyCode string can be used as a unique query identifier.

[0051] Step 104: Generate the process attribute information of the business process based on the field configuration data.

[0052] In this embodiment of the application, field configuration data is determined on the second configuration page by selecting controls or defining logical rules. Based on the preset backend service and combined with the field configuration data, process attribute information of the business process is generated.

[0053] The technical solution of this application, in response to a first selection operation on a first configuration page for any target attribute directory of a business process, displays multiple attribute tags under the target attribute directory on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process; in response to a second selection operation on any target attribute tag among the multiple attribute tags, a second configuration page is displayed, wherein the second configuration page displays multiple attribute fields under the target attribute tag; in response to a configuration operation on the multiple attribute fields on the second configuration page, field configuration data is obtained; and process attribute information of the business process is generated based on the field configuration data. This solution, by implementing multi-stage, multi-granularity, and multi-type business attribute tag configuration, allows relevant personnel to adjust the display of business attribute tags in a timely and flexible manner according to rules on a visual page through a user-friendly and simple interactive method. In most scenarios, adjustments take effect in real time, improving efficiency.

[0054] Figure 2 This is a flowchart illustrating another method for configuring business process attributes provided in this application embodiment. This embodiment further optimizes the above embodiments. For example... Figure 2 As shown in the embodiments of this application, the method for configuring business process attributes specifically includes:

[0055] Step 201: In response to the first selection operation of any target attribute directory of the business process on the first configuration page, display multiple attribute labels under the target attribute directory on the first configuration page.

[0056] The first configuration page displays at least one attribute directory for a business process. For example, the business process can be the business process of a financial product. Each financial product has corresponding characteristics, scenarios, and regulatory requirements. When a financial product is selected, the attribute directory of that product's business process is accessed. The business process has at least one stage of business nodes, such as credit granting, public, business, contract, and disbursement. When a business node is selected, the target attribute directory of that business node is accessed. Preferably, in this embodiment, the target attribute directory has multiple attribute tags.

[0057] Figure 3a This is a rendering of a first configuration page shown in an embodiment of this application. See also: Figure 3aIn the business process, the first configuration page has different regions for the rule framework of business attribute tags. In this embodiment, regions 311 and 321 are preferred. Region 311 displays the attribute directory of the business process, including various business nodes such as business, contract, and expenditure. Region 321 displays the target attribute, including attribute tags for each business node, such as attribute tag - policy type, attribute tag - agriculture, and attribute tag - poverty alleviation. Specifically, a specific attribute tag under the target attribute directory can be displayed as follows: ID, name, KeyCode, serial number, status, creation time, update time, creator, remarks, and updater. For example... Figure 3a The attribute tag - policy type shown is: 1494130561769082880, attribute tag - policy type, PolicyType-prjPlcyTp, 1, normal, 2022-02-17 10:04:20, 2022-09-19 09:10:20, lixiaowen.cn, test, xuzengwei.zh.

[0058] Specifically, in this embodiment, attribute tags under the selected attribute directory are obtained by switching the attribute directory entries in region 311. Technically, the directory ID can be used as the main input parameter, and the input parameter type can be set to indicate that the current query is for a business attribute tag type. The interface template / getPageList is then called to return all attribute tags under the target attribute directory.

[0059] It should be noted that the above figures and examples are only illustrative and do not represent the actual situation. Users can decide how to display attribute labels and corresponding data formats and data types according to their own needs.

[0060] Step 202: In response to a second selection operation on any target attribute tag among multiple attribute tags, display the second configuration page.

[0061] Preferably, in this embodiment, the second configuration page displays multiple attribute fields under the target attribute tag. The first configuration page also displays operation controls for the attribute tag, wherein the operation controls include edit, history, and delete; the second selection operation is triggered by the edit operation control.

[0062] For details, see Figure 3b , Figure 3bThis is a rendering of another first configuration page shown in the embodiments of this application, including area 312 and area 322. Each attribute label in area 322 has a corresponding operation control, which can be clicked to modify the attribute label, view the editing history, or delete the attribute label.

[0063] Preferably, in this embodiment, the second configuration page also displays an attribute field search control. The second configuration page also displays operation controls for the attribute fields, including clear, copy, and delete functions; users can operate on the attribute fields using these controls.

[0064] See Figure 4a , Figure 4a This is a rendering of a second configuration page according to an embodiment of this application. The second configuration page has different areas. Figure 4a Regions 411 and 421 are shown. Region 411 includes a display control for displaying predefined attribute fields for user viewing and selection. Region 411 also includes an attribute field search control for precise searching of predefined attribute fields. Region 421 includes a display control for displaying all attribute fields added to attribute labels. Optionally, each attribute field includes an operation control, including clear, copy, and delete functions. Users can click the control to clear all fields, copy the attribute field corresponding to the operation control, or delete the attribute field corresponding to the operation control.

[0065] Optionally, the area 421 can also display the attribute label being edited on the second configuration page, such as the poverty alleviation label. Accordingly, by clicking the corresponding control, one can clear, copy, or delete all attribute fields under the attribute label, or clear, copy, or delete the attribute label itself.

[0066] Step 203: In response to the input of search terms in the attribute field search control, display a list of candidate attribute fields corresponding to the search terms on the second configuration page; the candidate attribute fields are searched in a predefined attribute field component library.

[0067] Step 204: In response to the third selection operation on any target attribute field in the candidate attribute field list, add the target attribute field to the target attribute label.

[0068] The predefined attribute field component library consists of predefined attribute fields with pre-defined rules and configurations, which can be added and used directly.

[0069] For example, see Figure 4aArea 411 includes a display control. By default, this display control shows frequently used attribute fields. Optionally, the display control can be set to display newly created attribute fields. Users can enter search terms in the input box of the attribute field search control in area 411. The display control in area 411 will display a list of candidate attribute fields corresponding to the search terms in real time, including the target attribute field that the user wants to add to the attribute label. When the user selects a target attribute field, the target attribute field can be displayed in area 421.

[0070] Optionally, the first configuration page also displays controls for adding new attribute tags. In response to a fourth selection action on these controls, the second configuration page is displayed. For example, the above steps can be used to add a target attribute field to a new attribute tag. Specifically, the user can use the `baseField / getPageList` interface to query the attribute fields currently in the field library, returning a list of candidate attribute fields for selection.

[0071] Step 205: In response to configuration operations on multiple attribute fields on the second configuration page, obtain the field configuration data.

[0072] In this embodiment of the application, the configuration operation includes configuring at least one of the following basic items: basic information of the attribute field, whether it is displayed, whether it is editable, whether it is required, whether prompts are enabled, and validation rules.

[0073] Optionally, the second configuration page also displays property field configuration controls, which are used to configure multiple property fields simultaneously.

[0074] For details, see Figure 4a The second configuration page also includes an attribute field configuration control, located in area 411. When the user clicks the "Attribute Field Configuration Control," the display control in area 411 will show the corresponding configurable basic items, allowing configuration of common attributes for multiple attribute fields, such as mode (text, table), alignment (left, center, right), etc. Optionally, the display control in area 411 will also display an input box to accept user input parameter codes or modify existing parameter codes, configuring whether the multiple attribute fields are displayed, editable, or required. For example, this could be configured based on rules based on the data sensitivity of the input content.

[0075] Optionally, a specific attribute field can also be configured individually.

[0076] For details, see Figure 4b , Figure 4bThis is an illustration of another second configuration page as shown in an embodiment of this application, including areas 412, 422, and 432. When a user selects an attribute field in area 422, the second configuration page displays area 432. Area 432 has operation controls and display controls for configuring the attribute field selected by the user. The operation controls include basic and logical components. Configurable basic items are categorized into "basic" and "logical" categories based on predefined classification criteria. When the user clicks on the "basic" or "logical" operation control, the display control in area 432 displays the corresponding configurable basic item.

[0077] The configuration operations of the basic controls can include basic information, validation rules, etc. The basic information includes field name, field input box width, field input box height, alignment, sorting, field input method (such as direct input, drop-down selection, etc.), etc. The validation rules include at least one of landline, mobile phone, postal code, fax and email.

[0078] Configuration operations for logical controls can include whether to display, whether to make them editable, whether they are required, and whether to enable suggestions. For example, a selection control can be provided for the above configuration operations, allowing direct control to choose whether to display, whether to make them editable, whether they are required, and whether to enable suggestions. Optionally, configuration operations for logical controls can also include customizing the suggestion content; alternatively, configuration operations for logical controls can also include customizing the filtering type of the input content, for example, configuring the input numeric data to retain two decimal places.

[0079] Optionally, the configuration operation also includes logical configuration operations for the display conditions of the configuration data of the basic items. The display control in area 432 can provide an input box to accept user input parameter codes or modify existing parameter codes to configure the operable basic items under the logical control. Optionally, the configuration operation also includes logical configuration operations for the editing conditions, required conditions, and prompt conditions of the configuration data of the basic items.

[0080] Optionally, the second configuration page also displays information on the differences between the current field configuration data and the historical field configuration data for several attribute fields.

[0081] For details, see Figure 4bThe second configuration page also includes a differentiation control located in area 432. When the user clicks the "Differentiation" control, area 432 displays the differences between the current and historical configuration data of multiple attribute fields under the attribute label. Alternatively, when the user clicks the "Differentiation" control, area 432 displays the differences between the current configuration operation and the previous configuration operation in that attribute field. By displaying the differentiation information, errors that may occur due to the current configuration operation can be promptly identified and corrected.

[0082] Optionally, the second configuration page also displays operation controls for adding attribute fields. Users can create new attribute fields through the above configuration operations and save them to the attribute field component. For example, customized components with various business backgrounds can be pre-built, such as selecting customer contracts or credit contracts. These customized components include predefined configuration templates. When creating a new attribute field, users can choose from various styles of customized components for different business backgrounds. By simply modifying the configuration template, new attribute fields can be created quickly.

[0083] Specifically, for adding, modifying, or adding attribute fields under attribute tags, the update response can be used. When saving, the modified parts are defined as attribute rules in diffAttr and saved as parameters in JSON string format. The parameters can be modified to respond promptly to changes in requirements initiated by regulatory systems and other entities.

[0084] Step 206: Generate the process attribute information of the business process based on the field configuration data.

[0085] Based on the process attribute information, the display page of the business process is previewed. Specifically, the second configuration page also includes a preview control used to render and preview the process attribute information.

[0086] Optionally, the second configuration page also displays attribute field rule validation controls; see [link / reference]. Figure 4a The attribute field rule validation control belongs to region 411.

[0087] Accordingly, before generating the process attribute information of the business process based on the field configuration data, the method further includes:

[0088] The rule validation information is obtained through the attribute field rule validation control, wherein the rule validation information includes rules for validating the linkage relationship between field configuration data of any attribute fields;

[0089] The linkage relationship between field configuration data of any attribute fields is validated based on the rule validation information.

[0090] For example, when a user clicks the "Attribute Field Rule Validation Control" operation control, the display control in area 411 will also display an input box. This input box accepts user input parameter codes when editing attribute fields within the current attribute label, or modifies existing parameter codes. Based on judgment conditions such as business nature and application nature, it defines rules for the linkage relationship of field configuration data between any attribute fields within the current attribute label. For example, it checks whether there is a conflict between any two attribute fields, or whether there is a conflict between the input content of one attribute field and another attribute field when the input content of one attribute field is certain values ​​or characters.

[0091] The configuration method for business process attributes in this application is built around the rule system of business processes, reflecting strong and distinct business characteristics. It can introduce solution elements such as business nature, application nature, and available products into the business scenarios of the business process, and define and configure business attribute tags in multiple dimensions. It can meet the requirement of real-time configuration effectiveness in most scenarios, and has a simple and intuitive business attribute tag configuration page. It better overcomes the limitations of existing solutions, and to a certain extent lowers the threshold for operators' technical level and business understanding, supporting simple and intuitive rule configuration.

[0092] Figure 5 This is a schematic diagram of the structure of a configuration device for business process attributes provided in an embodiment of this application. Figure 5 As shown, the device includes:

[0093] The attribute label display module 501 is used to display multiple attribute labels under the target attribute directory on the first configuration page in response to a first selection operation of any target attribute directory of the business process on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process.

[0094] The attribute field display module 502 is used to display a second configuration page in response to a second selection operation on any target attribute tag among the plurality of attribute tags, wherein the second configuration page displays a plurality of attribute fields under the target attribute tag;

[0095] The field configuration data acquisition module 503 is used to acquire field configuration data in response to configuration operations on the multiple attribute fields on the second configuration page;

[0096] The process attribute information generation module 504 is used to generate process attribute information of the business process based on the field configuration data.

[0097] This solution enables multi-stage, multi-granularity, and multi-type configuration of business attribute tags, allowing relevant personnel to adjust the display of business attribute tags and related interaction rules in a timely and flexible manner on a visual page through a user-friendly and simple interactive method. In most scenarios, the adjustments can take effect in real time.

[0098] As an optional implementation, the first configuration page also displays operation controls for the attribute tags, wherein the operation controls include edit, history, and delete; the second selection operation is triggered by the edit operation control.

[0099] As an optional implementation, the second configuration page also displays an attribute field search control; correspondingly, the device further includes:

[0100] The attribute field adding module is used to display a list of candidate attribute fields corresponding to the search term on the second configuration page in response to the input operation of the search term in the attribute field search control; and to add the target attribute field to the target attribute tag in response to the third selection operation of any target attribute field in the list of candidate attribute fields.

[0101] As an optional implementation, the second configuration page also displays an attribute field rule validation control, and the device further includes:

[0102] The attribute field rule validation module is used to obtain rule validation information through the attribute field rule validation control, wherein the rule validation information includes rules for validating the linkage relationship of field configuration data between any attribute fields; and to validate the linkage relationship of field configuration data between any attribute fields according to the rule validation information.

[0103] As an optional implementation, the second configuration page also displays an attribute field configuration control for configuring the multiple attribute fields simultaneously.

[0104] As an optional implementation, the configuration operation includes configuring at least one of the following basic items: basic information of the attribute field, whether it is displayed, whether it is editable, whether it is required, whether prompts are enabled, and verification rules; wherein, the verification rules include at least one of landline, mobile phone, postal code, fax, and email.

[0105] As an optional implementation, the second configuration page also displays information showing the differences between the current field configuration data and the historical field configuration data of the plurality of attribute fields.

[0106] As an optional implementation, the candidate attribute fields are retrieved from a predefined attribute field component library.

[0107] As an optional implementation, the device further includes a display page preview module, used to preview the display page of the business process based on the process attribute information.

[0108] As an optional implementation, in the second aspect of this invention, the business process is a corporate lending business process.

[0109] The configuration device for business process attributes provided in this application embodiment can be used to execute the technical solution of the configuration method for business process attributes in the above embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0110] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. These modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. Furthermore, they can be stored as program code in the memory of the above device, and called and executed by one of the processing elements. Moreover, these modules can be fully or partially integrated together, or implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through the integrated logic circuits in the hardware of the processor element or through software instructions. The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0111] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device may include: a transceiver 601, a processor 602, and a memory 603.

[0112] The processor 602 executes computer execution instructions stored in the memory, causing the processor 602 to perform the scheme in the above embodiments. The processor 602 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0113] The memory 603 is connected to the processor 602 via the system bus and completes communication between them. The memory 603 is used to store computer program instructions.

[0114] Transceiver 601 can be used to acquire the task to be run and its configuration information. The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.

[0115] System buses can be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is used to represent them in the figure, but this does not mean that there is only one bus or one type of bus. Transceivers are used to enable communication between database access devices and other computers (e.g., clients, read-write libraries, and read-only libraries). Memory may include random access memory (RAM) and may also include non-volatile memory. The electronic device provided in this application embodiment can be the terminal device of the above embodiments.

[0116] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer performs the technical solution of the configuration method for business process attributes described in the above embodiments.

[0117] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the configuration method for business process attributes in the above embodiments. In the implementation of the computer program product, computer program code for executing the operations of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer through any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0118] Note that the above description is merely a preferred embodiment and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments. Many other equivalent embodiments may be included without departing from the concept of this application, and the scope of this application is determined by the scope of the appended claims.

Claims

1. A method for configuring business process attributes, characterized in that, include: In response to a first selection operation on any target attribute directory of a business process on a first configuration page, multiple attribute tags under the target attribute directory are displayed on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process. In response to a second selection operation on any target attribute tag among the plurality of attribute tags, a second configuration page is displayed, wherein the second configuration page displays a plurality of attribute fields under the target attribute tag; In response to configuration operations on the plurality of attribute fields on the second configuration page, obtain field configuration data; The process attribute information of the business process is generated based on the field configuration data, wherein the business process is a corporate credit business process; The second configuration page also displays an attribute field rule validation control; correspondingly, before generating the process attribute information of the business process based on the field configuration data, the method further includes: The rule validation information is obtained through the attribute field rule validation control, wherein the rule validation information includes rules for validating the linkage relationship between field configuration data of any attribute fields; The linkage relationship of the field configuration data between any attribute fields is verified according to the rule verification information. The second configuration page also includes a differentiation control, and displays information on the differences between the current and historical field configuration data of the multiple attribute fields, as well as the differences between the current configuration operation and the previous configuration operation in the attribute fields.

2. The method according to claim 1, characterized in that, The first configuration page also displays operation controls for the attribute tags, including edit, history, and delete; the second selection operation is triggered by the edit operation control.

3. The method according to claim 1, characterized in that, The second configuration page also displays an attribute field search control; correspondingly, the method further includes: In response to the input of a search term into the attribute field search control, a list of candidate attribute fields corresponding to the search term is displayed on the second configuration page; In response to a third selection operation on any target attribute field in the candidate attribute field list, the target attribute field is added to the target attribute tag.

4. The method according to claim 1, characterized in that, The second configuration page also displays attribute field configuration controls, which are used to configure the multiple attribute fields simultaneously.

5. The method according to claim 1, characterized in that, The configuration operation includes configuring at least one of the following basic items: basic information of the attribute field, whether it is displayed, whether it is editable, whether it is required, whether prompts are enabled, and verification rules; wherein, the verification rules include at least one of landline, mobile phone, postal code, fax, and email.

6. The method according to claim 5, characterized in that, The configuration operation also includes logical configuration operations for the display conditions of the configuration data of the basic item.

7. The method according to claim 3, characterized in that, The candidate attribute fields are retrieved from a predefined attribute field component library.

8. The method according to claim 1, characterized in that, Also includes: Based on the process attribute information, a preview of the business process display page is generated.

9. A configuration device for business process attributes, characterized in that, include: The attribute label display module is used to display multiple attribute labels under the target attribute directory on the first configuration page in response to a first selection operation on any target attribute directory of the business process on the first configuration page, wherein the first configuration page displays at least one attribute directory of the business process. The attribute field display module is used to display a second configuration page in response to a second selection operation on any target attribute tag among the plurality of attribute tags, wherein the second configuration page displays a plurality of attribute fields under the target attribute tag; The field configuration data acquisition module is used to acquire field configuration data in response to configuration operations on the multiple attribute fields on the second configuration page; The process attribute information generation module is used to generate process attribute information of the business process based on the field configuration data, wherein the business process is a corporate credit business process; The second configuration page also displays an attribute field rule validation control; the device further includes: The attribute field rule validation module is used to obtain rule validation information through the attribute field rule validation control, wherein the rule validation information includes rules for validating the linkage relationship of field configuration data between any attribute fields; and to validate the linkage relationship of field configuration data between any attribute fields according to the rule validation information. The second configuration page also includes a distinction control. The second configuration page also displays the difference information between the current field configuration data and the historical field configuration data of the multiple attribute fields, as well as the difference between the current configuration operation and the previous configuration operation in the attribute fields.

10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the configuration method for business process attributes as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the configuration method for business process attributes as described in any one of claims 1-8.

12. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the configuration method for the business process attributes of any one of claims 1-8.

Images