Page element processing method and device

Abstract

The invention discloses a page element processing method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the steps of obtaining page processing data, wherein the page processing data comprises a business identifier, a to-be-processed page element identifier and a processing type of a page element; verifying the page processing data according to the service identifier and the processing type; under the condition that the verification is passed, generating an auditing request corresponding to the page element identifier according to the page processing data, and auditing the page processing data according to the auditing request; and in response to passing of the audit, generating published information corresponding to the page element, and publishing the page element according to the published information. According to the implementation mode, the workload of APP page design is reduced, the page processing efficiency is improved, and the situation that other page functions are affected when page elements are modified is avoided.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a method and device for processing page elements. Background Art

[0002] Page elements refer to titles, buttons, text, links, and images in an APP (application). Currently, the page content of an APP is implemented through a fixed design. To change or add any element in the page, you need to redesign the page and modify the page code accordingly, and you need to wait for the application iteration version to be implemented. This not only increases the workload of APP page design, but also reduces the processing efficiency of page elements; and directly modifying the page code may also affect the function of the APP page. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a method and device for processing page elements. By decoupling page elements from page codes, when page elements need to be processed, they can be verified and audited according to corresponding page processing data, and the page elements can be released after verification and audit. It can be seen that the embodiment of the present invention does not need to wait for the iterative version of the application to modify or change the page elements, nor does it need to modify the page code, thereby reducing the workload of APP page design, improving the efficiency of page processing, and avoiding the impact of other page functions when the page elements are modified.

[0004] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present invention, a method for processing page elements is provided. A method for processing page elements in an embodiment of the present invention comprises: obtaining page processing data, the page processing data comprising a business identifier, an identifier of a page element to be processed, and a processing type of the page element;

[0005] Verify page processing data based on business identification and processing type;

[0006] If the verification is passed, a review request corresponding to the page element identifier is generated according to the page processing data, so as to review the page processing data according to the review request;

[0007] In response to the review being passed, publishing information corresponding to the page element is generated, and the page element is published according to the publishing information.

[0008] Optionally, publish page elements according to the publishing information, including:

[0009] Generate a grayscale release page based on the grayscale release page elements of the release information;

[0010] Compare the pixels of the first image corresponding to the grayscale published page with the second image corresponding to the initial page to determine the changed content;

[0011] Determine the test results of the grayscale release page based on the changed content;

[0012] In response to the test result being that the test passes, the page element is officially released.

[0013] Optionally, the page processing data is verified according to the business identifier and the processing type, including:

[0014] When the processing type is a modification type, determine whether the page processing data corresponds to an existing business module based on the business identifier; if so, determine whether the page element identifier exists in a pre-stored data dictionary, the data dictionary including multiple page element identifiers corresponding to each existing business module; if so, determine that the page processing data verification has passed.

[0015] Optionally, verifying the page processing data according to the processing type includes: if the processing type is a newly added type, determining whether the page processing data corresponds to an existing business module according to the business identifier;

[0016] If not, the format of the page processing data is verified; if the format verification passes, it is determined that the page processing data verification passes.

[0017] Optionally, after generating a review request corresponding to the page element identifier according to the page processing data, and before generating the publishing information corresponding to the page element, the method further includes: reviewing the page processing data according to the review request through a multi-level first review role, wherein the multi-level first review roles correspond to different first user permissions respectively;

[0018] Optionally, after generating the publishing information corresponding to the page element and before publishing the page element according to the publishing information, the method further includes:

[0019] The published information is reviewed through multi-level second review roles, and the multi-level second review roles correspond to different second user permissions respectively.

[0020] Optionally, the method further comprises:

[0021] Configure the page controlled element sets corresponding to multiple user roles;

[0022] When rendering the user interface corresponding to the first review role and / or the second review role, intercepting other controlled page elements outside the page controlled element set according to the page controlled element set corresponding to the first review role and / or the second review role respectively;

[0023] Optionally, page processing data is audited through multiple levels of first audit roles, including: determining the audit order of the multiple levels of first audit roles based on the first user authority; looping through the following steps in the first audit order until the subordinate audit role is the last first audit role or the audit fails: in response to the current level audit passing, forwarding the audit request and the current level audit result to the subordinate audit role.

[0024] Optionally, the method further includes: configuring a state of the page processing data according to a processing progress of the page processing data.

[0025] Optionally, in response to the page processing data passing the review of the second review role, the page processing data is configured to be in a to-be-published state; and further comprising: integrating multiple page processing data in the to-be-published state, and publishing page elements according to the integration result.

[0026] To achieve the above purpose, according to another aspect of an embodiment of the present invention, a device for processing page elements is provided. A device for processing page elements in an embodiment of the present invention comprises: an acquisition module, a verification module, an audit module and a publishing module; wherein:

[0027] The acquisition module is configured to: acquire page processing data, the page processing data including a business identifier, an identifier of a page element to be processed, and a processing type of the page element;

[0028] The verification module is configured as follows: verifying the page processing data according to the business identifier and processing type, and triggering the audit module if the verification passes;

[0029] The audit module is configured to: generate an audit request corresponding to the page element identifier according to the page processing data, so as to audit the page processing data according to the audit request, and trigger the publishing module if the audit is passed;

[0030] The publishing module is configured to generate publishing information corresponding to the page elements and publish the page elements according to the publishing information.

[0031] To achieve the above-mentioned purpose, according to another aspect of an embodiment of the present invention, an electronic device for processing page elements is provided. An electronic device for processing page elements in an embodiment of the present invention comprises: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement a method for processing page elements in an embodiment of the present invention.

[0032] To achieve the above object, according to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided. A computer-readable storage medium of an embodiment of the present invention stores a computer program, which, when executed by a processor, implements a page element processing method of an embodiment of the present invention.

[0033] To achieve the above objective, according to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, which, when executed by a processor, implements a page element processing method of an embodiment of the present invention.

[0034] One embodiment of the above invention has the following advantages or beneficial effects: by decoupling the page elements from the page code, when the page elements need to be processed, they can be verified and audited according to the corresponding page processing data, and the page elements can be released after the verification and audit are passed. It can be seen that the embodiment of the present invention does not need to wait for the application iteration version to realize the modification or change of the page elements, nor does it need to modify the page code, thereby reducing the workload of APP page design, improving the efficiency of page processing, and avoiding the impact of other page functions when the page elements are modified.

[0035] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0037] Figure 1 is a schematic diagram of main steps of a method for processing page elements according to an embodiment of the present invention;

[0038] Figure 2 is a schematic diagram of main steps of another method for processing page elements according to an embodiment of the present invention;

[0039] Figure 3 is a schematic diagram of main modules of a device for processing page elements according to an embodiment of the present invention;

[0040] Figure 4 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0041] Figure 5 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0042] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0043] It should be pointed out that the embodiments of the present invention and the technical features therein may be combined with each other without conflict.

[0044] Figure 1 A method for processing page elements according to an embodiment of the present invention mainly includes the following steps S101 to S104:

[0045] Step S101: Acquire page processing data, where the page processing data includes a business identifier, an identifier of a page element to be processed, and a processing type of the page element.

[0046] In an embodiment of the present invention, the page elements in the pages corresponding to each business module in the APP are decoupled from the page code, and the business module (corresponding to the business identifier) ​​and the page element are stored in the database in correspondence with the identifier. For example, a digital currency APP includes business functions such as payment, transfer, and wallet management, where each business function corresponds to a business module and a corresponding page. In order to facilitate the processing of APP page elements, the page elements of each business module are stored in the database in advance in the form of a data table shown in Table 1 according to their respective identifiers, forming a data dictionary corresponding to the APP, which includes multiple page element identifiers corresponding to each existing business module in the APP. In Table 1, the business module corresponds to the business identifier, and the element name is the page element identifier.

[0047] Table 1

[0048] Business Module Page Identification Element Name Chinese English A HomePage cancel Cancel Cancel B HomePage bindBankCard Unbind card Bind the Card …… …… …… …… ……

[0049] When the page function or page style needs to be updated, the page processing data can be submitted according to the page element identifier of the part to be updated and the processing type of the page element. For example, when the "cancel" element of business module A needs to be modified, the page processing data shown in Table 2 can be submitted. For another example, when a page element corresponding to the "logout card" needs to be added to business module B, the page processing data shown in Table 3 can be submitted. It can be understood that in Tables 2 and 3, the element name is the page element identifier, and the page code is the page identifier.

[0050] Table 2

[0051]

[0052] Table 3

[0053]

[0054] After the developer submits the page processing data, the device capable of processing the page elements provided in the embodiment of the present invention obtains the page processing data, and performs operations such as verification and review on the page processing data. After the verification and review are passed, the corresponding page elements are released. This process is described in detail in the subsequent embodiments.

[0055] Step S102: Verify the page processing data according to the business identifier and the processing type. If the verification passes, execute step S103. If the verification fails, perform error processing.

[0056] According to the implementation methods corresponding to Table 2 and Table 3 above, it can be seen that the processing types of page elements in the embodiment of the present invention include modification and addition. In the case where the processing type is a modification type, it can be determined whether the page processing data submitted this time corresponds to an existing business module based on the business identifier included in the page processing data. If so, it is determined whether the page element exists in a pre-stored data dictionary, and the data dictionary includes multiple page element identifiers corresponding to each existing business module; if the page element identifier exists in the data dictionary, it is determined that the page processing data verification has passed. It can be understood that the business identifier corresponds to the identifier of the business module in Tables 1-3, and the business identifier of business module A is "A"; the page element identifier corresponds to the "element name" in Tables 1-3. Since the modification type is to modify the page elements corresponding to the existing business functions, the page element identifier in the page processing data needs to correspond to the existing business module. If the page element identifier cannot correspond to the existing business module, an error processing is performed to enable the developer to modify and resubmit the page processing data. If the page element identifier can correspond to an existing business module, it is further determined whether the page element identifier exists in a pre-stored data dictionary. The data dictionary may be a data table storing multiple page element identifiers corresponding to each existing business module. If so, it means that the page element identifier to be modified submitted this time is correct, that is, the page processing data verification is determined to be passed; if the page element identifier does not exist in the data dictionary, it also means that the page element identifier in the page processing data submitted this time is wrong. In this case, an error is also reported to enable the developer to modify the page processing data in time and resubmit it.

[0057] In addition, when the processing type is a new type, in order to avoid duplication of the newly added page elements with the existing business modules, first determine whether the page processing data corresponds to the existing business module based on the business identifier. If so, it means that the existing business module may already have corresponding page elements, and the newly added page elements will be repeated. At this time, an error can be reported. Only when the business identifier does not correspond to the existing business module, the format of the page processing data is further verified. If the format verification passes, it means that the page processing data submitted this time meets the format requirements, and the page processing data verification is determined to pass; otherwise, if the page processing data does not meet the format requirements, an error is reported to allow the developer to modify the format and resubmit the page processing data.

[0058] By verifying the page processing data of different processing types as described above, the compatibility of the page processing data submitted this time with the existing business modules is guaranteed. On the one hand, it reduces the workload of subsequent audits, and on the other hand, it is also conducive to the efficient release of page elements. In addition, error reporting is performed when the verification fails, which can also remind developers to modify the corresponding page processing data in a timely manner, which is conducive to improving the efficiency of page element processing. It should be understood that the page processing data may include only one type of page element identifier, either a modified type or a newly added type, or may include both modified type and newly added type page element identifiers.

[0059] In addition, after the page processing data is verified according to the processing type, the verification data can be inserted into the log table, that is, the data that successfully verified or the data that failed to verify are inserted into the log table, so that the page update record can be traced back according to the log table later.

[0060] Step S103: Generate an audit request corresponding to the page element identifier according to the page processing data, so as to audit the page processing data according to the audit request; if the audit is passed, execute step S104, and if the audit is not passed, perform rejection processing.

[0061] After the page processing data is verified, an audit request can be generated according to the page processing data. In addition, in an embodiment of the present invention, during the audit process, the status of the page processing data can also be configured according to the processing progress of the page processing data, so as to manage the page processing data according to the status. Exemplarily, before entering the audit, the status of the page processing data is configured as a draft status. Then, according to the audit request, the page processing data is audited by a multi-level first audit role, wherein the multi-level first audit roles correspond to different first user permissions. During the audit process, the audit order of the multi-level first audit roles is determined according to the first user permissions, and then the page processing data corresponding to the audit request is audited in sequence according to the audit order, that is, after the local audit is passed, the audit request and the audit result of this level are forwarded to the subordinate audit role. Here, the first user permission of the subordinate audit role is higher than the first user permission of the audit role of this level. If the audit of this level fails, it is rejected and the audit request is no longer forwarded to the subordinate audit role. After the last first review role reviews, it can be determined whether the page processing data submitted this time has passed the review based on the review result of the first review role. That is, when the last first review role reviews and passes, it is determined that the page processing data has passed the review, otherwise it is determined that the page processing data has not passed the review. For example, the page processing data can be reviewed by two levels of first review roles, which are divided into preliminary review and re-review. After entering the review process, the status of the page processing data is updated from the draft status to the review status. If the preliminary review passes, it enters the re-review. If the preliminary review fails, the page processing data is returned to the draft status. If the preliminary review is successful, it enters the re-review process. If the re-review passes, it can be determined that the review has passed. Otherwise, it is determined that the page processing data has not passed the review, and the page processing data is rejected and returned to the draft status. After the review passes, the status of the page processing data is updated from "under review" to "prepared for release". It can be understood that although the two-level review is taken as an example here, in the specific implementation process, more review levels can be set according to actual needs to perform multi-level review on the page processing data.

[0062] Step S104: Generate publishing information corresponding to the page element, and publish the page element according to the publishing information.

[0063] After passing the multi-level review of the first review role, the release information corresponding to the page element can be generated. Corresponding to the review request, the embodiment of the present invention can also review the release information through the multi-level second review role, and the multi-level second review role corresponds to different second user permissions. Among them, the first review role and the second review role can correspond to the same user or different users. During the review process, the status of the release information (page processing data to be released) can be configured as the "release review" status. In the review process of multiple second review roles, the review results of this level and the release information can be forwarded to the lower-level review role after the review of this level is passed in accordance with the review order of the multi-level second review roles. If the review of this level fails, the rejection process is performed, so that the release information is returned from the release review state to the release preparation state. After the page processing data passes through the roles of multiple second review roles, its status can be updated to the pending release state, so that the release information can be integrated and processed according to the status.

[0064] Specifically, during the APP update process, there may be a situation where multiple developers submit page processing data in parallel. The page element processing device provided in the embodiment of the present invention can process different page processing data in parallel. After passing verification and review, these multiple page processing data are multiple page processing data (publishing information) in the state to be published. In the implementation mode of the present invention, these multiple page processing data in the state to be published are integrated, and the page is published according to the integration result, so as to realize the one-time publishing of page elements corresponding to multiple page processing data, and improve the publishing efficiency of page elements.

[0065] In addition, in order to facilitate the configuration and management of different roles, and to facilitate different review roles to view content within their respective permissions, in an embodiment of the present invention, a set of page controlled elements corresponding to multiple user roles can be configured; when rendering the user interface corresponding to the first review role and / or the second review role, other controlled page elements outside the page controlled element set are intercepted according to the page controlled element set corresponding to the first review role and / or the second review role.

[0066] Among them, the page controlled elements include buttons, fields, pictures, links and other page elements that are controlled to jump or displayed (visible or hidden). In an embodiment of the present invention, the corresponding relationship between user roles, user permissions and page controlled elements can be pre-configured, such as configuring the page controlled element set corresponding to each user role in the form of an array, the array name corresponds to the user role, and the elements in the array are the identifiers of the page controlled elements that the user role has the authority to view or trigger. When a user logs in through account information, the corresponding user role can be determined according to the account information, and then the page controlled element set corresponding to the user role can be determined. Then, according to the intersection of the page element corresponding to the page to be jumped and the page controlled element corresponding to the user role, the user interface corresponding to the user role can be rendered to intercept the controlled page elements other than the page controlled elements. Among them, the page to be jumped is the next page to be jumped according to the triggered page element after the user triggers the page element this time. For example, after the user enters the account information (account number and password) and triggers the "Login" button, the page to be jumped is the user's homepage. For the first audit role and the second audit role with audit authority, their controlled element sets include "audit" related page elements, so the rendered user homepage includes "audit" related buttons. For the user role that does not have audit authority, since its controlled element set does not include "audit" related page elements, the rendered user homepage does not include "audit" related buttons. For another example, when rendering user interfaces for the first audit role and / or the second audit role of different levels, only the "superior audit result" field is displayed in the user interface corresponding to the primary audit role, but this field cannot be triggered, while for the review audit role, the "superior audit result" field is displayed on its user interface, and this field can also be triggered. Therefore, the embodiment of the present invention realizes the rendering of corresponding user interfaces for user roles with different permissions based on user roles. On the one hand, this allows users to only focus on page elements within their authority range, thereby improving user processing efficiency; on the other hand, by decoupling the control strategy of page elements from the page code, it is convenient to modify the control strategy of page elements, and also simplifies the APP page update process.

[0067] In addition, when publishing page elements according to the release information, the embodiment of the present invention may first perform grayscale publishing, and then formally publish after the grayscale publishing test passes. Specifically, the page elements may first be grayscale published according to the release information, and a grayscale publishing page may be generated. Then, a pixel comparison is performed between the first image corresponding to the grayscale publishing page and the second image corresponding to the initial page to determine the changed content, and the test result of the grayscale publishing page is determined according to the changed content.

[0068] Among them, the initial page is the page before processing corresponding to the page processing data of this time, and its picture form is the second image. After the grayscale publishing page is generated, the page is screenshotted to obtain the first image corresponding to the grayscale publishing page. By comparing the pixels of the first image and the second image, the part with differences between the first image and the second image can be determined, and this part is the change content corresponding to the grayscale publishing, and then the test result of the grayscale publishing page can be further determined according to the change content. Exemplarily, the test result of the grayscale publishing page can be determined according to one or more of the following factors: ① Determine the test result according to the position of the change content in the first image. If the position is not within the preset range, it is determined that the grayscale publishing page test fails. For example, when it is necessary to add page elements such as fields or pictures at a specific position of the page, the newly added page elements should only appear at a specific position without affecting the position or style of other elements in the page. Therefore, the test result of the grayscale publishing page can be determined according to the position of the change content. ② Determine the test result according to the size of the area corresponding to the change content. If the size of the area corresponding to the change content does not correspond to the preset area range, it is determined that the grayscale publishing page test fails. For example, when modifying the image elements in the page, the area range occupied by the modified image (preset area range) can be designed in advance, and then the modification position of the image element can be preliminarily determined based on the area size corresponding to the changed content, thereby determining the test result of the grayscale release page. ③ Determine the test result based on the difference between the changed content and the standard image. Among them, the standard image is the design image actually designed by the page designer corresponding to the target performance effect. The difference can be calculated according to the similarity matching algorithm, such as calculating the difference between the changed content and the standard image according to their color histograms, or calculating the difference between the two according to aHash, pHash, etc. When the difference between the changed content and the standard image is greater than the preset threshold, it is determined that the grayscale release page test has failed, and the grayscale release page test is determined to have passed only when the difference is less than or equal to the preset threshold.

[0069] Therefore, the embodiment of the present invention uses image comparison to officially release page elements only after determining that the grayscale release page test has passed, thereby decoupling the page testing method from the page design and development process. Compared with the code testing method used in related technologies, there is no need to modify the corresponding test code every time the page is modified, thereby reducing testing costs and improving testing efficiency.

[0070] The following takes the two-level review of both the review request and the published information as an example to describe in detail the page element processing method provided by the embodiment of the present invention. Figure 2 As shown, the method may include the following steps:

[0071] Step S201: Obtain page processing data, which includes a business identifier, an identifier of a page element to be processed, and a processing type of the page element. If the processing type is a modification type, execute step S202; if the processing type is a new addition type, execute step S204.

[0072] Step S202: Determine whether the page processing data corresponds to an existing business module according to the business identifier. If yes, execute step S203; otherwise, execute step S207.

[0073] Step S203: Determine whether the page element identifier exists in a pre-stored data dictionary, where the data dictionary includes multiple page element identifiers corresponding to each existing business module. If yes, execute step S206; if not, execute step S207.

[0074] Step S204: Determine whether the page processing data corresponds to an existing business module according to the business identifier, if yes, execute step S207, otherwise execute step S205.

[0075] Step S205: Verify the format of the page processing data. If the verification passes, execute step S206; otherwise, execute step S207.

[0076] Step S206: Determine whether the page processing data verification has passed, and configure the page processing data to a draft state, and proceed to step S208.

[0077] Step S207: Perform error processing and end the current process.

[0078] Step S208: Generate an audit request corresponding to the page element identifier based on the page processing data, and send the audit request to the first primary audit role, so that the first primary audit role audits the audit request and configures the page processing data to the under-audit state; if the audit is passed, execute step S209, otherwise execute step S211.

[0079] Step S209: Send the audit result and audit request of the first primary audit role to the first review audit role, so that the first review audit role reviews the audit request; if the audit is passed, execute step S210, otherwise execute step S211.

[0080] Step S210: Generate publishing information corresponding to the page element, and configure the state of the page information to be a publishing ready state, and then proceed to step S212.

[0081] Step S211: reject the review request, update the status of the page processing data to the draft status, and end the current process.

[0082] Step S212: Send the published information to the second primary review role, so that the second primary review role reviews the published information and configures the status of the published information as a published review status. If the review is passed, execute step S213, otherwise execute step S217.

[0083] Step S213: Send the audit result and the published information of the second primary audit role to the second review audit role, so that the second review audit role reviews the published information. If the review is passed, execute step S214, otherwise execute step S217.

[0084] Step S214: configure the page processing data to be in a state to be published, integrate multiple page processing data in a state to be published, and generate a grayscale publishing page according to the integration result; perform pixel comparison between the first image corresponding to the grayscale publishing page and the second image corresponding to the initial page to determine the changed content.

[0085] Step S215: Determine the test result of the grayscale release page according to the changed content, and execute step S216 if the test passes; if the test fails, execute step S217.

[0086] Step S216: Officially publish the page element.

[0087] Step S217: Return the page information to the pending release state, so as to adjust the page information in the pending release state.

[0088] It can be seen from a method for processing page elements according to an embodiment of the present invention that by decoupling page elements from page codes, when page elements need to be processed, they can be verified and audited according to the corresponding page processing data, and the page elements can be released after the verification and audit are passed. It can be seen that the embodiment of the present invention does not need to wait for the iterative version of the application to realize the modification or change of page elements, nor does it need to modify the page code, thereby reducing the workload of APP page design, improving the efficiency of page processing, and avoiding the impact of other page functions when the page elements are modified.

[0089] Based on the same inventive concept as the above embodiments, the embodiment of the present invention also provides a device for processing page elements, such as Figure 3 As shown, the page element processing device 300 includes: an acquisition module 301, a verification module 302, an audit module 303 and a publishing module 304; wherein,

[0090] The acquisition module 301 is configured to: acquire page processing data, the page processing data including a business identifier, an identifier of a page element to be processed, and a processing type of the page element;

[0091] The verification module 302 is configured to: verify the page processing data according to the business identifier and the processing type, and trigger the review module 303 if the verification passes;

[0092] The review module 303 is configured to: generate a review request corresponding to the page element identifier according to the page processing data, to review the page processing data according to the review request, and trigger the publishing module 304 if the review is passed;

[0093] The publishing module 304 is configured to generate publishing information corresponding to the page element and publish the page element according to the publishing information.

[0094] In one embodiment of the present invention, the publishing module 304 is used to generate a grayscale publishing page based on the grayscale publishing page elements of the publishing information; perform pixel comparison between a first image corresponding to the grayscale publishing page and a second image corresponding to the initial page to determine the changed content; determine a test result of the grayscale publishing page based on the changed content; and formally publish the page elements in response to the test result being a passed test.

[0095] In one embodiment of the present invention, the verification module 302 is used to determine whether the page processing data corresponds to an existing business module based on the business identifier when the processing type is a modification type; if so, determine whether the page element identifier exists in a pre-stored data dictionary, the data dictionary including multiple page element identifiers corresponding to each existing business module; if so, determine that the page processing data verification has passed.

[0096] In one embodiment of the present invention, when the processing type is a newly added type, it is determined based on the business identifier whether the page processing data corresponds to an existing business module; if not, the format of the page processing data is verified; if the format verification passes, it is determined that the page processing data verification passes.

[0097] In one embodiment of the present invention, the audit module 303 is further configured to audit the page processing data according to the audit request through multiple levels of first audit roles, and the multiple levels of first audit roles correspond to different first user permissions respectively.

[0098] In one embodiment of the present invention, the review module 303 is further configured to review the published information through multiple levels of second review roles, and the multiple levels of second review roles correspond to different second user permissions respectively.

[0099] In one embodiment of the present invention, the audit module 303 is also used to configure a set of page controlled elements corresponding to multiple user roles; when rendering the user interface corresponding to the first audit role and / or the second audit role, other controlled page elements outside the page controlled element set are intercepted according to the set of page controlled elements corresponding to the first audit role and / or the second audit role.

[0100] In one embodiment of the present invention, the audit module 303 is used to determine the audit order of multiple levels of first audit roles based on the first user's permissions; according to the audit order, the following steps are executed in a loop until the lower-level audit role is the last first audit role or the audit fails: in response to the current level audit passing, the audit request and the current level audit result are forwarded to the lower-level audit role.

[0101] In one embodiment of the present invention, a state configuration module is further included; the state configuration module is used to configure the state of the page processing data according to the processing progress of the page processing data.

[0102] In one embodiment of the present invention, the status configuration module is used to configure the page processing data to a pending release state in response to the page processing data passing the review of the second review role; the publishing module is also used to integrate multiple page processing data in the pending release state and publish page elements according to the integration results.

[0103] According to the page element processing device provided by the above embodiment, it can be seen that by decoupling the page element from the page code, when the page element needs to be processed, it can be verified and audited according to the corresponding page processing data, and the page element can be released after the verification and audit are passed. It can be seen that the embodiment of the present invention does not need to wait for the application iteration version to realize the modification or change of the page element, nor does it need to modify the page code, thereby reducing the workload of APP page design, improving the efficiency of page processing, and avoiding the impact of other page functions when the page element is modified.

[0104] Figure 4 An exemplary system architecture 400 is shown to which a method for processing page elements and an apparatus for processing page elements according to an embodiment of the present invention can be applied.

[0105] like Figure 4 As shown, the system architecture 400 may include terminal devices 401, 402, 403, a network 404 and a server 405. The network 404 is used to provide a medium for a communication link between the terminal devices 401, 402, 403 and the server 405. The network 404 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc. A user may use the terminal devices 401, 402, 403 to interact with the server 405 through the network 404 to send page processing data or receive publishing results, etc. Various client applications may be installed on the terminal devices 401, 402, 403, such as form processing tools, shopping applications, payment applications, instant messaging tools, social platform software, etc. The terminal devices 401, 402, 403 may be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, etc.

[0106] Server 405 may be a server that provides various services, such as a backend data processing server that supports functions such as verification and review of page processing data submitted by users using terminal devices 401, 402, 403. It should be understood that Figure 4 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0107] Reference below Figure 5 , which shows a schematic diagram of the structure of a computer system 500 of a terminal device suitable for implementing an embodiment of the present invention. Figure 5 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0108] like Figure 5 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage part 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the system 500 are also stored. The CPU 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0109] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage section 508 as needed.

[0110] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the central processing unit (CPU) 501, the above-mentioned functions defined in the system of the present invention are executed.

[0111] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0112] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0113] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The described system may also be set in a processor, for example, it may be described as: a processor includes an acquisition module, a verification module, an audit module and a publishing module. The names of these systems do not constitute a limitation on the system itself in some cases, for example, the publishing module may also be described as a "module for publishing page elements".

[0114] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: obtaining page processing data, the page processing data includes a business identifier, a page element identifier to be processed, and a processing type of the page element; verifying the page processing data according to the business identifier and the processing type; if the verification passes, generating an audit request corresponding to the page element identifier according to the page processing data, so as to audit the page processing data according to the audit request; in response to the audit passing, generating publishing information corresponding to the page element, and publishing the page element according to the publishing information.

[0115] According to the technical solution of the embodiment of the present invention, by decoupling the page elements from the page code, when the page elements need to be processed, they can be verified and audited according to the corresponding page processing data, and the page elements can be released after the verification and audit are passed. It can be seen that the embodiment of the present invention does not need to wait for the application iteration version to realize the modification or change of the page elements, nor does it need to modify the page code, thereby reducing the workload of APP page design, improving the efficiency of page processing, and avoiding the impact of other page functions when the page elements are modified.

[0116] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for processing page elements, characterized in that: include: Acquire page processing data, the page processing data including a service identifier, an identifier of a page element to be processed, and a processing type of the page element; Verifying the page processing data according to the service identifier and the processing type; If the verification is passed, generating a review request corresponding to the page element identifier according to the page processing data, so as to review the page processing data according to the review request; In response to the review being passed, publishing information corresponding to the page element is generated, and the page element is published according to the publishing information.

2. The method according to claim 1, characterized in that: The step of publishing the page element according to the publishing information includes: Grayscale publishing of the page elements according to the publishing information to generate a grayscale publishing page; Comparing pixels of a first image corresponding to the grayscale publishing page with a second image corresponding to the initial page to determine the changed content; Determine a test result of the grayscale release page according to the changed content; In response to the test result being that the test is passed, the page element is officially released.

3. The method according to claim 1, characterized in that The verifying the page processing data according to the service identifier and the processing type includes: In the case where the processing type is a modification type, determining whether the page processing data corresponds to an existing business module according to the business identifier; if yes, determining whether the page element identifier exists in a pre-stored data dictionary, the data dictionary including a plurality of page element identifiers corresponding to each existing business module; if yes, determining that the page processing data verification has passed; and / or, In the case where the processing type is a newly added type, determining whether the page processing data corresponds to an existing business module according to the business identifier; If not, the format of the page processing data is verified; if the format verification passes, it is determined that the page processing data has passed the verification.

4. The method according to claim 1, characterized in that: After generating the audit request corresponding to the page element identifier according to the page processing data and before generating the publishing information corresponding to the page element, the method further includes: auditing the page processing data according to the audit request through a multi-level first audit role, wherein the multi-level first audit roles correspond to different first user permissions respectively; and / or, After generating the publishing information corresponding to the page element and before publishing the page element according to the publishing information, the method further includes: The published information is reviewed through multiple levels of second review roles, and the multiple levels of second review roles correspond to different second user permissions respectively.

5. The method according to claim 4, characterized in that The method further comprises: Configure the page controlled element sets corresponding to multiple user roles; When rendering the user interface corresponding to the first review role and / or the second review role, intercepting other controlled page elements outside the page controlled element set according to the page controlled element set corresponding to the first review role and / or the second review role respectively; and / or, The auditing of the page processing data through multi-level first audit roles includes: determining the audit order of the multi-level first audit roles according to the first user authority; looping through the following steps according to the audit order until the subordinate audit role is the last first audit role or the audit fails: in response to the audit passing at this level, forwarding the audit request and the audit result at this level to the subordinate audit role.

6. The method according to claim 4, characterized in that Also includes: According to the processing progress of the page processing data, the state of the page processing data is configured.

7. The method according to claim 6, characterized in that In response to the page processing data passing the review of the second review role, configuring the page processing data to be in a to-be-published state; The method also includes: integrating the processing data of multiple pages in a state to be published, and publishing the page elements according to the integration result.

8. A device for processing page elements, characterized in that: include: Acquisition module, verification module, review module and release module; among them, The acquisition module is configured to: acquire page processing data, the page processing data including a business identifier, an identifier of a page element to be processed, and a processing type of the page element; The verification module is configured to: verify the page processing data according to the business identifier and the processing type, and trigger the audit module if the verification passes; The audit module is configured to: generate an audit request corresponding to the page element identifier according to the page processing data, audit the page processing data according to the audit request, and trigger the publishing module if the audit passes; The publishing module is configured to generate publishing information corresponding to the page element, and publish the page element according to the publishing information.

9. An electronic device for processing page elements, characterized in that: include: one or more processors; a storage device for storing 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 page element processing method as described in any one of claims 1-7.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the page element processing method as described in any one of claims 1 to 7 is implemented.

Images