CN111460779B - Method for rendering and accessing flow form data based on Activiti - Google Patents
Method for rendering and accessing flow form data based on Activiti Download PDFInfo
- Publication number
- CN111460779B CN111460779B CN202010244339.1A CN202010244339A CN111460779B CN 111460779 B CN111460779 B CN 111460779B CN 202010244339 A CN202010244339 A CN 202010244339A CN 111460779 B CN111460779 B CN 111460779B
- Authority
- CN
- China
- Prior art keywords
- variable
- variables
- task
- flow
- data
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 238000009877 rendering Methods 0.000 title claims abstract description 29
- 230000000694 effects Effects 0.000 title claims abstract description 15
- 230000008569 process Effects 0.000 claims abstract description 23
- 230000007246 mechanism Effects 0.000 claims description 3
- 241001409866 Actitis Species 0.000 claims 1
- 230000009471 action Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention provides an action-based form data rendering method of a flow engine and a related form data access method, wherein the rendering method specifically comprises the following steps: a form data rendering method based on an Activiti flow engine is characterized by comprising the following steps: when a dynamic form is rendered, two parameters of a form Key and a flow variable are obtained, and a form page in the flow is obtained according to the context in the flow and the form Key, wherein the variables in the form are represented by variable names, and the flow variables are stored in Global and Task storage areas. And judging whether the variables defined in the form exist in the process variables or not according to the variable names. If the variable exists, the variable of the form page is replaced, if the variable does not exist, the variable is replaced by an empty string, and then the rendered page is returned to complete rendering. By the method, a new form data access process can be realized on the Activiti, new data can be created in the node, and the form content can be changed at minimum cost. And in each node the history of the previous node can be viewed.
Description
Technical Field
The application relates to an Activiti flow engine, an access of form data and a rendering method of a dynamic form.
Background
Based on the default dynamic form rendering mode of the flow of the active engine, firstly judging whether the Global variable has the form variable value or not during rendering, and if not, failing to render. So, in order to succeed in node rendering of the subsequent flow, the following method is mainly adopted at present:
the method comprises the steps that firstly, all form variables are displayed on a starting form at the beginning of a flow, and then all form variables are initialized;
the second method is that the default value of the variable in the dynamic form is represented by using an empty string.
The first disadvantage of the method is that if the content of the subsequent dynamic form needs to be newly added, the form of the starting node needs to be modified, and the form variable is initialized, so that the cost of modifying the form is increased.
The second disadvantage is that, because the variable default value of the dynamic form is an empty string, the variables cannot be displayed back using the rendering form method. Because the form has no variable value in the flow corresponding to the variable name, the history task form cannot be checked.
Disclosure of Invention
In view of the above-mentioned drawbacks or shortcomings in the prior art, the present invention provides an actigraphy-based flow chart data rendering method capable of viewing history data.
The technical scheme adopted by the invention is as follows:
a form data rendering method based on an Activiti flow engine comprises the following steps: a form data rendering method based on an Activiti flow engine is characterized by comprising the following steps: when a dynamic form is rendered, two parameters of a form Key and a flow variable are obtained, and a form page in the flow is obtained according to the context in the flow and the form Key, wherein the variables in the form are represented by variable names, and the flow variables are stored in Global and Task storage areas. And judging whether the variables defined in the form exist in the process variables or not according to the variable names. If the variable exists, the variable of the form page is replaced, if the variable does not exist, the variable is replaced by an empty string, and then the rendered page is returned to complete rendering.
Based on the rendering method, the form content of all the previous completed nodes can be checked at any node in the process, and if new content is to be added at a certain process node, no other node forms need to be modified.
Further, the rendering method establishes task implementation through a Command mechanism defined by an action flow engine.
Further, the storage of the form data is specifically:
in the process starting node, the back end stores the form variable in the process Global; in the Task node, the back end stores the editable form variable in the flow Global, and simultaneously acquires all Global variables and stores the Global variables in the Task. The Global variable takes a flow ID and a variable name as keys.
Further, the flow variable may be a Global variable or a Task variable, where the Task variable uses the variable names and Task IDs of all variables of the node as keys.
A form data access method based on an Activiti flow engine comprises the following steps:
(1) The variables in the form are set to be represented by variable names.
(2) The user initiates the process at the front end. And the back end receives the request, acquires the corresponding form by using the form Key and acquires the data of the context through the Acitiviti flow engine. And the variable names and the flow IDs in the back-end data are spliced to form a query key of the Global storage area, and the variables of the Global storage area are checked. And judging whether the variables defined in the form exist in the Global storage area according to the variable names:
a. if so, the corresponding value is taken to replace the variable in the form.
b. If not, the empty string is used to replace the variable in the form.
(3) The back end completes the replacement of all variables in the form, and the rendered dynamic form is returned to the front end, and the front end displays the dynamic form.
(4) The user edits data in the form displayed at the front end and submits the form, and the form variable is transmitted to the back end.
(5) The back end processes the form variables: and checking whether the Global storage area corresponds to the variable name.
A. If not, the variable name is created in Global, and the corresponding value is the value corresponding to the form.
B. If so, the value is updated directly to the value in the form.
(6) And combining variable names of all variables of the node with the Task ID to construct a new key, wherein the corresponding value is the value of the variable name in Global. The key value pairs are stored in the Task.
And (5) repeating the steps 2-6 to finish the data access to all nodes in the flow.
Further, if the history node data is to be checked, in step 2, the table is rendered by using the Task variable of the corresponding node, specifically as follows:
the user initiates to check the history data of a certain node at the front end. And the back end receives the request and acquires the data of the context through an aciiviti flow engine. And the back end splices the variable names in the data and the Task ID to form a query key of the Task storage area, and checks the variables of the Task storage area. And judging whether the variables defined in the form exist in the Task storage area or not according to the variable names:
a. if so, the corresponding value is taken to replace the variable in the form.
b. If not, the empty string is used to replace the variable in the form.
The back end completes the replacement of all variables in the form, the rendered dynamic form is returned to the front end, and the front end displays the historical data of the node.
The beneficial effects are that:
in the method, the contents displayed in each form are different, and the contents of the forms can be frequently changed according to the requirements. For this flow with the changing form content requirement type, it is a popular requirement to view the form for each task. The method of the invention can not only realize the checking of the historical task form of each flow, but also change the form content with minimum cost.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings, in which:
FIG. 1 is a flow chart of an Activiti-based flow chart data access scheme for viewing historical data.
Fig. 2 is a typical flow diagram suitable for the present scheme: job entering flow. Personnel, administration and IT nodes in the flow have frequently changed demands, such as increasing and decreasing elements of pages and the like, according to actual conditions.
FIG. 3 is a form page of a department manager approval in an job entry flow. The upper part of the form page represents the non-editable variable and the lower part represents the editable variable.
Fig. 4 is a flowchart of the entire completed job-entering flowchart. Clicking the view button can view the history form content of the node.
FIG. 5 shows the historical form content of a department manager approving nodes in the job entry flow.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the invention are shown in the drawings.
The invention provides a form data rendering method based on an Activiti flow engine, which comprises the following steps: a form data rendering method based on an Activiti flow engine is characterized by comprising the following steps: when a dynamic form is rendered, two parameters of a form Key and a flow variable are obtained, and a form page in the flow is obtained according to the context in the flow and the form Key, wherein the variables in the form are represented by variable names, and the flow variables are stored in Global and Task storage areas. And judging whether the variables defined in the form exist in the process variables or not according to the variable names. If the variable exists, the variable of the form page is replaced, if the variable does not exist, the variable is replaced by an empty string, and then the rendered page is returned to complete rendering.
By using the form rendering mode, if one flow node needs to add new content, the corresponding form content can be directly modified without modifying other node forms. The problem of error reporting when an active native rendering mode is used is avoided.
Preferably, the rendering method establishes task implementation through a Command mechanism customized by an Activiti flow engine.
A task is customized to render the dynamic form. The custom task requires two parameters, one is a form Key and one is a flow variable. The user-defined task acquires a form page in the flow according to the context in the flow and the input form Key, and then judges whether a variable defined in the form exists in the flow variable or not. If so, replacing the variable of the form page, if not, replacing the variable with the empty string, and then returning to the rendered page.
In the method, the storage of the form data is specifically as follows: the front end transmits the starting form variable to the back end, and the back end stores the form variable in the flow Global; the front end of the Task node transmits the form variable of the editable part to the back end, and the back end stores the form variable in the flow Global, and simultaneously acquires all the Global variables and stores the Global variables in the Task. The Global variable takes the flow ID and the variable name as keys, and the variables before the Global variable is covered each time are stored in the Global, and the Global variable is unique in the whole flow process. Form variables of the non-editable part are not transmitted to the back end, so that the cost of interface transmission can be reduced. In the method, global variables obtained by each Task node are backed up to the Task, and each Task can store a full-quantity flow variable in a Task state. The back end can check the historical form data by searching the form Key and returning the form rendered by using the Task variable to the front end.
Wherein, the variable names in the form cannot be represented by empty character strings, and are represented by variable symbols, such as: with this approach, the back-end renders the form to correctly reveal the history Task variable when viewing the history Task form.
In addition, the invention also provides a form data access method based on an action flow engine, and fig. 1 is a flow chart of the form data access method based on the action capable of viewing history data, as shown in fig. 1, the method comprises the following steps:
(1) The variables in the form are set to be represented by variable names.
(2) The user initiates the process at the front end. And the back end receives the request, acquires the corresponding form by using the form Key and acquires the data of the context through the Acitiviti flow engine. And the back end splices the variable names and the flow IDs in the data to form a query key of the Global storage area, and checks the variables of the Global storage area. And judging whether the variables defined in the form exist in the Global storage area according to the variable names:
a. if so, the corresponding value is taken to replace the variable in the form.
b. If not, the empty string is used to replace the variable in the form.
(3) The back end completes the replacement of all variables in the form, and the rendered dynamic form is returned to the front end, and the front end displays the dynamic form. (4) The user edits data in the form displayed at the front end and submits the form, and the form variable is transmitted to the back end.
(5) The back end processes the form variables: and checking whether the Global storage area corresponds to the variable name.
A. If not, the variable name is created in Global, and the corresponding value is the value corresponding to the form.
B. If so, the value is updated directly to the value in the form.
(6) And combining variable names of all variables of the node with the Task ID to construct a new key, wherein the corresponding value is the value of the variable name in Global. The key value pairs are stored in the Task.
And (5) repeating the steps 2-6 to finish the data access to all nodes in the flow.
The invention is further described below in connection with specific job-entering flows.
As shown in fig. 2, the process includes a process starting node, a department responsible person examining and approving node, an IT opening job entering account node, an administrative handling job entering procedure node, a personnel inputting complete information node, an IT equipment issuing node, an IT cancelling job entering account node, an OA account creating node, and the like, and each node sets a corresponding form Key when the process is created. The fields seen on each page are represented using variables such as the station number $ { placeNumber }, etc. When a user initiates a flow, a corresponding form is acquired by using the form Key, and the context data is acquired through an aciiviti flow engine. And the method of the invention is used for rendering and displaying the form at the front end, fig. 3 is a Task form page of the approval node of the department responsible person, the user submits the form after the front end inputs the information to be filled (resource allocation in fig. 3), the form variable of the editable part (resource allocation in fig. 3) is transmitted to the rear end, the rear end stores the form variable in the process Global, and all Global variables are acquired and stored in the Task. Because the data of each node is backed up to the Task, the Task form of each node can be checked, as shown in fig. 3, and the history data of a certain node is initiated to be checked by clicking a check button in the graph for the circulation record of the job entering flow, and the back end receives the request and acquires the data of the context through the Acitiviti flow engine. And the back end splices the variable names in the data and the Task ID to form a query key of the Task storage area, and checks the variables of the Task storage area. And judging whether the variables defined in the form exist in the Task storage area or not according to the variable names:
a. if so, the corresponding value is taken to replace the variable in the form.
b. If not, the empty string is used to replace the variable in the form.
The back end completes the replacement of all variables in the form, returns the rendered dynamic form to the front end, and the front end displays the historical data of the node, as shown in fig. 5.
Through the scheme, the front end can record the circulation as shown in fig. 4, click a view button in the diagram, and through the rendering method, the history form content as shown in fig. 5 can be displayed. And fields in the nodes can be added and deleted arbitrarily according to requirements without modifying other node contents. For example, a new field is added in the personnel entry complete information node in the job entry flow of fig. 2, and the contents of the corresponding form are directly modified without modifying other node forms. The problem of error reporting when an active native rendering mode is used is avoided.
Claims (5)
1. A form data rendering method based on an Activiti flow engine is characterized by comprising the following steps: when a dynamic form is rendered, two parameters of a form Key and a flow variable are obtained, and a form page in the flow is obtained according to the context in the flow and the form Key, wherein the variable in the form page is represented by a variable name, and the flow variable is stored in a Global and Task storage area, specifically:
in the process starting node, the back end stores the form variable in the process Global; in the Task node, the back end stores editable form variables in the flow Global, and simultaneously acquires all the Global variables and stores the Global variables in the Task; the Global variable takes a flow ID and a variable name as keys; then judging whether the variables defined in the form exist in the process variables or not according to the variable names; if the variable is present, replacing the variable of the form page with the value corresponding to the variable, if the variable is not present, replacing the variable with an empty string, and then returning to the rendered page to complete rendering;
when viewing the historical node data, the method specifically comprises the following steps:
a user initiates to check the history data of a certain node at the front end; the back end receives the request and acquires the data of the context through an aciiviti flow engine; the back end splices the variable names in the data and the Task ID to form a query key of the Task storage area, and checks the variables of the Task storage area; and judging whether the variables defined in the form exist in the Task storage area or not according to the variable names:
a. if the variable exists, a corresponding value is obtained, and the variable in the form is replaced;
b. if not, replacing variables in the form with empty strings;
the back end completes the replacement of all variables in the form, the rendered dynamic form is returned to the front end, and the front end displays the historical data of the task nodes.
2. The method of claim 1, wherein the rendering method is implemented by creating tasks through a Command mechanism customized by an actiti flow engine.
3. The method according to claim 1, wherein the flow variable may be a Global variable or a Task variable, and the Task variable uses a variable name and a Task ID of all variables of a Task node as keys.
4. The form data access method based on the Activiti flow engine is characterized by comprising the following steps of:
(1) Setting variables in the form to be represented by variable names;
(2) The user initiates a process at the front end; the back end receives the request, acquires the corresponding form by using the form Key and acquires the data of the context through the Acitiviti flow engine; the back end splices the variable names and the flow IDs in the data to form a query key of the Global storage area, and checks the variables of the Global storage area; and judging whether the variables defined in the form exist in the Global storage area according to the variable names:
a. if the variable exists, a corresponding value is obtained, and the variable in the form is replaced;
b. if not, replacing variables in the form with empty strings;
(3) The back end completes the replacement of all variables in the form, the rendered dynamic form is returned to the front end, and the front end displays the dynamic form;
(4) The user edits data in the form displayed at the front end, submits the form, and transmits the form variable to the rear end;
(5) The back end processes the form variables: checking whether the Global storage area corresponds to the value corresponding to the corresponding variable name:
A. if the variable name does not exist, the variable name is created in Global, and the corresponding value is the value corresponding to the form;
B. if so, directly updating the value into the value in the form;
(6) Combining variable names of all variables of the Task node with Task ID to construct a new key, wherein the corresponding value is the value of the variable name in Global; storing the key value pairs into a Task;
and (5) repeating the steps 2-6 to finish the data access to all nodes in the flow.
5. The form data access method based on the Activiti process engine of claim 4, wherein when viewing the history node data, the method is specifically as follows:
a user initiates to check the history data of a certain node at the front end; the back end receives the request and acquires the data of the context through an aciiviti flow engine; the back end splices the variable names in the data and the Task ID to form a query key of the Task storage area, and checks the variables of the Task storage area; and judging whether the variables defined in the form exist in the Task storage area or not according to the variable names:
a. if the variable exists, a corresponding value is obtained, and the variable in the form is replaced;
b. if not, replacing variables in the form with empty strings;
the back end completes the replacement of all variables in the form, the rendered dynamic form is returned to the front end, and the front end displays the historical data of the task nodes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010244339.1A CN111460779B (en) | 2020-03-31 | 2020-03-31 | Method for rendering and accessing flow form data based on Activiti |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010244339.1A CN111460779B (en) | 2020-03-31 | 2020-03-31 | Method for rendering and accessing flow form data based on Activiti |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111460779A CN111460779A (en) | 2020-07-28 |
| CN111460779B true CN111460779B (en) | 2024-03-15 |
Family
ID=71683466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010244339.1A Active CN111460779B (en) | 2020-03-31 | 2020-03-31 | Method for rendering and accessing flow form data based on Activiti |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111460779B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099679B (en) * | 2020-08-30 | 2023-09-19 | 浪潮金融信息技术有限公司 | TTU function packaging method based on software configuration |
| CN113434119B (en) * | 2021-06-24 | 2024-04-26 | 江苏创源电子有限公司 | Service processing method and device based on flow control |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461484A (en) * | 2013-09-16 | 2015-03-25 | 腾讯科技（深圳）有限公司 | Front-end template implementation method and device |
| CN105373523A (en) * | 2015-10-14 | 2016-03-02 | 浪潮软件集团有限公司 | Workflow solution method based on user-defined form and Activiti |
| JP2016162184A (en) * | 2015-03-02 | 2016-09-05 | キヤノン株式会社 | Information processing system, information processing device, control method and computer program |
| CN105989440A (en) * | 2015-02-12 | 2016-10-05 | 杨波 | Process customization processing method and workflow engine thereof |
| CN106779594A (en) * | 2016-12-01 | 2017-05-31 | 江苏鸿信系统集成有限公司 | A kind of Workflow management method based on Activiti |
| CN107122173A (en) * | 2017-03-28 | 2017-09-01 | 成都优易数据有限公司 | A kind of adaptation activiti, the list generation method that can be pulled |
| CN107578217A (en) * | 2017-09-13 | 2018-01-12 | 深圳市沃易科技有限公司 | A kind of working electronic stream is autonomously generated method, apparatus and office management system |
| CN107665170A (en) * | 2016-07-29 | 2018-02-06 | 高德软件有限公司 | A kind of flow testing method and device |
| CN110162760A (en) * | 2019-05-23 | 2019-08-23 | 武汉神算云信息科技有限责任公司 | A kind of form customization method based on procedure links |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130283141A1 (en) * | 2012-04-20 | 2013-10-24 | Latitude Geographics Group Ltd. | Client Agnostic Spatial Workflow Form Definition and Rendering |
-
2020
- 2020-03-31 CN CN202010244339.1A patent/CN111460779B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461484A (en) * | 2013-09-16 | 2015-03-25 | 腾讯科技（深圳）有限公司 | Front-end template implementation method and device |
| CN105989440A (en) * | 2015-02-12 | 2016-10-05 | 杨波 | Process customization processing method and workflow engine thereof |
| JP2016162184A (en) * | 2015-03-02 | 2016-09-05 | キヤノン株式会社 | Information processing system, information processing device, control method and computer program |
| CN105373523A (en) * | 2015-10-14 | 2016-03-02 | 浪潮软件集团有限公司 | Workflow solution method based on user-defined form and Activiti |
| CN107665170A (en) * | 2016-07-29 | 2018-02-06 | 高德软件有限公司 | A kind of flow testing method and device |
| CN106779594A (en) * | 2016-12-01 | 2017-05-31 | 江苏鸿信系统集成有限公司 | A kind of Workflow management method based on Activiti |
| CN107122173A (en) * | 2017-03-28 | 2017-09-01 | 成都优易数据有限公司 | A kind of adaptation activiti, the list generation method that can be pulled |
| CN107578217A (en) * | 2017-09-13 | 2018-01-12 | 深圳市沃易科技有限公司 | A kind of working electronic stream is autonomously generated method, apparatus and office management system |
| CN110162760A (en) * | 2019-05-23 | 2019-08-23 | 武汉神算云信息科技有限责任公司 | A kind of form customization method based on procedure links |
Non-Patent Citations (1)
| Title |
|---|
| 张瑞圆.Activiti工作流结合外置表单技术研究.《电子设计工程》.2016,24-30. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111460779A (en) | 2020-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6035300A (en) | Method and apparatus for generating a user interface from the entity/attribute/relationship model of a database | |
| US7039658B2 (en) | Method and apparatus for generating web pages from templates | |
| US6448981B1 (en) | Intermediate user-interface definition method and system | |
| US7620647B2 (en) | Hierarchy global management system and user interface | |
| US7827478B2 (en) | Dynamic generation of form pages for accessing a database | |
| US20040243613A1 (en) | System and method for creating a custom view from information in a managed data store | |
| US8106903B2 (en) | System and method for visually representing a project using graphic elements | |
| US20070005634A1 (en) | Templates in a schema editor | |
| US20080221952A1 (en) | Workflow management system, workflow management server, progress management method, and storage medium | |
| US20110289399A1 (en) | System and method for document construction | |
| JPWO2006098031A1 (en) | Keyword management device | |
| US20020147725A1 (en) | Method and apparatus for database table definition | |
| US8185562B2 (en) | Business object browser for business query language | |
| CN111784108B (en) | Modeling method and device of main data management platform | |
| US20050240562A1 (en) | Method, computer program product and device for importing a plurality of data sets into a system | |
| CN111460779B (en) | Method for rendering and accessing flow form data based on Activiti | |
| US7409642B2 (en) | Method and system for applying user interface elements to data | |
| CN108228762B (en) | Method and system for configuring master database universal templates | |
| US20100218139A1 (en) | Search-friendly templates | |
| US9767146B2 (en) | Use of generated SQL for evaluation of decision point rules in a workflow system | |
| US7698651B2 (en) | Heuristic knowledge portal | |
| KR101150121B1 (en) | Method and apparatus for constructing representations of objects and entities | |
| CN110929494A (en) | Method for generating report drop-down box based on hierarchical tree | |
| CN116401407A (en) | Node attribute configuration method, device, equipment and storage medium of mind map | |
| CN112596719A (en) | Method and system for generating front-end and back-end codes |
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 |