Found 503 results for "scripting node"
The search executed in 0.001736663 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / Features / RenditionExplore automatic web page rendering through the f:rendition feature with examples and configuration guidance.
Score: 1.0213699
|
![]() |
Gitana 4.0 / Content Engine / Aspects / RenditionExplore automatic web page rendering through the f:rendition feature with examples and configuration guidance.
Score: 1.0213699
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Inline LinksAutomatically parse text to discover and track inline links in Cloud CMS documents, ensuring robust linking and preventing accidental deletion.
Score: 1.0201302
|
![]() |
Gitana 4.0 / Content Engine / Aspects / Inline LinksEnhance content by automatically parsing and tracking inline links within HTML or text, creating standalone nodes for easy reference.
Score: 1.0201302
|
![]() |
Gitana 3.2 / Guide / Guide / TreeExplore the Tree API for efficient retrieval of folder and file structures in a single call. Ideal for deep path queries and dynamic content loading.
Score: 1.0195053
|
![]() |
Gitana 4.0 / Content Engine / TreeExplore the Tree API for efficient retrieval of folder and file structures in a single call. Ideal for deep path queries and dynamic content loading.
Score: 1.0195053
|
![]() |
How to get a content definition JSON from the Cloud CMS API?There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname} http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname} http://api.cloudcms.com/docs#!/branch/get_repositories_rep
Score: 1.017499
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Deployment ConfigOptimize deployment processes with the f:deployment-config feature, guiding handlers like S3, FTP, and File System for seamless, structured deployment.
Score: 1.0162565
|
![]() |
Gitana 4.0 / Content Engine / Aspects / Deployment ConfigOptimize your deployment with Gitana by using f:deployment-config to map content to paths for S3, FTP, and file systems effectively.
Score: 1.0162565
|
![]() |
Gitana 3.2 / Guide / Guide / Scripting / Workflow TransitionDiscover the components of Workflow Transition, including key properties like fromNodeId, id, and toNodeId, within our detailed guide.
Score: 1.0135343
|
![]() |
Workflow TransitionDiscover the components of Workflow Transition, including key properties like fromNodeId, id, and toNodeId, within our detailed guide.
Score: 1.0135343
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Knowledge RecipientDiscover how Cloud CMS manages the f:knowledge-recipient feature, enabling seamless knowledge sharing across nodes.
Score: 1.0092082
|
![]() |
Gitana 4.0 / Content Engine / Aspects / Knowledge RecipientDiscover how Cloud CMS manages the f:knowledge-recipient feature, enabling seamless knowledge sharing across nodes.
Score: 1.0092082
|
![]() |
Running Custom Scripts through Rules TestYou may want a complex action to occur in your project that is specific to your business requirements. We provide a number of out of the box actions that you can easily setup in a Content Rule, but sometimes the requirement goes beyond these functionalities. So, Cloud CMS allows you to write Javascript scripts that will run whenever a rule is triggered. In this example, we will be working with the following definition, call it custom:counter: { "title": "counter", "type": "object", "propertie
Score: 1.0085965
|
![]() |
What is the reason for "Failed to index node"?If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates
Score: 1.0079857
|
![]() |
Gitana 3.2 / Guide / Guide / Features / AuditMark content nodes as auditable with Cloud CMS, logging operations for analysis and integration with reporting tools.
Score: 1.0042887
|
![]() |
Gitana 4.0 / Content Engine / Aspects / AuditMark content nodes as auditable with Cloud CMS, logging operations for analysis and integration with reporting tools.
Score: 1.0042887
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Stats Sum CounterAggregate statistics counters in Cloud CMS using Stats Sum Counter to enhance data insights across associations efficiently.
Score: 1.0033295
|
![]() |
Gitana 4.0 / Content Engine / Aspects / Stats Sum CounterAggregate statistics counters in Cloud CMS using Stats Sum Counter to enhance data insights across associations efficiently.
Score: 1.0033295
|
![]() |
How do I retrieve the folder path for my content?In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C
Score: 1.0033295
|
![]() |
Gitana 3.2 / Guide / Guide / Conditions / Property EqualsTest a node property against a specific value using propertyEquals in your JSON schema configurations.
Score: 1.0012443
|
![]() |
Gitana 4.0 / Content Engine / Behaviors / Conditions / Property EqualsTest a node property against a specific value using propertyEquals in your JSON schema configurations.
Score: 1.0012443
|
![]() |
Gitana 3.2 / Guide / Guide / Actions / Send EmailSend personalized emails with configurable templates using various providers. Simplify email sending by customizing recipients, subjects, and body content.
Score: 1.0011172
|
![]() |
Gitana 4.0 / Content Engine / Behaviors / Actions / Send EmailSend personalized emails with configurable templates using various providers. Simplify email sending by customizing recipients, subjects, and body content.
Score: 1.0011172
|
![]() |
Gitana 4.0 / Forms / API / ConnectorsEnhance Alpaca forms with custom and default connectors to seamlessly load data, schemas, and options from remote sources like Cloud CMS.
Score: 0.9973769
|