Found 747 results for "appserver tags content"
The search executed in 0.002233339 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / UI Developers Guide / ContextsContexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi
Score: 0.64879084
|
|||||||||||||||||||||
Gitana / 4.0 / Developers / User Interface Customization / ContextsContexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi
Score: 0.64879084
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Search / Query String ReferenceQuery String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t
Score: 0.64397347
|
|||||||||||||||||||||
Gitana / 4.0 / Data Engine / Discovery / Search / Query String ReferenceQuery String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t
Score: 0.64397347
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / Deployment ConfigDeployment Config QName: f:deployment-config The Deployment Config feature lets you describe settings that should be considered by one or more Deployment Handlers during deployment. These settings may describe things such as a mappings of deployed content to file system paths. When a node is deployed, if it has the f:deployment-config feature on it, then that feature may instruct the Deployment Handler about how to deploy. Configuration The f:deployment-config feature is utilized by the followin
Score: 0.64104337
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / PrecompilePrecompile QName: f:precompile Marks a node as having zero or more text properties that contain markdown or templated text that should be compiled (or transformed) when the document is saved. This transformation should occur when the source property is modified and the result should be stored on a new property that will store the compiled text. Suppose you have a property on a node called text. It is a Markdown field where your editors make changes to text stored in the markdown format. When the
Score: 0.64104337
|
|||||||||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / Deployment ConfigDeployment Config QName: f:deployment-config The Deployment Config feature lets you describe settings that should be considered by one or more Deployment Handlers during deployment. These settings may describe things such as a mappings of deployed content to file system paths. When a node is deployed, if it has the f:deployment-config feature on it, then that feature may instruct the Deployment Handler about how to deploy. Configuration The f:deployment-config feature is utilized by the followin
Score: 0.64104337
|
|||||||||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / PrecompilePrecompile QName: f:precompile Marks a node as having zero or more text properties that contain markdown or templated text that should be compiled (or transformed) when the document is saved. This transformation should occur when the source property is modified and the result should be stored on a new property that will store the compiled text. Suppose you have a property on a node called text. It is a Markdown field where your editors make changes to text stored in the markdown format. When the
Score: 0.64104337
|
|||||||||||||||||||||
Introducing the Cloud CMS Open Source App ServerCloud CMS lets you create content once and reuse it everywhere - across all of your devices, web sites, mobile applications, tradeshow kiosks, digital signage surfaces and more. Our editorial environment is fully featured, extensible easy to use, letting you manage content and deliver it via our enterprise-class Content API. With Cloud CMS, customers are free to build apps on top of best-of-breed open-source frameworks while leveraging open-standards. They are empowered to continue to use the de
Score: 0.63783926
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Application Server / URL Addressability / Node URLsNode URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye
Score: 0.6372326
|
|||||||||||||||||||||
Gitana / 4.0 / Developers / Application Server / URL Addressability / Node URLsNode URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye
Score: 0.6372326
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Forms / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 0.6362399
|
|||||||||||||||||||||
Gitana / 4.0 / Forms / CMS / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 0.6362399
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-documentcontext-document If a Document (i.e. a content Node) is currently being observed. { "evaluator": "context-document" }
Score: 0.631366
|
|||||||||||||||||||||
Gitana / 4.0 / Developers / User Interface Customization / Evaluators / context-documentcontext-document If a Document (i.e. a content Node) is currently being observed. { "evaluator": "context-document" }
Score: 0.631366
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / ActionsActions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work
Score: 0.6306275
|
|||||||||||||||||||||
Gitana / 4.0 / Data Engine / Behaviors / ActionsActions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work
Score: 0.6306275
|
|||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / Translation
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Workflow Task Name: workflowTask Property Type Description id string The ID of the workflow task title string The title of the workflow task description string The description of the workflow task timeStarted calendar The time the workflow was started timeCompleted calendar The time the workflow was completed (if completed) context object Contextual variables being passed along with the workflow task workflowData object Data being passed along with the workflow task workflowId string The ID of t
Email Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: {
"templateKey": "abc"
}
Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik
release-subcontext [
{
"evaluator": "context-workspace-has-pending-merges",
"config": {
"release-subcontext": {
"items": [
{
"key": "release/workspaces",
"items": [
{
"key": "release/merges",
"title": "Pending Merges",
"uri": "#/projects/{projectId}/releases/{releaseId}/merges",
"iconClass": "fa fa-angle-right",
"order": 32000
}
release-subcontext [
{
"evaluator": "context-workspace-has-pending-merges",
"config": {
"release-subcontext": {
"items": [
{
"key": "release/workspaces",
"items": [
{
"key": "release/merges",
"title": "Pending Merges",
"uri": "#/projects/{projectId}/releases/{releaseId}/merges",
"iconClass": "fa fa-angle-right",
"order": 32000
}
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Workflow Task Name: workflowTask Property Type Description id string The ID of the workflow task title string The title of the workflow task description string The description of the workflow task timeStarted calendar The time the workflow was started timeCompleted calendar The time the workflow was completed (if completed) context object Contextual variables being passed along with the workflow task workflowData object Data being passed along with the workflow task workflowId string The ID of t
Email Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: {
"templateKey": "abc"
}
Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik
|