CN112328347A

CN112328347A - Application rule configuration method and device and page processing method

Info

Publication number: CN112328347A
Application number: CN202011222115.7A
Authority: CN
Inventors: 陈浩翔
Original assignee: Hangzhou Dasouche Auto Service Co ltd
Current assignee: Hangzhou Dasouche Auto Service Co ltd
Priority date: 2020-11-05
Filing date: 2020-11-05
Publication date: 2021-02-05

Abstract

The embodiment of the specification provides an application rule configuration method and device and a page processing method, wherein the application rule configuration method comprises the following steps: acquiring a selection action submitted by a trigger time point aiming at an application rule corresponding to an application page; determining the trigger time point selected by the selected action as a target time point for starting the condition detection of the application rule; determining a trigger condition detected in condition detection according to a condition configuration operation submitted aiming at an application rule; and determining the trigger action executed after the trigger condition is met by the action configuration request submitted by aiming at the application rule. Through the technical scheme of the embodiment of the specification, the attribute parameters of the fields or the objects on the application page can be changed through the configured application rules, the code modification developed by the back end is not depended on, the development workload of modifying the codes is reduced, and the display effect of the application page is adjusted according to the personalized requirements.

Description

Application rule configuration method and device and page processing method

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for configuring application rules, and a method for processing a page.

Background

The attribute parameters of objects such as fields, plug-ins, buttons and the like displayed on the application page are pre-configured through the back-end writing code, so that each object displayed on the application page is usually located in a fixed area. For the user of the application page, there is a need to change the attribute parameters of the object under certain personalized scenes to adjust the visual effect of the application page.

In the prior art, modifying the attribute parameters of each object contained in an application page depends on a professional back-end developer to modify on a code level, and is time-consuming, labor-consuming and low in efficiency.

Disclosure of Invention

One or more embodiments of the present specification provide an application rule configuration method. The application rule configuration method comprises the following steps:

acquiring a selection action submitted by a trigger time point aiming at an application rule corresponding to an application page;

determining a trigger time point selected by the selection action as a target time point for starting condition detection of the application rule;

determining a trigger condition detected in the condition detection according to a condition configuration operation submitted aiming at the application rule;

and determining the trigger action executed after the trigger condition is met through an action configuration request submitted by aiming at the application rule.

Optionally, in a case that it is detected that the target time point arrives, detection of a trigger condition included in the application rule corresponding to the application page is started, and if it is detected that the trigger condition is satisfied, a trigger action corresponding to the trigger condition is executed.

Optionally, the determining, according to the condition configuration action submitted according to the rule to be configured, the triggering condition corresponding to the condition detection includes:

acquiring parameter selection actions submitted aiming at the condition fields, operators and comparison value types;

determining a target field, a target operator and a target type selected by the parameter selection action;

determining at least one selectable comparison value according to the target field and the target type;

receiving a comparison value selection action submitted in the at least one selectable comparison value;

determining a selectable comparison value selected by the comparison value selection action as a target comparison value;

and determining the trigger condition that a comparison relation formed by the field value of the target field, the target operator and the comparison field value corresponding to the target comparison value is established.

Optionally, the determining at least one optional comparison value according to the target field and the target type includes:

if the target type is a field type, determining that the selectable comparison value is a field contained in the application page and/or a field having an association relation with the application page;

and if the target type is a value type, determining a field selectable value corresponding to the target field as the selectable comparison value.

Optionally, after the step of determining, by the action configuration request submitted according to the application rule, that the trigger action is executed after the trigger condition is satisfied, the method further includes:

when a processing request submitted by a user for the application page is acquired, detecting whether a target time point of an application rule corresponding to the application page is reached;

if yes, judging whether the trigger condition contained in the application rule is met according to the acquired request data of the processing request;

and if so, executing a trigger action corresponding to the trigger condition.

Optionally, the processing request submitted for the application page includes an editing request submitted for a specific field on the application page; whether the target time point of the application rule corresponding to the application page is reached is detected in the following mode:

when an editing request submitted by the user for a specific field on the application page is acquired, detecting whether a target time point of an application rule corresponding to the application page contains a field editing time point or not;

if not, detecting that the target time point does not arrive;

if yes, judging whether a target field corresponding to a trigger condition contained in the application rule contains the specific field;

if yes, detecting that the target time point arrives;

if not, detecting that the target time point does not arrive.

Optionally, whether the trigger condition included in the application rule is satisfied is determined by the following method:

determining a field to be judged corresponding to a target field contained in the trigger condition on the application page;

determining the field value of the field to be judged according to the request data and/or the service data corresponding to the field to be judged;

judging whether a comparison relation formed by the field value of the field to be judged, the target operator contained in the trigger condition and the comparison field value corresponding to the target comparison value contained in the trigger condition is established or not;

if so, determining that the trigger condition is met;

if not, determining that the triggering condition is not met.

Optionally, the triggering is a parameter configuration action for updating a visibility parameter of a target object from visible to invisible, and the executing of the triggering action corresponding to the triggering condition includes:

determining an object to be updated corresponding to the target object on the application page;

updating the visibility parameter of the object to be updated from visible to invisible;

moving the positions of the objects to be adjusted forward in sequence according to the object arrangement sequence in the application page; the object to be adjusted is an object behind the object to be updated in the object arrangement order.

One or more embodiments of the present specification provide a page processing method, including:

when a processing request of a user for an application page is acquired, detecting whether a trigger time point of an application rule corresponding to the application page is reached;

and if so, executing a trigger action corresponding to the trigger condition.

One or more embodiments of the present specification provide a page rule updating apparatus, including:

the time point selection module is used for acquiring selection actions submitted by triggering time points aiming at the application rules corresponding to the application pages;

a time point determining module, configured to determine a trigger time point selected by the selection action as a target time point for starting condition detection of the application rule;

a condition determining module, configured to determine, according to a condition configuration operation submitted for the application rule, a trigger condition detected in the condition detection;

and the action determining module is used for determining the trigger action executed after the trigger condition is met through an action configuration request submitted aiming at the application rule.

One or more embodiments of the present specification provide a page processing apparatus including:

the time point detection module is used for detecting whether the trigger time point of the application rule corresponding to the application page arrives or not when the processing request of the user for the application page is obtained;

the condition judgment module is used for judging whether the trigger condition contained in the application rule is met or not according to the acquired request data of the processing request if the trigger condition is met;

and the action execution module is used for executing the trigger action corresponding to the trigger condition if the trigger action is positive.

In an application rule configuration method provided in one or more embodiments of the present specification, a selection action submitted at a trigger time point for an application rule corresponding to an application page is acquired; determining the trigger time point selected by the selected action as a target time point for starting the condition detection of the application rule; determining a trigger condition detected in condition detection according to a condition configuration operation submitted aiming at an application rule; the method comprises the steps of determining a trigger action executed after a trigger condition is met through an action configuration request submitted by aiming at an application rule, changing attribute parameters of fields or objects on an application page through the configured application rule, not depending on code modification developed at the back end, reducing development workload of modified codes, and adjusting the visual effect of the application page according to personalized requirements.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.

FIG. 1 is a process flow diagram of a method for applying rule configuration in accordance with one or more embodiments of the present disclosure;

FIG. 2 is a process flow diagram of a page processing method according to one or more embodiments of the present disclosure;

fig. 3 is a schematic diagram of an application scenario of an application rule configuration method according to one or more embodiments of the present specification;

fig. 4 is a schematic diagram of an application rule configuration apparatus according to one or more embodiments of the present disclosure.

Fig. 5 is a schematic diagram of a page processing apparatus according to one or more embodiments of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

An embodiment of an application rule configuration method provided in this specification:

fig. 1 is a process flow diagram of an application rule configuration method according to one or more embodiments of the present disclosure.

Referring to fig. 1, the method for configuring application rules provided in this embodiment includes steps S102 to S108.

Step S102, obtaining selection actions submitted by the trigger time points of the application rules corresponding to the application pages.

The application may be a system that provides services to users, for example, a SaaS (Software-as-a-Service) system, that is, a system that provides Software services via a network. The SaaS platform supplier uniformly deploys the application software on the server of the SaaS platform supplier, a client can order the required application software service from a manufacturer through the Internet according to the actual working requirement, pay the cost to the manufacturer according to the ordered service and the time, and obtain the service provided by the Saas platform supplier through the Internet. The application may also be an application developed on the electronic device side by an intermediary website (e.g., a trading platform) through which a user can process business after registering as a member of the intermediary website. The application may also be an application developed on the electronic device side by a social platform, or the like. The application may be a mobile phone application, a computer application, or an application running on other electronic devices, which is not limited in the present invention.

The application rules are business rules configured for the layout of the application, including, but not limited to, page layout, button layout, and object layout. Each page layout corresponds to one application page in the application, and the application rule corresponding to the page layout, that is, the application rule corresponding to the application page, is collectively stated hereinafter by taking the application rule corresponding to the application page as an example.

Each application page corresponds to one or more application rules. The trigger time points of the application rules corresponding to the same application page may be the same or different.

Before the processor of the electronic device executes step S102, the following steps may also be executed: acquiring a rule processing action aiming at an application rule on the page layout of an application page; in response to the rule processing action, a configuration page is entered that displays a list of rules corresponding to the application page. The configuration page displays the rule name, the target time point, the rule description and the update time of each application rule corresponding to the application page, and displays the operation area corresponding to each rule. Including but not limited to buttons corresponding to new create operations, edit operations, copy operations, enable operations, and delete operations.

In some cases, upon receiving a click operation for a key "enable", the application rule corresponding to the key "enable" is validated, and the key "delete" disappears, and the key "enable" is updated to the key "disable". After receiving the click operation for the key "disable", the application rule corresponding to the key "enable" is not validated, and the key "disable" is updated to the key "enable".

Receiving a new operation aiming at the application rule, and displaying a basic information configuration page of the application rule according to the new operation, wherein the basic information includes and is not limited to the name, the code, the trigger time point and the description of the application rule. Wherein the code is a custom code for identifying the respective application rule.

The trigger time points for applying the rules include, but are not limited to: a page access time point, a field edit time point, and a timing detection time point.

A page access time point refers to a time point when a processor of an electronic device loads an application page, and typically occurs after the processor of the electronic device receives a request to access the application page.

A field editing time point refers to a time point at which a processor of the electronic device performs editing processing on a specific field in response to an editing action for the specific field on an application page. It should be noted that, if the trigger time point of the application rule is configured as the field editing time point, the target field in the trigger condition needs to be configured in the subsequent step to determine the actual trigger time point of the application rule.

The timing detection time points are a plurality of time points determined according to a predetermined start time point and a detection time period, for example, if the page access time point is the start time point and the detection time period is 10 seconds, the timing detection time points are a plurality of time points such as 10 seconds, 20 seconds, 30 seconds after the page access time point.

The selection action may be a selection action submitted by a user or a selection action automatically submitted by a processor of the electronic device.

And step S104, determining the trigger time point selected by the selected action as a target time point for starting the condition detection of the application rule.

There may be one or more target time points for the same application rule. For example, the target time point corresponding to the application rule 1 includes both the page access time point and the field editing time point.

The field editing time point is a time point for performing editing processing on a target field configured in the trigger condition, and is not a time point for performing editing processing on any field in any application page. For example, if the trigger time point of the application rule is a field editing time point and the target field is configured as a field "phone number" in the trigger condition, the processor of the electronic device will initiate the condition checking operation only when the field "phone number" is edited, and will not initiate the condition checking operation when other fields are edited, such as the field "home address" and the field "order number".

Starting condition detection of the application rule at the target time point means that at the target time point, a judgment is performed once to judge whether the trigger condition detected in the condition detection is satisfied. For example, the trigger time point "page access time point" and "field edit time point" selected by the selected action are determined as the target time point of condition detection for starting the application rule, and the target field included in the trigger condition is "phone number", then in case that the arrival of the page access time point is detected, it is determined whether the trigger condition is satisfied once, and in case that the arrival of the field edit time point is detected, it is determined again whether the trigger condition is satisfied once.

In some cases, the trigger condition of the application rule only includes one branch, and the content of the trigger condition is empty, and no condition detection is started when any field is edited, that is, "field editing time point" has no practical meaning for the application rule.

Step S106, according to the condition configuration operation submitted aiming at the application rule, determining the trigger condition detected in the condition detection.

And after the target time point is determined, generating a rule configuration page of the application rule corresponding to the target time point. And acquiring a condition creating action submitted by aiming at the trigger condition on the rule configuration interface, and displaying a condition configuration area according to the condition creating action. The condition configuration area contains, but is not limited to, condition fields, operators and comparison value types and selectable comparison values and corresponding selection menus. Wherein:

condition Field (Field): and the field body is used for detecting conditions and supports fields on the application page.

Operator (Operator): an operator for comparing a field value of the target field and a comparison field value corresponding to the target comparison value, for example, greater than, equal to, less than, not equal to, null, non-null, etc.

Comparison value Type (Type): the types of the comparison values may be selected, including field type and value type.

Alternative comparison Value (Value): comparison values for condition detection (if a field supports selection of a field on a superior (Lookup) object or other associated object).

Optionally, determining a trigger condition corresponding to the condition detection according to the condition configuration action submitted according to the rule to be configured includes: acquiring parameter selection actions submitted aiming at the condition fields, operators and comparison value types; determining a target field, a target operator and a target type selected by the parameter selection action; determining at least one selectable comparison value according to the target field and the target type; receiving a comparison value selection action submitted in at least one selectable comparison value; determining the selectable comparison value selected by the comparison value selection action as a target comparison value; the trigger condition is determined such that a comparison relation formed by a field value of the target field, the target operator, and a comparison field value corresponding to the target comparison value is established.

The method comprises the steps of obtaining a parameter selection action submitted on a selection menu corresponding to a condition field, an operator and a comparison value type, and determining a target field, a target operator and a target type selected by the parameter selection action, wherein the selected target field is a field sequence number, the selected target operator is a field sequence number, and the target type is a value type.

Optionally, determining at least one optional comparison value according to the target field and the target type, including: if the target type is a field type, determining that the selectable comparison value is a field contained in the application page and/or a field having an association relation with the application page; and if the target type is the value type, determining the field selectable value corresponding to the target field as a selectable comparison value.

And if the target type is a field type, determining that the optional comparison values are all fields, wherein the fields can be fields contained in the application page or fields in an object which is not on the application page but has an association relationship with the application page. For example, there is an association relationship between the field "order number" on the application page and the object "order", and even if each field in the object "order" is not on the aforementioned application page, each field included in the object "order" can be used as an optional comparison value.

And if the target type is the value type, determining the optional comparison value as a field optional value corresponding to the target field. For example, if the field selectable values corresponding to the target field "sequence number" include values "1", "2", and "3", the selectable comparison values are values "1", "2", and "3". And if the target field does not have the corresponding field selectable value, acquiring an input action aiming at the selectable comparison value, and determining the target comparison value according to the input action.

Receiving a comparison value selection action submitted on a selection menu corresponding to the selectable comparison value, and determining the selectable comparison value selected by the comparison value selection action as a target comparison value, for example, providing two selectable comparison values, namely a value "1" and a value "2", in the selection menu corresponding to the selectable comparison value, and if the selectable comparison value selected by the comparison value selection action is the value "1", then the target comparison value is the value "1".

The field value of the target field can be obtained through request data of a processing request sent by a user aiming at the access page and/or business data corresponding to the target field. For example, when the target time point is an access page time point, a page access request submitted by a user for an application page does not involve editing a field on the application page, and business data corresponding to the target field is inquired before the page is loaded as a field value of the target field; when the target time point is an editing field time point, the field value of the specific field on the application page is changed by an editing request submitted by a user aiming at the specific field on the application page, and then the field value of the target field is determined according to the request data of the editing request.

If the target comparison value is a value type, the comparison field value corresponding to the target comparison value is the target comparison value, for example, a fixed value "1"; if the target comparison value is a field type, the comparison field value corresponding to the target comparison value is a field value of the comparison field corresponding to the target comparison value, for example, if the target comparison value is a field "order quantity", the comparison field value is a field value of a field "order quantity". The field value of the target field can be compared with a fixed static value through the target comparison value of the value type; by the target comparison value of the field type, the field value of the target field can be compared with the field value of the comparison field which dynamically changes.

The trigger condition is determined such that a comparison relation composed of a field value of the target field, a target operator, and a comparison field value corresponding to the target comparison value is satisfied, for example, if the target field is a field "number", the target operator is "═ and the comparison field value corresponding to the target comparison value is a numerical value" 2 ", and the trigger condition is satisfied such that the comparison relation in which the field value of the field" number "is equal to 2 is satisfied. If the comparison relation is established, the triggering condition is met; if the comparison relation is not satisfied, the trigger condition is not satisfied.

In other cases, obtaining a parameter selection action submitted for the condition field; determining a target field selected by the parameter selection action; determining an optional value of an operator according to the attribute value of the target field; receiving an operator selection action submitted for an optional value of an operator; determining a target operator selected by the operator selection action; the trigger condition is determined that a relational expression formed by the field value of the target field and the target operator holds.

For example, if the target field is a field "sales status", and the type of the field included in the attribute value is a radio type, the field value of the field "sales status" is one of "sold" and blank. And determining that the optional value of the operator is blank or non-blank according to the attribute value of the target field. Taking the target operator as "blank", the trigger condition is determined such that a relational expression made up of a field value of the field "sales status" and the target operator "blank" is established. Namely, if the field value of the field 'sale state' is 'sold', the trigger condition is not satisfied; if the field value of the field "sales status" is blank, the trigger condition is satisfied.

It should be noted that the trigger condition may include a plurality of parallel branches, or may include only one branch. If the trigger condition includes a plurality of parallel branches, normally, the order of the branches of each trigger condition in the page is configured according to a rule, and whether each trigger condition is satisfied is sequentially determined. In a special case, the trigger condition includes only one branch, and the content of the branch is blank, so that the execution action corresponding to the blank trigger condition can be executed after the target time point is reached.

In other cases, the trigger condition of the application rule corresponding to the application page includes a plurality of branches, and after the content of the last branch in the arrangement order of each branch in the rule configuration page is blank, if the target time point is reached, the trigger conditions except for the last branch are sequentially judged whether to be satisfied according to the arrangement order of the branches of each trigger condition in the rule configuration page, and if not, the trigger action corresponding to the trigger condition of the branch with the blank content is executed.

And step S108, determining the trigger action executed after the trigger condition is met through the action configuration request submitted by aiming at the application rule.

And after the target time point is determined, generating a rule configuration interface of the application rule corresponding to the target time point. And acquiring an action creating request submitted by aiming at the trigger action on the rule configuration interface, and displaying an action configuration area according to the action creating request. The action configuration area includes, but is not limited to, trigger actions, action objects and action parameters, and corresponding selection menus. Wherein, different trigger actions correspond to different action objects and action parameters. And receiving action selection operation submitted on a selection menu corresponding to the trigger action, determining the trigger action selected by the action selection operation as a target action, and updating a page to display an action object and action parameters corresponding to the target action.

The trigger action includes and sets field padding, sets visibility, lock or unlock fields. The target action is the one or more trigger actions selected for execution after the trigger condition is satisfied.

Regarding the trigger action "set field padding", the trigger action refers to a padding configuration action that sets a specified field to padding or padding unnecessary, specifically, updates the padding parameter of the field to be processed set in the trigger action from padding necessary to padding unnecessary. After the selection target action is filled as a setting field, rendering and updating the page to display an action object field, a corresponding selection menu, an action parameter required filling property and a corresponding selection menu.

For example, after a user selects "set field must be filled" in a selection menu of a trigger action, and a processor of the electronic device renders and updates a page, the user selects a field "phone number" in the selection menu corresponding to the "field", and selects "must be filled" in the selection menu corresponding to the "must be filled", when a trigger condition is satisfied, the processor of the electronic device determines a to-be-processed field "phone number" corresponding to the field "phone number" on an application page, and if the original must be filled of the to-be-processed field "phone number" is must be filled, the must be filled of the to-be-processed field is updated from must be filled to must be filled; if the original necessary filling property of the field to be processed, namely the telephone number, is not necessary filling, no operation is executed.

The priority corresponding to the application rule is higher than the priority of the attribute parameters of the field to be processed, so that the application rule can execute the trigger action if the trigger condition is met after the target time point is reached, so that the filling property of the field to be processed corresponding to the trigger action is updated from filling to filling, or from filling to filling, thereby changing the attribute parameters of the field to be processed. The field to be processed corresponding to the trigger action is usually a field included in the application page, and the field to be processed may be displayed on the application page or may not be displayed on the application page.

In addition, field fillable is not involved in application pages that are only allowed to view, so application rules that trigger actions to set field fill are typically in force in both the newly created application page and the editing application page.

In some cases, for a trigger action, an application rule that must be filled as a set field is not validated if a to-be-processed field corresponding to the trigger action is deleted.

Regarding the trigger action "set visibility", the trigger action refers to setting visibility of an object on an application page, the object includes and is not limited to field group, associated object, plug-in, button, specifically a parameter configuration action that updates visibility parameters of a target object from visible to invisible or a parameter configuration action that updates visibility parameters of a target object from invisible to visible. In the application page, a plurality of fields included in a specific area may be previously divided into the same field group. After the target action is selected as the visibility setting, the page is rendered and updated to display an action object 'layout element' and a corresponding selection menu and an action parameter 'whether to display' and a corresponding selection control.

It should be noted that, if the visibility parameter of the object to be updated corresponding to the action object, which is determined in the application page, is updated from visible to invisible, the object to be updated is not displayed in the application page, and the positions of the objects to be adjusted are sequentially moved forward according to the arrangement sequence of the objects in the application page; the object to be adjusted is an object behind the object to be updated in the object arrangement order.

For example, after the user selects "set visibility" in the selection menu for triggering the action, the processor of the electronic device renders and updates the page, the user selects "field" in the selection menu corresponding to "layout element", the processor renders and updates the page again to display the action sub-object "field" and the corresponding selection menu, the user selects field "phone number" in the selection menu corresponding to the action sub-object "field", and selects control "no" in the selection control corresponding to "whether to display" action parameter. If the visibility parameter "of the to-be-updated object" phone number "corresponding to the action sub-object" phone number "is displayed as" yes "after the trigger condition is met, updating the visibility parameter of the to-be-updated object from" yes "to" no "; the field "telephone number" is not displayed on the application page, and the positions of the objects after the field "telephone number" are sequentially moved forward in accordance with the order of arrangement of the objects in the application page.

In other cases, the visibility parameter of the object to be updated corresponding to the action object, which is determined in the application page, is updated from invisible to visible, which is similar to the technical concept of the previous case of updating the visibility parameter from visible to invisible, and is not described herein again.

By moving the position of the object to be adjusted behind the object to be updated forward or backward in sequence according to the object arrangement sequence in the application page, the situation that a plurality of objects are overlapped or an abrupt blank is left in the application page can not occur after the visibility of the object to be updated is changed, and the visual effect of the application page is effectively beautified.

And aiming at triggering the application rule used for setting the visibility, the priority of the application authority is higher than that of the application rule, and the priority of the application rule is higher than the attribute parameter of the object to be updated on the application page. And the application rule can take effect in the application pages of new creation, editing and viewing types.

With regard to the trigger action "lock or unlock a field", the trigger action refers to locking a certain field/field group to be uneditable, or unlocking a certain field/field group to be editable, specifically, an editability configuration action that updates the editability parameters of the field/field group to be processed set in the trigger action from allowing editing to disallowing editing or from disallowing editing to editable.

After the field is set to not allow editing, the field does not allow editing and only allows viewing; the field group is set to disallow editing the fields in the entire field group to disallow editing to allow viewing only.

This example of the trigger action is similar to the aforementioned examples of the trigger action "set field must be filled" and the trigger action "set visibility", and will not be described here again.

In some cases, a post-trigger condition detected in the detection of a condition initiated after a trigger action is performed is determined by configuring an operation for the post-condition of the application rule. For example, when the field value of the trigger condition field "serial number" is equal to the numerical value "1", the trigger action is executed to update the visibility of the field "serial number" to be invisible, and then whether the field value of the post-trigger condition field "mobile phone number" is empty is detected, and if yes, the post-trigger action is executed to update the visibility of the field "mobile phone number" to be visible.

Receiving configuration confirmation operation aiming at application rules corresponding to the application pages; and enabling the application rule to take effect according to the configuration confirmation operation. After the application rule takes effect, after a processing request of a user for the application page is obtained, a processor of the electronic equipment detects whether a target time point arrives, if so, the detection of the trigger condition is started, namely, whether the trigger condition is met is judged, and if so, a trigger action corresponding to the trigger condition is executed.

Optionally, after step S108 is executed, the following steps are further executed: when a processing request submitted by a user for an application page is acquired, detecting whether a target time point of an application rule corresponding to the application page is reached; if yes, judging whether the trigger condition contained in the application rule is met according to the acquired request data of the processing request; if yes, executing the trigger action corresponding to the trigger condition.

Processing requests submitted for an application page include, and are not limited to, page access requests for an application page and editing requests submitted for specific fields on an application page.

When a page access request submitted by a user for an application page is acquired, whether a target time point of an application rule corresponding to the application page contains a page access time point is detected. If yes, the arrival of the target time point is detected, and if not, the non-arrival of the target time point is detected. If the target time point is detected to arrive, inquiring service data corresponding to the target field in service data corresponding to the application page as a field value of the target field according to a page identifier of the application page carried by the acquired request data of the processing request and the target field in the trigger condition; judging whether the triggering condition is met or not according to the field value of the target field, the target operator in the triggering condition and the comparison field value corresponding to the target comparison value; if yes, executing a trigger action corresponding to the trigger condition; if not, the triggering action corresponding to the triggering condition is not executed.

Optionally, the processing request for the application page includes an editing request for a specific field on the application page; whether a target time point of an application rule corresponding to an application page is reached is detected in the following mode: when an editing request of a user for a specific field on an application page is acquired, whether a detected target time point comprises a field editing time point or not is detected; if not, detecting that the target time point does not arrive; if yes, judging whether a target field corresponding to a trigger condition contained in the application rule contains a specific field; if yes, detecting that the target time point arrives; if not, detecting that the target time point does not arrive.

When an editing request for a specific field on an application page is acquired, whether an application rule with a target time point as a field editing time point exists in an application rule corresponding to the application page is detected. And if the target time point does not reach, executing the next judgment, and if the target time point does not reach, detecting that the target time point does not reach. If the application rule with the target time point as the field editing time point is detected to exist, whether the target field corresponding to the trigger condition contained in the application rule with the target time point as the field editing time point contains the specific field is judged. If yes, detecting that the target time point arrives; if not, detecting that the target time point does not arrive.

Optionally, whether the trigger condition included in the application rule is satisfied is determined by the following method: determining a field to be judged corresponding to a target field contained in the trigger condition on the application page; determining the field value of the field to be judged according to the request data and/or the service data corresponding to the field to be judged; judging whether a comparison relation formed by the field value of the field to be judged, the target operator contained in the trigger condition and the comparison field value corresponding to the target comparison value contained in the trigger condition is established or not; if so, determining that the trigger condition is met; if not, determining that the triggering condition is not met.

For example, a field "sequence number" to be judged corresponding to a target field "sequence number" included in the trigger condition is determined in the application page; determining that the field value of the field sequence number to be judged is changed into 1 after editing according to the request data of the field editing request; whether a comparison relation expression consisting of "1", a target operator "and a comparison field value" 2 "corresponding to a target comparison value included in the trigger condition is satisfied is determined, and a result that 1 is not satisfied and the trigger condition is not satisfied is obtained.

Optionally, the triggering action is a parameter configuration action for updating the visibility parameter of the target object from visible to invisible, and the triggering action corresponding to the triggering condition is executed, including: determining an object to be updated corresponding to a target object on an application page; updating the visibility parameter of the object to be updated from visible to invisible; moving the positions of the objects to be adjusted forward in sequence according to the object arrangement sequence in the application page; the object to be adjusted is an object behind the object to be updated in the object arrangement order.

In the application rule configuration method provided in one or more embodiments shown in fig. 1, a selection action submitted at a trigger time point for an application rule corresponding to an application page is obtained; determining the trigger time point selected by the selected action as a target time point for starting the condition detection of the application rule; determining a trigger condition detected in condition detection according to a condition configuration operation submitted aiming at an application rule; the method comprises the steps of determining a trigger action executed after a trigger condition is met through an action configuration request submitted by aiming at an application rule, changing attribute parameters of fields or objects on an application page through the configured application rule, not depending on code modification developed at the back end, reducing development workload of modified codes, and adjusting the display effect of the application page according to personalized requirements.

Fig. 2 is a processing flow diagram of a page processing method according to one or more embodiments of the present disclosure.

Referring to fig. 2, the page processing method provided in this embodiment includes steps S202 to S206.

Step S202, when a processing request of a user for an application page is acquired, whether the triggering time point of the application rule corresponding to the application page is reached is detected.

When a page access request submitted by a user for an application page is acquired, whether a trigger time point of an application rule corresponding to the application page contains a page access time point is detected. If yes, the arrival of the trigger time point is detected, and if not, the non-arrival of the trigger time point is detected. If the trigger time point is detected to arrive, inquiring service data corresponding to the target field in service data corresponding to the application page as a field value of the target field according to a page identifier of the application page carried by the acquired request data of the processing request and the target field in the trigger condition; judging whether the triggering condition is met or not according to the field value of the target field, the target operator in the triggering condition and the comparison field value corresponding to the target comparison value; if yes, executing a trigger action corresponding to the trigger condition; if not, the triggering action corresponding to the triggering condition is not executed.

Optionally, the processing request for the application page includes an editing request for a specific field on the application page; whether the trigger time point of the application rule corresponding to the application page is reached is detected by the following method: when an editing request of a user for a specific field on an application page is acquired, whether a detected trigger time point comprises a field editing time point or not is detected; if not, detecting that the trigger time point does not arrive; if yes, judging whether a target field corresponding to a trigger condition contained in the application rule contains a specific field; if yes, detecting that the trigger time point arrives; if not, detecting that the trigger time point does not arrive.

When an editing request for a specific field on an application page is acquired, whether an application rule with a trigger time point as a field editing time point exists in an application rule corresponding to the application page is detected. And if the trigger time point does not reach, executing the next judgment, and if the trigger time point does not reach, detecting that the trigger time point does not reach. If the application rule with the trigger time point being the field editing time point is detected to exist, whether the target field corresponding to the trigger condition contained in the application rule with the trigger time point being the field editing time point contains the specific field is judged. If yes, detecting that the trigger time point arrives; if not, detecting that the trigger time point does not arrive.

After step S202 is executed, if it is detected that the trigger time point arrives, step S204 is executed.

Step S204, judging whether the trigger condition contained in the application rule is satisfied according to the acquired request data of the processing request.

And if the trigger time point is detected to arrive, judging whether the trigger condition contained in the application rule is met according to the acquired request data of the processing request. And if the trigger time point is detected not to arrive, not performing the condition detection processing corresponding to the application rule. The trigger condition detected in the condition detection is a trigger condition contained in the application rule.

The trigger condition may be that a comparison relationship formed by a field value of a target field included in the trigger condition, a target operator, and a comparison field value corresponding to a target comparison value is satisfied. If the comparison relation is established, the triggering condition is met; if the comparison relation is not satisfied, the trigger condition is not satisfied.

The trigger condition may be that a relational expression made up of a field value of a target field included in the trigger condition and a target operator is satisfied.

For example, if the target field is field "sold state" and the target operator is "blank", the trigger condition is not satisfied if the field value of the field "sold state" is "sold"; if the field value of the field "sales status" is blank, the trigger condition is satisfied.

After step S204 is performed, if it is determined that the trigger condition is satisfied, step S206 is performed.

In step S206, a trigger action corresponding to the trigger condition is executed.

And if the trigger condition is met, executing a trigger action corresponding to the trigger condition. And if the trigger condition is not met, the trigger action corresponding to the trigger condition is not executed.

The trigger action includes and sets field padding, sets visibility, lock or unlock fields.

Regarding the trigger action "set field padding", the trigger action refers to a padding configuration action that sets a specified field to padding or padding unnecessary, specifically, updates the padding parameter of the field to be processed set in the trigger action from padding necessary to padding unnecessary.

Regarding the trigger action "set visibility", the trigger action refers to setting visibility of an object on an application page, the object includes and is not limited to field group, associated object, plug-in, button, specifically a parameter configuration action that updates visibility parameters of a target object from visible to invisible or a parameter configuration action that updates visibility parameters of a target object from invisible to visible. In the application page, a plurality of fields included in a specific area may be previously divided into the same field group.

As shown in fig. 2, in a page processing method provided in one or more embodiments, when a processing request of a user for an application page is acquired, whether a trigger time point of an application rule corresponding to the application page arrives is detected; if yes, judging whether the trigger condition contained in the application rule is met according to the acquired request data of the processing request; if so, executing a trigger action corresponding to the trigger condition to change the attribute parameters of the fields or other objects on the application page, avoiding code modification developed at the back end, improving the working efficiency of changing the attribute parameters, and adjusting the visual effect of the application page according to the personalized requirements.

Fig. 3 is a schematic diagram of an application scenario of an application rule configuration method according to one or more embodiments of the present specification.

Fig. 3 illustrates a rule configuration page of the application rule corresponding to the target time point, the application rule being the application rule corresponding to the application page.

The start icon 302 corresponds to a target point in time. According to the configuration in the figure, if the trigger condition 304, the trigger condition 308, and the trigger condition 316 are all application rules corresponding to the target time point, the execution sequence of the configured application rules is as follows:

after the target time point arrives, whether the trigger condition 304 is satisfied is judged: if so, perform a triggering action 306; if not, then trigger action 306 is skipped.

After determining whether trigger condition 304 is satisfied and executing or skipping execution of trigger action 306, it is determined whether trigger condition 308 is satisfied: if so, perform trigger action 310; if not, then trigger action 310 is skipped. After performing the trigger action 310, it is determined whether the trigger condition 312 is satisfied: if so, perform trigger action 314; if not, then the trigger action 314 is skipped.

After skipping trigger action 310, or after performing or skipping trigger action 314, it is determined whether trigger condition 316 is satisfied: if so, then trigger action 318 is performed; if not, then trigger action 318 is skipped.

Note that the content of the trigger condition 316 is blank, which means that if neither the trigger condition 304 nor the trigger condition 308 is satisfied, it is determined that the trigger condition 316 is satisfied.

Referring to the upper right area of fig. 3, a conditional field 320, an operator 322, a comparison value type 324, and an optional comparison value 326, and a corresponding selection menu are displayed in the condition configuration area of the trigger condition 1, i.e., the trigger condition 304. The user may configure the target field, target operator, target type, and target comparison value of the trigger condition 304 by selecting a menu.

The embodiment shown in fig. 3 may implement the embodiments of the application rule configuration method in the above embodiments, and details are not described here.

An embodiment of an authority processing apparatus provided in this specification is as follows:

in the above embodiment, an application rule configuration method is provided, and correspondingly, an application rule configuration device is also provided, which is described below with reference to the accompanying drawings.

Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.

The embodiment provides an application rule configuration apparatus 400, which includes:

a time point selection module 402, configured to obtain a selection action submitted by a trigger time point for an application rule corresponding to an application page;

a time point determining module 404, configured to determine a trigger time point selected by the selected action as a target time point for starting condition detection of the application rule;

a condition determining module 406, configured to determine a trigger condition detected in condition detection according to a condition configuration operation submitted for the application rule;

an action determining module 408, configured to determine, through the action configuration request submitted for the application rule, a trigger action to be executed after the trigger condition is satisfied.

Optionally, the condition determining module 406 includes:

the parameter selection unit is used for acquiring parameter selection actions submitted by a user aiming at the condition fields, operators and comparison value types;

the parameter determining unit is used for determining a target field, a target operator and a target type selected by the parameter selecting action;

the optional comparison value determining unit is used for determining at least one optional comparison value according to the target field and the target type;

a comparison value selection unit for receiving a comparison value selection action submitted in at least one selectable comparison value;

a target comparison value determination unit for determining an optional comparison value selected by the comparison value selection action as a target comparison value;

and the condition determining unit is used for determining the trigger condition that a comparison relation formed by the field value of the target field, the target operator and the comparison field value corresponding to the target comparison value is established.

Optionally, the optional comparison value determining unit is specifically configured to:

and if the target type is the value type, determining the field selectable value corresponding to the target field as a selectable comparison value.

Optionally, the application rule configuration apparatus 400 further includes:

the target time point detection module is used for detecting whether a target time point of an application rule corresponding to the application page arrives or not when a processing request of a user for the application page is acquired;

the trigger condition judging module is used for judging whether the trigger condition contained in the application rule is met or not according to the acquired request data of the processing request if the trigger condition is met;

and the trigger action execution module is used for executing the trigger action corresponding to the trigger condition if the trigger action is executed.

Optionally, the processing request for the application page includes an editing request for a specific field on the application page; whether a target time point of an application rule corresponding to an application page is reached is detected in the following mode:

when an editing request of a user for a specific field on an application page is acquired, detecting whether a target time point of an application rule corresponding to the application page contains a field editing time point or not;

if not, detecting that the target time point does not arrive;

if yes, judging whether a target field corresponding to a trigger condition contained in the application rule contains a specific field;

if yes, detecting that the target time point arrives;

if not, detecting that the target time point does not arrive.

if so, determining that the trigger condition is met;

if not, determining that the triggering condition is not met.

Optionally, the triggering action is a parameter configuration action for updating the visibility parameter of the target object from visible to invisible; the trigger action execution module is specifically configured to:

determining an object to be updated corresponding to a target object on an application page;

In an application rule configuration method provided in one or more embodiments of the present specification, a selection action submitted at a trigger time point for an application rule corresponding to an application page is acquired; determining the trigger time point selected by the selected action as a target time point for starting the condition detection of the application rule; determining a trigger condition detected in condition detection according to a condition configuration operation submitted aiming at an application rule; the method comprises the steps of determining a trigger action executed after a trigger condition is met through an action configuration request submitted by aiming at an application rule, changing attribute parameters of fields or objects on an application page through the configured application rule, not depending on code modification developed at the back end, reducing development workload of modified codes, and adjusting the display effect of the application page according to personalized requirements.

In the foregoing embodiment, a page processing method is provided, and a page processing apparatus is provided, which is described below with reference to the accompanying drawings.

The present embodiment provides a page processing apparatus 500, including:

a time point detection module 502, configured to detect whether a trigger time point of an application rule corresponding to an application page arrives when a processing request of a user for the application page is obtained;

a condition determining module 504, configured to determine, if yes, whether a trigger condition included in the application rule is satisfied according to the obtained request data of the processing request;

and an action executing module 506, configured to execute the trigger action corresponding to the trigger condition if the trigger action is positive.

Optionally, the processing request for the application page includes an editing request for a specific field on the application page; whether the trigger time point of the application rule corresponding to the application page is reached is detected by the following method:

when an editing request of a user for a specific field on an application page is acquired, detecting whether a trigger time point of an application rule corresponding to the application page contains a field editing time point;

if not, detecting that the trigger time point does not arrive;

if yes, detecting that the trigger time point arrives;

if not, detecting that the trigger time point does not arrive.

if so, determining that the trigger condition is met;

if not, determining that the triggering condition is not met.

Optionally, the triggering action is a parameter configuration action for updating the visibility parameter of the target object from visible to invisible, and the action execution module 506 is specifically configured to:

In the page processing method provided in one or more embodiments of the present specification, when a processing request of a user for an application page is acquired, whether a trigger time point of an application rule corresponding to the application page arrives is detected; if yes, judging whether the trigger condition contained in the application rule is met according to the acquired request data of the processing request; if so, executing a trigger action corresponding to the trigger condition to change the attribute parameters of the fields or other objects on the application page, avoiding code modification developed at the back end, improving the working efficiency of changing the attribute parameters, and adjusting the visual effect of the application page according to the personalized requirements. The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. An application rule configuration method, comprising:

2. The method according to claim 1, wherein, when it is detected that the target time point arrives, the detection of a trigger condition included in the application rule corresponding to the application page is started, and if it is detected that the trigger condition is satisfied, a trigger action corresponding to the trigger condition is executed.

3. The method according to claim 1, wherein the determining, according to the condition configuration action submitted for the rule to be configured, the trigger condition corresponding to the condition detection comprises:

4. The method of claim 3, wherein determining at least one selectable comparison value based on the target field and the target type comprises:

5. The method according to claim 1, wherein after the step of performing the trigger action after determining that the trigger condition is satisfied is performed by the action configuration request submitted for the application rule, the method further comprises:

and if so, executing a trigger action corresponding to the trigger condition.

6. The method of claim 5, wherein the processing request submitted for the application page comprises an editing request submitted for a particular field on the application page; whether the target time point of the application rule corresponding to the application page is reached is detected in the following mode:

if not, detecting that the target time point does not arrive;

if yes, detecting that the target time point arrives;

if not, detecting that the target time point does not arrive.

7. The method of claim 5, wherein whether the trigger condition included in the application rule is satisfied is determined by:

if so, determining that the trigger condition is met;

if not, determining that the triggering condition is not met.

8. The method of claim 5, wherein the triggering is a parameter configuration action that updates a visibility parameter of a target object from visible to invisible, and wherein the performing of the triggering action corresponding to the triggering condition comprises:

9. A page processing method is characterized by comprising the following steps:

and if so, executing a trigger action corresponding to the trigger condition.

10. An application rule configuration apparatus, comprising: