Found 310 results for "access-policies conditions feature"
The search executed in 0.001063252 seconds. That's fast.
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / FTP Deployment HandlerFTP Deployment Handler Handles the deployment of one or more Deployment Packages to an SFTP or FTP server. The remote S/FTP server is described by a URL, username and password. The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configuration { "url": "{url}", "username": "{username}", "pass
Score: 1.3734934
|
||||||
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Amazon S3 Deployment HandlerAmazon S3 Deployment Handler Handles the deployment of one or more Deployment Packages to an Amazon S3 bucket. The Amazon S3 bucket is described by: accessKey secretKey region bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configuration { "accessKey": "{a
Score: 1.3734934
|
||||||
Gitana / 3.2 / Guide / Guide / Features / BehaviorBehavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }
Score: 1.3711622
|
||||||
Gitana / 4.0 / Data Engine / Aspects / BehaviorBehavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }
Score: 1.3711622
|
||||||
Single Sign On (SSO)Cloud CMS introduces a Single Sign-On service that will make it easy for the users to connect using their already existing business accounts. Cloud CMS supports two Enterprise SSO features – SAML 2.0 and JWT. These are two popular SSO mechanisms that work with many commercial and open-source identity providers including Microsoft Active Directory Federation Services (ADFS), JBoss Keycloak etc. Using SAML 2.0 and JWT, Cloud CMS can be easily integrated with your corporate security infrastructure.
Score: 1.3608601
|
||||||
Cloud CMS JavaScript Driver Release 1.0.3 is out!The Cloud CMS team is pleased to announce the immediate availability of version 1.0.3 of the Cloud CMS JavaScript Driver for jQuery, Dojo, Javascript/HTML5 and Node.js applications. Download today from http://github.com/gitana/gitana-javascript-driver. JavaScript Driver for Cloud CMS The Cloud CMS JavaScript Driver is a JS library that you can drop into your HTML5/JS applications to take advantage of the authoring and delivery APIs of the Cloud CMS server. It makes it easier for developers to ut
Score: 1.3608601
|
||||||
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / File System Deployment HandlerFile System Deployment Handler Handles the deployment of one or more Deployment Packages to a file system. A file system is described by a local path on disk, such as: /www/files /data /Users/joesmith/files These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage). The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails
Score: 1.3574483
|
||||||
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / File System Deployment HandlerFile System Deployment Handler Handles the deployment of one or more Deployment Packages to a file system. A file system is described by a local path on disk, such as: /www/files /data /Users/joesmith/files These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage). The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails
Score: 1.3574483
|
||||||
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / IBM COS Deployment HandlerIBM COS Deployment Handler Handles the deployment of one or more Deployment Packages to an IBM Cloud Object Store (COS) bucket. The IBM Cloud Object Store bucket is described by: apiKey serviceInstanceId endpointUrl location bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proce
Score: 1.341774
|
||||||
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / IBM COS Deployment HandlerIBM COS Deployment Handler Handles the deployment of one or more Deployment Packages to an IBM Cloud Object Store (COS) bucket. The IBM Cloud Object Store bucket is described by: apiKey serviceInstanceId endpointUrl location bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proce
Score: 1.341774
|
||||||
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Azure Blob Storage Deployment HandlerAzure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configurat
Score: 1.3264574
|
||||||
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Azure Blob Storage Deployment HandlerAzure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configurat
Score: 1.3264574
|
||||||
Content definition - JSON Schema v4 document1. A content definition is a JSON Schema v4 document. As such, the valid property types are those supported by JSON Schema itself, described more thoroughly here: http://json-schema.org/latest/json-schema-core.html (Specifically, look under section 4.2.1 Instance Data Model) 2. The default path capability is frequently used to make sure that content of a given type is stored into a predictable "folder" structure. You're right to be inquisitive about what this means since everything in Cloud CMS
Score: 1.3264574
|
||||||
Gitana / 3.2 / Guide / Guide / Features / Knowledge SpaceKnowledge Space QName: f:knowledge-space Used to indicate that a node should behave as a Knowledge Space. A Knowledge Space has zero or more knowledge properties. A knowledge property is a regular old property on your JSON object that is special in that its value may propagate to other nodes automatically. A Knowledge Space is holds the "master value" for those knowledge properties. When those properties change, their new values are pushed to any other nodes that are sharing the knowledge from t
Score: 1.3162689
|
||||||
Gitana / 4.0 / Data Engine / Aspects / Knowledge SpaceKnowledge Space QName: f:knowledge-space Used to indicate that a node should behave as a Knowledge Space. A Knowledge Space has zero or more knowledge properties. A knowledge property is a regular old property on your JSON object that is special in that its value may propagate to other nodes automatically. A Knowledge Space is holds the "master value" for those knowledge properties. When those properties change, their new values are pushed to any other nodes that are sharing the knowledge from t
Score: 1.3162689
|
||||||
How do I run custom validation before something is deleted?Cloud CMS provides several ways to run validation ahead of deletion. There are many use cases where this employed - such as: Preventing an Image from being deleted when it is being referenced by a live Web Page Preventing a required sub-object from being deleted Preventing something from deleted when one or more other things are referencing it or depend on it in some way Here are a few approaches which are commonly used: ## Content Model Dependencies We implement link validation via the graph. S
Score: 1.3162689
|
||||||
Gitana / 3.2 / Guide / Guide / Features / ContainerContainer QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl
Score: 1.2968498
|
||||||
Gitana / 4.0 / Data Engine / Aspects / ContainerContainer QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl
Score: 1.2968498
|
||||||
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Remove Features
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 1.2875979
|
||||||
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Remove Features
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 1.2875979
|
||||||
Terms of Service - GitanaTerms of Service - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and c
Score: 1.2849257
|
||||||
Gitana / 3.2 / Guide / Guide / Content Modeling / ScriptsScripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/
Score: 1.2795184
|
||||||
Gitana / 3.2 / Guide / Guide / Features / Renditionable
Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration
| ||||||
Gitana / 4.0 / Data Engine / Aspects / Renditionable
Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration
| ||||||
Gitana / 4.0 / Data Engine / Content Models / ScriptsScripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/
Score: 1.2795184
|