Search Results

Official Documentation 1808
ソート
Resource Type
Deployment Approach
Capability
Feature
アカウントへの組織の追加
Adding Organizations to Accounts Organizations can be added to an Account to simplify the management and administration of accounts. To learn more about using Organizations with Accounts see Using...
アカウントへのユーザーの招待
Inviting Users to an Account This article documents how to invite users to an account. Corporate accounts can have more than one user assigned to handle various aspects of a transaction. There are...
コマースアカウントの役割
Commerce Account Roles Account roles are sets of permissions that grant users specific abilities within an account context. These roles can be used to delegate account responsibilities, or paired...
新規アカウントグループの作成
Creating a New Account Group Account Groups allow accounts to be grouped based on business criteria, such as grouping accounts by geographic region (US West Coast, the Midwest, and the South)....
コマースの役割と権限
Commerce Roles and Permissions The permissions assigned to a user role determine the Liferay applications and resources they can access and use. You can scope each role to an instance, site,...
アセットリストをスプレッドシートにエクスポートする
Exporting Assets List To a Spreadsheet The Content Dashboard can export a spreadsheet (.xls file) of content related metadata for further analysis. To export the asset list to a spreadsheet, ...
アカウント管理
Account Management Available Liferay 7.3 and Below In Liferay, accounts store customer information, such as billing and shipping addresses, order details, and VAT number. Once created, accounts...
Commerce 2.1 以前のバージョンのアカウントへの組織の追加
Adding Organizations to Accounts for Commerce 2.1 and Earlier Versions Organizations can be added to an Account to simplify the management and administration of accounts. To learn more about using...
Commerce 2.1 以前のバージョンのアカウントへのユーザーの招待
Inviting Users to an Account for Commerce 2.1 and Earlier Versions This article documents how to invite users to an account. Corporate accounts can have more than one user assigned to handle...
コンテンツダッシュボード
Content Dashboard Available 7.3+ This feature works only with Elasticsearch. The Content Dashboard is a global application for managing your content. From the Content Dashboard page, content...
メンションの設定
Configuring Mentions Mentions are enabled by the Mentions app. By default, the Mentions app is enabled globally. However, this can be enabled or disabled either globally or per site. Configuring...
廃止されたコンテンツ機能
Deprecated Content Features These content features are deprecated and no longer actively developed in Liferay. While still available for compatibility and migration purposes, they are not...
Web コンテンツ テンプレート
Web Content Templates With Web Content Templates, you can define how content appears, ensuring that your web content aligns with your brand and functional requirements. Learn how to create...
Webコンテンツの記事をプレビューする
Previewing Web Content Articles After creating a web content article, you can preview it using the selected default template or display page template before publishing, so you can make adjustments...
通知とリクエスト
Notifications and Requests Notifications and requests keep users informed about important activity, such as mentions, site invitations, or workflow tasks. You can manage how users are notified,...
Webコンテンツストラクチャー
Web Content Structures Web content structures are the building blocks for web content articles. They determine the information you can include when writing web content. Structures provide these key...
バッチ YAML 構成リファレンス
Batch YAML Configuration Reference Use a client-extension.yaml file to define a batch client extension. Usage Details This client-extension.yaml file defines a client extension of type batch: ...
はじめに
Getting Started Previously, Poshi tests could only be executed by downloading and creating the test files within the Liferay source code. The Poshi Standalone gradle project enables you to use...
テストの実行
Running a Test Open the poshi-ext.properties file on your poshi-standalone directory and add the following line, replacing the TestCaseFileName#TestCaseName with the one you created in Creating A...
Liferay DXPをマーケットプレイスに接続する
Connecting Liferay DXP to Marketplace Liferay DXP 2025.Q1+/GA132+ You can connect Liferay DXP to Marketplace in Instance Settings. With this integration, you can add supported apps from the...
ページフラグメントの開発リファレンス
Developing Page Fragments Reference The Developing Fragments Reference provides essential information on key aspects of fragment development in Liferay. It covers command references, configuration...
マクロファイルの作成
Creating a Macro File Test Scenario Write your first macro file using the test scenario below: You would like to test that your name does not appear on any learn.liferay.com article. The steps you...
リソースのバンドル
Bundling Resources
構文の検証
Syntax Validation The Poshi Standalone grade projects includes a validation task that can be used to check your code for syntax errors before running your test. To use this, simply run ./gradlew...
設定
Setup Prerequisites A supported version of Java. Google Chrome. Gradle or Gradle Wrapper 6.6.1 or higher. Setting up the Poshi Standalone Gradle Project Create a new directory, example...
IFrame YAML 設定リファレンス
IFrame YAML Configuration Reference You can define an IFrame client extension with a client-extension.yaml file. Data Usage This client-extension.yaml file defines an IFrame client extension: ...
テスト結果とテストのデバッグについて
Understanding Test Results and Debugging Tests Poshi tests are run on the terminal or command line. When a test run is completed there are multiple ways to view the test results and diagnose test...
Poshiレイヤー
Poshi Layers
Poshiのメリット
Poshi Advantages Simplified Syntax To make it easier for less technical testers to read and write test automation, Poshi uses a simplified Groovy-like script syntax. It is less wordy than most...
関数
Functions In Poshi, Functions handle extra WebDriver commands that an element might require to interact with a page object or element. Functions combine the basic methods defined in the...
Poshiの基本
Poshi Basics New features, improvements, and system upgrades can sometimes introduce unexpected behaviors and bugs. Running suites of automated tests is an advantageous method of identifying issues...
マクロ
Macros A macro is a set of functions that perform a task. Macros are where locators (paths) and functions are brought together to script interactions that a user performs on the system being...
変数の使用
Using Variables Though not a Poshi layer, variables are a large part of Poshi tests. Variables, like in other programming languages, are used to store data which can be referenced and reused in...
Poshiのリソース
Poshi Resources To give Poshi test writers easy access to commonly used functions or other files, Poshi resources were created to store existing Poshi files as dependencies that can be loaded apart...
リファレンス
Reference Node Version Information
コアフレームワーク
Core Frameworks
構成フレームワーク
Configuration Framework Setting and Accessing Configurations Categorizing a Configuration Scoping Configurations Portlet Level Configuration Configuration Form Renderer DDM Form Annotations ...
Paths
Paths A path is an element on a page that a test will interact with. An element can be a button, text field, link, image, paragraph, or just about anything you would need to assert, click, or type...
依存性注入
Dependency Injection
サーブレット
Servlets
Expando
Expando Accessing Custom Fields with Expando
データスコープ
Data Scopes
データフレームワーク
Data Frameworks
キャッシュ
Cache
Webアプリケーションの開発
Developing a Web Application
リファレンス
Reference
チャートタグライブラリ
Chart Tag Library Lines, splines, bars, pies and more, the Chart tag Library provides everything you need to model data. Each taglib gives you access to the corresponding Clay component. These...
リファレンス
Reference
Clayタグライブラリ
Clay Tag Library The Liferay Clay tag library provides a set of tags for creating Clay UI components in your app. AUI taglibs are deprecated as of Liferay 7.1. We recommend that you use Clay...
マルチスレッド処理
Multithreading Process Liferay DXP 7.4 U10+ or Liferay Portal 7.4 GA14+ Your Upgrade Processes may involve making complex changes to large data sets. If performance is critical, use the...
Clayボタン
Clay Buttons Buttons come in several types and variations. This tutorial covers the different styles and variations of buttons you can create with the Clay taglibs. Types Primary button: Used for...
JSFの使用
Using JSF Liferay Faces is an umbrella project that provides support for the JavaServer[™] Faces (JSF) standard in Liferay DXP/Portal. Here are the Liferay Faces topics: Introduction to Liferay...
Using Bean Portlet
Using Bean Portlet Portlet 3.0, the JSR 362 standard, features a style of portlet development called Bean Portlets that use Contexts and Dependency Injection (CDI). Bean Portlets fully leverage all...
Clay Badges
Clay Badges Badges help highlight important information such as notifications or new and unread messages. Badges have circular borders and are only used to specify a number. This covers the...
Clayアイコン
Clay Icons The Liferay Clay taglibs provide several icons that you can use in your apps. Use the clay:icon tag and specify the icon with the symbol attribute: You can include icons in your app...
Clayナビゲーションバー
Clay Navigation Bars Similar to dropdown menus, navigation bars display a list of navigation items. The key difference is navigation bars are displayed in a horizontal bar with all navigation items...
Clay進捗バー
Clay Progress Bars You can add progress bars to your app with the clay:progressbar tag. These indicate the completion percentage of a task and come in three status styles: default (blue), warning...
Clayラベルとリンク
Clay Labels and Links Liferay Clay taglibs provide tags for creating labels and links in your app. Both of these elements are covered below. Labels The Liferay Clay taglibs provide a few different...
Clayステッカー
Clay Stickers Whereas badges display numbers and labels display short information, stickers are small visual indicators of the content (usually the content type). They can include a small label or...
Liferay Util Get URLの使用
Using Liferay Util Get URL The get URL tag scrapes the URL provided by the url attribute. If a value is provided for the var attribute, the content from the screen scrape is scoped to that...