Workflow work order configuration method and system based on ames and medium

Abstract

The invention provides an ais-based workflow work order configuration method and system and a medium, and the method comprises the steps: embedding an aims engine in a Vue3 architecture, and constructing to obtain a front-end platform configured with a visual configuration management interface; pre-configuring an ais template through a visual configuration management interface, and storing a corresponding template JSON configuration according to a template identifier; when a link in a workflow is configured, establishing a static mapping relationship between the link in the workflow and the corresponding template identifier by specifying the corresponding template identifier; according to the static mapping relation, template JSON configuration corresponding to the link is obtained, and then the template JSON configuration and work order basic data are constructed to obtain a JSON configuration file; and according to the JSON configuration file, rendering to generate a corresponding display interface. According to the method, the complex and dynamic workflow work order can be quickly, efficiently and flexibly generated, the development cost is remarkably reduced, and the delivery efficiency and the system adaptability are improved.

Description

Technical Field

[0001] This invention relates to the field of computer code technology, and in particular to a workflow work order configuration method, system and medium based on AMIS. Background Technology

[0002] The existing technologies for implementing work order display and processing pages in workflow systems each have their inherent drawbacks: 1. Poor configurability: Traditional work order displays often use fixed front-end templates. When adding or modifying steps in the workflow or adjusting work order information fields, the front-end code needs to be modified and redeployed, which cannot quickly adapt to business changes and results in high development and maintenance costs.

[0003] 2. Low configuration efficiency: Some solutions that support custom configuration lack visual tools, requiring developers to manually write complex front-end configuration code. The configuration process is cumbersome and error-prone, making it difficult to meet the rapid configuration needs of non-technical personnel.

[0004] 3. High coupling: The association logic between workflow nodes and work order display interface is usually hard-coded in the front-end program. When the nodes and display rules need to be adjusted, the association code needs to be modified synchronously, resulting in insufficient system scalability and high maintenance difficulty.

[0005] Therefore, it is necessary to provide a new workflow work order configuration solution that can overcome the above-mentioned shortcomings at the same time. Summary of the Invention

[0006] The technical problem to be solved by this invention is to provide a workflow work order configuration method, system and medium based on AMIS, which can quickly, efficiently and flexibly generate complex and dynamic workflow work orders, significantly reduce development costs, improve delivery efficiency and system adaptability.

[0007] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: The workflow ticket configuration method based on AMIS includes: By embedding the aims engine into the Vue3 architecture and introducing the amis-editor visual configurator, a front-end platform with a visual configuration management interface is built. The visual configuration management interface pre-configures two or more AMIS templates and stores the corresponding template JSON configurations according to the template identifiers; When configuring a step in a workflow in the visual configuration management interface, a static mapping relationship between the step in the workflow and its corresponding template identifier is established by specifying the corresponding template identifier. Upon receiving a click instruction corresponding to a step in the workflow, the template JSON configuration corresponding to the step is obtained based on the static mapping relationship, and then together with the work order basic data corresponding to the workflow, the JSON configuration file of the step is constructed. The aimms engine renders and generates the corresponding display interface based on the JSON configuration file of the previous step.

[0008] Optionally, the step of pre-configuring two or more AMIS templates through the visual configuration management interface and storing the corresponding template JSON configurations according to the template identifiers specifically includes: In the template management section of the front-end platform, the content and template information of an AMIS template are pre-configured through a separate visual configuration management interface; the content of an AMIS template includes the interface layout, fields, buttons, and interface linkage logic; the template information of an AMIS template includes the template identifier, template name, and creation time. The template JSON configuration, template information, and the association between the content of the aforementioned AMIS template and the template identifier are stored in the backend database.

[0009] Optionally, when configuring a step in a workflow in the visual configuration management interface, a static mapping relationship is established between the step in the workflow and its corresponding template identifier by specifying a corresponding template identifier, specifically including: During the process configuration, all the steps included in a workflow are configured through the visual configuration management interface. When configuring the specific attributes of a step, a template identifier is selected to configure the display interface of the step during work order processing. Establish a static mapping relationship between a step in the workflow and its corresponding template identifier.

[0010] Optionally, establishing a static mapping relationship between a stage in the workflow and its corresponding template identifier specifically involves: Establish a static mapping relationship between a combined identifier consisting of the process identifier of the workflow and the stage identifier of the stage, and a specified template identifier.

[0011] Optionally, obtaining the template JSON configuration corresponding to the first step based on the static mapping relationship specifically includes: Based on the workflow identifier and the stage identifier of the step in the click instruction, the corresponding template identifier is determined by querying the static mapping relationship; Based on the determined template identifier, obtain the corresponding template JSON configuration.

[0012] Optionally, it also includes: After an authorized user enters the required information in the display interface of the first step, the submission instruction for the corresponding first step is triggered. The aims engine stores the relevant data generated by the interaction behavior corresponding to the first stage to the backend database according to the submission instruction.

[0013] Optionally, the front-end platform encapsulates the AmisRender.vue component as the core renderer, and the input properties of the AmisRender.vue component include a JSON object and an initial data context.

[0014] Optionally, the aimms engine renders and generates the corresponding display interface based on the JSON configuration file of the previous step, specifically including: On the front-end platform, the template JSON configuration in the JSON configuration file of the first step is used as a JSON object, and the basic work order data therein is used as the initial data context and input into the AmisRender.vue component; The AmisRender.vue component calls the aims engine to render and generate the display interface of the first step in the work order.

[0015] Another technical solution provided by this invention is: A workflow work order configuration system based on Amis includes a front-end platform with a visual configuration management interface; the front-end platform is built by embedding the Amis engine in the Vue3 architecture and introducing the Amis-editor visual configurator; the front-end platform encapsulates the AmisRender.vue component as the core renderer, and the input properties of the AmisRender.vue component include a JSON object and an initial data context; The aforementioned front-end platform can implement the steps included in the workflow work order configuration method based on AMIS.

[0016] Another technical solution provided by this invention is: A computer-readable storage medium having a computer program stored thereon, which, when executed by the processor of the front-end platform, is capable of implementing the steps included in the above-described workflow work order configuration method based on AMIS.

[0017] The beneficial effects of this invention include at least the following four points: (1) Improved delivery efficiency: Through visual configuration and dynamic rendering of Amis JSON configuration, adjustments to workflow work order display rules can be made without modifying the front-end code, and the changes take effect in real time after configuration. Compared with traditional template development methods, the business adaptation cycle is shortened by more than 80%, significantly reducing development and maintenance costs.

[0018] (2) Enhanced system scalability: A loosely coupled relationship is established between workflow links and template JSON configurations; when a new link is added or a link is adjusted, only the corresponding template JSON configuration needs to be added / adjusted and the relationship needs to be re-established, without changing the existing system architecture and code, supporting the infinite expansion of work order display requirements for multiple types of workflows.

[0019] (3) The configuration threshold is significantly reduced: With the help of the amis-editor visual configurator, non-technical personnel can directly complete the configuration of the work order workflow interface through simple operations such as drag and drop and check. Compared with manually writing configuration code, the configuration efficiency is improved by more than 60%, and the configuration error rate is reduced by 90%, which can effectively shorten the business launch cycle.

[0020] (4) Reduced system maintenance costs: The unified visual configuration management interface and standardized interface design make the maintenance of AMIS configuration centralized and standardized, reducing the redundant work caused by decentralized maintenance; at the same time, the decoupling of workflow and display configuration not only reduces the risk in the system iteration process, but also reduces the maintenance workload by more than 70%. Attached Figure Description

[0021] Figure 1 A flowchart illustrating the workflow work order configuration method based on AMIS provided in this embodiment of the invention; Figure 2 This is an example diagram illustrating the management of multiple pre-configured AMIS templates in a backend database according to a specific embodiment of the present invention. Figure 3 This is an example diagram of a work order workflow configured in a specific embodiment of the present invention; Figure 4 This is an example diagram of the configuration interface provided to the user in a specific embodiment of the present invention, showing how the process is associated and bound with the AMIS template. Figure 5 This is an example of the working principle of the system architecture based on the aforementioned front-end platform in this invention. Detailed Implementation

[0022] To explain in detail the technical principles, specific implementable solutions, possible application scenarios, and achievable objectives and effects of the present invention, exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. It is understood that the embodiments described herein and the embodiments shown in the accompanying drawings are only used to more clearly illustrate the technical solutions of the present invention, and are therefore only examples intended to explain the present invention, and should not be construed as limiting the present invention. It should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0023] This invention aims to generate complex and dynamic workflow work order interfaces quickly and efficiently through pure configuration; by establishing a static mapping relationship between workflow stages and AMIS template JSON configuration, it supports flexible configuration of the display interface of workflow stages, realizing differentiated display and interaction of work orders under different projects and stages; it can significantly reduce development costs, improve delivery efficiency and system adaptability.

[0024] Explanation of technical terms involved in this invention: AMIS is a low-code front-end framework open-sourced and continuously maintained by Baidu. Its core goal is to quickly generate various pages through JSON configuration without writing a large amount of front-end code (HTML, CSS, JavaScript). It can be understood as a "page rendering engine"; simply provide JSON data that conforms to its specifications, and AMIS can render that JSON data into a fully functional and highly interactive web page.

[0025] Vue3 architecture: responsible for the overall project architecture, routing, state management (such as Pinia), build and packaging, and those highly customized and complex business components.

[0026] Amis engine: also known as Amis SDK, is responsible for quickly rendering standard middle and back-end pages, such as forms, tables, and charts, based on JSON configuration.

[0027] amis-editor Visual Configurator: This is a standalone visual configuration tool that allows non-front-end developers (such as product managers and operations staff) to easily configure the work order interface through drag-and-drop and check-in operations, and generate the corresponding amis JSON configuration.

[0028] The AmisRender.vue component is a bridge connecting the Vue world and the amis world. It passes Vue's reactive data and methods to amis and passes events from within amis back to Vue. In this invention, it serves as the core renderer, and its input properties include: (1) schema, which is the JSON configuration of amis, or simply a JSON object. This is the blueprint of the page, defining what components are available, how they are laid out, and what behaviors they exhibit; (2) data, which is the initial data context passed to the amis page, used to provide globally accessible shared data for the amis engine.

[0029] Please see Figure 1 This invention provides a workflow work order configuration method based on AMIS.

[0030] like Figure 1 As shown in the figure, an embodiment of the present invention provides a workflow work order configuration method based on AMIS, which includes the following steps: S1: Build the front-end platform.

[0031] Specifically, the front-end platform of this embodiment is constructed by embedding the aims engine in the Vue3 architecture, encapsulating an AmisRender.vue component as the core renderer, and introducing the amis-editor visual configurator to build a visual configuration management interface.

[0032] The basic working principle of the aforementioned front-end platform is as follows: Users can build a visual configuration management interface through the amis-editor visual configurator, and complete the configuration of the work order interface through convenient operations such as drag and drop and check boxes, generating the corresponding amis JSON configuration. The core renderer receives the "template JSON configuration" as its schema input attribute and the "work order basic data" as its data input attribute, and then internally calls the amis engine to complete the interface rendering, generating the display interface of the corresponding step in the work order.

[0033] S2: Two or more AMIS templates are pre-configured through the visual configuration management interface, and the corresponding template JSON configurations are stored according to the template identifier.

[0034] In other words, developers will utilize a visual configuration management interface to pre-configure multiple AMIS templates—that is, various types / styles of work order interfaces—through convenient operations such as drag-and-drop and checkboxes. Then, the template JSON configuration for each AMIS template will be associated and stored with its template identifier (such as a custom / system-generated unique template number). This means that the corresponding template JSON configuration data can be retrieved quickly and accurately using the template identifier.

[0035] In some specific implementations, step S2 is implemented through the following sub-steps: S21: In the template management section of the front-end platform, an AMIS template is pre-configured through an independent visual configuration management interface.

[0036] Here, users can configure each AMIS template visually, including but not limited to: interface layout, fields, buttons, and interface linkage logic. Once the content of each AMIS template is configured, corresponding template information will be automatically generated, including but not limited to: template identifier, template name, and creation time. Optionally, the template information can also be customized by the user, especially the "template identifier" and "template name," to meet personalized needs and facilitate subsequent retrieval.

[0037] S22: Store the template JSON configuration corresponding to the content of a configured AMIS template, as well as the template information and template identifier of the AMIS template, and the relationship between them to the backend database.

[0038] The above operations complete the pre-configuration and storage of an AMIS template, which can then be retrieved and applied to any workflow stage. Preferably, users can pre-configure multiple AMIS templates, providing more options for subsequent application retrieval and improving development efficiency.

[0039] For example, multiple pre-configured AMIS templates are used... Figure 2 The template format is stored in the backend database for easier management and maintenance. The template number serves as a unique identifier for each AMIS template; clicking on a template number allows users to visually view its corresponding AMIS template content, i.e., the template's JSON configuration. Preferably, the retrieved AMIS template content is displayed through the visual configuration management interface during operation, providing a clear view of the interface and allowing authorized users to directly modify the configuration as needed.

[0040] In other specific implementations, users pre-configure the corresponding AMIS templates for each stage of the target work order workflow in the visual configuration management interface. Preferably, information related to the "stage name" is used as the template identifier, and the AMIS templates corresponding to each stage are pre-stored in the backend database. Therefore, in the subsequent target work order workflow stage configuration phase, the association between each completed stage and its corresponding target AMIS template can be efficiently and accurately bound according to the correlation between the "template identifier" and the "stage name".

[0041] S3: When configuring a step in a workflow in the visual configuration management interface, a static mapping relationship between the step in the workflow and the specified template identifier is established by specifying the corresponding template identifier.

[0042] It is understandable that this step establishes the association and binding between each stage of the workflow and its target application's AMIS template.

[0043] In some specific implementations, step S3 is implemented through the following sub-steps: S31: In the process configuration, all the steps included in a workflow are configured through the visual configuration management interface.

[0044] One work order corresponds to one workflow, and one workflow contains multiple steps. In this embodiment, the user can efficiently configure all the steps in the workflow corresponding to a work order in a visual form through the visual configuration management interface. Here, the configuration only provides a workflow framework, initially defining the basic information of the workflow and its various steps, including but not limited to: workflow name, step name, workflow identifier, step identifier (which may be an ID), etc.; but it does not include the specific attribute configuration of each step in the work order's display interface.

[0045] For example, a work order workflow configured through the visual configuration management interface is as follows: Figure 3 As shown.

[0046] S32: When configuring the specific attributes of a step, the display interface of the step during work order processing is configured by selecting a template identifier.

[0047] For example, the configuration interface for associating and binding the "stage" provided to the user in the visual configuration management interface with the AMIS template of their target application is as follows: Figure 4 As shown.

[0048] For each step, you can specify the AMIS template to use through this step.

[0049] S33: Establish a static mapping relationship between the combined identifier consisting of the process identifier of the workflow and the stage identifier of the stage and the specified template identifier.

[0050] For each step, a static mapping relationship is established between "workflow process identifier + step identifier → template identifier" to achieve the association and binding between each step in the workflow and its target application's AMIS template.

[0051] For example, such as Figure 4 As shown, for Figure 3 In the "Low-voltage new installation" workflow, the "site inspection" step is configured to display the AMIS template "site inspection (1)-001" when the work order is processed or the details are viewed, and a static mapping relationship is established between "low-voltage new installation (workflow) + site inspection (step) → pending work order processing (site inspection (1)-001)".

[0052] Preferably, the static mapping relationships involved in all stages of the workflow are pre-stored according to the "workflow identifier," such as the process ID, or the work order identifier / work order name, and managed and stored uniformly in the form of a static mapping relationship table. In the subsequent stage of querying the static mapping relationship to confirm the AMIS template corresponding to the target stage, the AMIS template identifier of the target stage can be obtained more efficiently and accurately.

[0053] This embodiment extends the configuration attributes of the process template in the work order workflow through the above-mentioned S3 step, supports efficient, dynamic, flexible and visual configuration of the display interface of the process in the workflow, and can support the display needs of infinitely expanding multiple types of work order workflows without changing the existing system architecture and front-end code, significantly improving development efficiency and reducing maintenance costs.

[0054] S4: After receiving a click instruction triggered by a user corresponding to a step in the workflow, obtain the template JSON configuration corresponding to the step according to the static mapping relationship, and then construct the JSON configuration file of the step together with the work order basic data corresponding to the workflow.

[0055] After configuring the AMS templates for all or any stage of the workflow corresponding to a work order in the visual configuration management interface, you only need to trigger the "Submit" command, and the AMS-editor visual configurator will store the relevant configuration information.

[0056] In some specific implementations, the amis-editor visual configurator associates the JSON configuration file of a step in a workflow with the corresponding work order identifier / name (such as work order ID) or workflow process identifier / name and stores it in the backend database.

[0057] In some other specific embodiments, S4 is implemented through the following sub-steps: S41: When a user accesses a work order, they click on a step in the workflow corresponding to that work order and want to view the specific information of that step in the work order. S42: After receiving a click instruction carrying a work order identifier (such as work order ID), a workflow process identifier (such as process ID), and a step identifier (such as step ID), the front-end platform determines the corresponding template identifier based on the "process identifier" + "step identifier" by querying the static mapping relationship pre-stored in the back-end database.

[0058] If a static mapping table of all steps involved in a workflow is stored in advance according to the work order identifier / work order name or the workflow process identifier / process name, the target template identifier can be determined directly by querying the corresponding static mapping table, which is more efficient and accurate.

[0059] S43: Based on the determined template identifier, retrieve the corresponding template JSON configuration from the backend database; S44: Combine the obtained template JSON configuration with the basic data of the work order to construct the JSON configuration file for the clicked step.

[0060] S5: The aims engine renders and generates the corresponding display interface based on the JSON configuration file of the previous step.

[0061] In some specific implementations, the JSON configuration file of the clicked step needs to input the template JSON configuration as a JSON object and the basic work order data as the initial data context, and input them together into the AmisRender.vue component in the front-end platform. The AmisRender.vue component then calls the aims engine to dynamically generate and render the Vue component tree, thereby realizing the dynamic interface generation and interaction logic binding.

[0062] It's understandable that AMIS's JSON configuration is static, requiring data-driven logic to trigger page interaction based on different data. Therefore, in addition to obtaining AMIS's JSON configuration, the basic data corresponding to the current work order is also needed, so that the AMIS engine can render the required work order display effect and support the corresponding interaction logic.

[0063] In some other embodiments, step S5 is followed by: S6: Authorized users execute each step of the corresponding workflow based on the work order interface displayed in the Vue3 architecture by the aimms engine, and after entering the required information in the display interface of the specified step, the submission command of the corresponding step is triggered.

[0064] S7: The aims engine stores the relevant data generated by the interaction behavior of the corresponding stage to the backend database according to the submission instruction.

[0065] Please see Figure 5 Another embodiment of the present invention provides a workflow work order configuration system based on AMIS, based on the above embodiments.

[0066] This embodiment provides a workflow work order configuration system based on Amis, including a front-end platform with a visual configuration management interface. The front-end platform is built by embedding the Amis engine within the Vue3 architecture and introducing the Amis-editor visual configurator. Preferably, the front-end platform encapsulates the AmisRender.vue component as the core renderer, and the input attributes of the AmisRender.vue component include a JSON object (i.e., a schema) and an initial data context (i.e., data).

[0067] An example of how the system architecture based on the aforementioned front-end platform works is as follows: Figure 5 As shown.

[0068] The aforementioned front-end platform can implement the steps included in the workflow work order configuration method based on AMIS described in the above embodiments. The specific steps are not detailed here; please refer to the description in the previous embodiment for more information.

[0069] This embodiment constructs a visual, highly configurable, dynamic front-end platform. The Amis visual configuration management page provides graphical generation capabilities for the JSON configuration of work order workflows; the Vue project based on the AmisRender.vue component only requires JSON configuration to dynamically generate the corresponding interface content. Compared to the traditional generation method that requires hard coding, changes to the interface content only require modifying the JSON configuration, without modifying the Vue code or repackaging and deploying. The Vue project simply serves as a powerful runtime environment.

[0070] Another embodiment of the present invention provides a computer-readable storage medium based on any of the above embodiments.

[0071] This embodiment provides a computer-readable storage medium storing a computer program. When executed by the processor of the front-end platform, the computer program can implement the steps included in the workflow work order configuration method based on AMIS described in the first embodiment. The specific steps are not detailed here; please refer to the description in the previous embodiment for more information.

[0072] Those skilled in the art will understand that all or part of the processes in the above technical solutions can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the methods described above. After being executed by a processor, the program can also achieve the beneficial effects of the corresponding methods.

[0073] The storage medium can be a disk, optical disc, read-only memory (ROM), or random access memory (RAM), etc.

[0074] Based on any of the above embodiments, the present invention also provides a specific application example.

[0075] 1. Developers complete the development of the AmisRender.vue component in a Vue3 project by importing the amis SDK; and import amis-editor to build an amis visual configuration management page.

[0076] 2. Developers or implementers can create an AMS template JSON configuration for the "Site Survey" stage in the "Low-voltage New Installation" process through the template management section of the AMS visual configuration management page. The configuration includes user information, survey information, and metering point information. After storing the AMS template, the corresponding template number "ALP-XCKC-1-001" is obtained.

[0077] 3. In the process template designer, edit the "Attribute Configuration Page" of the "Site Survey" step in the "Low-voltage New Installation" process to configure the AMIS template used in this step: Select template number "ALP-XCKC-1-001" to establish a static mapping relationship between the "Site Survey" step in the "Low-voltage New Installation" process and template number "ALP-XCKC-1-001".

[0078] 4. If an authorized user clicks on the "On-site Inspection" step in the "Low-voltage New Installation" process through the work order link and wants to view the work order details for that step, then the static mapping relationship is queried based on the process ID and step ID to determine the corresponding AMIS template number as "ALP-XCKC-1-001". Based on the template number "ALP-XCKC-1-001", the JSON configuration of the corresponding AMIS template is retrieved from the backend database.

[0079] 5. Integrate the obtained AMIS template JSON configuration and basic work order data (such as work order ID, work order status, etc.) to construct a JSON configuration file.

[0080] 6. Pass the JSON configuration file to the AmisRender.vue component, call the amis SDK to render and generate a work order interface containing relevant survey information in the "Site Survey" stage. Users can fill in the survey results and other relevant data on the interface and submit it. The interaction is handled by the amis SDK and synchronized to the backend.

[0081] Although preferred embodiments of the invention have been described, those skilled in the art, upon understanding the basic inventive concept, can make other changes and modifications to the embodiments. Therefore, the appended claims are intended to cover the preferred embodiments and all equivalent modifications falling within the scope of protection defined by the claims and their equivalents. Clearly, those skilled in the art can make various alterations and variations to the invention without departing from its spirit and scope. If such modifications and variations fall within the scope of protection defined by the claims and their equivalents, the invention also intends to include them.

[0082] It should be noted that any reference signs placed between parentheses in the claims should not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention can be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware.

[0083] In this invention, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "multiple" means two or more, unless otherwise explicitly specified. The term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone.

[0084] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0085] In this specification, the use of terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refers to a specific feature, structure, material, or characteristic described in connection with that embodiment or example, which is included in at least one embodiment or example of the present invention. The illustrative expressions of the above terms in this specification should not be construed as necessarily referring to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0086] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A workflow work order configuration method based on AMIS, characterized in that, include: By embedding the aims engine into the Vue3 architecture and introducing the amis-editor visual configurator, a front-end platform with a visual configuration management interface is built. The visual configuration management interface pre-configures two or more AMIS templates and stores the corresponding template JSON configurations according to the template identifiers; When configuring a step in a workflow in the visual configuration management interface, a static mapping relationship between the step in the workflow and its corresponding template identifier is established by specifying the corresponding template identifier. Upon receiving a click instruction corresponding to a step in the workflow, the template JSON configuration corresponding to the step is obtained based on the static mapping relationship, and then together with the work order basic data corresponding to the workflow, the JSON configuration file of the step is constructed. The aimms engine renders and generates the corresponding display interface based on the JSON configuration file of the previous step.

2. The workflow work order configuration method based on AMIS as described in claim 1, characterized in that, The process of pre-configuring two or more AMIS templates through the visual configuration management interface and storing the corresponding template JSON configurations according to the template identifiers specifically includes: In the template management section of the front-end platform, the content and template information of an AMIS template are pre-configured through a separate visual configuration management interface; the content of an AMIS template includes the interface layout, fields, buttons, and interface linkage logic; the template information of an AMIS template includes the template identifier, template name, and creation time. The template JSON configuration, template information, and the association between the content of the aforementioned AMIS template and the template identifier are stored in the backend database.

3. The workflow work order configuration method based on AMIS as described in claim 1, characterized in that, When configuring a step in a workflow in the visual configuration management interface, a static mapping relationship is established between the step in the workflow and its corresponding template identifier by specifying a corresponding template identifier, specifically including: During the process configuration, all the steps included in a workflow are configured through the visual configuration management interface. When configuring the specific attributes of a step, a template identifier is selected to configure the display interface of the step during work order processing. Establish a static mapping relationship between a step in the workflow and its corresponding template identifier.

4. The workflow work order configuration method based on AMIS as described in claim 1, characterized in that, The establishment of a static mapping relationship between a stage in the workflow and its corresponding template identifier specifically involves: Establish a static mapping relationship between a combined identifier consisting of the process identifier of the workflow and the stage identifier of the stage, and a specified template identifier.

5. The workflow work order configuration method based on AMIS as described in claim 4, characterized in that, The step of obtaining the template JSON configuration corresponding to the first step based on the static mapping relationship specifically includes: Based on the workflow identifier and the stage identifier of the step in the click instruction, the corresponding template identifier is determined by querying the static mapping relationship; Based on the determined template identifier, obtain the corresponding template JSON configuration.

6. The workflow work order configuration method based on AMIS as described in claim 1, characterized in that, Also includes: After an authorized user enters the required information in the display interface of the first step, the submission instruction for the corresponding first step is triggered. The aims engine stores the relevant data generated by the interaction behavior corresponding to the first stage to the backend database according to the submission instruction.

7. The workflow work order configuration method based on AMIS as described in claim 1, characterized in that, The front-end platform encapsulates the AmisRender.vue component, which serves as the core renderer. The input properties of the AmisRender.vue component include a JSON object and an initial data context.

8. The workflow work order configuration method based on AMIS as described in claim 7, characterized in that, The aimms engine renders and generates the corresponding display interface based on the JSON configuration file of the first step, specifically including: On the front-end platform, the template JSON configuration in the JSON configuration file of the first step is used as a JSON object, and the basic work order data therein is used as the initial data context and input into the AmisRender.vue component; The AmisRender.vue component calls the aims engine to render and generate the display interface of the first step in the work order.

9. A workflow work order configuration system based on AMIS, characterized in that, It includes a front-end platform with a visual configuration management interface; the front-end platform is built by embedding the aims engine in the Vue3 architecture and introducing the amis-editor visual configurator; the front-end platform encapsulates the AmisRender.vue component as the core renderer, and the input properties of the AmisRender.vue component include a JSON object and an initial data context; The front-end platform can implement the steps included in the workflow work order configuration method based on AMIS as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, It stores a computer program, which, when executed by the processor of the front-end platform, can implement the steps included in the workflow work order configuration method based on AMIS as described in any one of claims 1 to 8.

Images