Invoice expansion method and device, electronic device, and storage medium
By introducing an extension plugin to the document interface to generate a custom page, the problem of the inability to expand the document approval function was solved, flexible document configuration was achieved, labor costs were reduced, and diverse internal needs of enterprises were met.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- 北京合思信息技术有限公司
- Filing Date
- 2022-12-14
- Publication Date
- 2026-07-21
AI Technical Summary
The document approval function of existing office software cannot be flexibly expanded, resulting in high costs for enterprises in document configuration and the inability to meet internal needs in a timely manner.
By introducing an extension plugin into the document interface, a custom page can be generated, including an extension tab. The description file uses a JSON data structure format, supports iframe embedding or React components, and performs validity checks, thus enabling the generation and display of the custom page.
It enables flexible expansion of the document interface, reduces labor costs, meets the diverse needs of internal business scenarios, and avoids redundant and secondary development.
Smart Images
Figure CN115756438B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of document processing technology, and more specifically, to a document expansion method, apparatus, electronic device, and storage medium. Background Technology
[0002] Document approval is a standard feature of modern enterprise office software. However, regardless of the type of office software, there will inevitably be scenarios where its built-in document approval function cannot meet or fulfill certain needs.
[0003] If software has a certain degree of openness, companies using it can leverage their own IT developers or outsource them to implement flexible functional expansion. Allowing third-party developers to flexibly extend the content of approval documents will optimize the configuration of corporate document approval processes and reduce manual intervention.
[0004] There is currently no effective solution to the problem of the inability to extend document configuration in related technologies. Summary of the Invention
[0005] The main objective of this application is to provide a document expansion method, device, electronic device, and storage medium to solve the problem of document configuration not being expandable.
[0006] To achieve the above objectives, according to one aspect of this application, a document expansion method is provided.
[0007] The document extension method according to this application includes:
[0008] Confirm document interface;
[0009] Based on the document interface, a custom page is generated through an extension plugin, wherein the custom page includes an extension tab related to the document interface.
[0010] Furthermore, the extension plugin includes a description file for the extension tab, and the description file adopts a JSON data structure format.
[0011] Furthermore, the step of generating a custom page based on the document interface through an extension plugin includes:
[0012] Based on the document interface, a custom page embedded in an iframe or a custom page of a React component is generated through the description file in the extended plugin.
[0013] Furthermore, the step of generating a custom page based on the document interface through an extension plugin includes:
[0014] Based on the document interface, the custom page is generated after the legality is verified by the extended plugin.
[0015] Furthermore, the verification validity includes:
[0016] Send a POST request to the reserved callback interface;
[0017] Based on the POST request, submit the content of the custom page and display the corresponding verification prompts according to the return value of the callback interface.
[0018] Furthermore, the method also includes:
[0019] When creating a new document, if the extended tab is not available in the custom page, the tab navigation bar will not be displayed on the document interface.
[0020] Furthermore, the method also includes:
[0021] When creating a new document, if the aforementioned extended tabs are injected into the custom page, the tab navigation bar will be displayed on the document interface.
[0022] To achieve the above objectives, according to another aspect of this application, a document expansion device is provided.
[0023] The document expansion device according to this application includes:
[0024] The "Determine" module is used to determine the document interface.
[0025] An extended generation module is used to generate custom pages based on the document interface through extended plugins, wherein the custom pages include extended tabs related to the document interface.
[0026] According to another aspect of this application, a storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
[0027] According to another aspect of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0028] In this embodiment, a method of determining the document interface is adopted. Based on the document interface, a custom page is generated through an extension plugin. Since the custom page includes an extension tab related to the document interface, the technical effect of document expansion is achieved, thereby solving the technical problem that document configuration cannot be expanded. Attached Figure Description
[0029] The accompanying drawings, which form part of this application, are used to provide a further understanding of the application and to make other features, objects, and advantages of the application more apparent. The illustrative embodiments and descriptions of this application are used to explain the application and do not constitute an undue limitation of the application. In the drawings:
[0030] Figure 1 This is a flowchart illustrating a document expansion method according to an embodiment of this application;
[0031] Figure 2 This is a schematic diagram of the structure of a document expansion device according to an embodiment of this application;
[0032] Figure 3 This is a schematic diagram of a custom page in the document expansion method according to an embodiment of this application;
[0033] Figure 4 This is a schematic diagram of the legality verification prompt of a custom page in the document expansion method according to an embodiment of this application. Detailed Implementation
[0034] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.
[0035] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0036] In this application, the terms "upper," "lower," "left," "right," "front," "rear," "top," "bottom," "inner," "outer," "middle," "vertical," "horizontal," "lateral," and "longitudinal" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. These terms are primarily for the purpose of better describing this application and its embodiments, and are not intended to limit the indicated device, element, or component to having a specific orientation, or to be constructed and operated in a specific orientation.
[0037] Furthermore, in addition to indicating location or positional relationship, some of the aforementioned terms may also have other meanings. For example, the term "above" may also be used in some cases to indicate a certain dependency or connection relationship. Those skilled in the art can understand the specific meaning of these terms in this application based on the specific circumstances.
[0038] Furthermore, the terms "installation," "setup," "equipped with," "connection," "linking," and "socketing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral structure; 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, or an internal connection between two devices, components, or parts. Those skilled in the art can understand the specific meaning of these terms in this application based on the specific circumstances.
[0039] The inventors discovered during their research that if service providers need to expand functionality or create new approval documents for each document approval process, it would increase labor costs and fail to meet the company's internal document approval needs in a timely manner.
[0040] This application provides a mechanism for extending the software interface, allowing enterprise developers or third-party developers to extend custom views and functions into the document approval function by implementing external plugins without modifying the software code, thereby flexibly meeting the needs of internal business scenarios.
[0041] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.
[0042] like Figure 1 The diagram shown is a flowchart of a user virtual asset management method in an embodiment of this application. The method includes the following steps S110 to S120:
[0043] Step S110: Determine the document interface.
[0044] On the user's end, the document interface is selected and confirmed according to actual needs. This document interface is related to the actual business operations; for example, it might be a confirmation interface for expense approval documents. The document interface can include multiple preset tabs, which can be fixed or customized by third parties as needed.
[0045] Users can also switch between different document interfaces according to the actual business scenario, and this application does not impose specific restrictions.
[0046] Step S120: Based on the document interface, generate a custom page through an extension plugin, wherein the custom page includes an extension tab related to the document interface.
[0047] Based on the previously selected document interface, a custom page can be generated on the user's end through relevant extension plugins. The custom page includes extension tabs related to the document interface. In other words, the custom page is displayed as an extension tab on the document interface.
[0048] It's important to note that you can generate approval documents through the custom page. These approval documents include, but are not limited to, expense reimbursements and payment requests.
[0049] Third-party developers are typically allowed to flexibly extend the content of approval documents, acting as providers of such extension plugins and custom pages. These third-party developers can be internal operational personnel or external developers; no specific limitations are imposed in the embodiments of this application.
[0050] The above extension methods enable the expansion of custom pages on the user end, and these custom pages are displayed as extension tabs related to the document interface, eliminating the need for repeated development or secondary development specifically for changes or additions in business scenarios.
[0051] As can be seen from the above description, this application achieves the following technical effects: by defining the document interface, a custom page is generated based on the document interface through an extension plugin. Since the custom page includes extension tabs related to the document interface, the document can be expanded, thereby solving the technical problem that the document configuration cannot be expanded.
[0052] In this preferred embodiment, the extension plugin includes a description file for the extension tab, and the description file adopts a JSON data structure format.
[0053] In practice, an extensible interface is provided on the user-side visual interface. For example, users can open tabs implemented by third-party developers, and the entire page content is provided by the third-party developers.
[0054] When implementing third-party tabs, developers need to provide a description file that describes the tab's behavior. This description file is provided in JSON data structure, and one possible implementation is as follows:
[0055]
[0056]
[0057] Using the aforementioned description file, business data can be imported according to actual needs, and custom pages can be generated based on the aforementioned extension plugin.
[0058] As a preferred embodiment, generating a custom page based on the document interface via an extension plugin includes: generating a custom page embedded in an iframe or a custom page of a React component based on the document interface via the description file in the extension plugin.
[0059] like Figure 3 As shown, the document interface provides more tabs on top of the existing form interface, each of which is extended by a third-party developer. For example... Figure 3 The "Document Details" is the document interface provided by the user client itself, while the "Remuneration Details" is a custom page provided by a third-party developer.
[0060] Based on the document interface, a custom page is attached to the document tab through the description file in the extension plugin. The page content is an independent page embedded in an iframe or a React component provided by the extension.
[0061] As is understandable, iframe embedding, also known as embedded frame, allows you to embed the frame and content of a webpage into an existing webpage.
[0062] For React components, you can build modular components, combine them, and finally assemble them into a complex application.
[0063] As a preferred embodiment, generating a custom page based on the document interface via an extension plugin includes: generating the custom page based on the document interface after verifying its legality through the extension plugin.
[0064] For some third-party extensions, it may be necessary to perform certain checks when submitting documents to ensure that the form content filled in on the third-party tab is also valid.
[0065] like Figure 4 As shown, you can also add a step to validate the content in a custom page.
[0066] In a preferred embodiment, the verification includes: sending a POST request to a reserved callback interface; submitting content from a custom page based on the POST request; and displaying a corresponding verification prompt based on the return value of the callback interface.
[0067] In practice, when a document is submitted, the software will send a POST request to the callback address reserved by the third-party developer, submit the content of the third-party extended tab in this document, and display the corresponding prompts based on the interface return value.
[0068] The following is a data format for the return value in one optional implementation:
[0069]
[0070] As a preferred embodiment, the method further includes: when creating a new document, if the extended tab is not present in the custom page, then the navigation bar of the tab is not displayed on the document interface.
[0071] In practice, when creating a new document, if there is no extended tab, the tab navigation bar will not be displayed.
[0072] As a preferred embodiment, the method further includes: when creating a new document, if the extended tab is injected into the custom page, then displaying the tab's navigation bar on the document interface.
[0073] In practice, if an extension is injected with tabs, the tab navigation bar will be displayed, and the document page that comes with the user's client will be named "Document Details".
[0074] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.
[0075] According to embodiments of this application, an apparatus for implementing the above method is also provided, such as... Figure 2 As shown, the device 200 includes:
[0076] Module 210 is used to determine the document interface;
[0077] The extension generation module 220 is used to generate a custom page based on the document interface through an extension plugin, wherein the custom page includes an extension tab related to the document interface.
[0078] The extension plugin includes a description file for the extension tab, and the description file uses a JSON data structure format.
[0079] The step of generating a custom page based on the document interface through an extension plugin includes: generating a custom page embedded in an iframe or a custom page of a React component based on the document interface through the description file in the extension plugin.
[0080] The step of generating a custom page based on the document interface through an extension plugin includes: generating the custom page based on the document interface after verifying its legality through the extension plugin.
[0081] The verification process includes: sending a POST request to the reserved callback interface; submitting content from a custom page based on the POST request; and displaying corresponding verification prompts based on the return value of the callback interface.
[0082] The method further includes: when creating a new document, if the extended tab is not present in the custom page, then the tab navigation bar is not displayed on the document interface.
[0083] The method further includes: when creating a new document, if the extended tab is injected into the custom page, then displaying the tab's navigation bar on the document interface.
[0084] In the determination module 210 of this application embodiment, the user selects and determines the document interface according to actual needs. It can be understood that the document interface is related to actual business, for example, the determined document interface is the expense approval document interface.
[0085] Users can also switch between different document interfaces according to the actual business scenario, and this application does not impose specific restrictions.
[0086] In this embodiment of the application, the extended generation module 220 can generate a custom page on the user end based on the previously selected document interface through related extended plugins. The custom page includes an extended tab related to the document interface. In other words, the custom page is displayed on the document interface as an extended tab.
[0087] The above extension methods enable the expansion of custom pages on the user end, and these custom pages are displayed as extension tabs related to the document interface, eliminating the need for repeated development or secondary development specifically for changes or additions in business scenarios.
[0088] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device, or fabricating them separately as individual integrated circuit modules, or fabricating multiple modules or steps as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.
[0089] To better understand the methods in the embodiments of this application, such as Figure 3 The diagram shown is a schematic of a custom page in a document expansion method according to an embodiment of this application.
[0090] Define the document interface; based on the document interface, generate a custom page using an extension plugin, wherein the custom page includes extension tabs related to the document interface.
[0091] The extension plugin includes a description file for the extension tab, and the description file adopts a JSON data structure format.
[0092] On the document interface, in addition to the existing form interface, more tabs are provided, each of which is extended by a third-party developer. For example... Figure 3 The "Document Details" is the document interface provided by the user client itself, while the "Remuneration Details" is a custom page provided by a third-party developer.
[0093] The process of generating a custom page based on the document interface via an extension plugin includes: generating a custom page embedded in an iframe or a custom page using a React component based on the document interface via the description file in the extension plugin.
[0094] Figure 4 This is a schematic diagram of the legality verification prompt of a custom page in the document extension method according to an embodiment of this application; the step of generating a custom page based on the document interface through an extension plugin includes: generating the custom page after verifying its legality through the extension plugin based on the document interface.
[0095] When a document is submitted, the software will send a POST request to the callback address reserved by the third-party developer, submitting the content of the third-party extended tab in this document, and displaying corresponding prompts based on the interface return value. And as... Figure 4 The "exclamation mark reminder" shown is displayed on the user's device.
[0096] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A document expansion method, characterized in that, The method includes: Define the document interface, which includes multiple preset tabs; Based on the document interface, a custom page is generated through an extension plugin. The custom page includes an extension tab related to the document interface, and the custom page is displayed as an extension tab on the document interface. The extension plugin includes a description file for the extension tab, and the description file adopts a JSON data structure format. The description file defines the tab title, unique identifier, sorting weight, and content definition. The content definition specifies the resource path URL and the specific implementation type, i.e., REACT_COMPONENT or IFRAME, according to different devices and document status. Different devices are WEB or APPLET. The step of generating a custom page based on the document interface through an extension plugin includes: generating a custom page embedded in an iframe or a custom page of a React component based on the document interface through the description file in the extension plugin; The step of generating a custom page based on the document interface via an extension plugin includes: generating the custom page after verifying the validity of the document interface through the extension plugin; the validity verification includes: Send a POST request to the reserved callback interface; Based on the POST request, submit the content of the custom page and display the corresponding verification prompts according to the return value of the callback interface.
2. The method according to claim 1, characterized in that, The method further includes: When creating a new document, if the extended tab is not available in the custom page, the tab navigation bar will not be displayed on the document interface.
3. The method according to claim 1, characterized in that, The method further includes: When creating a new document, if the aforementioned extended tabs are injected into the custom page, the tab navigation bar will be displayed on the document interface.
4. A document expansion device, characterized in that, The device includes: The determination module is used to determine the document interface, which includes multiple preset tabs; An extension generation module is used to generate custom pages based on the document interface through extension plugins. These custom pages include extension tabs related to the document interface, and are displayed as extension tabs on the document interface. The extension plugin includes a description file for the extension tabs, and the description file uses a JSON data structure format. This description file defines the tab title, unique identifier, sorting weight, and content definition. The content definition specifies the resource path URL to be used based on different devices and document statuses, and the specific implementation type is either REACT_COMPONENT or IFRAME. Different devices are designated as WEB or APPLET. The step of generating a custom page based on the document interface through an extension plugin includes: generating a custom page embedded in an iframe or a custom page of a React component based on the document interface through the description file in the extension plugin; The step of generating a custom page based on the document interface via an extension plugin includes: generating the custom page after verifying the validity of the document interface through the extension plugin; the validity verification includes: Send a POST request to the reserved callback interface; Based on the POST request, submit the content of the custom page and display the corresponding verification prompts according to the return value of the callback interface.
5. An electronic device, comprising: processor; as well as A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the method of any one of claims 1 to 3.
6. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of applications, cause the electronic device to perform the method of any one of claims 1 to 3.