Liferay Data Engine

With Liferay Data Engine, use high level APIs to quickly assemble scalable, flexible business applications. Without writing persistence code or complex custom business logic, you can call the Data Engine APIs to create an entire application.

The Data Definition API is at the core of the Data Engine. It lets you:
  • Define the fields of the data definition.
  • Execute CRUD operations on Data Definitions.
  • Define validation rules for data definition elements.
The Data Record Collection API collects the data records backed by the data definition.
  • Execute CRUD operations on Data Record Collections and their Data Records.

The Data Layouts API lets you add and edit data layouts to style the Data Definition's form.

This kind of flexible app builder helps modern businesses remain competitive. Customized digital solutions don't build themselves, but the Data Engine's APIs make it painless to rapidly create new applications.

Últimos cambios
  • LPS-91318 Merge to Master
  • LPS-91401 Merge to Master
  • LPS-91429 Enable com.liferay.portlet.title.localization.test.PortletTitleTest
  • LPS-91627 Propagate description, queryparams and info to OpenAPI doc
  • LPS-91804 Move DataDefinition define validation rules for data definition elements to Rest resource
  • LPS-91898 Move DataView search data layouts to Rest resource
  • LPS-92012 Merge to Master
  • LPS-92053 [Reports] See process item detail page
  • LPS-92056 Merge to Master
  • LPS-92526 Upgrade JSON Java to 20180813
  • LPS-92556 Make Rules Extensible
  • LPS-92618 Use toDto(json) and toDtos(json) in StructuredContentResourceTest
  • LPS-93139 DataDefinition - Move Tests of add search for data definitions to Rest resource
  • LPS-93141 DataDefinition - Move Tests of define validation rules for data definition elements to Rest resource
  • LPS-93164 Investigate data engine permission issues
  • LPS-93219 Add Permissions to data record
  • LPS-93335 Adjust Data Layout portlet names
  • LPS-93561 Fix data record collection search feature
  • LPS-93840 Remove old data engine code
  • LPS-93861 Create renderer taglib User View for Data Engine
  • LPS-93944 Generate tests for segmentation APIs: obtain content space segments
  • LPS-93983 Fix permission in Data Engine
  • LPS-94274 org.junit.ComparisonFailure when asserting expected values
  • LPS-94301 Class in modules that are not exported should be in internal package
  • LPS-94642 Change DataRecordValues from Array to Map in DataRecord
  • LPS-94765 Change LocalizedValues From Array to Map
  • LPS-94809 Create layout-builder taglib
  • LPS-94991 Support Map<String, Object> in REST builder
  • LPS-95232 HttpInvoker to support multipart
  • LPS-95267 Deserialize layout definition into model classes
  • LPS-95723 HttpInvoker to support PATCH
  • LPS-95924 Use Client Resource in DocumentResourceTest
  • LPS-96029 HttpInvoker to support headers
  • LPS-96153 Add a key to Data Definition so it can be fetched by a known key
  • LPS-96161 Verify page size when listing data records
  • LPS-96185 Add ability to submit records for a Data Definition
  • LPS-96186 Add ability to pass predefined values to Data Layout Renderer Tag
  • LPS-96319 NullPointerException in *ResourceTest
  • LPS-96373 Implement getting and filtering change tracking collections business logic
  • LPS-96627 Upgrade GraphQL version
  • LPS-96628 Support pagination in GraphQL
  • LPS-96632 Support filter, sort and Search in GraphQL
  • LPS-96637 Include relationships support in GraphQL
  • LPS-96649 Add operations to REST service to retrieve Data Layout by key
  • LPS-96698 Add tests for GraphQL
  • LPS-96699 Javadoc Documentation
  • LPS-97079 Prepare to activate automated linting
  • LPS-97089 Include a data-engine-taglib js-unit test and enable test
  • LPS-97093 Add a key to Data Record Collection so it can be fetched by a known key
  • LPS-97115 REST resource interfaces should be marked ProviderType
  • LPS-97127 Add copyright.js and apply ESLint auto-fix to add header to all *.js files
  • LPS-97203 [BE] Add sorting to data definitions
  • LPS-97221 Add a default Data Record Collection for a Data Definition
  • LPS-97414 [BE] Add sorting to Data Layout
  • LPS-97463 Deal with lint suppressions in data-engine-taglib
  • LPS-97496 Move DataEngineStorage from SPI to API
  • LPS-97663 Move SPI to API
  • LPS-97971 @Context for JAX-RS is slowing down boot up
  • LPS-98032 Reactivate .jsp formatting
  • LPS-98083 As a developer, I want to search Data Record Collection
  • LPS-98104 Unify "sort" parameter name in REST and GraphQL
  • LPS-98133 [API] POST and GET endpoints of Data Layout are missing 's' in Data-Layout
  • LPS-98140 Deprecate SoyHTMLData and related stuff
  • LPS-98183 Remove data layouts when removing a data definition
  • LPS-98186 Add an adapter to transform DataDefinition/DataLayout into DDMForm/DDMFormLayout
  • LPS-98277 JSX formatting: sort properties and use double quotes
  • LPS-98334 Remove redundant ESLint extensions
  • LPS-98366 Create integration tests for the endpoint
  • LPS-98387 Example JS application with GraphQL APIs
  • LPS-98422 [BE] Create App Builder REST API structure
  • LPS-98447 Rename GraphQL mutations using non HTTP related verbs
  • LPS-98468 When saving a Data Definition, fieldset field properties are not being persisted.
  • LPS-98519 404 error in dynamic-data-mapping-form-builder CSS in case of configuring Liferay with a non-ROOT context
  • LPS-98660 CommentResourceTest and DataRecordResourceTest are failing in acceptance
  • LPS-98743 Fix data layout rendering issues
  • LPS-98787 REST client is not escaping strings inside Maps
  • LPS-98797 Add Cookie authentication to client project
  • LPS-98817 Add SF rules for Java: Always use generics for new List
  • LPS-98853 Fix data layout attribute name
  • LPS-98871 Wrong GraphQL relation between organization and web-url
  • LPS-98877 Sync portlet-api version
  • LPS-98879 Sync servlet-api versions
  • LPS-98907 Rendered template shows relative URLs
  • LPS-98931 REST Client doesn't serialize arrays inside an object
  • LPS-98962 Standardize Ajax requests in dynamic-data-mapping
  • LPS-99035 Data Definition cannot be saved if optional properties are not filled
  • LPS-99076 Client project is not parsing maps that are inside of maps<String, Object>
  • LPS-99077 The list of options available in some field properties should be localizable
  • LPS-99372 Data definition is missing available language ids and default language id
  • LPS-99389 Migrate dynamic-data-mapping-service to use DS instead of Spring
  • LPS-99413 UI is crashing when leaving a page with data layout builder tag applied
  • LPS-99566 Data Layout Builder is not rendering properly
  • LPS-99569 AssertionError in Data Engine
  • LPS-99657 Enforce consistency for packages
  • LPS-99893 Call list methods when keywords field is empty
  • LRQA-51488 Clarifying strings
Show More

Clientes que vieron esto tambien compraron