Game issuing process management method and device, equipment and storage medium

Abstract

The embodiment of the invention discloses a game issuing process management method and device, equipment and a storage medium. According to the technical scheme provided by the embodiment of the invention, the method comprises the following steps: constructing a graphical process canvas according to a set process node component and a process construction component; according to the configuration attribute of each process node component in the graphical process canvas and the execution sequence corresponding to the process construction component, constructing a game issuing process; and issuing the game issuing process to push the corresponding process node to the client of the corresponding authority personnel. According to the technical scheme provided by the embodiment of the invention, the technical problem that the game issuing process creation and management efficiency is relatively low can be solved, the game issuing process is automatically constructed based on the set process node component and the process construction component, and the game issuing process creation and management efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, device and storage medium for managing the game release process. Background Technology

[0002] Against the backdrop of the booming digital entertainment industry, the game publishing process, as a crucial link in the development and market transformation of game products, involves multiple core nodes such as planning review, technical review, compliance review, and operational scheduling. Its management efficiency and standardization directly impact the time cost of game launch, resource coordination effectiveness, and compliance risk control. Efficient process management ensures orderly collaboration among departments and rapid, accurate approval decisions, thereby enhancing the market competitiveness of game products.

[0003] The existing game publishing process typically relies on professional developers writing large amounts of code. This management model not only consumes significant time, but also results in a lengthy development cycle—from requirements analysis, design, and coding to testing—significantly lagging behind the rapidly evolving needs of the game business. Therefore, the existing game publishing process is inefficient in its construction and management. Summary of the Invention

[0004] This application provides a game release process management method, apparatus, device, and storage medium, which can solve the technical problem of low efficiency in the creation and management of game release processes. It automatically constructs game release processes based on set process node components and process construction components, thereby improving the efficiency of game release process creation and management.

[0005] In a first aspect, embodiments of this application provide a game publishing process management method, including:

[0006] Based on the configured process node components and process building components, construct a graphical process canvas;

[0007] The game release process is constructed based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process building components.

[0008] Release the game release process to push the corresponding process nodes to the clients of the authorized personnel.

[0009] Furthermore, based on the configured process node components and process building components, a graphical process canvas is constructed, including:

[0010] It accepts drag-and-drop operations on the configured process node components and process building components;

[0011] By dragging and dropping, process node components and corresponding process building components are combined to construct a graphical process canvas.

[0012] Furthermore, it accepts drag-and-drop operations on the configured process node components and process building components, including:

[0013] It receives drag and drop operations on the configured process node components and generates node instances when the process node components are dragged to the canvas area.

[0014] It receives drag-and-drop operations on the configured process building components. When the process building components are dragged to the canvas area, the execution order of the corresponding node instances is determined according to the pointer of the process building components.

[0015] Furthermore, after generating node instances, the process also includes:

[0016] Receive click operations on the process node components in the canvas area and pop up the node configuration interface;

[0017] The node configuration interface receives configuration information for process node components, including associated authorized personnel and processing time limits.

[0018] Furthermore, based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process building components, a game release process is constructed, including:

[0019] Iterate through each process node component in the graphical process canvas and determine the configuration properties corresponding to each process node component.

[0020] The configuration properties are encapsulated into the node instance of the corresponding process node component;

[0021] The corresponding node instances are assembled according to the execution order of the components in the process to obtain the game release process.

[0022] Furthermore, following the release of the game publishing process, it also includes:

[0023] Determine the processing deadline for each process node;

[0024] Based on the time interval before the processing deadline, reminder notifications are sent to the clients of the corresponding authorized personnel using a tiered notification strategy and the corresponding reminder method.

[0025] Furthermore, based on the time interval remaining until the processing deadline, reminder notifications are sent to the clients of the corresponding authorized personnel using a tiered notification strategy and corresponding reminder methods, including:

[0026] At the first time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via the internal reminder method of the process system;

[0027] At the second time interval before the processing deadline, a reminder notification is sent to the client of the corresponding permission administrator via email. The second time interval is shorter than the first time interval.

[0028] At the third time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via telephone, SMS, or social communication software. The third time interval is shorter than the second time interval.

[0029] In a second aspect, embodiments of this application provide a game publishing process management device, comprising:

[0030] The process canvas building module is used to build a graphical process canvas based on the set process node components and process building components;

[0031] The game publishing process construction module is used to construct the game publishing process based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process construction components.

[0032] The process release module is used to release the game release process, so that the corresponding process nodes are pushed to the clients of the authorized personnel.

[0033] In a third aspect, embodiments of this application provide a game publishing process management device, comprising:

[0034] Memory and one or more processors;

[0035] Memory, used to store one or more programs;

[0036] When one or more programs are executed by one or more processors, the one or more processors implement the game release process management method as described in the first aspect.

[0037] In a fourth aspect, embodiments of this application provide a storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to perform the game release process management method as described in the first aspect.

[0038] This application embodiment constructs a graphical process canvas based on set process node components and process building components during game release process management. The game release process is then built and published according to the configuration attributes of each process node component and the execution order of the corresponding process building components, pushing the corresponding process nodes to the clients of authorized personnel. Using this technical means, the game release process can be automatically constructed through set process node components and process building components. This avoids the technical problem of low efficiency in game release process construction and management caused by manual coding. No coding is required; the game release process can be automatically constructed simply by dragging and dropping set process node components and process building components, greatly improving the efficiency of game release process creation and management.

[0039] The beneficial effects of the game distribution process management device, game distribution process management equipment, and storage medium provided above can be referenced in relation to the beneficial effects of the game distribution process management method. Attached Figure Description

[0040] Figure 1 This is a flowchart of a game publishing process management method provided in an embodiment of this application;

[0041] Figure 2 This is a schematic diagram of a process construction interface provided in an embodiment of this application;

[0042] Figure 3 This is a flowchart illustrating another game publishing process management method provided in an embodiment of this application;

[0043] Figure 4 This is a flowchart illustrating another game publishing process management method provided in the embodiments of this application;

[0044] Figure 5 This is a schematic diagram of a node configuration interface provided in an embodiment of this application;

[0045] Figure 6 This is a flowchart illustrating another game publishing process management method provided in an embodiment of this application;

[0046] Figure 7 This is a schematic diagram of the structure of a game publishing process management device provided in an embodiment of this application;

[0047] Figure 8 This is a schematic diagram of the structure of a game release process management device provided in an embodiment of this application. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0049] The existing game publishing process typically relies on professional developers writing large amounts of code. This management model not only consumes significant time, but also results in a lengthy development cycle—from requirements analysis, design, and coding to testing—significantly lagging behind the rapidly evolving needs of the game business. Therefore, the existing game publishing process is inefficient in its construction and management.

[0050] Based on this, the present application provides a game release process management method, apparatus, device, and storage medium. The aim is to construct a graphical process canvas based on set process node components and process construction components during game release process management. Then, based on the configuration attributes of each process node component in the graphical process canvas and the execution order corresponding to the process construction components, the game release process is constructed and published, pushing the corresponding process nodes to the clients of authorized personnel. Using the above technical means, the game release process can be automatically constructed through set process node components and process construction components. Compared to existing methods that require professionals to manually write a large amount of code to construct the game release process, this embodiment eliminates the need for coding. The game release process can be automatically constructed simply by dragging and dropping set process node components and process construction components. This avoids the technical problem of low efficiency in game release process construction and management caused by manual coding, greatly improving the efficiency of game release process creation and management.

[0051] Figure 1A flowchart of a game publishing process management method provided in this application embodiment is given. The game publishing process management method provided in this embodiment can be executed by a game publishing process management device, which can be implemented by software and / or hardware. The game publishing process management device can consist of two or more physical entities, or it can consist of a single physical entity. Generally, the game publishing process management device can be a computer device.

[0052] The following description uses computer equipment as the main body for implementing the game release process management method.

[0053] Reference Figure 1 The specific management methods for the game's release process include:

[0054] S11. Based on the set process node components and process building components, construct a graphical process canvas.

[0055] Process node components are the basic units that constitute a graphical process, representing a specific step in the process and possessing independent attribute configurations, interaction configurations, and business functions. Each process node component corresponds to an operation or decision point in the process and is the smallest carrier of process logic. Node types can be predefined according to business scenarios, such as start nodes, approval nodes, conditional branch nodes, sub-process nodes, and end nodes. Each type of node is presented as a process node component in the process building interface, and each process node component has its own unique appearance and functional logic. Process building components are a collection of tools for connecting, laying out, and managing process nodes, responsible for the logical relationships between nodes, canvas interactions, and the visual presentation of the process structure. Process building components do not directly represent business steps but rather provide the technical capabilities that support the combination of nodes into a complete process.

[0056] Icons and styles for different node types and process building components are pre-defined. For example, approval node components are displayed as rectangles, conditional branch components as diamonds, and process building components as connecting tools and swimlane separators. When creating a game release process, users can drag and drop the pre-defined node and building components in the process building interface according to actual process building needs. This drag-and-drop operation connects the node and building components, creating a graphical process canvas. This drag-and-drop approach significantly reduces process modeling time compared to traditional code configuration or form filling, thus improving the efficiency of game release process building. Furthermore, the dynamic combination of process node components through visual drag-and-drop allows for adaptation to complex business scenarios in game release, enhancing the flexibility and scalability of game release process building.

[0057] Figure 2 This is a schematic diagram of a process construction interface provided in an embodiment of this application, referred to as follows. Figure 2 The left side of the process construction interface 1 contains a component library area 11, and the right side contains a canvas area 12. In the component library area 11, process node components and process construction components are displayed according to their functions, such as start node components, internal test node components, internal test branch components, external test node components, external test branch components, compliance approval node components, end components, and connector components. It should be noted that the specific process node components and process construction components can be set according to the actual process requirements of the game release. For example, some scenarios may not require external test node components, only internal testing needs to be completed, i.e., only internal test node components are needed. Each process node component and process construction component is presented as an icon or card, supporting mouse hover to display a function description, and clicking or long-pressing to trigger drag operations. The system listens for drag events in the node component area 11 of the process construction interface 1. When a drag event is detected, the corresponding process node component or process construction component is dragged to the canvas area 12 according to the drag operation. For example, when a user clicks on a process node component or process building component in the node component area, a drag event is triggered. Based on the user's dragging of the process node component or process building component, the preview position of the dragged process node component or process building component on canvas area 12 is updated in real time (e.g., it is semi-transparent). When the user drags the process node component or process building component to canvas area 12 and releases the mouse, a placement event is triggered, placing the corresponding process node component or process building component on canvas area 12 at the position corresponding to the mouse release. For example, based on the user's drag operation, a... Figure 2 The graphical workflow canvas shown in canvas area 12 includes a start workflow node component (component name "Start"), an internal test node component (component name "Internal Test"), an internal test branch component (component name "Internal Test Pass / Fail"), an external test node component (component name "External Test"), an external test branch component (component name "External Test Pass / Fail"), a compliance review node component (component name "Compliance Approval"), an end node component (component name "Release"), and a product adjustment node component (component name "Product Adjustment"). These workflow node components are connected using connector components (i.e., workflow building components) to obtain... Figure 2 The graphical workflow canvas shown in canvas area 12.

[0058] As described above, a graphical canvas can be built by setting process nodes and process building components, eliminating the need for writing code or filling out forms, which greatly improves the efficiency of creating and managing game release processes. Furthermore, the release processes for different games can be reused by setting process node components and process building components, reducing duplicate code and further improving the efficiency of creating and managing game release processes.

[0059] S12. Construct the game release process based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process building components.

[0060] Each process node component includes corresponding configuration attributes, including basic attributes, execution attributes, input / output attributes, interface configuration attributes, and access control attributes. Basic attributes include node identifier, node name, node type, node version number, node creator, and node creation time. Execution attributes include execution script, processing deadline, number of retries, synchronous execution flag, and asynchronous execution flag. Input / output attributes include input parameter definitions (name, type, and default value), output parameter definitions, and data mapping relationships. Interface configuration attributes include node icon, node color, display label, prompts, and operation buttons. Access control attributes include execution role (processor, approver, or reviewer), visibility role (e.g., marketing department or R&D department), and operation permissions (edit or read-only). Configuration attributes can be preset, and the corresponding process node components are configured according to the preset configuration attributes after the graphical process canvas is built. Configuration attributes can also be manually configured or changed after the graphical process canvas is built.

[0061] Based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process building components, the game release process is constructed. This eliminates the need for professionals to write code, improving the efficiency and accuracy of game release process construction and management.

[0062] For example, each process node component in the graphical process canvas can be traversed, and each process node component can be parsed to determine its corresponding configuration attributes. A corresponding node instance is created for each process node component, and the parsed configuration attributes are encapsulated into the corresponding process node component's node instance. The configuration attributes can be encapsulated as objects and saved to the corresponding node instances. The corresponding node instances are assembled according to the execution order of the process building components to obtain the game release process. For example, a node mapping table is created, using the node identifier (i.e., node ID) of the configuration information in the process node component as the key to associate and store node instances for easy subsequent retrieval. The process building components (i.e., connector components) are parsed, and the source and target nodes (i.e., execution order) are determined according to the pointers of the process building components. A list of subsequent nodes and a list of predecessor nodes are added to each node instance. An executable process model, i.e., the game release process, is generated based on the list of subsequent nodes and the list of predecessor nodes for each node instance. As described above, by encapsulating the configuration attributes of process node components through node instances, when business rules change, only the configuration attributes of the corresponding process node components need to be modified, without adjusting the overall process logic, which greatly reduces maintenance costs and improves the maintainability of game release process management.

[0063] S13. Publish the game release process to push the corresponding process nodes to the clients of the authorized personnel.

[0064] After the graphical workflow canvas is built, a release request is submitted to trigger the construction and release of the game release workflow. After the game release workflow is released, the corresponding authorized personnel can be determined based on the configuration information of the corresponding node instance. The corresponding workflow nodes are then pushed to the clients of the authorized personnel. For example, internal testing nodes can be pushed to the clients of the corresponding developers, enabling them to complete relevant internal testing tasks. For instance, a long-lived connection can be established when a user logs into their client. After the game release workflow is generated, it can be immediately pushed to the workflow system interface of the relevant authorized personnel's clients via this long-lived connection. The authorized personnel can view the detailed content of the workflow nodes in their own client's workflow system interface. This detailed content includes the workflow name, current node, deadline, and operation buttons (annotation, rejection, and viewing details, etc.). By publishing the game release workflow after its construction and pushing the corresponding workflow nodes to the clients of the authorized personnel, the authorized personnel can process the nodes immediately, reducing workflow downtime and improving the response speed of the game release workflow.

[0065] As described above, a graphical process canvas is constructed based on the set process node components and process building components. The game release process is then built and published according to the configuration attributes of each process node component and the execution order of the corresponding process building components, pushing the corresponding process nodes to the clients of authorized personnel. Using this technique, the game release process can be automatically constructed through the set process node components and process building components. Compared to existing methods that require professionals to manually write large amounts of code to construct game release processes, this embodiment eliminates the need for coding. The game release process can be automatically constructed simply by dragging and dropping the set process node components and process building components. This avoids the technical problem of low efficiency in game release process construction and management caused by manual coding, greatly improving the efficiency of game release process creation and management.

[0066] Figure 3 This is a flowchart illustrating another game publishing process management method provided in this application embodiment, see below. Figure 3 The game release process management method, used to construct a graphical process canvas, specifically includes:

[0067] S111, Receive drag and drop operations on the configured process node components and process building components.

[0068] When creating a game release process, drag and drop the pre-set process node components and process building components in the process building interface according to the actual process building requirements. The specific drag-and-drop process is the same as the aforementioned step S11, and will not be repeated here.

[0069] S112. Receive drag and drop operations on the set process node components, and generate node instances when the process node components are dragged to the canvas area.

[0070] The drag-and-drop operation can be understood as dragging the corresponding process node component and process building component from the component library area to the canvas area. It receives drag-and-drop operations on the configured process node component, and when the process node component is dragged to the canvas area, a node instance corresponding to that process node is generated after the drag-and-drop operation is completed.

[0071] S113. Receive drag and drop operation on the set process building component. When the process building component is dragged to the canvas area, determine the execution order of the corresponding node instances according to the pointer of the process building component.

[0072] Drag and drop operations can be understood as dragging the corresponding process node components and process building components from the component library area to the canvas area. It receives drag and drop operations on the configured process building components. When dragging the process building component to the canvas area, after the drag operation is complete, the execution order of the corresponding node instances is determined based on the pointer of the process building component. For example, refer to... Figure 2 The start node component (node ​​name "Start") points to the internal test node component (node ​​name "Internal Test") based on the connector component (i.e., the process building component). For example, a list of subsequent nodes and a list of predecessor nodes can be added to each node instance based on the source and target nodes of the process building component (e.g., the connector component). The addition of a list of subsequent nodes and a list of predecessor nodes to each node instance represents the execution order of each node instance.

[0073] S114. By dragging and dropping, the process node components and the corresponding process building components are joined together to build a graphical process canvas.

[0074] The graphical workflow canvas can be built by dragging and dropping, which greatly shortens the workflow modeling time compared to traditional code configuration or form filling, thereby improving the efficiency of game publishing workflow construction. Furthermore, the dynamic splicing of workflow node components through visual dragging and dropping can adapt to complex business scenarios in game publishing, improving the flexibility and scalability of game publishing workflow construction.

[0075] Figure 4 This is a flowchart illustrating another game publishing process management method provided in the embodiments of this application, referred to... Figure 4 The game release process management method, after generating node instances, specifically includes:

[0076] S115. Receive the click operation on the process node component in the canvas area and pop up the node configuration interface.

[0077] After dragging and dropping the corresponding process node component onto the canvas area to generate a corresponding node instance, the process node component may have preset configuration attributes encapsulated within the node instance, or the process node component may have some preset configuration information, while other key configuration information requires manual configuration, such as associated authorized personnel and processing time limits. Users can configure or change the configuration attributes of the process node component. Users can click on the process node component in the canvas area that requires configuration attribute modification, either by single-clicking or double-clicking. Receiving a click on a process node component in the canvas area will pop up the node configuration interface, where configuration attributes can be configured or modified subsequently.

[0078] S116. Receive configuration information of process node components based on the node configuration interface. The configuration information includes preset node attributes, associated authorized personnel, and processing time limits.

[0079] Users can input corresponding configuration information through the node configuration interface. The computer device receives the configuration information for the process node components through this interface. This configuration information includes preset node attributes, associated authorized personnel, and processing time limits. Based on the received configuration information and the preset configuration information, the device generates the completed configuration attributes for the process node component. After the configuration attributes of the process node component are configured or changed, the device updates the display status of the process node component, for example, by adding a "Configured" indicator and re-rendering the canvas to reflect the latest configuration.

[0080] Figure 5 This is a schematic diagram of a node configuration interface provided in an embodiment of this application, referring to... Figure 5 Suppose a click operation is performed on the internal test node component (node ​​name "internal test") in the canvas area, and a node configuration interface 121 pops up based on this click operation. The interface receives configuration information input based on the node configuration interface 121, such as the associated permission user being Zhang San and the processing period being 5 days.

[0081] As described above, clicking on the process node components directly leads to the configuration interface without needing to navigate to other pages, shortening the operation path and improving the efficiency of node attribute configuration, thereby enhancing the user experience.

[0082] Figure 6 This is a flowchart illustrating another game publishing process management method provided in this application embodiment, see below. Figure 6 This game release process management method, used after the game release process is published, specifically includes:

[0083] S21. Determine the processing deadline for each process node.

[0084] Based on the configuration attributes of each process node, the processing deadline for each process node is determined, and the corresponding authorized personnel can be notified in advance to process the process based on the processing deadline.

[0085] S22. Based on the time interval before the processing deadline, send reminder notifications to the clients of the corresponding authorized personnel using a tiered notification strategy and the corresponding reminder method.

[0086] Based on the current time and the processing deadline, determine the time interval between the current time and the processing deadline. Then, according to the time interval between the current time and the processing deadline, send reminder notifications to the clients of the corresponding authorized personnel using the corresponding reminder methods through a tiered notification strategy.

[0087] At the first time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via the internal reminder method of the workflow system. For example, if there are less than 24 hours left before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via the internal reminder method of the workflow system. At the second time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via email, where the second time interval is shorter than the first time interval. For example, if there are less than 12 hours left before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via email. At the third time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via telephone, SMS, or social communication software, where the third time interval is shorter than the second time interval. For example, if there are less than 3 hours left before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via telephone, SMS, or social communication software.

[0088] The above-mentioned multi-level notification strategy gradually strengthens the reminder intensity, ensures timely response from processing personnel, improves the efficiency of process execution, and reduces the risk of delays.

[0089] In one embodiment, a machine learning model can be used to predict the timeout probability of the current process node. The machine learning model can be trained based on historical process data, which includes historical data such as node type, processing time, personnel involved, deadline, actual completion time, timeout records, task complexity, dependent resources, and collaborating departments. Real-time process data for the current process node is acquired, including the remaining time of the current node, personnel involved, their current workload, and system load status. This real-time process data is input into the trained machine learning model for prediction processing to obtain the timeout probability. Based on the timeout probability, a tiered notification strategy is used to send reminder notifications to the corresponding authorized personnel using appropriate methods. When the timeout probability is greater than or equal to a first threshold, a reminder notification is sent to the client of the corresponding authorized administrator via telephone, SMS, or social communication software. For example, the first threshold is 70%. When the timeout probability is greater than or equal to a second threshold but less than the first threshold, a reminder notification is sent to the client of the corresponding authorized administrator via email, where the second threshold is less than the first threshold. For example, the second threshold is 30%. When the timeout probability is less than the second threshold, a reminder notification is sent to the client of the corresponding authorized administrator through the internal reminder methods of the process system. As described above, by predicting timeout points in advance and gradually increasing the intensity of reminders through a multi-level notification strategy, we can ensure that processing personnel respond in a timely manner, improve the efficiency of process execution, and reduce the risk of delays.

[0090] In one embodiment, after the game release process is launched, the status of each process node is acquired in real time. When the status of a corresponding process node changes, a status change event is generated. A status change notification is generated based on the status change event and sent to the client of each authorized person involved in the game release process, ensuring that each authorized person involved in the game release process is promptly informed of the latest status. This event-driven architecture captures node status changes in real time, ensuring that all authorized persons receive notifications within seconds, improving the real-time nature and transparency of the process status. All process participants can view real-time progress on a unified dashboard, eliminating information silos and reducing cross-departmental communication costs.

[0091] Based on the above embodiments, Figure 7 This is a schematic diagram of a game publishing process management device provided in an embodiment of this application. (Reference) Figure 7 The game release process management device provided in this embodiment specifically includes: a process canvas construction module 21, a game release process construction module 22, and a process release module 23.

[0092] Among them, the process canvas construction module 21 is used to construct a graphical process canvas based on the set process node components and process construction components;

[0093] The game publishing process construction module 22 is used to construct the game publishing process based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process construction components.

[0094] The process release module 23 is used to release the game release process, so as to push the corresponding process nodes to the client of the corresponding authorized personnel.

[0095] In one embodiment, the process canvas construction module 21 includes: a drag-and-drop receiving submodule and a canvas construction submodule;

[0096] The drag-and-drop receiving submodule is used to receive drag-and-drop operations on the configured process node components and process building components;

[0097] The canvas construction submodule is used to connect process node components and corresponding process construction components based on drag-and-drop operations to build a graphical process canvas.

[0098] In one embodiment, the drag-and-drop receiving submodule includes: a first drag-and-drop receiving unit, an instance generation unit, a second drag-and-drop receiving unit, and an execution order determination unit;

[0099] The first drag-and-drop receiving unit is used to receive drag-and-drop operations on the set process node components;

[0100] The instance generation unit is used to generate node instances when a process node component is dragged and dropped onto the canvas area;

[0101] The second drag-and-drop receiving unit is used to receive drag-and-drop operations on the set process building components;

[0102] The execution order determination unit is used to determine the execution order of the corresponding node instances based on the pointer of the process building component when the process building component is dragged to the canvas area.

[0103] In one embodiment, the game release process management device further includes: a click operation receiving module, a node interface pop-up module, and a configuration information receiving module;

[0104] The click operation receiving module is used to receive click operations on the process node components in the canvas area;

[0105] The node interface pop-up module is used to bring up the node configuration interface;

[0106] The configuration information receiving module is used to receive configuration information of process node components based on the node configuration interface. The configuration information includes associated authorized personnel and processing time limits.

[0107] In one embodiment, the game publishing process construction module 22 includes: a configuration attribute determination submodule, a configuration attribute encapsulation submodule, and an instance assembly submodule;

[0108] The configuration attribute determination submodule is used to traverse each process node component in the graphical process canvas and determine the configuration attribute corresponding to each process node component.

[0109] The configuration attribute encapsulation submodule is used to encapsulate configuration attributes into the node instances of the corresponding process node components;

[0110] The instance assembly submodule is used to assemble the corresponding node instances according to the execution order of the process building components to obtain the game release process.

[0111] In one embodiment, the game release process management device further includes: a deadline determination module and a tiered notification module;

[0112] The deadline determination module is used to determine the processing deadline for each process node;

[0113] The tiered notification module is used to send reminder notifications to the clients of authorized personnel according to the time intervals remaining until the processing deadline, using a tiered notification strategy and corresponding reminder methods.

[0114] In one embodiment, the hierarchical notification module includes: a first notification submodule, a second notification submodule, and a third notification submodule;

[0115] The first notification submodule is used to send a reminder notification to the client of the corresponding authorized administrator through the internal reminder method of the process system at the first time interval before the processing deadline;

[0116] The second notification submodule is used to send a reminder notification to the client of the corresponding permission administrator via email at the second time interval before the processing deadline, wherein the second time interval is shorter than the first time interval;

[0117] The third notification submodule is used to send a reminder notification to the client of the corresponding permission administrator via telephone, SMS or social communication software at the third time interval before the processing deadline. The third time interval is shorter than the second time interval.

[0118] The game release process management device provided in this application embodiment can be used to execute the game release process management method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0119] This application provides a game publishing process management device, referring to... Figure 8 The game distribution process management device includes: a processor 31, a memory 32, a communication module 33, an input device 34, and an output device 35. The game distribution process management device may have one or more processors, and the game distribution process management device may have one or more memories. The processor, memory, communication module, input device, and output device of the game distribution process management device can be connected via a bus or other means.

[0120] The memory 32, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the game release process management method in any embodiment of this application (e.g., the process canvas construction module, game release process construction module, and process publishing module in the game release process management device). The memory may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application required for a function; the data storage area may store data created based on the use of the device, etc. Furthermore, the memory may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0121] The communication module 33 is used for data transmission.

[0122] The processor 31 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the memory, thereby realizing the game release process management method described above.

[0123] Input device 34 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 35 may include display devices such as a display screen.

[0124] The game release process management device provided above can be used to execute the game release process management method provided in the above embodiments, and has corresponding functions and beneficial effects.

[0125] This application embodiment also provides a storage medium for storing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute a game release process management method. The game release process management method includes: constructing a graphical process canvas based on set process node components and process construction components; constructing a game release process based on the configuration attributes of each process node component in the graphical process canvas and the execution order corresponding to the process construction components; and publishing the game release process to push the corresponding process nodes to the clients of the corresponding authorized personnel.

[0126] Storage medium – any type of memory device or storage device. The term “storage medium” is intended to include: mounting media, such as CD-ROM, floppy disk, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. Storage medium may also include other types of memory or combinations thereof. Furthermore, storage medium may reside in a first computer system in which the program is executed, or it may reside in a different second computer system connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term “storage medium” can include two or more storage media residing in different locations (e.g., in different computer systems connected via a network). Storage medium may store program instructions (e.g., specifically implemented as a computer program) executable by one or more processors.

[0127] Of course, the computer-executable instructions stored in the storage medium provided in the embodiments of this application are not limited to the game release process management method described above, but can also execute related operations in the game release process management method provided in any embodiment of this application.

[0128] The game release process management device, storage medium, and game release process management equipment provided in the above embodiments can execute the game release process management method provided in any embodiment of this application. For technical details not described in detail in the above embodiments, please refer to the game release process management method provided in any embodiment of this application.

[0129] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart 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, and may include more other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the claims.

Claims

1. A method for managing the game publishing process, characterized in that, include: Based on the configured process node components and process building components, construct a graphical process canvas; The game release process is constructed based on the configuration attributes of each process node component in the graphical process canvas and the execution order of the process building components. The game release process is published to push the corresponding process nodes to the clients of the authorized personnel.

2. The method according to claim 1, characterized in that, The step of constructing a graphical process canvas based on the set process node components and process construction components includes: It accepts drag-and-drop operations on the configured process node components and process building components; The process node components and corresponding process building components are combined using the drag-and-drop operation to construct a graphical process canvas.

3. The method according to claim 2, characterized in that, The receiving of drag-and-drop operations on the configured process node components and process construction components includes: Receive drag and drop operations on the set process node components, and generate node instances when the process node components are dragged to the canvas area; The system receives drag-and-drop operations on the configured process building components. When the process building components are dragged to the canvas area, the execution order of the corresponding node instances is determined according to the pointer of the process building components.

4. The method according to claim 3, characterized in that, Following the generation of node instances, the following is also included: Upon receiving a click operation on a process node component in the canvas area, a node configuration interface pops up; The configuration information of the process node component is received through the node configuration interface. The configuration information includes the associated authorized personnel and the processing period.

5. The method according to claim 1, characterized in that, The process of constructing a game release process based on the configuration attributes of each process node component in the graphical process canvas and the execution order corresponding to the process construction components includes: Traverse each process node component in the graphical process canvas and determine the configuration attributes corresponding to each process node component. The configuration attributes are encapsulated into the node instance of the corresponding process node component; The corresponding node instances are assembled according to the execution order of the components constructed in the process described, thus obtaining the game release process.

6. The method according to claim 1, characterized in that, Following the release of the game publishing process, the following is also included: Determine the processing deadline for each process node; Based on the time interval from the processing deadline, reminder notifications are sent to the clients of the corresponding authorized personnel using a tiered notification strategy and corresponding reminder methods.

7. The method according to claim 6, characterized in that, The step of sending reminder notifications to the clients of authorized personnel according to the time interval from the processing deadline, using a tiered notification strategy and corresponding reminder methods, includes: At the first time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via an internal reminder method within the process system; At a second time interval before the processing deadline, a reminder notification is sent to the client of the corresponding access administrator via email, wherein the second time interval is shorter than the first time interval; At a third time interval before the processing deadline, a reminder notification is sent to the client of the corresponding authorized administrator via telephone, SMS, or social communication software. The third time interval is shorter than the second time interval.

8. A game distribution process management device, characterized in that, include: The process canvas building module is used to build a graphical process canvas based on the set process node components and process building components; The game release process construction module is used to construct the game release process based on the configuration attributes of each process node component in the graphical process canvas and the execution order corresponding to the process construction components. The process publishing module is used to publish the game release process, so as to push the corresponding process nodes to the clients of the corresponding authorized personnel.

9. A game distribution process management device, characterized in that, include: Memory and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the game release process management method as described in any one of claims 1-7.

10. A storage medium for storing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a processor, are used to perform the game release process management method as described in any one of claims 1-7.

Images