Found 766 results for "gitana 4.0 developers api resources node delete-repositories-repositoryid-b-branchid-lists-listkey"
The search executed in 0.002575269 seconds. That's fast.
|
Workflow TransitionDiscover the components of Workflow Transition, including key properties like fromNodeId, id, and toNodeId, within our detailed guide.
Score: 1.0026917
|
|
|
Gitana 3.2 / Guide / Guide / Features / Stats Sum CounterLeverage Cloud CMS Stats Sum Counter to aggregate custom statistics between associations, enhancing data insights and content popularity.
Score: 1.0022646
|
|
|
Gitana 4.0 / Content Engine / Aspects / Stats Sum CounterLeverage Cloud CMS Stats Sum Counter to aggregate custom statistics between associations, enhancing data insights and content popularity.
Score: 1.0022646
|
|
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: 0.9977404
|
|
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: 0.997115
|
|
|
Gitana 3.2 / Guide / Guide / Conditions / Property EqualsTest a node property against a specific value using propertyEquals in your JSON schema configurations.
Score: 0.99052167
|
|
|
Gitana 3.2 / Guide / Guide / Features / AuditEnhance content management with Cloud CMS auditing, ensuring secure operations through detailed logs and audit records for seamless third-party reporting.
Score: 0.99052167
|
|
|
Gitana 4.0 / Content Engine / Aspects / AuditEnhance content management with Cloud CMS auditing, ensuring secure operations through detailed logs and audit records for seamless third-party reporting.
Score: 0.99052167
|
|
|
Gitana 4.0 / Content Engine / Behaviors / Conditions / Property EqualsTest a node property against a specific value using propertyEquals in your JSON schema configurations.
Score: 0.99052167
|
|
|
Gitana 4.0 / Content Engine / Aspects / Auto Analyze TextEnhance your content's full-text search indexing with automated text analysis integration using the auto-analyze-text feature.
Score: 0.9856895
|
|
|
Gitana 3.2 / Guide / Guide / AuditingOptimize your content strategy with Cloud CMS's audit system, tracking user interactions and content access in on-premise Docker environments.
Score: 0.9760453
|
|
|
Gitana 4.0 / Content Engine / Platform / AuditingEnable comprehensive auditing in Cloud CMS for Docker environments with a robust built-in system detailing user and content interactions.
Score: 0.9760453
|
|
|
Gitana 4.0 / Content Engine / Aspects / Auto OCR ExtractAuto OCR Extract automatically processes binary attachments with OCR, enhancing full-text search and tooling with extracted content.
Score: 0.9739263
|
|
|
Gitana 3.2 / Guide / Guide / Features / IndexableOptimize your content indexing with Cloud CMS. Configure search-index updates, exclude paths, and enhance performance for precise search results.
Score: 0.9735687
|
|
|
Gitana 4.0 / Content Engine / Aspects / IndexableOptimize your content indexing with Cloud CMS. Configure search-index updates, exclude paths, and enhance performance for precise search results.
Score: 0.9735687
|
|
|
Gitana 4.0 / Reference / Types / ChangesetExplore Changeset API for Cloud CMS to manage your branch content with ease. Enhance content curation and authoring with advanced features.
Score: 0.97018677
|
|
|
Pagination optionsYou can specify pagination options in an optional second argument to the queryNodes function, basically like this: Chain(branch).queryNodes({ "_type": "video:essentials" }, { "sort": { "title": -1 }, "limit": 10, "skip": 30 }).then(function() { ... }); In this example, the results will start at index 30 in the record set and will contain the next 10 entries. The record set is sorted by "title" in a descending order ahead of being returned. If pagination sort isn't provided, then the o
Score: 0.96908
|
|
|
Gitana 3.2 / Guide / Guide / Features / RelatedOptimize Cloud CMS node relationships with the f:related feature, enhancing relator association efficiency automatically.
Score: 0.96419054
|
|
|
Gitana 4.0 / Content Engine / Aspects / RelatedOptimize node relationships with Cloud CMS using the 'related' feature for efficient data management and mapping across connected nodes.
Score: 0.96419054
|
|
|
Gitana 3.2 / Guide / Guide / Applications / Public ServicesSimplify mobile and web app development with Cloud CMS's backend services for user registration, password resets, and more.
Score: 0.9600512
|
|
|
Gitana 3.2 / Guide / Guide / Application Server / Services / InsightOptimize your web app's analytics with Cloud CMS Insight, seamlessly capturing data via web sockets into the Cloud CMS data warehouse.
Score: 0.9600512
|
|
|
Gitana 4.0 / Developers / Application Server / Services / InsightOptimize your web app's analytics with Cloud CMS Insight, seamlessly capturing data via web sockets into the Cloud CMS data warehouse.
Score: 0.9600512
|
|
|
Gitana 4.0 / Content Engine / Platform / Applications / Public ServicesSimplify user registration and password management with Cloud CMS application services for web and mobile platforms.
Score: 0.9600512
|
|
|
Connecting via a Corporate ProxyThe Cloud CMS drivers support connectivity through a corporate proxy. The means of doing so are slightly different depending on which driver you're using. Node.js The Cloud CMS Node.js driver detects the following environment variable: HTTP_PROXY If this environment variable is specified, all API calls with be routed through the proxy server at that location. This proxy server may support either HTTP or HTTPS. For example, you may set the environment variable like this: HTTP_PROXY=http://127.0.0
Score: 0.9600512
|
|
|
Gitana 3.2 / Guide / Guide / Features / GeolocationEnhance node capabilities with geolocation features including fast MongoDB queries using latitude and longitude properties. No configuration needed.
Score: 0.95852816
|