A workflow generation method, device and medium

Abstract

The application discloses a workflow generation method and device and a medium. The method comprises the following steps: receiving an extension request of a workflow in a specified business scenario type, obtaining attribute information of an extension attribute and associated process information; filling the field content of the extension attribute field according to the attribute information; if the associated process information is not empty, associating the extension attribute with the specified business type and / or associating the extension attribute with the specified workflow type according to the associated process information; obtaining the workflow framework of multiple workflow types in the specified business scenario type, determining the workflow framework associated with the extension attribute, fusing the extension attribute and the general attribute of the associated workflow framework to obtain an extended workflow framework; and configuring the attribute content of the extension attribute and the general attribute in the extended workflow framework in a workflow designer to generate the workflow of the specified business scenario type. The flexibility of the workflow generation is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a workflow generation method, device and medium. Background Technology

[0002] In enterprise ERP systems, workflows emerged primarily to optimize and automate internal business processes. As businesses grow and their operations become more complex, traditional manual processes often become inefficient, error-prone, and difficult to track and monitor. Therefore, introducing the concept of workflow management allows for the standardized and regulated design and execution of various internal business processes. Workflows can encompass everything from routine operations such as leave requests, purchasing, approvals, and expense reimbursements to more complex core business processes like sales order processing and production scheduling.

[0003] Currently, workflow designers provide basic attribute configuration items to meet the design needs of common scenarios. However, basic attributes cannot meet the needs of every business scenario type. Adapting to actual business scenarios will bring many drawbacks: First, if the standard product (the pre-set workflow) is modified according to specific business needs, it will not only delay delivery time and increase workload, but also make the product more complex due to a large number of personalized requirements, losing the original flexibility of the standard product. Second, the adjustment of the standard product depends on the development of the workflow designer, making it difficult to respond to specific project needs in a timely manner. Different projects have different needs, and the developers have difficulty in deeply identifying suitable attribute design solutions for each project, resulting in problems such as delayed development progress, unreasonable design solutions, and inconvenience for secondary adjustments to the project.

[0004] Therefore, once standard products have begun delivery, if new requirements and changes arise that cannot be configured on-site by the implementation team, it is necessary to contact product development for functional adjustments. Such scenarios consume significant development time and impact project delivery schedules. In conclusion, in a wide range of business scenarios, workflow generation suffers from poor flexibility and low efficiency. Summary of the Invention

[0005] This application provides a workflow generation method, device, and medium to address the problem of poor flexibility and low efficiency in generating workflows under a large number of business scenario types.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] On one hand, embodiments of this application provide a workflow generation method, which includes: receiving an extension request for a workflow in a specified business scenario type; parsing the extension request to obtain attribute information of the extension attribute and associated process information; filling the field content of a pre-defined extension attribute field according to the attribute information; if the associated process information is not empty, associating the extension attribute with a specified business type and / or associating the extension attribute with a specified workflow type according to the associated process information; the specified business type includes multiple workflow types; obtaining workflow frameworks of multiple workflow types in the specified business scenario type; determining workflow frameworks associated with the extension attribute; merging the extension attribute with the regular attributes of the associated workflow framework to obtain an extended workflow framework for the specified business scenario type; configuring the attribute content between the extension attribute and the regular attributes in the extended workflow framework in a workflow designer to generate a workflow for the specified business scenario type.

[0008] In one example, the step of filling the pre-defined extended attribute fields with content based on the attribute information specifically includes: determining that the attribute information includes a first-level attribute title and a second-level attribute title, so as to set the field content of the first-level attribute title to the first-level attribute title and the field content of the second-level attribute title to the second-level attribute title; the first-level attribute is used to divide attribute groups; the second-level attribute is the attribute type of the first-level attribute; obtaining the attribute value of the second-level attribute based on the attribute mapping information carried by the second-level attribute, so as to set the attribute value field content of the second-level attribute to the attribute value; the attribute value includes one of text type, enumeration type, and boolean type; determining that the attribute information includes the display level of the first-level attribute, so as to set the display level field content of the first-level attribute to the display level, the display level including one of workflow type and workflow node.

[0009] In one example, associating the extended attribute with a specified business type and / or associating the extended attribute with a specified process type based on the associated process information specifically includes: in the associated process information, if the extended attribute has a bound specified business type number, then the field content of the business type number of the extended attribute is set to the specified business type number to associate the extended attribute with all workflow frames under the specified business type number; if the extended attribute has a bound specified workflow type number, then the field content of the process type number of the extended attribute is set to the specified workflow type number to associate the extended attribute with the workflow frame corresponding to the specified workflow type number.

[0010] In one example, configuring the attribute content between extended attributes and regular attributes in the extended workflow framework within the workflow designer to generate a workflow for the specified business scenario type specifically includes: in the workflow designer, displaying the first-level attribute title on the extended workflow framework based on the display level field content and the field content of the first-level attribute title; receiving a click action on the first-level attribute and displaying a visual interface for the second-level attribute title based on the field content of the second-level attribute title; validating the user's configuration content for the second-level attribute in the visual interface based on the attribute value field content of the second-level attribute; and if the validation passes, determining the configuration content as the attribute content of the second-level attribute.

[0011] In one example, the method further includes: if the configuration content of the secondary attribute fails to be validated, then the configuration content of the secondary attribute is matched with the attribute value field content of the secondary attribute; if the match is successful, then the configuration content of the secondary attribute is converted into configuration content to be verified that matches the attribute value field content of the secondary attribute; the configuration content to be verified is displayed to the user in a pop-up window, and after the user confirms, the configuration content to be verified is determined as the attribute content of the secondary attribute.

[0012] In one example, after configuring the attribute content between extended attributes and regular attributes in the extended workflow framework in the workflow designer to generate a workflow for the specified business scenario type, the method further includes: receiving a user's request to fill in extended attributes for the workflow; obtaining the extended attributes through a pre-defined calling interface; obtaining the attribute content of the extended attributes through the key value of the extended attributes; where the key value is the attribute field content of the extended attributes.

[0013] In one example, the method further includes: if the associated process information is empty, generating unassociated notification information for the extended attribute; sending the unassociated notification information to the management user terminal; receiving confirmation information from the management user terminal regarding the unassociated notification information; and associating the extended attribute with all workflow types of the specified business scenario type.

[0014] In one example, associating the extended attribute with all workflow types of the specified business scenario type specifically includes: obtaining a pre-defined specific number representing all business types; setting the business type field content of the extended attribute to the specific number to associate the extended attribute with all workflow frameworks of all business types; and setting the process type field content of the extended attribute to the specific number.

[0015] On the other hand, embodiments of this application provide a workflow generation device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: receive an extension request for a workflow in a specified business scenario type; parse the extension request to obtain attribute information of an extension attribute and associated process information; fill in the content of a pre-defined extension attribute field according to the attribute information; if the associated process information is not empty, associate the extension attribute with a specified business type and / or associate the extension attribute with a specified workflow type according to the associated process information; the specified business type includes multiple workflow types; obtain workflow frameworks of multiple workflow types in the specified business scenario type, determine workflow frameworks associated with the extension attribute, merge the extension attribute with the regular attributes of the associated workflow framework to obtain an extended workflow framework for the specified business scenario type; in a workflow designer, configure the attribute content between the extension attribute and the regular attributes in the extended workflow framework to generate a workflow for the specified business scenario type.

[0016] On the other hand, embodiments of this application provide a non-volatile computer storage medium for generating workflows, storing computer-executable instructions. These computer-executable instructions are configured to: receive an extension request for a workflow in a specified business scenario type; parse the extension request to obtain attribute information of the extension attribute and associated process information; fill in the content of pre-defined extension attribute fields according to the attribute information; if the associated process information is not empty, associate the extension attribute with a specified business type and / or associate the extension attribute with a specified workflow type according to the associated process information; the specified business type includes multiple workflow types; obtain workflow frameworks for multiple workflow types in the specified business scenario type; determine workflow frameworks associated with the extension attribute; merge the extension attribute with the regular attributes of the associated workflow framework to obtain an extended workflow framework for the specified business scenario type; and configure the attribute content between the extension attribute and the regular attributes in the extended workflow framework in a workflow designer to generate a workflow for the specified business scenario type.

[0017] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:

[0018] By creating attribute information and associated process information for extended attributes, it is possible to customize the extended attribute fields. Furthermore, by associating extended attributes with specified workflow types, extended attributes can be displayed on specified workflow frameworks. Thus, by introducing custom extended attributes, it is possible to personalize extended workflow frameworks based on specified business scenario types, thereby generating customized workflows for specified business scenario types and improving the flexibility and efficiency of workflow generation. Attached Figure Description

[0019] To more clearly illustrate the technical solution of this application, some embodiments of this application will be described in detail below with reference to the accompanying drawings, in which:

[0020] Figure 1 A flowchart illustrating a workflow generation method provided in an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of the interface of a first-level attribute according to an embodiment of this application;

[0022] Figure 3 An application provided in the embodiments of this application is used in Figure 2 A schematic diagram of the interface for the secondary attributes;

[0023] Figure 4 This is a schematic diagram of a workflow generation device provided in an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] Some embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0026] Figure 1 This is a flowchart illustrating a workflow generation method provided in an embodiment of this application. This method can be applied to different business domains, such as internet finance, e-commerce, instant messaging, gaming, and government services. Certain input parameters or intermediate results in the workflow can be manually adjusted to help improve accuracy.

[0027] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a server as an example.

[0028] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations on this.

[0029] Figure 1 The process includes the following steps:

[0030] S101: Receive an extension request for a workflow in a specified business scenario type, parse the extension request, and obtain the attribute information of the extension attributes and the associated workflow information.

[0031] The attribute information includes the first-level attribute title, the second-level attribute title, the display level of the first-level attribute, the attribute mapping information carried by the second-level attribute, the internal code of the first-level attribute, and the internal code of the group to which the second-level attribute belongs. The associated process information includes the business type number and the workflow type number.

[0032] It should be noted that attribute mapping information refers to the attribute value type of the secondary attribute.

[0033] It should be noted that, in order to facilitate configuration and management within the graphical user interface, clear and explicit primary and secondary attributes need to be designed. Primary attributes are actually used for grouping and do not handle specific attribute value configurations, while secondary attributes handle specific attribute value configurations. Attribute value types include text, enumeration, and boolean values.

[0034] In addition, the display level of a first-level attribute includes the workflow type and the nodes of the workflow. For example, if the display level is only for workflow type d, then the first-level attribute will be displayed in all nodes of workflow type d. If the display level is only for node e of workflow type d, then the first-level attribute will be displayed in node e.

[0035] In conclusion, improving usability by designing simple and clear attribute groupings and attribute titles can greatly reduce delivery difficulty and improve implementation efficiency.

[0036] S102: Fill the pre-defined extended attribute fields with their contents based on the attribute information.

[0037] In some embodiments of this application, the extended attribute fields include a first-level attribute title, a second-level attribute title, the display level of the first-level attribute, the attribute value of the second-level attribute, the internal code of the first-level attribute, the internal code of the group to which the second-level attribute belongs, the display order of the first-level attribute, the business type number, and the workflow type number.

[0038] It should be noted that the specified business scenario type includes multiple business types, and each business type includes multiple workflow types. For example, if the specified business scenario type is the retail industry, the business types include product listing, inventory management, and order processing. Product listing includes multiple workflows related to listing.

[0039] Based on this, populating the content of pre-defined extended attribute fields can include the following:

[0040] Set the field content of the first-level attribute header to the first-level attribute header in the attribute information, and set the field content of the second-level attribute header to the second-level attribute header in the attribute information.

[0041] Based on the attribute mapping information carried by the secondary attribute, the attribute value of the secondary attribute is obtained, and the content of the attribute value field of the secondary attribute is set to that attribute value. For example, the attribute value is text.

[0042] Set the content of the display level field of the first-level attribute to the display level in the attribute information, for example, a workflow with a display level of type A.

[0043] Set the content of the primary attribute's internal code field to the primary attribute's internal code in the attribute information, and set the content of the secondary attribute's group's internal code field to the internal code of the secondary attribute's group in the attribute information. For example, if the primary attribute's internal code is 'a', and the secondary attribute is in the same group as the primary attribute, then the internal code of the secondary attribute's group is 'a'.

[0044] S103: If the associated process information is not empty, associate the extended attribute with the specified business type and / or associate the extended attribute with the specified workflow type according to the associated process information.

[0045] The specified business type includes multiple workflow types.

[0046] For example, business type X includes workflow type x and workflow type y. If the workflow type is specified as workflow type x, but the extended attributes are not associated with business type X, then workflow type y has no association. However, if the business type is specified as business type X, then both workflow type x and workflow type y are associated with the extended attributes.

[0047] In some embodiments of this application, multi-scenario and multi-dimensional configuration level restrictions are provided to limit the display scope of extended attributes.

[0048] Based on this, in the associated process information, if the extended attribute has a bound specified business type number, then the field content of the business type number of the extended attribute is set to the specified business type number, so as to associate the extended attribute with all workflow frameworks under the specified business type number.

[0049] If the extended attribute has a bound specified workflow type number, then the content of the workflow type number field of the extended attribute is set to the specified workflow type number, so as to associate the extended attribute with the workflow framework corresponding to the specified workflow type number.

[0050] That is, in the workflow designer, extended properties have the authority to be displayed in the workflow framework for the specified business type and the specified workflow type.

[0051] It should be noted that multiple workflow frameworks can be displayed by setting the first-level attribute through the associated process information. The display level of the first-level attribute can be used to set which workflow frameworks or process nodes will be displayed in these multiple workflow frameworks.

[0052] S104: Obtain workflow frameworks for multiple workflow types within the specified business scenario type, determine workflow frameworks associated with the extended attribute, and merge the extended attribute with the regular attribute of the associated workflow framework to obtain the extended workflow framework for the specified business scenario type.

[0053] S105: In the workflow designer, configure the attribute content between extended attributes and regular attributes in the extended workflow framework to generate the workflow of the specified business scenario type.

[0054] It's important to note that the field content of extended attributes allows you to set the actions that can be performed on the extended attribute within the extended workflow framework. For example, the first-level attribute title can be "Image Rescanning," and the associated workflow information can be used to set multiple workflow frameworks that can be displayed for image rescanning. The display level of the first-level attribute can be used to set which workflow frameworks or nodes will be displayed for image rescanning within these multiple workflow frameworks. The group code of the second-level attribute allows you to set the corresponding first-level attribute to "Image Rescanning," and the second-level attribute title to "Image Type," "Rescanning Required," and "Image Title." The attribute value of the second-level attribute allows you to set the attribute value type; for example, the attribute value for "Image Type" can be Boolean, and the attribute value for "Image Title" can be Text.

[0055] In addition, the extended attribute content is the specific configuration content that the user sets for the secondary attribute, such as the specific information of the image title.

[0056] In some embodiments of this application, the description of the configuration items is adjusted by the user. When designing a workflow, the user can edit the attributes at both the workflow and workflow node levels through a visual interface, which serve as important credentials for the workflow to run.

[0057] Based on this, in the workflow designer, the first-level attribute title is displayed on the extended workflow framework according to the field content of the first-level attribute display level and the field content of the first-level attribute title.

[0058] It should be noted that if the workflow type displayed at the first-level attribute level includes the currently configured extended workflow framework, then the first-level attribute title will be displayed on the extended workflow framework. If there are still workflow nodes of this workflow type, then the first-level attribute title will be displayed on the specific workflow node corresponding to the extended workflow framework.

[0059] It receives click actions for the primary attribute and displays a visual interface for the secondary attribute title based on the field content of the secondary attribute title, so that users can configure the attribute content of the secondary attribute.

[0060] In other words, in the workflow designer's configuration interface, the primary attributes of extended properties will be displayed on the corresponding workflow or process node according to the set field content. Clicking on the primary attribute will expand the corresponding visual secondary menu graphical interface, where the secondary attributes can be configured.

[0061] Next, since the configuration content entered by the user may not conform to the attribute value type of the secondary attribute, it is necessary to validate the configuration content.

[0062] Based on this, the configuration content of the user for the secondary attribute is validated according to the attribute value field content of the secondary attribute.

[0063] If the verification passes, the configuration content will be determined as the attribute content of the second-level attribute.

[0064] If the configuration content of the second-level attribute fails to be validated, the configuration content of the second-level attribute will be matched with the content of the attribute value field of the second-level attribute.

[0065] If a match is found, the configuration content of the second-level attribute will be converted into the configuration content to be verified for the attribute value field content that matches the second-level attribute.

[0066] The configuration content to be verified is displayed to the user in a pop-up window. After the user confirms, the configuration content to be verified is determined as the attribute content of the second-level attribute.

[0067] For example, if the attribute value of a second-level attribute is Boolean and the user inputs "shi", then the user's actual configuration content is "yes".

[0068] More intuitively, Figure 2 This is a schematic diagram of the interface of a first-level attribute according to an embodiment of this application.

[0069] exist Figure 2 In the middle, the primary attributes include image rescanning and budget control.

[0070] Figure 3 An application provided in the embodiments of this application is used in Figure 2 A schematic diagram of the interface for a secondary attribute.

[0071] exist Figure 3 In the image rescanning process, the secondary attributes of the primary attribute image rescanning include image type, whether it is rescanned, and image title.

[0072] Among them, the image type attribute value is Boolean, which is the option content for user configuration of image type; the rescan attribute value is Boolean, which is the option content for user configuration of whether to rescan; and the image title attribute value is text, which is the title information for user configuration of image title.

[0073] In some embodiments of this application, if the associated process information is empty, an unassociated notification message with extended attributes is generated. This unassociated notification message is sent to the management user terminal. The management user terminal's confirmation message regarding the unassociated notification message is received, and the extended attributes are associated with all workflow types of the specified business scenario type.

[0074] Specifically, when associating extended attributes with all workflow types of a specified business scenario type, a pre-defined specific number representing all business types is obtained, and the business type field content of the extended attribute is set to the specific number to associate the extended attribute with all workflow frameworks of all business types, and the workflow type field content of the extended attribute is set to the specific number.

[0075] In some embodiments of this application, after generating a workflow for a specified business scenario type, the runtime obtains the previously configured extended attributes through the interface provided by the workflow, uses the agreed key in the attribute field content as a feature to obtain the configured attribute content, and forms a corresponding relationship by introducing custom extended attributes.

[0076] Specifically, it receives user requests for extended attributes related to the workflow. It retrieves these extended attributes through a pre-defined API call. Finally, it retrieves the attribute content using the key-value pairs of the extended attributes. The key-value pairs are the content of the title field of the extended attribute.

[0077] In summary, this solves the problem that basic, conventional attributes in the workflow designer cannot meet the needs of specific scenarios, and improves the flexibility and ease of use of the workflow designer.

[0078] It should be noted that, although the embodiments in this application are based on... Figure 1 Steps S101 to S105 will be described sequentially, but this does not mean that steps S101 to S105 must be performed in a strict order. The reason this embodiment follows this order is... Figure 1 The order in which steps S101 to S105 are described is provided to facilitate understanding of the technical solutions of the embodiments of this application by those skilled in the art. In other words, in the embodiments of this application, the order of steps S101 to S105 can be appropriately adjusted according to actual needs.

[0079] pass Figure 1 This method allows for the creation of extended attribute information and associated process information, enabling the customization of extended attribute fields. By associating extended attributes with specified workflow types, extended attributes can be displayed on specified workflow frameworks. Thus, by introducing custom extended attributes, extended workflow frameworks can be personalized based on specified business scenario types, thereby generating customized workflows for specified business scenario types and improving the flexibility and efficiency of workflow generation.

[0080] Based on the same idea, some embodiments of this application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0081] Figure 4 A schematic diagram of a workflow generation device provided in this application embodiment includes:

[0082] At least one processor; and,

[0083] A memory communicatively connected to the at least one processor; wherein,

[0084] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0085] Receive an extension request for a workflow in a specified business scenario type, parse the extension request, and obtain the attribute information of the extension attributes and the associated workflow information;

[0086] Based on the attribute information, the pre-defined extended attribute fields are populated with their content.

[0087] If the associated process information is not empty, the extended attribute is associated with a specified business type and / or the extended attribute is associated with a specified workflow type based on the associated process information; the specified business type includes multiple workflow types;

[0088] Obtain workflow frameworks for multiple workflow types within the specified business scenario type, determine workflow frameworks associated with the extended attributes, and merge the extended attributes with the regular attributes of the associated workflow frameworks to obtain the extended workflow framework for the specified business scenario type.

[0089] In the workflow designer, the attribute content between extended attributes and regular attributes in the extended workflow framework is configured to generate the workflow for the specified business scenario type.

[0090] Some embodiments of this application provide a workflow for generating a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0091] Receive an extension request for a workflow in a specified business scenario type, parse the extension request, and obtain the attribute information of the extension attributes and the associated workflow information;

[0092] Based on the attribute information, the pre-defined extended attribute fields are populated with their content.

[0093] If the associated process information is not empty, the extended attribute is associated with a specified business type and / or the extended attribute is associated with a specified workflow type based on the associated process information; the specified business type includes multiple workflow types;

[0094] Obtain workflow frameworks for multiple workflow types within the specified business scenario type, determine workflow frameworks associated with the extended attributes, and merge the extended attributes with the regular attributes of the associated workflow frameworks to obtain the extended workflow framework for the specified business scenario type.

[0095] In the workflow designer, the attribute content between extended attributes and regular attributes in the extended workflow framework is configured to generate the workflow for the specified business scenario type.

[0096] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0097] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0098] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0099] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0100] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0101] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0102] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0103] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0104] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0105] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0106] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the technical principles of this application should fall within the protection scope of this application.

Claims

1. A workflow generation method, characterized in that, The method includes: Receive an extension request for a workflow in a specified business scenario type, parse the extension request to obtain attribute information of the extension attributes and associated workflow information; the specified business scenario type includes multiple business types; Based on the attribute information, the pre-defined extended attribute fields are populated with their content. If the associated process information is not empty, the extended attribute is associated with a specified business type and / or the extended attribute is associated with a specified workflow type based on the associated process information; the specified business type includes multiple workflow types; Obtain workflow frameworks for multiple workflow types within the specified business scenario type, determine workflow frameworks associated with the extended attributes, and merge the extended attributes with the regular attributes of the associated workflow frameworks to obtain the extended workflow framework for the specified business scenario type. In the workflow designer, the attribute content between extended attributes and regular attributes in the extended workflow framework is configured to generate the workflow for the specified business scenario type; wherein, the attribute content is the configuration content of the extended attributes and the configuration content of the regular attributes.

2. The method according to claim 1, characterized in that, The step of filling the pre-defined extended attribute fields with content based on the attribute information specifically includes: The attribute information is determined to include a first-level attribute title and a second-level attribute title, so that the field content of the first-level attribute title is set as the first-level attribute title, and the field content of the second-level attribute title is set as the second-level attribute title; the first-level attribute is used to divide attribute groups; the second-level attribute is the attribute type of the first-level attribute; Based on the attribute mapping information carried by the secondary attribute, the attribute value of the secondary attribute is obtained, so as to set the content of the attribute value field of the secondary attribute to the attribute value; the attribute value includes one of text type, enumeration type, and boolean type; The attribute information is determined to include the display level of the first-level attribute, so that the content of the display level field of the first-level attribute is set to the display level, wherein the display level includes one of workflow type and workflow node.

3. The method according to claim 1, characterized in that, The step of associating the extended attribute with a specified business type and / or associating the extended attribute with a specified process type based on the associated process information specifically includes: In the associated process information, if the extended attribute has a bound specified business type number, then the field content of the business type number of the extended attribute is set to the specified business type number, so as to associate the extended attribute with all workflow frameworks under the specified business type number; If the extended attribute has a bound specified workflow type number, then the content of the workflow type number field of the extended attribute is set to the specified workflow type number, so as to associate the extended attribute with the workflow framework corresponding to the specified workflow type number.

4. The method according to claim 2, characterized in that, In the workflow designer, the configuration of attribute content between extended attributes and regular attributes in the extended workflow framework to generate a workflow for the specified business scenario type specifically includes: In the workflow designer, the title of the first-level attribute is displayed on the extended workflow framework based on the content of the display level field of the first-level attribute and the content of the title field of the first-level attribute. Receive a click action for the first-level attribute, and display a visualization interface for the second-level attribute title based on the field content of the second-level attribute title; Based on the attribute value field content of the secondary attribute, the configuration content of the user for the secondary attribute in the visualization interface is validated; If the verification passes, the configuration content will be determined as the attribute content of the secondary attribute.

5. The method according to claim 4, characterized in that, The method further includes: If the configuration content of the secondary attribute fails to be validated, the configuration content of the secondary attribute will be matched with the attribute value field content of the secondary attribute. If a match is successful, the configuration content of the secondary attribute is converted into the configuration content to be verified that matches the attribute value field content of the secondary attribute. The configuration content to be verified is displayed to the user in a pop-up window. After the user confirms, the configuration content to be verified is determined as the attribute content of the secondary attribute.

6. The method according to claim 1, characterized in that, After configuring the attribute content between extended attributes and regular attributes in the extended workflow framework in the workflow designer to generate the workflow for the specified business scenario type, the method further includes: Receive user requests to fill in extended attributes for the workflow; The extended attributes are obtained through a pre-defined API call interface; The attribute content of the extended attribute is obtained through the key value of the extended attribute; the key value is the attribute field content of the extended attribute.

7. The method according to claim 1, characterized in that, The method further includes: If the associated process information is empty, generate the unassociated notification information for the extended attribute; Send the unrelated notification information to the management user terminal; Receive confirmation information from the management user terminal regarding the unrelated notification information, and associate the extended attribute with all workflow types of the specified business scenario type.

8. The method according to claim 7, characterized in that, The step of associating the extended attribute with all workflow types of the specified business scenario type specifically includes: Obtain a pre-defined specific number representing all business types, and set the business type field content of the extended attribute to the specific number to associate the extended attribute with all workflow frameworks of all business types; Set the content of the process type field of the extended attribute to the specific number.

9. A workflow generation device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to: perform a workflow generation method as described in any one of claims 1-8.

10. A workflow generates a non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are configured to execute a workflow generation method as described in any one of claims 1-8.

Images