When should I use the Object Entry Manager client extension type?

• The source-of-truth for an Object lives outside Liferay and Liferay is just a UI. • You need to back an Object with an ERP / CRM / warehouse system.

How do I create a Object Entry Manager client extension?

1. Ship a paired `oAuthApplicationUserAgent`. 2. Implement the CRUD contract at `resourcePath` (see Liferay docs).

What fields are required on a Object Entry Manager client extension?

resourcePath (string): CRUD handler path. oAuth2ApplicationExternalReferenceCode (string): Ref code of the paired `oAuthApplicationUserAgent`.

Object Entry Manager

Externalize the CRUD lifecycle of a Liferay Object.

type: objectEntryManager·Microservice

# description

Replaces Liferay's built-in Object entry storage with your own service. Reads / writes / lists all route through your endpoint.

Externalize business logic — actions, validation, workflow, notifications.

# when to use

→The source-of-truth for an Object lives outside Liferay and Liferay is just a UI.
→You need to back an Object with an ERP / CRM / warehouse system.

# how to use

01Ship a paired oAuthApplicationUserAgent.
02Implement the CRUD contract at resourcePath (see Liferay docs).

# required fields

field	type	description
`resourcePath`required	`string`	CRUD handler path.
`oAuth2ApplicationExternalReferenceCode`required	`string`	Ref code of the paired `oAuthApplicationUserAgent`.

# optional fields

field	type	description
`name`	`string`	Display name.

# example

client-extension.yaml

external-orders:
    type: objectEntryManager
    name: External Orders
    resourcePath: /objects/orders
    oAuth2ApplicationExternalReferenceCode: my-oauth-ua

# related types

Usually shipped alongside Object Entry Manager:

❯OAuth Application (User Agent)— Register a browser / SPA OAuth application.

# more in microservice

cd ..scaffold this type in VS Code →