CN114756234B - APP development method based on traditional application and dynamic configuration strategy - Google Patents
APP development method based on traditional application and dynamic configuration strategy Download PDFInfo
- Publication number
- CN114756234B CN114756234B CN202210659157.XA CN202210659157A CN114756234B CN 114756234 B CN114756234 B CN 114756234B CN 202210659157 A CN202210659157 A CN 202210659157A CN 114756234 B CN114756234 B CN 114756234B
- Authority
- CN
- China
- Prior art keywords
- component
- event
- function
- app
- controller
- 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
Images
Classifications
-
- 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/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to an APP development method based on traditional application and dynamic configuration strategy, comprising the following steps: receiving demand content provided by a client; checking whether the UI component middle layer and the event control middle layer have corresponding interaction; if so, assembling corresponding configuration files to generate a new product; if the UI component is not found in the middle layer; developing the UI component, storing the UI component in the middle layer, and assembling corresponding configuration files to generate a new product; if the event controller is not found in the middle layer; developing an event controller, storing the event controller in the middle layer, and assembling corresponding configuration files to generate a new product; the method solves the efficiency problem of traditional development and function iteration.
Description
Technical Field
The invention relates to the technical field of software development, in particular to an APP development method based on traditional application and dynamic configuration strategy.
Background
At present, due to rapid development of the internet era, the requirements of business on rapid innovation and iteration of APP products are higher and higher, and more severe requirements are provided for flexible change of online business and coverage rate and timeliness. In the prior art, when a service needs to add a new service product in an APP, the service needs to be developed to redevelop an application program and released to an application market, and the product can be displayed to a user after the user updates; when a service person finds that a product has a defect, the service person may achieve the defect repairing purpose by means of hot repair or re-shelving application. Such variety is clearly a challenge for companies that demand fast iterations, have flexible configuration of products on-line, and have flexible configurations.
Existing requirements, if iteration is needed, need to rewrite the corresponding UI and integrate it into the layout, and then need to be compatible with its logic in the page, such as: regular checks, special interaction logic, etc. The existing mode needs to repeatedly write corresponding UI and logic, UI components cannot be seamlessly used, and the existing mode is not very friendly to businesses which need to iterate quickly. What is more, it is important that the consistency of the interactions between the Android and the iOS cannot be guaranteed, and it takes a lot of time to make the two ends compatible when the two ends are inconsistent. Moreover, after the application is released to the online, if the native UI and the service logic need to be dynamically updated, the application can only be performed in an application updating manner, which is very inflexible.
Disclosure of Invention
Based on this, there is a need to provide an APP development method based on traditional application and dynamic configuration strategy, which has better flexibility and can be updated quickly by iteration.
The embodiment of the invention provides an APP development method based on a traditional application and a dynamic configuration strategy, which comprises the following steps:
receiving demand content provided by a client;
checking whether the UI component middle layer and the event control middle layer have corresponding interaction;
if so, assembling corresponding configuration files to generate a new product;
if the UI component is not found in the middle layer;
developing the UI component, storing the UI component in the middle layer, and assembling corresponding configuration files to generate a new product;
if the event controller is not found in the middle layer;
and developing an event controller, storing the event controller into the middle layer, and assembling corresponding configuration files to generate a new product.
Preferably, the APP comprises a UI component, a UI component logic interaction module and a service logic interaction function module, and the following mechanism is designed:
the UI component is dynamically updated, and developers can recombine the UI component according to the appointed UI configuration and generate a new service interface;
UI service logic configuration is updated, each configured UI can be written in advance and compatible according to service requirements or scenes where the component is used, and the new requirements can realize the self-service logic of the UI only by corresponding configuration;
and the application can utilize the existing UI components and the independent business process to recombine a new business process by configuring the JSON file meeting the strategy, so as to complete the creation of a new product.
Preferably, each UI component inherits a BaseView component, and implements a defined Base interface in the BaseView component.
Preferably, the Base interface includes initData, initView, and ondechfromwindow functions;
the initData function is mainly used in APP and used for processing UI component data;
the initView function is mainly used in the APP and used for view initialization operation of the UI component;
the ontechfromwindow function is mainly used for APP and is used for performance monitoring operation of UI components.
Preferably, the initData function is used for loading a JSON file, reading data, displaying the JSON file and the data into a UI control and finishing initialization operation of the data;
the initView function is used for rendering the UI component and displaying the UI component to a user;
the ontechfromwindow function is used to monitor memory jitter and memory overflow.
Preferably, the Base interface further comprises an isneedledsubscript function; the isNedSubscribe function is used for judging whether the UI component needs to receive the control of the event controller, if the UI component is set to true, the UI component indicates that the UI component needs to be classified into the control of the event controller, and if the UI component does not need to receive the control of the event controller, the isNedSubscribe function is opposite to the control of the event controller;
the Base interface also includes a getViewType function for returning the View type of the corresponding UI component and for interacting with the Event control in Event.
Preferably, the Base interface further comprises a getLineView function; the getLineView function is mainly used for returning whether the control needs underlining or not, if yes, an underlining object is returned, and if not, null is returned.
Preferably, the APP includes a dynamic form policy Event total, an actionType is defined in the dynamic form policy Event total, the actionType finds the corresponding Event through the corresponding mapping, and when the configuration file configures the corresponding component with the corresponding attribute, the program finds the Event through the corresponding mapping.
Preferably, a ShowViewEvent is arranged in the dynamic form strategy Event total, and the ShowViewEvent is used for displaying and hiding views; the UI component middle layer and the dynamic form strategy Event layer are in a combined relation, and therefore a complete UI dynamic change framework is formed.
Preferably, the APP comprises a component container and a controller, the component container and the controller together form a page, wherein the controller is a functional logic process.
Preferably, the container components include DataPickerView and EditContentView; the controller includes a service class controller and a functional service controller.
The invention solves the efficiency problem of traditional development and function iteration, and particularly can quickly assemble UI controls and event controllers to form a new product when the system faces some form submission scene services; for online products, business products can be dynamically added without updating APP versions, so that the user experience is improved, the development is more efficient, and the product iteration cycle is quicker.
Drawings
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings. Like reference numerals refer to like parts throughout the drawings, and the drawings are not intended to be drawn to scale in actual dimensions, emphasis instead being placed upon illustrating the principles of the invention.
FIG. 1 is a flowchart of APP development according to the present invention;
FIG. 2 is a flow diagram of a dynamic configuration policy scheme of the present invention;
FIG. 3 is a flow chart of dynamic publishing and updating of dynamic forms in accordance with the present invention;
FIG. 4 is a form policy component UI implementation diagram of the present invention;
FIG. 5 is a diagram of the form policy architecture of the present invention.
Detailed Description
The present invention will be better understood and implemented by those skilled in the art by the following detailed description of the embodiments taken in conjunction with the accompanying drawings, which are not intended to limit the scope of the present invention.
As shown in fig. 1 to 5, an embodiment of the present invention provides an APP development method based on a legacy application and a dynamic configuration policy, including the following steps, with reference to fig. 1:
receiving demand content provided by a client;
checking whether the UI component middle layer and the event control middle layer have corresponding interaction;
if so, assembling corresponding configuration files to generate a new product;
if the UI component is not found in the middle layer;
developing the UI component, storing the UI component in the middle layer, and assembling corresponding configuration files to generate a new product;
if the event controller is not found in the middle layer;
and developing an event controller, storing the event controller into the middle layer, and assembling corresponding configuration files to generate a new product. Event controller, refers to a process that can control business logic, such as: the method comprises the steps of network request of a page, regular verification of elements such as a mobile phone number and the like, whether the elements of the page are displayed or hidden and the like.
Referring to fig. 1, when a technical developer receives a demand provided by a product, a dynamic form scheme may maximize development efficiency of the developer and iteration of the product. When technical personnel develop, if the UI component middle layer and the event control middle layer have corresponding interaction, a new product can be generated only by assembling corresponding configuration files; if the UI component is not found in the middle layer, only the workload of developing the UI component needs to be newly increased, so that the labor is saved, the UI library of the middle layer is accumulated more and more, and the technical improvement and project management are facilitated. Of course, the same is true of the event control middle layer.
On the basis of traditional application development, the method integrates a whole set of complete and flexible APP dynamic form realization method by designing a coping application change strategy, and effectively overcomes the defects of flexibility, timeliness and the like brought by the existing mode.
In a preferred embodiment, the method provides a UI component, a UI component logic interaction module and a business logic interaction function module based on the dynamic configuration policy for the APP, and designs the following mechanisms on the basis:
the UI component is dynamically updated, and developers can recombine the UI component according to the appointed UI configuration and generate a new service interface;
UI service logic configuration is updated, each configured UI can be written in advance and compatible according to service requirements or scenes where the component is used, and the new requirements can realize the self-service logic of the UI only by corresponding configuration;
and by configuring the JSON file meeting the strategy, the application can utilize the existing UI component and the independent business process to recombine a new business process, and the creation and the iteration of a new product are completed. JSON (JavaScript Object Notation) is a lightweight data exchange format).
The scheme strategy is suitable for the iOS and Android platforms, and effectively solves the problem of inconsistency of two ends and quick iteration or replacement of online versions.
Through configuration file configuration, wherein type attributes, corresponding UI component mapping can generate similar EditContentView (input box), option selector (datapickeview), picture display control, and the like. Then, through page loading, the configured UI components can dynamically compose a new APP page for the user to use. Namely, reading the file configuration of the UI, namely finding a mapped and developed UI middle layer through the type attribute, namely, APP loading the configuration file, and then generating a page for the user to display.
The embodiment is a process for dynamically updating UI components and page logic through configuration files. The DataPickerView (custom UI element of a UI selector) and the EditContentView (custom UI element of an input box) are dynamically generated according to the configuration file and then added into the APP interface, and the data PickerView and the event processor are combined to form a complete APP page.
Referring to FIG. 4, in the preferred embodiment, each UI component inherits a BaseView component in which to implement a well-defined Base interface. The BaseView is an interface, and the defined interface of the BaseView is used for enabling subsequent user-defined UI components to be realized by the interface, so that the management of service attributes is facilitated. In addition, the BaseView interface is mainly used for defining the appearance of the implementation class, namely the definition of the behavior of the implementation class, and is used for restricting the behavior of the implementation class.
In a preferred embodiment, the Base interface includes initData, initView, and ontechfromwindow functions;
the initData function is a self-defined interface method, and is used for processing UI component data, such as loading a UI component data source, loading a JSON file, reading data, and displaying the data in a UI control to complete initialization operation of the data, and the corresponding UI component can realize interactive logic of data processing.
The initView function is a self-defined interface method and is used for view initialization operation of the UI component, such as UI component rendering and UI component loading layout, loading and rendering to a corresponding layer, and displaying to a user;
the ontechfromwndo function is a self-defined interface method used for performance monitoring operations of UI components, such as monitoring memory jitter and memory overflow. The method can also be used for optimizing the memory jitter of the UI component, and the method can assist in recording and optimizing the performance of the UI of the corresponding component.
The Base interface also includes a getViewType function; the getViewType function is used to return the View type of the corresponding UI component and to control the corresponding interaction with the Event in the Event.
The Base interface also comprises an isNeedSubscripte function; the isNedSubscribe function is used for judging whether the UI component is controlled by an Event or not, and if the UI component is set to be true, the IeNedSubscribe function is added into the logic processing of the Event control master;
the Base interface also comprises a getLineView function; getLineView is used for the underlining of UI controls, returning an underlining to Event for logical operations.
After the getViewType is realized, the View type of the corresponding UI component can be returned, and the View type is used for interacting with the Event control in the Event correspondingly, such as dynamically displaying and hiding some field UIs according to rules. getViewType is mainly used for obtaining the type of the user-defined UI component, and the purpose is to return the View type of the corresponding UI component through the method for corresponding interaction in event control.
The isNedSubscribe is used for judging whether the UI component is controlled by the Event or not, and if the Event is set to true, the IeNedSubscribe is added into the logic processing of the Event control master; the isneedledsubscrible is used for judging whether the UI component needs to receive the control of the event controller, if the control is set to true, the control needs to be included in the event controller, and if not, the control is opposite.
getLineView, then underline for UI control, return an underline to Event for some logical operations; getLineView is mainly used for returning whether the control needs to be underlined, if yes, an underlined object is returned, and if not, null is returned.
Referring to FIG. 5, in the preferred embodiment, an actionType is defined in the dynamic form policy Event headquarters, and the actionType finds the corresponding Event through the corresponding mapping, and when the corresponding attributes are configured for the corresponding component in the configuration file, the program finds the Event through the corresponding mapping.
In the preferred embodiment, a showViewEvent is set in the dynamic form policy Event total, the showViewEvent is used for showing View and hiding View, and the showViewEvent is an Event controller used for showing the display and hiding functions of the page UI control. The UI component middle layer and the dynamic form strategy Event layer are in a combined relation, so that a complete UI dynamic change framework is formed.
The dynamic form policy Event headquarters is the logical processing headquarters for the control page, i.e., the Event controller described above. An actionType attribute is defined herein that can be mapped to a corresponding event controlled profile to find a desired representation of business logic, such as: mobile phone number verification, page request, interaction of page controls and the like.
And observing a dynamic form policy Event summary, for example, a developer defines an actionType, and the actionType finds a corresponding Event through a corresponding mapping, where showViewEvent is taken as an example, and the implemented functions in the showViewEvent are to show View and hide View. When corresponding attributes are configured for corresponding components in a configuration file, the program finds the Event through corresponding mapping, and the phenomenon of displaying the Event to a user layer is that when a user clicks a UI component configured with corresponding rules, a corresponding interactive process is realized. The UI control middle layer and the dynamic form strategy Event layer are in a combined relation. Therefore, a complete UI dynamic change framework is formed. Adapting to rapid iterations of traffic.
In the preferred embodiment, the component container and the controller together form a page, the controller is a functional logic process, and the container component comprises DataPickerView and EditContentView; the controller includes a service class controller and a functional service controller.
The invention solves the efficiency problems of traditional development and function iteration, and particularly can quickly assemble UI controls and event controllers to form a new product when some forms submit scene services; for online products, business products can be dynamically added without updating APP versions, so that the user experience is improved, the development is more efficient, and the product iteration cycle is quicker.
Referring to fig. 2, when a user enters a product developed in a dynamic form scheme, the APP reads configured UI control and event controller configuration from a data source JSON file. And after the application program is assembled to complete the corresponding UI interface and the effect event corresponding to the UI control, forming an available APP product meeting the product requirement and delivering the APP product to the user for use.
The data source configuration here is as follows:
{ "type": 13, "title": immediate application "," showSuperscript ": true," extraInfo ": {" actionType ": 1 } },
type corresponds to different UI controls, actionType is corresponding event control configuration, and when the UI control is given actionType event control configuration, it has corresponding event control, such as: entering the next page, checking whether the current element is legal, displaying a popup window and the like. When the control operated by the user contains an interface request, that is, actionType is 3, the policy logic will go to the control to take out the following configurations:
"params": {
“requestParams”:”key1,key2,key3,key4,key5” "requestName": "XXX/XXX" },
then, a request is assembled and sent to a back end to complete business operation.
Referring to fig. 3, our form version may be issued by a remote server, and an operator uploads a corresponding form file and configures a corresponding form file version. The APP can be matched with a form version configured by a server before a page written by a dynamic form scheme is opened, and if the APP has updating, an updating process is started: firstly, verifying the file validity (md 5), verifying whether the UI control of the file needs to be updated after the file is legal, and updating the UI control if the UI control needs to be updated; and after updating, searching whether the newly added event controller configuration exists, and updating the corresponding event controller if the corresponding event controller configuration is updated to form a highly available APP product for the user.
The invention solves the efficiency problem of traditional development and function iteration, concentrates on the precipitation of technical components, optimizes the iteration and user experience of online products and improves the production efficiency. Particularly, when some forms submit scene services, the UI control and the event controller can be quickly assembled to form a new product. For online products, business products can be dynamically added without updating APP versions, so that the user experience is improved, the development is more efficient, and the product iteration cycle is quicker. For example: the company enters the owner of the product and credits, and the development by adopting the scheme can be produced in half a day, however, if the development is native, 3-5 working days are possibly required; if some regular check interactions are required to be added on the basis of the original incoming form, the scheme only needs to change the configuration once, only about 1 hour is required from development to release, however, the original development possibly needs to face business logic rewriting, and then links such as release, patching and updating are carried out, and the period can reach 1-2 days; for another example, the business needs to increase or decrease some UI controls and corresponding logic operations in the original product, and with the scheme, the version can be released at any time only within half an hour of the development cycle, however, with the traditional native development, operations such as layout file rearrangement, business logic rewriting and the like may be required, and the cycle may reach 3 to 4 days. Such as the efficiency improvements above, this strategy has obvious advantages.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. An APP development method based on traditional application and dynamic configuration strategy is characterized by comprising the following steps:
receiving demand content provided by a client;
checking whether the UI component middle layer and the event control middle layer have corresponding interaction;
if so, assembling corresponding configuration files to generate a new product;
if the UI component is not found in the middle layer;
developing the UI component, storing the UI component in the middle layer, and assembling corresponding configuration files to generate a new product;
if the event controller is not found in the middle layer;
developing an event controller, storing the event controller in the middle layer, and assembling corresponding configuration files to generate a new product;
the APP comprises a UI component, a UI component logic interaction module and a service logic interaction function module, and the following mechanisms are designed:
dynamically updating the UI component, and carrying out UI component recombination and generating a new service interface by developers according to the appointed UI configuration;
UI service logic configuration is updated, each configured UI can be written in advance and compatible according to service requirements or scenes where the component is used, and the new requirements can realize the self-service logic of the UI only by corresponding configuration;
and the application can utilize the existing UI components and the independent business process to recombine a new business process by configuring the JSON file meeting the strategy, so as to complete the creation of a new product.
2. The APP development method based on legacy applications and dynamic configuration policies of claim 1, wherein each UI component inherits a BaseView component and implements a defined Base interface in the BaseView component.
3. The APP development method based on legacy applications and dynamic configuration policies of claim 2, wherein the Base interface comprises initData, initView and onDetachFromWindow functions;
the initData function is used for processing UI component data in the APP;
the initView function is used for view initialization operation of the UI component in the APP;
the ontechfromwindow function is used in APP for performance monitoring operation of UI components.
4. The APP development method based on the traditional application and the dynamic configuration strategy as claimed in claim 3, wherein the initData function is used for loading JSON files, reading data, displaying the JSON files and the data into a UI control, and completing initialization operation of the data;
the initView function is used for rendering the UI component and displaying the UI component to a user;
the ontechfromwindow function is used to monitor memory jitter and memory overflow.
5. The legacy application and dynamic configuration policy based APP development method of claim 3, wherein the Base interface further comprises an isneedledsubscript function; the isNedSubscribe function is used for judging whether the UI component needs to receive the control of the event controller, if the UI component is set to true, the UI component indicates that the UI component needs to be classified into the control of the event controller, and if the UI component does not need to receive the control of the event controller, the isNedSubscribe function is opposite to the control of the event controller;
the Base interface further comprises a getViewType function, wherein the getViewType function is used for returning the View type of the corresponding UI component and controlling corresponding interaction with the Event in the Event;
the Base interface further comprises a getLineView function; the getLineView function is used for returning whether the control needs underlining, if yes, an underlining object is returned, and if not, null is returned.
6. The APP development method based on traditional applications and dynamic configuration policies of claim 5, wherein the APP comprises a dynamic form policy Event headquarters, an actionType is defined in the dynamic form policy Event headquarters, the actionType finds the corresponding Event through the corresponding mapping, and when the configuration file configures the corresponding attributes for the corresponding component, the program finds the Event through the corresponding mapping.
7. The APP development method based on the traditional application and the dynamic configuration strategy according to claim 6, characterized in that a ShowViewEvent is set in the dynamic form strategy Event total, and the ShowViewEvent is used for showing View and hiding View; the UI component middle layer and the dynamic form strategy Event layer are in a combined relationship, so that a complete UI dynamic change framework is formed.
8. The APP development method based on the traditional application and the dynamic configuration policy of claim 1, wherein the APP comprises a component container and a controller, the component container and the controller together form a page, and the controller is a functional logic process.
9. The legacy application and dynamic configuration policy based APP development method of claim 8, wherein the component container comprises a datapickrview and an EditContentView; the controller includes a service class controller and a functional service controller.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210659157.XA CN114756234B (en) | 2022-06-13 | 2022-06-13 | APP development method based on traditional application and dynamic configuration strategy |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210659157.XA CN114756234B (en) | 2022-06-13 | 2022-06-13 | APP development method based on traditional application and dynamic configuration strategy |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114756234A CN114756234A (en) | 2022-07-15 |
| CN114756234B true CN114756234B (en) | 2022-09-30 |
Family
ID=82337233
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210659157.XA Active CN114756234B (en) | 2022-06-13 | 2022-06-13 | APP development method based on traditional application and dynamic configuration strategy |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114756234B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485680A (en) * | 2021-06-30 | 2021-10-08 | 重庆长安汽车股份有限公司 | APP (application) component control system and method based on vehicle-mounted system |
| WO2022042162A1 (en) * | 2020-08-25 | 2022-03-03 | 华为技术有限公司 | Method and apparatus for implementing user interface |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108154569B (en) * | 2017-12-27 | 2021-02-12 | 广州奥格智能科技有限公司 | Patrol acquisition method based on object modeling configuration |
| CN108228253A (en) * | 2017-12-29 | 2018-06-29 | 武汉璞华大数据技术有限公司 | A kind of APP construction methods and system |
| CN109284103A (en) * | 2018-08-30 | 2019-01-29 | 长春玖佰软件技术有限公司 | A kind of Web application and development and update method based on control development mode |
| CN109634758A (en) * | 2018-12-10 | 2019-04-16 | 四川长虹电器股份有限公司 | Method and middleware platform based on JSON document control event and behavior |
| CN109634573A (en) * | 2018-12-18 | 2019-04-16 | 宁夏隆基宁光仪表股份有限公司 | Android operation system App development approach, device and medium |
| CN111443911A (en) * | 2020-03-24 | 2020-07-24 | 五八有限公司 | Page development method and device, electronic equipment and computer storage medium |
| CN113448611B (en) * | 2021-08-31 | 2021-11-30 | 中邮消费金融有限公司 | Method and system for quickly and thermally updating application program |
-
2022
- 2022-06-13 CN CN202210659157.XA patent/CN114756234B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022042162A1 (en) * | 2020-08-25 | 2022-03-03 | 华为技术有限公司 | Method and apparatus for implementing user interface |
| CN113485680A (en) * | 2021-06-30 | 2021-10-08 | 重庆长安汽车股份有限公司 | APP (application) component control system and method based on vehicle-mounted system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114756234A (en) | 2022-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8417715B1 (en) | Platform independent plug-in methods and systems for data mining and analytics | |
| JP5809328B2 (en) | Widget framework, real-time service integration and real-time resource aggregation | |
| US20220215120A1 (en) | Providing a computational script into an input slot of a computational step of a data pipeline | |
| US8949789B2 (en) | Adaptable business objects | |
| US20170140307A1 (en) | Plan modeling and task management | |
| US20150135160A1 (en) | System and method for providing an application development and distribution social platform | |
| US7360215B2 (en) | Application interface for analytical tasks | |
| US20130254755A1 (en) | Dynamically updating on-demand runtime platforms executing business applications | |
| US7370316B2 (en) | Mining model versioning | |
| US20120210296A1 (en) | Automatically creating business applications from description of business processes | |
| US20230054383A1 (en) | Unstructured data processing in plan modeling | |
| US20080172414A1 (en) | Business Objects as a Service | |
| CN109766075B (en) | Enterprise-level software construction method and system based on microservice | |
| US20130067456A1 (en) | Application configuration framework for enterprise resource planning application installation | |
| CN107102848A (en) | Provide user interface element | |
| Ackerman et al. | Patterns-based engineering: Successfully delivering solutions via patterns | |
| JP7353306B2 (en) | Flexible energy information aggregation | |
| US9760552B2 (en) | Document renewal and translation | |
| Hamdaqa et al. | Stratus ML: A layered cloud modeling framework | |
| CN115640045A (en) | Low-code development platform based on domain-driven design and business system creation method | |
| WO2008025514A1 (en) | Systems and methods for rapid application configuration and deployment | |
| CN114756234B (en) | APP development method based on traditional application and dynamic configuration strategy | |
| US20040230978A1 (en) | Analytical task invocation | |
| US20240126759A1 (en) | Converting an api into a graph api | |
| CN113692582B (en) | User interface for establishing a data privacy pipeline and contract agreement to share data |
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 |