Found 717 results for "api datatypes node"
The search executed in 0.002362813 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Features / AuditAudit QName: f:audit Marks a content node as auditable. Operations against this node will be logged and recorded by the Cloud CMS auditing service and stored as audit records on your platform. These audit records can then be viewed within the Cloud CMS user interface or downloaded for use in third-party reporting systems. Configuration Audit Example { "title": "My Content Instance", "_features": { "f:audit": { } } }
Score: 1.0304548
|
|
|
Gitana / 4.0 / Data Engine / Aspects / AuditAudit QName: f:audit Marks a content node as auditable. Operations against this node will be logged and recorded by the Cloud CMS auditing service and stored as audit records on your platform. These audit records can then be viewed within the Cloud CMS user interface or downloaded for use in third-party reporting systems. Configuration Audit Example { "title": "My Content Instance", "_features": { "f:audit": { } } }
Score: 1.0304548
|
|
|
Gitana / 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon DocumentDBAmazon DocumentDB Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Cloud CMS works out-of-the-box with Amazon DocumentDB as an alternative to running MongoDB on your own or using a MongoDB hosted service. Amazon DocumentDB provides an easy and convenient way for customers to manage their own MongoDB installations, data and backup. To learn more, check out API Server.
Score: 1.0286192
|
|
|
Gitana / 3.2 / Guide / Guide / Integrations / Google / TranslateGoogle Translate Google Translation Services offer the ability to quickly translate between languages, using the best model for your content needs. You can build custom models using AutoML Translation or leverage Google’s pre-trained models using Translation API. Cloud CMS provides a Google Translation Services Provider that works with Google Translate to automatically create and update I18N translations as changes are made to content by your editorial team. To learn more, check out Auto Transla
Score: 1.0286192
|
|
|
Gitana / 4.0 / Data Engine / Integrations / Amazon Web Services / Amazon DocumentDBAmazon DocumentDB Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Cloud CMS works out-of-the-box with Amazon DocumentDB as an alternative to running MongoDB on your own or using a MongoDB hosted service. Amazon DocumentDB provides an easy and convenient way for customers to manage their own MongoDB installations, data and backup. To learn more, check out API Server.
Score: 1.0286192
|
|
|
Gitana / 4.0 / Data Engine / Integrations / Google / TranslateGoogle Translate Google Translation Services offer the ability to quickly translate between languages, using the best model for your content needs. You can build custom models using AutoML Translation or leverage Google’s pre-trained models using Translation API. Cloud CMS provides a Google Translation Services Provider that works with Google Translate to automatically create and update I18N translations as changes are made to content by your editorial team. To learn more, check out Auto Transla
Score: 1.0286192
|
|
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.0280077
|
|
|
Gitana / 3.2 / Guide / Guide / Conditions / Property EqualsProperty Equals The propertyEquals condition tests whether a node property is equal to a given value. JSON Schema { "title": "Property Equals", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "string", "title": "Value" } } } Example #1 Suppose you wanted to test whether a node has a property called published which was set to true. You could set up the condit
Score: 1.0269911
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Conditions / Property EqualsProperty Equals The propertyEquals condition tests whether a node property is equal to a given value. JSON Schema { "title": "Property Equals", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "string", "title": "Value" } } } Example #1 Suppose you wanted to test whether a node has a property called published which was set to true. You could set up the condit
Score: 1.0269911
|
|
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.0248976
|
|
|
Gitana / 3.2 / Guide / Guide / Features / Stats Sum CounterStats Sum Counter QName: f:stats-sum-counter Applied to an association to indicate that a statistics counter from one of end of the association should be aggregated up into another counter on the other end of the association. This feature builds on the existing Node Statistics capabilities of Cloud CMS by letting you define custom sum counters from one end of an association to be applied to the other end. Statistics counters are accumulated once on create and decremented once on delete. Configur
Score: 1.0206549
|
|
|
Gitana / 4.0 / Data Engine / Aspects / Stats Sum CounterStats Sum Counter QName: f:stats-sum-counter Applied to an association to indicate that a statistics counter from one of end of the association should be aggregated up into another counter on the other end of the association. This feature builds on the existing Node Statistics capabilities of Cloud CMS by letting you define custom sum counters from one end of an association to be applied to the other end. Statistics counters are accumulated once on create and decremented once on delete. Configur
Score: 1.0206549
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment MappingsDeployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c
Score: 1.0143564
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment MappingsDeployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c
Score: 1.0143564
|
|
|
Gitana / 3.2 / Guide / Guide / Actions / Send EmailSend Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All
Score: 1.0142576
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Send EmailSend Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All
Score: 1.0142576
|
|
|
Gitana / 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon Elastic Search ServiceAmazon Elastic Search Service Amazon Elastic Search Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time. Cloud CMS works out-of-the-box with Amazon Elastic Search Service as an alternative to running Elastic Search on your own or using a Elastic Search hosted service. Amazon Elastic Search Service provides an easy and convenient way for customers to manage their own Elastic Search installations, data and backup.
Score: 1.0115278
|
|
|
Gitana / 4.0 / Data Engine / Integrations / Amazon Web Services / Amazon Elastic Search ServiceAmazon Elastic Search Service Amazon Elastic Search Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time. Cloud CMS works out-of-the-box with Amazon Elastic Search Service as an alternative to running Elastic Search on your own or using a Elastic Search hosted service. Amazon Elastic Search Service provides an easy and convenient way for customers to manage their own Elastic Search installations, data and backup.
Score: 1.0115278
|
|
|
Gitana / 3.2 / Guide / Guide / Features / RelatedRelated QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For
Score: 1.003383
|
|
|
Gitana / 4.0 / Data Engine / Aspects / RelatedRelated QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For
Score: 1.003383
|
|
|
How to find the Repository ID for a Project?There are a few ways to get the repository ID for a project. The easiest way is: log in to your tenant go to your Project add "/stack" to the url The "/stack" suffix will show you the members of the stack. If you then click on "workbench 'content' repository", you'll see the ID for the repository in the URL. Another way is to click on a document in your project and then click on "View in API". The URL that comes up will have the repository ID in it as well.
Score: 1.0004455
|
|
|
Gitana / 3.2 / Guide / Guide / Features / GeolocationGeolocation QName: f:geolocation Indicates that this node supports geolocation properties. This feature provisions the node with a loc property that contains two sub-properties - lat and long. { "properties": { "loc": { "type": "object", "title": "Geolocation Details", "properties": { "lat": { "type":"number", "title": "Latitude", "minimum": -180, "maxim
Score: 0.99683595
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @iter@iter Iterate over the keys of an object. Useful when looking for a particular json key. Makes the following available to the context of each iteration: $key $value $type Syntax {@iter obj=
Score: 0.99683595
|
|
|
Gitana / 4.0 / Developers / Application Server / Tags / @iter@iter Iterate over the keys of an object. Useful when looking for a particular json key. Makes the following available to the context of each iteration: $key $value $type Syntax {@iter obj=
Score: 0.99683595
|
|
|
Gitana / 4.0 / Data Engine / Aspects / GeolocationGeolocation QName: f:geolocation Indicates that this node supports geolocation properties. This feature provisions the node with a loc property that contains two sub-properties - lat and long. { "properties": { "loc": { "type": "object", "title": "Geolocation Details", "properties": { "lat": { "type":"number", "title": "Latitude", "minimum": -180, "maxim
Score: 0.99683595
|