CN114003272A - Method for configuring embedded point parameters and trigger conditions - Google Patents
Method for configuring embedded point parameters and trigger conditions Download PDFInfo
- Publication number
- CN114003272A CN114003272A CN202111281816.2A CN202111281816A CN114003272A CN 114003272 A CN114003272 A CN 114003272A CN 202111281816 A CN202111281816 A CN 202111281816A CN 114003272 A CN114003272 A CN 114003272A
- Authority
- CN
- China
- Prior art keywords
- variable
- buried point
- value
- dsl
- condition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000006870 function Effects 0.000 claims description 43
- 230000001960 triggered effect Effects 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000012856 packing Methods 0.000 claims description 2
- 230000010485 coping Effects 0.000 abstract 1
- 238000011161 development Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000009545 invasion Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 150000001720 carbohydrates Chemical class 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method for collocating a buried point parameter and a trigger condition, which is characterized by comprising the following steps of 1, pulling and updating a DSL code; step 2, executing DSL codes; step 3, creating a variable management unit; step 4, creating a hook function of a target, step 5, configuring a preset buried point condition, and analyzing specific content of the buried point condition constraint according to the buried point condition; step 6, embedding point data assembly, namely assembling the embedding point data according to the structure of the Props and reporting; if the report condition is not met, the process is ended. By integrating DSL execution SDK at the APP end and issuing DSL codes by a far-end server, the embedded point dynamic is realized, and the operation deployment capability can be issued to the APP as a patch at any time and can be dynamically executed. The capability of coping with complex services and requirements is stronger, and the method is closer to the actual application scene.
Description
Technical Field
The invention relates to the field of APP data acquisition, in particular to a method for configuring a buried point parameter and a trigger condition in an APP complex service scene.
Background
When the number of users and daily lives of the APP reach a certain scale, the user behavior data collection of the APP becomes very important. Some existing embedded point acquisition and analysis products in the market at present, such as Growing IO, policies and the like, usually intercept behavior operations of users or life cycles of some controls on an acquisition layer of an APP end, and achieve the effect of 'fully embedding points'. However, in a complex service scenario or a situation that complex service data needs to be reported is weak, and in a complex and special service scenario, conditions for triggering a point burying also come up endlessly, for example, when condition a is satisfied, one point burying is triggered, and when condition B is satisfied, another point burying is triggered. Or when the page A comes from the page B, the data carried by the buried point of a trigger event needs an assembly mode; when the A page comes from the C page, the data carried by the buried point needs another assembling mode. The development technology of the APP terminal is complex and diverse at present, the development languages are different, and the problem of universality exists; the operation deployment capability needs to be achieved, the operation deployment capability can be issued to the APP as a patch at any time, and the operation deployment capability can be dynamically executed. A more sophisticated solution is needed.
Therefore, a method for configuring a buried point parameter and a trigger condition under an APP complex service scene is needed.
Disclosure of Invention
The technical problem to be solved by the invention is to overcome the defect of the existing business scheme for supporting a complex service scene, and provide a DSL-based method for configuring a buried point parameter and a trigger condition in an APP complex service scene. The full name of DSL is Domain specific Language, a Domain specific Language.
In order to solve the technical problem, the invention provides a method for configuring a buried point parameter and a trigger condition, wherein a variable template is provided in a designed DSL grammar to support access to all variables in an APP; and the conditional logic judgment grammar which can be combined with the variable template is designed, the effect of comprehensively replacing the original APP embedded sample plate code is achieved, and the method is characterized by comprising the following steps:
step 1, pulling and updating DSL codes; the method specifically comprises the following steps: reading a local embedded point configuration version number when the APP is started, and initiating a request to an embedded point configuration management service to obtain the latest configuration and configuration version number; the configuration comprises a DSL code, and the DSL code comprises the agreed 6 syntax keywords: the method comprises the following steps of modules, functions, buried point types, buried point names, buried point conditions and buried point data; the DSL code is used for reporting a corresponding embedded point type, an embedded point name and embedded point data of a embedded point if a function in the module is called and a embedded point condition is met, and the APP transmits the DSL code into the executor and updates a local embedded point configuration version number;
step 2, executing DSL codes; the method specifically comprises the following steps: analyzing corresponding modules, functions, buried point types, buried point names, buried point conditions and buried point data in DSL codes according to 6 grammatical keywords agreed by the DSL based on the Json character string;
step 3, creating a variable management unit; the method specifically comprises the following steps: the variable management unit is a key-value memory and is used for associating the variable template in the DSL code with the variable in the APP; assigning a key in a variable template in the DSL code so as to assign a variable in the APP to the key, and obtaining a value through the key when a buried point is triggered; the variable template is defined as: { "IAMValueCapture": value CaptureKey "}, wherein the value CaptureKey is the unique identifier of the variable in the APP;
step 4, creating a hook function of the target, specifically: resolving the type and function of a target according to the buried point type and function field in the DSL, and creating a hook function of the function; when the target function is called, the hook function is entered for assembling and reporting the corresponding embedded point type, embedded point name and embedded point data of the embedded point;
step 5, configuring a preset buried point condition, and analyzing specific content of the buried point condition constraint according to the buried point condition;
step 6, buried point data assembly, which specifically comprises the following steps: according to buried point data in the DSL, the value of a variable management unit is taken according to a variable template, and finally, the buried point data is assembled according to the structure of the Props and reported; if the report condition is not met, the process is ended.
In step 1, the buried point configuration management service includes a remote server, and the 6 syntax keywords in the DSL code are configured as description rules of the buried point, specifically:
[{"ModuleName":"",
"FuncName":"",
"EventType":"",
"EventName":"",
"Conditions":[{"l":"","opt":"","r":""}],
"Props":{}}]
wherein, ModuleName refers to a module; FuncName refers to a function; EventType refers to the type of the buried point event; EventName refers to a buried point name; conditions refer to buried point Conditions; the tips refers to buried point data, which contains service parameters.
In step 3, in the variable management unit, the variable in the APP is assigned to the valueCaptureKey through a variable capture grammar, where the variable capture grammar includes: packing the addValueForKey function of the variable management unit by macro definition or global function; the addValueForKey function is used for associating the variable in the APP with the valueCaptureKey, deeply copying the transmitted variable and storing the deeply copied variable into the variable management unit; if the value CaptureKey is the same, the old value is covered, and if the value is the object with the property of the closure, the object with the property of the closure is deeply copied and then stored in the variable management unit.
In the step 3, the variable management unit further includes a value forkey, and the value forkey is used for acquiring a specific variable through a value capturekey. The value is obtained from the variable management unit through the incoming value capturekey. If value is an object of closure properties, then the object of closure properties is executed and the value of return is returned to the variable management unit.
In the step 5, the buried point condition is an array including a plurality of condition units; each condition unit comprises a left value, a condition symbol and a right value, for each object, each condition unit sets the left value as 1 and the right value as r, the l and the r support constant and variable templates, and the condition symbol is set as opt, and the method comprises the following steps: equal, regular matching, greater than, less than, greater than or equal to, less than or equal to.
In step 5, the value of opt is specifically as follows:
1: equal;
2, regular matching;
4, greater than;
8, less than;
5, is greater than or equal to;
9: less than or equal to.
The invention achieves the following beneficial effects:
through a DSL-based mode, the embedded point semantization is realized. And the condition description grammar and the variable template grammar are originally created and are used for describing the trigger condition of the embedded point and reporting data. Any variable can be accessed by accessing the variable in the program through the DSL, and the method is not limited by the context of the program and the scope of the variable and is not limited by the scope of the development language; based on the condition description grammar, the variables in the APP program can be directly used to participate in condition judgment, and the method is closer to the actual scene of the buried point. After the DSL language is used, the relevant template codes of the embedded points do not need to be inserted into each end of the APP, and the embedded point maintenance cost and the code invasion are reduced.
According to the invention, the SDK is executed by integrating the DSL at the APP terminal, the DSL code can be issued by the remote server, the embedded point is dynamic, the APP does not need to be reissued when the embedded point needs to be adjusted, and the operation deployment capability can be issued to the APP as a patch at any time and can be dynamically executed.
Compared with a common buried point acquisition scheme in the prior art, the method has stronger capability of dealing with complex services and requirements and is closer to an actual application scene.
Drawings
FIG. 1 is a method flow diagram of an exemplary embodiment of the present invention;
FIG. 2 is a flow chart illustrating the operation of a variable template in an exemplary embodiment of the invention.
Detailed Description
The invention will be further described with reference to the drawings and the exemplary embodiments:
as shown in fig. 1, in the method for configuring a buried point parameter and a trigger condition in an APP complex service scenario, in this embodiment, a json-format character string is finally used as a description language, and a fixed key or template is used to describe a specific trigger time and a specific service scenario, which specifically includes:
step 1-1, pulling and updating DSL codes; the method specifically comprises the following steps: reading a local embedded point configuration version number when an APP is started, and initiating a request to a remote server in embedded point configuration management service to obtain the latest configuration and configuration version number; the configuration comprises a DSL code, and the DSL code comprises the agreed 6 syntax keywords: the method comprises the following steps of modules, functions, buried point types, buried point names, buried point conditions and buried point data; and the DSL code is used for reporting a corresponding embedded point type, an embedded point name and embedded point data of a embedded point if a function in the module is called and the embedded point condition is met, and the APP transmits the DSL code into the executor and updates the local embedded point configuration version number.
In step 1-1, the syntax keyword in the DSL code is configured in a description rule of a buried point, where the description rule specifically includes:
[{"ModuleName":"",
"FuncName":"",
"EventType":"",
"EventName":"",
"Conditions":[{"l":"","opt":"","r":""}],
"Props":{}}]
wherein, ModuleName refers to a module or a class name; FuncName refers to the notation of a method/function; EventType refers to the type of the buried point event; the EventName refers to a unique name defined in a buried point event; can be defined by the business side; conditions are triggered by buried points, and the Conditions are an array and comprise a plurality of condition units; each condition unit includes a left value, a condition symbol, and a right value, and for each object, each condition unit sets the left value as l and the right value as r, where l and r support constant and variable templates, and the condition symbol is opt, which may include: equality, regular matching, greater than, less than, greater than or equal to, less than or equal to; and the preps is buried point data, and the buried point data comprises service parameters.
Step 1-2, DSL code execution; the method specifically comprises the following steps: and resolving the DSL code according to a standard json format character string to obtain 6 corresponding grammar keywords in the DSL code: module, function, buried point type, buried point name, buried point condition and buried point data.
Step 1-3, creating a variable management unit; the method specifically comprises the following steps: the variable management unit is a key-value memory and is used for associating the variable template in the DSL code with the variable in the APP; assigning a key in a variable template in the DSL code so as to assign a real variable in the APP to the key, and obtaining a value through the key when a buried point is triggered; the variable template is defined as: { "IAMValueCapture": a valueCaptureKey "}, wherein the valueCaptureKey is the unique identifier of the variable in the APP.
A grammar template is designed in the DSL of the invention for matching variables in an APP program. The core idea is to use a "key" to obtain "value". This key is asserted in the DSL code and the APP creates a "key-value" management module that assigns the correct value of the variable to the "key" at the appropriate time using the variable capture grammar.
Variables in the APP are assigned to the valueCaptureKey through variable capture grammatical saccharides, including: wrapping addValueForKey function of the variable management unit by macro definition (iOS) or global function (android, RN);
the implementation principle of the variable management unit is as follows:
the addValueForKey function is used for associating variables in the APP with the valueCaptureKey, deeply copying the values of the transmitted variables, and storing the deeply copied values of the variables into a key-value memory of the variable management unit; to avoid memory leaks. If the value CaptureKey is the same, the old value is covered, and if the value is an object of the closure property, such as the arrow function of block of iOS, lambda of android and js, the object of the closure property is deeply copied and then stored in the key-value memory of the variable management unit.
The variable management unit also comprises a valueForKey which is used for acquiring specific variable assignment through a valueCaptureKey. The value is obtained from the variable management unit through the incoming value capturekey. If value is an object of closure properties, then the object of closure properties is executed and the value of return is returned to the variable management unit.
Step 1-4, creating a hook function of the target, specifically: resolving the type and function of a target according to the buried point type and function field in the DSL, and creating a hook function of the function; when the target function is called, the hook function is entered for assembling and reporting the corresponding embedded point type, embedded point name and embedded point data of the embedded point;
step 1-5, configuring a preset buried point condition, and analyzing specific content of the buried point condition constraint according to the buried point condition; the convenience of the DSL and APP memory access is realized to the greatest extent;
in an exemplary embodiment of the present invention, the value of the conditional symbol opt is specifically: 1: equal; 2, regular matching; 4, greater than; 8, less than; 5, is greater than or equal to; 9: less than or equal to. Namely 1< <0, 1< <1, 1< <2, 1< <3, 5 is 1 and 4 bitwise and is equivalent to (1< <0) & (1< < 2); 9 is a 1 and 8 bitwise and.
Then use the code
{"ModuleName":"TestClass",
"FuncName":"testFun",
"EventType":"test_event_type",
"EventName":"test_event_name",
"Conditions":[{"l":{"IAMValueCapture":"a"},"opt":4,"r":2}],
"Props":{"userId":{"IAMValueCapture":"b"}}}
For example, the effect is described as: when a testFun method in a testClass is called, if the value of a local variable a is greater than 2, reporting a buried point, wherein the type of the buried point is test _ event _ type, and the unique identification name of the buried point is test _ event _ name; the carried data is userId, and the value is the value of the local variable b.
Pseudo code equivalent to:
class TestClass{
void testFun(){
int a＝3,b＝2；
If(a>2){
sendDataAnalytics("test_event_type",
"test_event_name",
{"userId",b})；
}
}
}
TestClass.testFun()；
step 1-6, embedding data assembly, specifically comprising: according to buried point data in the DSL, the value of a variable management unit is taken according to a variable template, and finally, the buried point data is assembled according to the structure of the Props and reported; if the report condition is not met, the process is ended.
As shown in fig. 2, the specific workflow of the variable management unit includes: wrapping the specific service variable by using variable capture grammar sugar in the specific service code, and delivering the wrapped specific service variable to a variable management unit for key-value storage; when the DSL syntax interpreter identifies a variable template in the DSL, a specific variable value is acquired from the variable management unit according to the value CaptureKey in the variable template in the DSL, so that the variable template is accessed to a program variable.
The patent mainly needs to embody the condition logic judgment that the custom language can replace the source code, such as if (a ═ 1& & b >2), and a variable template can support the set of custom language to obtain any variable of the APP, so that the embedded point 'template' code scattered everywhere can be replaced.
The invention is mainly used for providing a method for configuring the parameter of the embedded point and the trigger condition in the APP complex service scene, and realizes the semantization of the embedded point through a DSL-based mode. And the condition description grammar and the variable template grammar are originally created and are used for describing the trigger condition of the embedded point and reporting data. Any variable can be accessed by accessing the variable in the program through the DSL, and the method is not limited by the context of the program and the scope of the variable and is not limited by the scope of the development language; based on the condition description grammar, the variables in the APP program can be directly used to participate in condition judgment, and the method is closer to the actual scene of the buried point. After the DSL language is used, the relevant template codes of the embedded points do not need to be inserted into each end of the APP, and the embedded point maintenance cost and the code invasion are reduced.
According to the invention, the SDK is executed by integrating the DSL at the APP terminal, the DSL code can be issued by the remote server, the embedded point is dynamic, the APP does not need to be reissued when the embedded point needs to be adjusted, and the operation deployment capability can be issued to the APP as a patch at any time and can be dynamically executed.
Compared with a common buried point acquisition scheme in the prior art, the method has stronger capability of dealing with complex services and requirements and is closer to an actual application scene.
The above embodiments do not limit the present invention in any way, and all other modifications and applications that can be made to the above embodiments in equivalent ways are within the scope of the present invention.
Claims (6)
1. A method for configuring embedded point parameters and trigger conditions is characterized by comprising the following steps:
step 1, pulling and updating DSL codes; the method specifically comprises the following steps: reading a local embedded point configuration version number when the APP is started, and initiating a request to an embedded point configuration management service to obtain the latest configuration and configuration version number; the configuration comprises a DSL code, and the DSL code comprises the agreed 6 syntax keywords: the method comprises the following steps of modules, functions, buried point types, buried point names, buried point conditions and buried point data; the DSL code is used for reporting a corresponding embedded point type, an embedded point name and embedded point data of a embedded point if a function in the module is called and a embedded point condition is met, and the APP transmits the DSL code into the executor and updates a local embedded point configuration version number;
step 2, executing DSL codes; the method specifically comprises the following steps: analyzing corresponding modules, functions, buried point types, buried point names, buried point conditions and buried point data in DSL codes according to 6 grammatical keywords agreed by the DSL based on the Json character string;
step 3, creating a variable management unit; the method specifically comprises the following steps: the variable management unit is a key-value memory and is used for associating the variable template in the DSL code with the variable in the APP; assigning a key in a variable template in the DSL code so as to assign a variable in the APP to the key, and obtaining a value through the key when a buried point is triggered; the variable template is defined as: { "IAMValueCapture": value CaptureKey "}, wherein the value CaptureKey is the unique identifier of the variable in the APP;
step 4, creating a hook function of the target, specifically: resolving the type and function of a target according to the buried point type and function field in the DSL, and creating a hook function of the function; when the target function is called, the hook function is entered for assembling and reporting the corresponding embedded point type, embedded point name and embedded point data of the embedded point;
step 5, configuring a preset buried point condition, and analyzing specific content of the buried point condition constraint according to the buried point condition;
step 6, buried point data assembly, which specifically comprises the following steps: according to buried point data in the DSL, the value of a variable management unit is taken according to a variable template, and finally, the buried point data is assembled according to the structure of the Props and reported; if the report condition is not met, the process is ended.
2. The method of claim 1, wherein the method further comprises: in step 1, the buried point configuration management service includes a remote server, and the 6 syntax keywords in the DSL code are configured as description rules of the buried point, specifically:
[{"ModuleName":"",
"FuncName":"",
"EventType":"",
"EventName":"",
"Conditions":[{"l":"","opt":"","r":""}],
"Props":{}}]
wherein, ModuleName refers to a module; FuncName refers to a function; EventType refers to the type of the buried point event; EventName refers to a buried point name; conditions refer to buried point Conditions; the tips refers to buried point data, which contains service parameters.
3. The method as claimed in claim 2, wherein the method comprises: in step 3, in the variable management unit, the variable in the APP is assigned to the valueCaptureKey through a variable capture grammar, where the variable capture grammar includes: packing the addValueForKey function of the variable management unit by macro definition or global function; the addValueForKey function is used for associating the variable in the APP with the valueCaptureKey, deeply copying the transmitted variable and storing the deeply copied variable into the variable management unit; if the value CaptureKey is the same, the old value is covered, and if the value is the object with the property of the closure, the object with the property of the closure is deeply copied and then stored in the variable management unit.
4. The method as claimed in claim 3, wherein the method comprises: in the step 3, the variable management unit further includes a value forkey, where the value forkey is used to obtain a specific variable through a value capturekey, and obtain a value from the variable management unit through the introduced value capturekey; if value is an object of closure properties, then the object of closure properties is executed and the value of return is returned to the variable management unit.
5. The method as claimed in claim 4, wherein the method comprises: in the step 5, the buried point condition is an array including a plurality of condition units; each condition unit comprises a left value, a condition symbol and a right value, for each object, each condition unit sets the left value as 1 and the right value as r, the l and the r support constant and variable templates, and the condition symbol is set as opt, and the method comprises the following steps: equal, regular matching, greater than, less than, greater than or equal to, less than or equal to.
6. The method as claimed in claim 5, wherein in step 5, opt has a value:
1: equal;
2, regular matching;
4, greater than;
8, less than;
5, is greater than or equal to;
9: less than or equal to.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111281816.2A CN114003272B (en) | 2021-11-01 | 2021-11-01 | Buried point parameter and trigger condition collocation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111281816.2A CN114003272B (en) | 2021-11-01 | 2021-11-01 | Buried point parameter and trigger condition collocation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114003272A true CN114003272A (en) | 2022-02-01 |
| CN114003272B CN114003272B (en) | 2024-04-16 |
Family
ID=79925973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111281816.2A Active CN114003272B (en) | 2021-11-01 | 2021-11-01 | Buried point parameter and trigger condition collocation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114003272B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109241080A (en) * | 2018-09-29 | 2019-01-18 | 焦点科技股份有限公司 | A kind of the building application method and its system of FQL query language |
| WO2019100614A1 (en) * | 2017-11-22 | 2019-05-31 | 平安科技（深圳）有限公司 | Buried point data processing method, device, computer device and storage medium |
| CN110489597A (en) * | 2018-05-10 | 2019-11-22 | 华为技术有限公司 | A kind of method and terminal device obtaining data |
| WO2020082558A1 (en) * | 2018-10-26 | 2020-04-30 | 深圳壹账通智能科技有限公司 | Function name-based breakpoint setting method, device, computer apparatus, and storage medium |
| CN112230903A (en) * | 2020-10-12 | 2021-01-15 | 上海赛可出行科技服务有限公司 | Lightweight decoupling type point burying method and device based on iOS application |
| CN112256701A (en) * | 2020-10-22 | 2021-01-22 | 广东万唯计算机服务有限公司 | Dynamic buried point data acquisition system and use method thereof |
| CN112506492A (en) * | 2020-09-02 | 2021-03-16 | 上海赛可出行科技服务有限公司 | Visual point burying method supporting dynamic scene configuration |
| CN112905944A (en) * | 2021-04-06 | 2021-06-04 | 成都新希望金融信息有限公司 | Page online dynamic generation method and device, electronic equipment and readable storage medium |
-
2021
- 2021-11-01 CN CN202111281816.2A patent/CN114003272B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019100614A1 (en) * | 2017-11-22 | 2019-05-31 | 平安科技（深圳）有限公司 | Buried point data processing method, device, computer device and storage medium |
| CN110489597A (en) * | 2018-05-10 | 2019-11-22 | 华为技术有限公司 | A kind of method and terminal device obtaining data |
| CN109241080A (en) * | 2018-09-29 | 2019-01-18 | 焦点科技股份有限公司 | A kind of the building application method and its system of FQL query language |
| WO2020082558A1 (en) * | 2018-10-26 | 2020-04-30 | 深圳壹账通智能科技有限公司 | Function name-based breakpoint setting method, device, computer apparatus, and storage medium |
| CN112506492A (en) * | 2020-09-02 | 2021-03-16 | 上海赛可出行科技服务有限公司 | Visual point burying method supporting dynamic scene configuration |
| CN112230903A (en) * | 2020-10-12 | 2021-01-15 | 上海赛可出行科技服务有限公司 | Lightweight decoupling type point burying method and device based on iOS application |
| CN112256701A (en) * | 2020-10-22 | 2021-01-22 | 广东万唯计算机服务有限公司 | Dynamic buried point data acquisition system and use method thereof |
| CN112905944A (en) * | 2021-04-06 | 2021-06-04 | 成都新希望金融信息有限公司 | Page online dynamic generation method and device, electronic equipment and readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 廖爱红;罗铭涛;: "埋点管理系统分析与设计", 办公自动化, no. 16, 15 August 2020 (2020-08-15), pages 35 - 37 * |
| 曹嘉欣;童蕙;: "大数据分析在商业银行零售业务创新中的实践", 信息技术与标准化, no. 05, 10 May 2020 (2020-05-10), pages 29 - 33 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114003272B (en) | 2024-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8719784B2 (en) | Assigning runtime artifacts to software components | |
| CN111158674B (en) | Component management method, system, device and storage medium | |
| CN108446223B (en) | Business scene automatic testing method based on dynamic compilation | |
| CN104077140A (en) | Automatic compiling method and compiling device for continuous integration | |
| CN101515232A (en) | Software continuous integration system and method | |
| CN104331366A (en) | Test case design efficiency promotion method and system | |
| CN109558304B (en) | Component association analysis method and device and electronic equipment | |
| CN109144533A (en) | A kind of method, system and the computer installation of update and the load of application program | |
| CN108763323B (en) | Meteorological grid point file application method based on resource set and big data technology | |
| WO2011032072A1 (en) | System and method of substituting parameter sets in self-contained mini-applications | |
| CN112328226B (en) | Embedded system automatic test code generation method and device | |
| CN110069259A (en) | Analytic method, device, electronic equipment and storage medium based on idl file | |
| CN111984228A (en) | Interface document processing method and device, computer equipment and storage medium | |
| CN111382070A (en) | Compatibility testing method and device, storage medium and computer equipment | |
| CN114595201A (en) | Method, equipment and storage medium for inquiring acquisition record of interface access log | |
| CN101483562B (en) | Method, system and related equipment for routine test | |
| CN104461531A (en) | Implementing method for self-defined functions of reporting system | |
| CN113360799A (en) | Access behavior log acquisition method and device, computer equipment and storage medium | |
| CN112667287A (en) | Method, device and equipment for creating rule file and computer readable storage medium | |
| CN114003272A (en) | Method for configuring embedded point parameters and trigger conditions | |
| CN111858258A (en) | Memory monitoring method and device, electronic equipment and storage medium | |
| CN110162299A (en) | Web program and its Quick Development Framework, development approach and relevant device | |
| CN112596823B (en) | Safety control method and device and electronic equipment | |
| CN112637085B (en) | Flow recording method and device, computer equipment and storage medium | |
| CN114371884A (en) | Method, device, equipment and storage medium for processing Flink calculation task |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |