CN113672228A - Visual development method and system based on component and data asset transaction - Google Patents
Visual development method and system based on component and data asset transaction Download PDFInfo
- Publication number
- CN113672228A CN113672228A CN202111090794.1A CN202111090794A CN113672228A CN 113672228 A CN113672228 A CN 113672228A CN 202111090794 A CN202111090794 A CN 202111090794A CN 113672228 A CN113672228 A CN 113672228A
- Authority
- CN
- China
- Prior art keywords
- data
- component
- user
- screen
- asset
- 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.)
- Pending
Links
- 238000011161 development Methods 0.000 title claims abstract description 38
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000000007 visual effect Effects 0.000 title claims abstract description 16
- 238000013461 design Methods 0.000 claims abstract description 51
- 230000008569 process Effects 0.000 claims abstract description 9
- 238000012797 qualification Methods 0.000 claims abstract description 4
- 238000012795 verification Methods 0.000 claims abstract description 4
- 230000000694 effects Effects 0.000 claims description 33
- 230000006870 function Effects 0.000 claims description 23
- 238000004458 analytical method Methods 0.000 claims description 21
- 238000007726 management method Methods 0.000 claims description 13
- 238000013523 data management Methods 0.000 claims description 6
- 230000003068 static effect Effects 0.000 claims description 6
- 238000012360 testing method Methods 0.000 claims description 6
- 238000003860 storage Methods 0.000 claims description 5
- 230000008901 benefit Effects 0.000 claims description 4
- 230000002452 interceptive effect Effects 0.000 claims description 4
- 238000012163 sequencing technique Methods 0.000 claims description 4
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims description 3
- 230000002457 bidirectional effect Effects 0.000 claims 1
- 230000000875 corresponding effect Effects 0.000 description 19
- 230000006399 behavior Effects 0.000 description 8
- 238000009877 rendering Methods 0.000 description 7
- 238000007405 data analysis Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000003825 pressing Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000000712 assembly Effects 0.000 description 2
- 238000000429 assembly Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000000265 homogenisation Methods 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 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/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- 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
- 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
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Accounting & Taxation (AREA)
- Marketing (AREA)
- Finance (AREA)
- Technology Law (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a visual development method and a system based on component and data asset transaction, which comprises the following steps: s1: the method comprises the following steps that both a component developer and a data asset publisher log in a BI platform, a developer publisher application process is started, whether the type of the component is an enterprise type or not is judged, enterprise authentication information (a company name, a business license and a public account) is filled, if not, a personal authentication information name, an identity card and a mobile phone number are filled, applied qualification is checked, and the logged account is identified as the component developer if the verification is passed; the invention has basic component framework and large screen design capability, the platform is provided with a common data chart and a display component, and supports perfect component dragging and attribute panel editing and configuring capabilities, so that a user can rapidly design and develop a screen with rich content through simple operation.
Description
Technical Field
The invention relates to a visual development method, in particular to a visual development method and a visual development system based on component and data asset transaction, and belongs to the technical field of data asset transaction.
Background
With the popularization of the information system in various industries, the software system also enters the lives of people in various aspects, and more people use the software system; meanwhile, data generated in the process of using the software system by people is larger and larger, and the birth of a large data storage technology is promoted. The big data storage technology provides a bottom-layer technical support for storage of mass data, but the storage of the mass data is not targeted, and a user finally wants to dig out valuable information from the big data; therefore, big data processing technologies such as batch computation, stream computation, algorithm modeling, machine learning and the like based on big data come into play, and valuable information really concerned by a user can be extracted from huge data through the technologies so as to be used and continuously analyzed by the user.
How to quickly and intuitively let the user see the data analysis result after the value information is extracted by the big data processing technology, and the significance of the data analysis result is seen clearly, so that the important work is achieved; because the user can only clearly understand the actual meaning expressed by the data analysis result, the user can make correct selection and decision on the subsequent working direction or working method.
Various existing BI visualization platforms, hereinafter referred to as BI platforms for short, are online tools which are based on the requirements and specially help users to perform visualization analysis on data; a user can design a data analysis large screen by using a BI platform through modes of dragging components, binding data, configuring component attributes and the like, and can understand various conditions such as change trends, distribution areas, index ratios and the like at a glance.
Although the BI platform can provide data chart analysis capability for users conveniently, each BI platform also provides some built-in components on the platform for users to use, but the types of the components are limited, the style is single, and the users cannot customize the components according to the needs of the users; the analysis mode and the display mode of the data by the user are severely limited, and for some users with certain development capacity, besides basic data analysis and display by using components and data, more style setting and behavior control are expected to be carried out on the components by writing front-end codes, and the association interaction between the components is increased; these are capabilities that the existing BI platforms cannot provide.
In the process of using the BI platform, a user has a plurality of large-screen pages in a plurality of scenes, and the large screens can be freely switched according to certain association logic, so that the problem of insufficient display areas of a single large screen can be solved; secondly, different display dimensions of data can be distinguished by taking a large screen as a unit, more visual angles are provided for a user, however, the existing BI platform provides a single-page large screen for design, and finally, a large screen page is output to the user, and design and interaction of multiple pages of large screens cannot be realized.
In addition, many users hope to add functions which are not provided by some BI platforms for secondary development after the large-screen display effect is realized by using the BI platform design; moreover, for the purposes of security and convenience of self-management, it is also desirable to deploy large-screen applications in their own servers; these needs are all substantial where existing BI platforms do not exist.
In summary, all or some of the existing BI platforms have the following problems: limited components result in severe homogenization of the large screen designed by the user; simple drag and drop configuration limits the user's ability to customize depth; the single-page large screen limits the space and the layering sense of data display; the inability to deploy independently by accessing through the BI platform significantly limits the user's need for security, flexibility, and brand exposure themselves.
Disclosure of Invention
The invention aims to provide a visual development method and a visual development system based on component and data asset transaction, so as to solve the problems in the background technology.
In order to achieve the purpose, the invention provides the following technical scheme: a visual development method based on component and data asset transactions, comprising the steps of:
s1: the method comprises the following steps that both a component developer and a data asset publisher log in a BI platform, a developer publisher application process is started, whether the type of the component is an enterprise type or not is judged, enterprise authentication information (a company name, a business license and a public account) is filled, if not, a personal authentication information name, an identity card and a mobile phone number are filled, applied qualification is checked, and the logged account is identified as the component developer if the verification is passed;
s2: the method comprises the steps that a component developer customizes a development component according to component rules, packages custom component codes and resources, judges whether the component developer exists, uploads packaged contents through a BI platform component uploading function and fills in custom component names and descriptions according to prompts if the component developer exists, submits the custom component to create a component record (including creator and component information) in a component table, and adds a use authority record (the component creator defaults to have use authority on the component) in the component use authority table;
s3: finding out the components needing to be published in my components, selecting the components and clicking to publish, inputting publishing price information according to the prompt of whether the components are developers, clicking to determine to publish, and updating the corresponding state of the component table to be published;
s4: finding a component to be purchased in a component market, selecting the component for purchase, carrying out payment operation, and adding a use authority record (containing information of a purchaser and the component) in a component use authority table after successful payment;
s5: uploading a static data file, setting a name after data uploading to ensure uniqueness), setting file analysis parameters, setting file analysis parameter titles, initial lines and separators, analyzing the uploaded file content according to the analysis parameters, adjusting analysis results (column names and storage columns, creating a data table according to the analysis contents, storing the analysis contents into a data table, adding a data asset record pointing to the data asset (through the name, the table name, the type and the owner) in the data asset table, and adding a use authority record (the data asset creator defaults to have use authority on the asset);
s6: setting database connection parameters, trying to connect a database and returning an available database table of the database, selecting a data table to be used, setting a query condition of the data table, setting a name of a data asset, and adding a record direction to the data asset table (adding a use authority record in a data asset authority table through the name, the type, the configuration and the data asset of an owner (a data asset creator has a default use authority on the asset);
s7: setting an API access address, configuring API related information (signature, request mode and parameters), trying to request an API interface, configuring column information (display name) for a return result, setting a data asset name, adding a record pointing to the data asset (by name, type, configuration and owner) in a data asset table, and adding a use authority record (a data asset creator has a default use authority for the asset);
s8: searching needed data assets in a data market, judging whether the data assets are free to use, if not, paying the use fee of the data assets, and adding a use authority record (data assets, purchasers and use period) in a data asset authority table;
s9: a data asset publisher logs in a Bl platform to enter a data asset management page, if the data asset publisher is the asset publisher, the data asset to be published is selected, publishing parameters (price and duration) are set, a piece of publishing information (the data asset and the publishing parameters) is stored in a data asset publishing table, and the state of the data asset is set as published;
as a preferred technical solution of the present invention, a system for a visual development method based on component and data asset transactions, the system comprising a front-end presentation, a back-end service and a database, the system being bidirectionally connected to third-party data assets and local data assets, wherein:
front-end display: the system is used for providing the design development and release display capability of a large screen of a user;
back-end service: access for accessing user-designed large-screen content and related data assets;
a database: for storing a usable data table.
As a preferred technical solution of the present invention, the front-end display includes a large-screen list, a large-screen template, a large-screen design, a large-screen release, a large-screen export, a component market, data management, and data transaction, wherein:
large screen list: the large-screen list sub-module is a first function page after a user logs in the system and is an entrance of the user, and in the function page, the user can check the created large-screen list information and provide the user with sequencing according to the large-screen name, the creation time or the update time; a shrinkage ratio graph of a large screen is displayed in the list, so that a user can directly know the content of the large screen conveniently; when a mouse is moved to the thumbnail, the thumbnail is highlighted, and a quick operation button is highlighted on the top layer of the thumbnail, wherein the quick operation button comprises editing, previewing, releasing, copying and deleting, meanwhile, functions of newly-built blank large screens and entering large screen templates are provided in a list page, a dialog box of the newly-built large screens needs to be popped up by clicking a 'blank large screen' button, and a user can successfully create a blank large screen by clicking a 'confirm' button after inputting the name of the large screen;
a large screen template: the system is provided to help a user to quickly create a green channel of a large screen, the system can carry a batch of typical templates with the large screen, the user can find a template required by the user or a template similar to the user's expectation by checking thumbnails or previewing the actual effect, the user can create a new large screen by utilizing the selected template after clicking a ' use ' button and inputting the name of the large screen, the new large screen already contains the content provided by the template, the component style and the overall layout are designed, and the user only needs to finely adjust and replace the data with the actual service data of the user;
designing a large screen: the designer is used for carrying out component layout, data binding and behavior event control on the large screen; the whole designer is divided into a layer control area, a component list area, a design area, an attribute editor, a toolbar and other areas, and provides the capabilities of component design, attribute editing, layer control, event programming, data binding, multi-screen management, effect preview and the like for a user; through the capabilities, a user can design various large-screen effects according to business needs and display various data indexes; and can add more behavior control and interactive effect for the assembly and large screen through event programming; meanwhile, the multi-page large-screen capability can enable a user to create a plurality of large screens and perform switching display according to specified rules or user operation;
and (4) large-screen release: the large-screen publishing means is a way for providing the large-screen design effect for a user to use, large-screen pages can be published into a link through the large-screen publishing, the user can see the large-screen display effect through the link, and the large-screen publishing can be divided into private publishing and public publishing according to the publishing type;
private publishing-private publishing is a publishing way in which a user can customize an access password, and an access link published by the way can be accessed to see a display effect only by using the access password. When issuing, the user can also set the issuing validity period, and once the validity period is exceeded, the issuing cannot be carried out even if the access password is used;
the open publishing-open publishing refers to a mode that a large screen page can be opened by a browser to see a large screen display effect as long as a publishing link address is known, and the mode can be published only by setting an effective period; all people can open the release link within the valid period;
and (3) large screen export: the designed large-screen page can be published into a link for a user to access, and the link is based on a BI platform and depends on the existence of the BI platform; in some scenes, for safety or other certain aspects, a user wants to deploy a large-screen page on own server resources and use a domain name link designated by the user; at this time, the relevant resources and codes of the large-screen page can be exported to the local through the large-screen export function, and a user can freely deploy the large-screen page according to needs; meanwhile, the content exported by the large screen comprises complete source code resources, a user with development capability can carry out secondary development based on the exported source code, more functions and effects are added on the basis of the finished large screen design, and more user requirements are met;
component market: the system comprises a large number of system components for users, wherein the system components comprise rich chart components, table components and map components; the component marketplace provides the ability for users to customize extension components and use custom extension components, following the previously described component data specification and defined format, users can develop test custom components locally; after the test is correct, the user can package and upload the custom assembly to a BI platform and release the custom assembly, but before the assembly is released, the user needs to apply for the assembly developer to obtain the right of uploading and releasing the assembly, meanwhile, the user needs to obey the relevant specification of releasing the assembly and undertake the relevant legal constraints, and after the release, all the users including the developer can find the assembly in the assembly market and perform transaction;
data management: management and maintenance of data owned by a user; the data referred to herein includes types of Excel/CSV data imported by a user from a local site, directly connected database data, imported API interface data, and data purchased by a data market 4, different types of data include management functions of addition, configuration, and deletion, and the contents of addition and configuration are different according to the types;
data transaction: and when the data assets are traded, the user can release the data owned by the user or authorized by the owner to the data market within the allowed range of laws and regulations according to the requirement, and defines a proper price for the data assets for other people to purchase and use, so that the benefit is earned for the data publisher.
Compared with the prior art, the invention has the beneficial effects that:
the platform is provided with a common data chart and a common display component, and supports perfect component dragging and attribute panel editing and configuring capabilities, so that a user can rapidly design and develop a screen with rich content through simple operation.
The platform supports static input data, Excel/CSV file import data, database direct connection query data, API interface request data and data asset market purchase data; different components can select different data binding forms according to requirements; the user can flexibly and conveniently use the data of the own or the third party.
The design of a multi-page complex large screen gives more possibility to the platform, and the platform jumps out of the setting that only a single-page simple logic large screen can be designed; the user is allowed to design any number of large screens, the large screens can be mutually associated, drilled down and rolled up, and scenes with more complex and systematic service requirements are met.
The high-order user-defined event programming capability provides a user with certain code development capability with more open capability, and the user can express more effects and realize more complex interactive logic.
The self-defined development and transaction of the components, the system components of the platform are only a part which is limited and commonly used, and users with new requirements can not be met forever; the capability supports the user or other third-party developers to self-define the development component according to the needs, and the self-developed component is released to the component trading market, so that the needed user can purchase and use; therefore, a module ecological circle integrating production, supply and marketing is formed, and continuous new modules can be provided for the platform to support various new requirements.
The publishing and trading of data assets, the capabilities and component development and trading being similar, except that the subject corresponds to the data assets; for the platform, the data is the soul, and the large screen can be enriched and valuable only if the data is owned; however, the data we need is not necessarily the data we own; the data distribution and trading market provides a channel for earning profits for people who possess data to distribute the data, and users who need the data can use the data provided by others only by paying the data use fee; therefore, for a data user, the data can be conveniently and economically found and used; for a data publisher, the data publisher can obtain benefits from own data, so that the enthusiasm of the publisher is improved, and an ecological closed loop is formed.
The platform has secondary development and independent deployment capabilities, all the capabilities of the platform are based on the platform, and even if a link is published on a large screen, the link runs on the basis of the platform and cannot exist after being separated from the platform. However, in order to meet the requirements of many users on safety and own large-screen brands, the users can use the export function of the platform to export the large screen designed by the users into an independent project completely, secondary development can be carried out in the exported project, the development mode is simple as common programming development, and new skills do not need to be learned; for the derived project, the user can independently deploy and bind to the own brand domain name, so that the user can completely control the own brand domain name
Drawings
FIG. 1 is a schematic diagram of the system of the present invention;
FIG. 2 is a logic diagram illustrating the operation undo redo of the present invention;
FIG. 3 is a logical view of the process flow of the property editor for switching among selected components in the workbench according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-3, the present invention provides a visual development method and system based on component and data asset transaction, and the technical solution is as follows: the method comprises the following steps:
s1: the method comprises the following steps that both a component developer and a data asset publisher log in a BI platform, a developer publisher application process is started, whether the type of the component is an enterprise type or not is judged, enterprise authentication information (a company name, a business license and a public account) is filled, if not, a personal authentication information name, an identity card and a mobile phone number are filled, applied qualification is checked, and the logged account is identified as the component developer if the verification is passed;
s2: the method comprises the steps that a component developer customizes a development component according to component rules, packages custom component codes and resources, judges whether the component developer exists, uploads packaged contents through a BI platform component uploading function and fills in custom component names and descriptions according to prompts if the component developer exists, submits the custom component to create a component record (including creator and component information) in a component table, and adds a use authority record (the component creator defaults to have use authority on the component) in the component use authority table;
s3: finding out the components needing to be published in my components, selecting the components and clicking to publish, inputting publishing price information according to the prompt of whether the components are developers, clicking to determine to publish, and updating the corresponding state of the component table to be published;
s4: finding a component to be purchased in a component market, selecting the component for purchase, carrying out payment operation, and adding a use authority record (containing information of a purchaser and the component) in a component use authority table after successful payment;
s5: uploading a static data file, setting a name after data uploading to ensure uniqueness), setting file analysis parameters, setting file analysis parameter titles, initial lines and separators, analyzing the uploaded file content according to the analysis parameters, adjusting analysis results (column names and storage columns, creating a data table according to the analysis contents, storing the analysis contents into a data table, adding a data asset record pointing to the data asset (through the name, the table name, the type and the owner) in the data asset table, and adding a use authority record (the data asset creator defaults to have use authority on the asset);
s6: setting database connection parameters, trying to connect a database and returning an available database table of the database, selecting a data table to be used, setting a query condition of the data table, setting a name of a data asset, and adding a record direction to the data asset table (adding a use authority record in a data asset authority table through the name, the type, the configuration and the data asset of an owner (a data asset creator has a default use authority on the asset);
s7: setting an API access address, configuring API related information (signature, request mode and parameters), trying to request an API interface, configuring column information (display name) for a return result, setting a data asset name, adding a record pointing to the data asset (by name, type, configuration and owner) in a data asset table, and adding a use authority record (a data asset creator has a default use authority for the asset);
s8: searching needed data assets in a data market, judging whether the data assets are free to use, if not, paying the use fee of the data assets, and adding a use authority record (data assets, purchasers and use period) in a data asset authority table;
s9: a data asset publisher logs in a Bl platform to enter a data asset management page, if the data asset publisher is the asset publisher, the data asset to be published is selected, publishing parameters (price and duration) are set, a piece of publishing information (the data asset and the publishing parameters) is stored in a data asset publishing table, and the state of the data asset is set as published;
a system of a visual development method based on component and data asset transactions, the system comprising a front-end presentation, a back-end service and a database, the system being bi-directionally connected with third party data assets and local data assets, wherein:
front-end display: the system is used for providing the design development and release display capability of a large screen of a user;
back-end service: access for accessing user-designed large-screen content and related data assets;
a database: for storing a usable data table.
The front-end display comprises a large-screen list, a large-screen template, a large-screen design, a large-screen release, a large-screen export, a component market, data management and data transaction, wherein:
large screen list: the large-screen list sub-module is a first function page after a user logs in the system and is an entrance of the user, and in the function page, the user can check the created large-screen list information and provide the user with sequencing according to the large-screen name, the creation time or the update time; a shrinkage ratio graph of a large screen is displayed in the list, so that a user can directly know the content of the large screen conveniently; when a mouse is moved to the thumbnail, the thumbnail is highlighted, and a quick operation button is highlighted on the top layer of the thumbnail, wherein the quick operation button comprises editing, previewing, releasing, copying and deleting, meanwhile, functions of newly-built blank large screens and entering large screen templates are provided in a list page, a dialog box of the newly-built large screens needs to be popped up by clicking a 'blank large screen' button, and a user can successfully create a blank large screen by clicking a 'confirm' button after inputting the name of the large screen;
a large screen template: the system is provided to help a user to quickly create a green channel of a large screen, the system can carry a batch of typical templates with the large screen, the user can find a template required by the user or a template similar to the user's expectation by checking thumbnails or previewing the actual effect, the user can create a new large screen by utilizing the selected template after clicking a ' use ' button and inputting the name of the large screen, the new large screen already contains the content provided by the template, the component style and the overall layout are designed, and the user only needs to finely adjust and replace the data with the actual service data of the user;
designing a large screen: the designer is used for carrying out component layout, data binding and behavior event control on the large screen; the whole designer is divided into a layer control area, a component list area, a design area, an attribute editor, a toolbar and other areas, and provides the capabilities of component design, attribute editing, layer control, event programming, data binding, multi-screen management, effect preview and the like for a user; through the capabilities, a user can design various large-screen effects according to business needs and display various data indexes; and can add more behavior control and interactive effect for the assembly and large screen through event programming; meanwhile, the multi-page large-screen capability can enable a user to create a plurality of large screens and perform switching display according to specified rules or user operation;
as a complement to the preferred solution of large screen design:
component list: the components are basic elements of the system, and are minimum display units for designing large screens, each component represents a data display dimension and effect, all components which can be used by a current user are displayed in a component list (more component users can purchase in a component market and can also display in the component list after purchasing), the user can select different components to construct large screen layout according to the self business requirements to form a final display effect, the components must comply with component specifications, the component specifications are defined from the components internal data, attribute configuration and component registration 3 parts, and each component needs to store the self specification definition into a Json file for use in the invention; the internal data of the component defines all style definitions and data definitions required by the component, such as the position, the size, the name, the type, configuration items, default data and the like of the component, and the part of the content is named and defined as an object named data in a Json file.
Attribute configuration: the method is a bridge between the internal data of the component and the attribute editor, wherein the internal data of the component defines the overall style, the data content and the specific display effect of the component; the property editor is an interface window for users to edit and modify the internal data of the component; property configurations are used to define which data users can edit, what the form in which data is presented on a property editor (e.g., an input box, a drop-down list, a check box, etc.), when properties can be edited, when properties are visible, etc.; the part of content is named and defined as an array named as props in a Json file;
component registration: the defined components are placed in the operation system of the invention, so that the user can see, use and display the components, and the registration of the components is uniformly defined in an index.js file;
through the 3 aspects of the specification, define the component from defining to registering, user use the interface rule of the whole life cycle, follow these 3 rules, users can expand and increase one or more assemblies flexibly on the basis of the invention, enrich the effect in the large-screen design, the component definition is developed, and after registering, will be shown in the component tabulation, load into the appropriate group according to its configuration information; at this time, the user may drag it to the design area for design.
The flow of component loading into the component list is as follows:
the first step is as follows: traversing the component definition directory to obtain component definition information;
the second step is that: traversing the component definition information to obtain a system component list, and inquiring a user-defined component list of which the current user has the use authority through an interface;
the third step: and merging the system component list and the user-defined component list, grouping and sequencing the merged list according to the component configuration, performing front-end rendering on the grouped and sequenced data, and hooking a dragging event.
Designing a region: is an area provided for the user to freely design; the whole area comprises 3 parts of a scale area, a workbench and a zooming area;
the ruler is used for assisting the large screen design and helping a user to position components, and when a mouse is hovered on the horizontal ruler or the vertical ruler, a coordinate prompt line (a dotted line) appears in a design area; a user can click at a proper position on the scale, a vertical or horizontal coordinate positioning line (solid line) appears in the design area, and the assembly can be adsorbed when dragged to be close to the positioning line, so that horizontal alignment or vertical alignment among a plurality of assemblies is ensured; the positioning lines can be arranged in any number, so that in order to avoid too many positioning lines affecting the design of the assembly, the hiding and displaying of the positioning lines can be controlled through a coordinate positioning line switch at the upper left corner;
a workbench: the main area of the large screen design is also the content area displayed on the large screen; the user can drag the components from the component list to the design area, and the components are arranged according to the requirement to form the integral display effect of the large screen; the specified component can be selected by clicking a mouse, and the specific style and the data content of the component can be modified by matching with the attribute editor; a right-click menu is supported on the selected component, and the selected component can be deleted, copied and controlled by the layer through the right-click menu; the selection of a plurality of components can be completed by pressing a left mouse button to drag a selection box or pressing a Ctrl button to click a component; after selecting a plurality of components, a user can combine the selected components through a right-click menu and convert the selected components into a combined component, and at the moment, the combined components can be subjected to unified operation, such as moving, copying, deleting and the like, just like operating one component; in the process of designing in the workbench, the operation can be cancelled and redone, so that misoperation of a user is prevented;
the flow logic for dragging from the component list to the workbench is as follows:
the first step is as follows: clicking a component to be placed on the workbench in the component list, and finding definition information and configuration data of the component according to the identification of the clicked component;
the second step is that: copying one part of the component data to be added into the component list data of the workbench, and re-rendering all the components by the workbench according to the component list data;
the flow logic for the selected component is as follows:
clicking a component to be selected, finding data corresponding to the clicked component from the component list data of the workbench, copying the found data and storing the copied data in a component data list selected by the workbench, changing the component state into a selected state, and re-rendering all the components by the workbench;
the flow logic of the multiple selection is as follows:
pressing a ctrl key to click the component, finding data corresponding to the clicked component from the data of the workbench component list, copying the found data to add the data to the workbench multi-choice component data list, changing the state of the clicked component into a selected state, and re-rendering all components by the workbench;
the flow logic for a multi-component assembly is as follows:
selecting the components to be combined through multi-selection operation, triggering the combination operation through a right-click menu, creating and initializing a combined container component, judging whether component data exist in a multi-selection component list or not, taking one topmost component data in the multi-selection component list as the taken component data according to the display sequence of layers, adding parentld to the container component for association, adding the taken component data into a chilcren effect group of the container component, calculating the position and the size of the container component according to the taken component data, deleting the component data in the multi-selection component list, setting the size and the position of the container component according to the final calculation result, and re-rendering all the components;
the flow logic of operation undo redo is shown in FIG. 2 as follows:
and (3) layer control: refers to the relationship of the upper and lower layers of components, and when the two components are in the same size and position, the upper layer of components will cover the lower layer of components, so that the user can not see the contents of the lower layer of components. The layer control area is used for displaying the upper and lower hierarchical relations of all the components in the current design area, and the items displayed in the list of the layer control area and the components in the design area are in one-to-one correspondence. The user can adjust the upper and lower levels of list items in the layer control area through dragging or arrow control, and corresponding changes can be carried out on the component layers in the corresponding design areas; meanwhile, the selected component corresponding to the design area can be switched by clicking the layer list item in the layer control area; otherwise, the selected component in the design area changes, and the list options in the layer control area also change; for the response of the component change in the design area, the layer control area is performed by monitoring the data change of the multi-choice component list, and when the component in the design area changes, which causes the data change of the multi-choice component list, the layer control area is triggered, and the specific content is as follows:
canceling the selected state of all list items in the layer control list area, judging whether the multi-selection component data list is empty or not, initializing the serial number to be 0, wherein the serial number is less than the number of the list items of the multi-selection component data, acquiring the component data of the corresponding serial number position in the multi-selection component data list, finding the corresponding list item of the component data in the layer control area list, and setting the found list item to be the selected state, namely, the serial number is + 1;
the logic flow of the display hierarchy of the layer control area adjustment component is as follows:
dragging the list item to a proper position in the layer control area through a mouse and releasing the list item, moving the list item to a new position according to the mouse release position, finding corresponding component data in a component data list area of the workbench according to the dragged list item, moving the found component data to an index position indicated by the list item corresponding to the layer control area, and re-rendering all components by the workbench;
an attribute editor: the property editor can find corresponding component data and property configuration information of the corresponding component type according to the selected component when a certain component is selected, display the configured property and render an editing control of a proper type according to the property configuration information, and simultaneously acquire the data of the corresponding property from the component data for initialization; when a user edits and modifies data in an editing control in the attribute editor, the modified data can be reflected on a selected component in real time, and the modification effect can be seen immediately;
when the components selected by the workbench are switched, the processing flow logic of the attribute editor is as shown in fig. 3:
the flow logic after the user modifies the property values through the editing control in the property editing is as follows:
modifying a value in a certain attribute editing control in the attribute editor, finding a Json path corresponding to the data of the selected component corresponding to the attribute according to attribute configuration information corresponding to the editing control, modifying the data of the corresponding attribute of the currently selected component by using the modified value of the editing control and matching with the Json path, and re-rendering all components by using the workbench;
and (3) data binding: to solve the problem of what content is presented; from the loading mode of binding data, the method can be divided into static data and dynamic data assets (data assets for short);
the static data setting is a mode that a user directly inputs and edits the data of the selected component in the attribute editor panel in the large-screen design process by hand, and finally the data is replaced to the designated position of the component configuration information and is stored and loaded along with the component configuration information; the form can be normally displayed after the component list and the corresponding configuration information are loaded on the large screen, and a data interface is not required to be additionally requested to acquire component data.
The dynamic data assets refer to the form of requesting a specified data interface when data is acquired and returning specific data contents according to request parameters. Dynamic data assets are further classified into 4 categories from the data source; the method comprises the steps of firstly, importing data from an Excel/CSV file uploaded locally, secondly, directly connecting data queried by a database, thirdly, requesting returned data through an API (application programming interface) interface, and fourthly, purchasing data through a data trading market.
The Excel/CSV file import data is characterized in that a user inputs data contents frequently used by the user into an Excel or CSV file, then submits and analyzes the data contents in a gateway file uploading mode in a platform, and then stores an analyzed data asset in a platform database, and the user can repeatedly use the data contents.
The database is directly connected, namely a server, an account number and a password which are connected with the database, a connected data table and query conditions are set for the component by a user when the user designs a large screen, and the data queried according to the setting is used as the component display content to be bound.
The API data refers to a mode of providing display contents for the component by accessing an API interface provided by a user when the user designs a large screen; this approach requires that the API interface return data format provided by the user conform to the format requirements of the component presentation content,
the data trading market data is a mode that a user acquires the use right of data provided by other users in a data trading market in a purchasing or free mode, and then the data acquired through the data trading market interface is bound to the component for displaying;
event programming: the user with certain development capability provides the opportunity and the capability of controlling the behaviors of the large screen and various components, different components have different events and can also provide different input parameters in the events, the user can program the required events according to the needs, and the components or the large screen are subjected to pattern setting or behavior operation through codes and the input parameters of the events;
a plurality of pages of large screens: the multi-page large-screen capacity support is to expand the traditional pure data analysis and display of the BI platform into a complete business process design capacity capable of supporting complex logics such as drill-down and scroll-up, user behavior cross interaction, page association skip and the like.
And (4) large-screen release: the large-screen publishing means is a way for providing the large-screen design effect for a user to use, large-screen pages can be published into a link through the large-screen publishing, the user can see the large-screen display effect through the link, and the large-screen publishing can be divided into private publishing and public publishing according to the publishing type;
private publishing-private publishing is a publishing way in which a user can customize an access password, and an access link published by the way can be accessed to see a display effect only by using the access password. When issuing, the user can also set the issuing validity period, and once the validity period is exceeded, the issuing cannot be carried out even if the access password is used;
the open publishing-open publishing refers to a mode that a large screen page can be opened by a browser to see a large screen display effect as long as a publishing link address is known, and the mode can be published only by setting an effective period; all people can open the release link within the valid period;
and (3) large screen export: the designed large-screen page can be published into a link for a user to access, and the link is based on a BI platform and depends on the existence of the BI platform; in some scenes, for safety or other certain aspects, a user wants to deploy a large-screen page on own server resources and use a domain name link designated by the user; at this time, the relevant resources and codes of the large-screen page can be exported to the local through the large-screen export function, and a user can freely deploy the large-screen page according to needs; meanwhile, the content exported by the large screen comprises complete source code resources, a user with development capability can carry out secondary development based on the exported source code, more functions and effects are added on the basis of the finished large screen design, and more user requirements are met;
component market: the system comprises a large number of system components for users, wherein the system components comprise rich chart components, table components and map components; the component marketplace provides the ability for users to customize extension components and use custom extension components, following the previously described component data specification and defined format, users can develop test custom components locally; after the test is correct, the user can package and upload the custom assembly to a BI platform and release the custom assembly, but before the assembly is released, the user needs to apply for the assembly developer to obtain the right of uploading and releasing the assembly, meanwhile, the user needs to obey the relevant specification of releasing the assembly and undertake the relevant legal constraints, and after the release, all the users including the developer can find the assembly in the assembly market and perform transaction;
data management: management and maintenance of data owned by a user; the data referred to herein includes types of Excel/CSV data imported by a user from a local site, directly connected database data, imported API interface data, and data purchased by a data market 4, different types of data include management functions of addition, configuration, and deletion, and the contents of addition and configuration are different according to the types;
data transaction: and when the data assets are traded, the user can release the data owned by the user or authorized by the owner to the data market within the allowed range of laws and regulations according to the requirement, and defines a proper price for the data assets for other people to purchase and use, so that the benefit is earned for the data publisher.
In the description of the present invention, it is to be understood that the indicated orientations or positional relationships are based on the orientations or positional relationships shown in the drawings and are only for convenience in describing the present invention and simplifying the description, but are not intended to indicate or imply that the indicated devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and are not to be construed as limiting the present invention.
In the present invention, unless otherwise explicitly specified or limited, for example, it may be fixedly attached, detachably attached, or integrated; can be mechanically or electrically connected; the terms may be directly connected or indirectly connected through an intermediate, and may be communication between two elements or interaction relationship between two elements, unless otherwise specifically limited, and the specific meaning of the terms in the present invention will be understood by those skilled in the art according to specific situations.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (3)
1. A method for visual development of component and data asset transactions, comprising the steps of:
s1: the method comprises the following steps that both a component developer and a data asset publisher log in a BI platform, a developer publisher application process is started, whether the type of the component is an enterprise type or not is judged, enterprise authentication information (a company name, a business license and a public account) is filled, if not, a personal authentication information name, an identity card and a mobile phone number are filled, applied qualification is checked, and the logged account is identified as the component developer if the verification is passed;
s2: the method comprises the steps that a component developer customizes a development component according to component rules, packages custom component codes and resources, judges whether the component developer exists, uploads packaged contents through a BI platform component uploading function and fills in custom component names and descriptions according to prompts if the component developer exists, submits the custom component to create a component record (including creator and component information) in a component table, and adds a use authority record (the component creator defaults to have use authority on the component) in the component use authority table;
s3: finding out the components needing to be published in my components, selecting the components and clicking to publish, inputting publishing price information according to the prompt of whether the components are developers, clicking to determine to publish, and updating the corresponding state of the component table to be published;
s4: finding a component to be purchased in a component market, selecting the component for purchase, carrying out payment operation, and adding a use authority record (containing information of a purchaser and the component) in a component use authority table after successful payment;
s5: uploading a static data file, setting a name after data uploading to ensure uniqueness), setting file analysis parameters, setting file analysis parameter titles, initial lines and separators, analyzing the uploaded file content according to the analysis parameters, adjusting analysis results (column names and storage columns, creating a data table according to the analysis contents, storing the analysis contents into a data table, adding a data asset record pointing to the data asset (through the name, the table name, the type and the owner) in the data asset table, and adding a use authority record (the data asset creator defaults to have use authority on the asset);
s6: setting database connection parameters, trying to connect a database and returning an available database table of the database, selecting a data table to be used, setting a query condition of the data table, setting a name of a data asset, and adding a record direction to the data asset table (adding a use authority record in a data asset authority table through the name, the type, the configuration and the data asset of an owner (a data asset creator has a default use authority on the asset);
s7: setting an API access address, configuring API related information (signature, request mode and parameters), trying to request an API interface, configuring column information (display name) for a return result, setting a data asset name, adding a record pointing to the data asset (by name, type, configuration and owner) in a data asset table, and adding a use authority record (a data asset creator has a default use authority for the asset);
s8: searching needed data assets in a data market, judging whether the data assets are free to use, if not, paying the use fee of the data assets, and adding a use authority record (data assets, purchasers and use period) in a data asset authority table;
s9: the data asset publisher logs in a Bl platform to enter a data asset management page, if the data asset publisher is the asset publisher, the data asset to be published is selected, publishing parameters (price and duration) are set, a piece of publishing information (the data asset and the publishing parameters) is stored in a data asset publishing table, and the state of the data asset is set as published.
2. A system for visual development of a method based on component and data asset transactions, characterized by: the system comprises a front-end display, a back-end service and a database, and is in bidirectional connection with third-party data assets and local data assets, wherein:
front-end display: the system is used for providing the design development and release display capability of a large screen of a user;
back-end service: access for accessing user-designed large-screen content and related data assets;
a database: for storing a usable data table.
3. A method for visual development of component and data asset transactions according to claim 2 and wherein: the front-end display comprises a large-screen list, a large-screen template, a large-screen design, a large-screen release, a large-screen export, a component market, data management and data transaction, wherein:
large screen list: the large-screen list sub-module is a first function page after a user logs in the system and is an entrance of the user, and in the function page, the user can check the created large-screen list information and provide the user with sequencing according to the large-screen name, the creation time or the update time; a shrinkage ratio graph of a large screen is displayed in the list, so that a user can directly know the content of the large screen conveniently; when a mouse is moved to the thumbnail, the thumbnail is highlighted, and a quick operation button is highlighted on the top layer of the thumbnail, wherein the quick operation button comprises editing, previewing, releasing, copying and deleting, meanwhile, functions of newly-built blank large screens and entering large screen templates are provided in a list page, a dialog box of the newly-built large screens needs to be popped up by clicking a 'blank large screen' button, and a user can successfully create a blank large screen by clicking a 'confirm' button after inputting the name of the large screen;
a large screen template: the system is provided to help a user to quickly create a green channel of a large screen, the system can carry a batch of typical templates with the large screen, the user can find a template required by the user or a template similar to the user's expectation by checking thumbnails or previewing the actual effect, the user can create a new large screen by utilizing the selected template after clicking a ' use ' button and inputting the name of the large screen, the new large screen already contains the content provided by the template, the component style and the overall layout are designed, and the user only needs to finely adjust and replace the data with the actual service data of the user;
designing a large screen: the designer is used for carrying out component layout, data binding and behavior event control on the large screen; the whole designer is divided into a layer control area, a component list area, a design area, an attribute editor, a toolbar and other areas, and provides the capabilities of component design, attribute editing, layer control, event programming, data binding, multi-screen management, effect preview and the like for a user; through the capabilities, a user can design various large-screen effects according to business needs and display various data indexes; and can add more behavior control and interactive effect for the assembly and large screen through event programming; meanwhile, the multi-page large-screen capability can enable a user to create a plurality of large screens and perform switching display according to specified rules or user operation;
and (4) large-screen release: the large-screen publishing means is a way for providing the large-screen design effect for a user to use, large-screen pages can be published into a link through the large-screen publishing, the user can see the large-screen display effect through the link, and the large-screen publishing can be divided into private publishing and public publishing according to the publishing type;
private publishing-private publishing is a publishing way in which a user can customize an access password, and an access link published by the way can be accessed to see a display effect only by using the access password. When issuing, the user can also set the issuing validity period, and once the validity period is exceeded, the issuing cannot be carried out even if the access password is used;
the open publishing-open publishing refers to a mode that a large screen page can be opened by a browser to see a large screen display effect as long as a publishing link address is known, and the mode can be published only by setting an effective period; all people can open the release link within the valid period;
and (3) large screen export: the designed large-screen page can be published into a link for a user to access, and the link is based on a BI platform and depends on the existence of the BI platform; in some scenes, for safety or other certain aspects, a user wants to deploy a large-screen page on own server resources and use a domain name link designated by the user; at this time, the relevant resources and codes of the large-screen page can be exported to the local through the large-screen export function, and a user can freely deploy the large-screen page according to needs; meanwhile, the content exported by the large screen comprises complete source code resources, a user with development capability can carry out secondary development based on the exported source code, more functions and effects are added on the basis of the finished large screen design, and more user requirements are met;
component market: the system comprises a large number of system components for users, wherein the system components comprise rich chart components, table components and map components; the component marketplace provides the ability for users to customize extension components and use custom extension components, following the previously described component data specification and defined format, users can develop test custom components locally; after the test is correct, the user can package and upload the custom assembly to a BI platform and release the custom assembly, but before the assembly is released, the user needs to apply for the assembly developer to obtain the right of uploading and releasing the assembly, meanwhile, the user needs to obey the relevant specification of releasing the assembly and undertake the relevant legal constraints, and after the release, all the users including the developer can find the assembly in the assembly market and perform transaction;
data management: management and maintenance of data owned by a user; the data referred to herein includes types of Excel/CSV data imported by a user from a local site, directly connected database data, imported API interface data, and data purchased by a data market 4, different types of data include management functions of addition, configuration, and deletion, and the contents of addition and configuration are different according to the types;
data transaction: and when the data assets are traded, the user can release the data owned by the user or authorized by the owner to the data market within the allowed range of laws and regulations according to the requirement, and defines a proper price for the data assets for other people to purchase and use, so that the benefit is earned for the data publisher.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111090794.1A CN113672228A (en) | 2021-09-17 | 2021-09-17 | Visual development method and system based on component and data asset transaction |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111090794.1A CN113672228A (en) | 2021-09-17 | 2021-09-17 | Visual development method and system based on component and data asset transaction |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113672228A true CN113672228A (en) | 2021-11-19 |
Family
ID=78549544
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111090794.1A Pending CN113672228A (en) | 2021-09-17 | 2021-09-17 | Visual development method and system based on component and data asset transaction |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113672228A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114371809A (en) * | 2021-12-14 | 2022-04-19 | 南京中孚信息技术有限公司 | Vue-based large screen visualization module dragging technology research |
| CN114845154A (en) * | 2022-04-28 | 2022-08-02 | 四川虹魔方网络科技有限公司 | Quick adaptation method of media asset data |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050102154A1 (en) * | 2003-11-12 | 2005-05-12 | Dodd Ryan A. | Method, computer useable medium, and system for enterprise resource management |
| US20140289829A1 (en) * | 2012-03-20 | 2014-09-25 | Guangdong Electronics Industry Institute Ltd | Computer account management system and realizing method thereof |
| WO2015004452A1 (en) * | 2013-07-09 | 2015-01-15 | Maxymiser Ltd | Method of optimization for an application |
| CN110807015A (en) * | 2019-09-25 | 2020-02-18 | 上海悦程信息技术有限公司 | Big data asset value delivery management method and system |
| US20200110796A1 (en) * | 2018-10-04 | 2020-04-09 | Binyamin Tsabba | Customized customer relationship management platform method and devices |
| US20200242174A1 (en) * | 2019-01-25 | 2020-07-30 | Karen Biran | Methods and systems for facilitating procurement of construction goods and services |
-
2021
- 2021-09-17 CN CN202111090794.1A patent/CN113672228A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050102154A1 (en) * | 2003-11-12 | 2005-05-12 | Dodd Ryan A. | Method, computer useable medium, and system for enterprise resource management |
| US20140289829A1 (en) * | 2012-03-20 | 2014-09-25 | Guangdong Electronics Industry Institute Ltd | Computer account management system and realizing method thereof |
| WO2015004452A1 (en) * | 2013-07-09 | 2015-01-15 | Maxymiser Ltd | Method of optimization for an application |
| US20200110796A1 (en) * | 2018-10-04 | 2020-04-09 | Binyamin Tsabba | Customized customer relationship management platform method and devices |
| US20200242174A1 (en) * | 2019-01-25 | 2020-07-30 | Karen Biran | Methods and systems for facilitating procurement of construction goods and services |
| CN110807015A (en) * | 2019-09-25 | 2020-02-18 | 上海悦程信息技术有限公司 | Big data asset value delivery management method and system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114371809A (en) * | 2021-12-14 | 2022-04-19 | 南京中孚信息技术有限公司 | Vue-based large screen visualization module dragging technology research |
| CN114845154A (en) * | 2022-04-28 | 2022-08-02 | 四川虹魔方网络科技有限公司 | Quick adaptation method of media asset data |
| CN114845154B (en) * | 2022-04-28 | 2023-05-09 | 四川虹魔方网络科技有限公司 | Quick adaptation method for media data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7361609B2 (en) | Integrated system for editing and simulating rules, version control, and business process management | |
| US8904342B2 (en) | System and method for rapid development of software applications | |
| US7600182B2 (en) | Electronic data capture and verification | |
| JP6487282B2 (en) | Method for developing application to be executed in workflow management system, and apparatus for supporting generation of application to be executed in workflow management system | |
| US8412741B2 (en) | Product network management system and method | |
| US7730446B2 (en) | Software business process model | |
| US20130332241A1 (en) | System and Method for Decision-Driven Business Performance Measurement | |
| CN113672228A (en) | Visual development method and system based on component and data asset transaction | |
| US20040107214A1 (en) | Customized document portfolio system integrating IP libraries and technology documents | |
| US20110225484A1 (en) | Cloud based modeling for enhancing spreadsheets | |
| US20110246535A1 (en) | Apparatus and Method for Constructing Data Applications in an Unstructured Data Environment | |
| Powell | Microsoft Power BI cookbook: Creating business intelligence solutions of analytical data models, reports, and dashboards | |
| CN111563200A (en) | Information display method, device, equipment and medium | |
| US20080091551A1 (en) | Knowledge-based customizable product design system | |
| CN111880839A (en) | API processing method and device | |
| CN114819430A (en) | Wind control management method and device, electronic equipment and storage medium | |
| US8589821B1 (en) | Storyboard method of end-user programming with natural language confirmation | |
| Mackey et al. | Introducing. NET 4.5 | |
| Çatal | Content management system | |
| Polino | Building Dashboards with Microsoft Dynamics GP 2013 and Excel 2013 | |
| Vesterli | Oracle ADF Survival Guide: Mastering the Application Development Framework | |
| Beckner et al. | Administering, Configuring, and Maintaining Microsoft Dynamics 365 in the Cloud | |
| Lidberg | Getting Started with SQL Server 2012 Cube Development | |
| Chennamaneni et al. | An inventory management app in Salesforce | |
| Wijethunga | Reception Hall and Catering Management System For New Sampath Caterers and Reception Hall |
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 |