Found 1151 results for "access-policies conditions and"
The search executed in 0.001579956 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / API ClusterAPI Cluster The api-cluster kit defines the following services: ui api1 api2 apilb mongodb elasticsearch This kit differs from the quickstart in how it handles API requests. Requests are sent to the apilb container which runs a load balancer, distributing work between api1 and api2. It is worth reviewing the cluster settings for both of your api servers in order for them to correctly communicate. Running Use the following commands: docker-compose build --force-rm docker-compose up And then open
Score: 0.29861534
|
|||||||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / EmailEmail 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
Score: 0.29861534
|
|||||||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 4.0 / Data Engine / Aspects / 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
Files The Cloud CMS Bulk Import tool makes it easy to import content from a file system into a Cloud CMS content repository. Let's imagine that you have some images sitting in an images directory. You wish to ingest these into Cloud CMS as part of an Image Library application. The image directory might look like this: images\
chunio.jpg
disney.jpg
pavlov.jpg
These images are just files on disk. They could be any file type, really. Cloud CMS can ingest files of any format including p
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
Getting started with Cloud CMS for a website takes minimal setup: Fork a copy of https://github.com/gitana/sdk Note the URL of your repo; you’ll need this later… Login to your tenant or signup for a trial of Cloud CMS When prompted upon login create a Web Content Management starter project From the resulting Project Dashboard navigate to “Applications” in Manage Project Select “Sample Web Application” > Deployments Tick the radio button on the right Navigate to Selected > Undeploy (upper right)
context-document-has-feature If a Document is currently being observed and has a specific feature. {
"evaluator": "context-document-has-feature",
"condition": "{featureId}"
}
Example: {
"evaluator": "context-document-has-feature",
"condition": "f:audit"
}
context-document-has-qname If a Document is currently being observed and has a specific QName. {
"evaluator": "context-document-has-qname",
"condition": "{qname}"
}
Example: {
"evaluator": "context-document-has-qname",
"condition": "o:abcdef123456"
}
context-document-has-type If a Document is currently being observed and has a specific Type. {
"evaluator": "context-document-has-type",
"condition": "{type}"
}
Example: {
"evaluator": "context-document-has-type",
"condition": "my:article"
}
context-document-has-feature If a Document is currently being observed and has a specific feature. {
"evaluator": "context-document-has-feature",
"condition": "{featureId}"
}
Example: {
"evaluator": "context-document-has-feature",
"condition": "f:audit"
}
context-document-has-qname If a Document is currently being observed and has a specific QName. {
"evaluator": "context-document-has-qname",
"condition": "{qname}"
}
Example: {
"evaluator": "context-document-has-qname",
"condition": "o:abcdef123456"
}
context-document-has-type If a Document is currently being observed and has a specific Type. {
"evaluator": "context-document-has-type",
"condition": "{type}"
}
Example: {
"evaluator": "context-document-has-type",
"condition": "my:article"
}
Python Cookbook Getting Started To get started with the Python driver, visit Gitana Python Driver Page or the Github Page. It is written with Python 3 and can be used in any compatible project. You can install the driver via the command line: pip install cloudcms
or
pip3 install cloudcms
Or add something like this to your requirements.txt: cloudcms==1.1.0
Connecting to Gitana You can connect to Gitana by providing a config file or the oauth variables directly. Using a Gitana JSON file You ca
Python Cookbook Getting Started To get started with the Python driver, visit Gitana Python Driver Page or the Github Page. It is written with Python 3 and can be used in any compatible project. You can install the driver via the command line: pip install cloudcms
or
pip3 install cloudcms
Or add something like this to your requirements.txt: cloudcms==1.1.0
Connecting to Gitana You can connect to Gitana by providing a config file or the oauth variables directly. Using a Gitana JSON file You ca
Ad hoc Approval with Email Template Here is a variation of the Ad hoc Approval workflow where we set up some Email Templates to use in sending emails to the participants in the workflow. See the Ad hoc Approval Workflow article for a basic understanding of how this workflow model works. Here is the modified workflow model that we'll use: {
"id": "sample:adhoc",
"title": "Sample Adhoc Approval (with Email Template)",
"nodes": {
"start": {
"type": "start",
Ad hoc Approval with Email Template Here is a variation of the Ad hoc Approval workflow where we set up some Email Templates to use in sending emails to the participants in the workflow. See the Ad hoc Approval Workflow article for a basic understanding of how this workflow model works. Here is the modified workflow model that we'll use: {
"id": "sample:adhoc",
"title": "Sample Adhoc Approval (with Email Template)",
"nodes": {
"start": {
"type": "start",
10. Fortune Cookie 9. Weight Loss Tips 8. Cheese Cake Receipt 7. Photo Album 6. Organization Chart 5. User Reviews 4. PDF Preview 3. Food Web 2. LOTR Social Graph 1. Touch and Play
Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has
Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has
@form A form can be rendered from Cloud CMS by identifying the definition and form key. Forms are rendered on the client-side using Alpaca Forms. For a working example, see: https://github.com/gitana/sdk/tree/master/app-server/appserver-form-sample Parameters parameter required description definition yes the type definition QName form yes the form key list no the data list to populate successUrl no the URL to redirect to upon success failureUrl no the URL to redirect to upon failure formId no ov
@form A form can be rendered from Cloud CMS by identifying the definition and form key. Forms are rendered on the client-side using Alpaca Forms. For a working example, see: https://github.com/gitana/sdk/tree/master/app-server/appserver-form-sample Parameters parameter required description definition yes the type definition QName form yes the form key list no the data list to populate successUrl no the URL to redirect to upon success failureUrl no the URL to redirect to upon failure formId no ov
The Cloud CMS REST API allows for elasticsearch queries against a branch. The API endpoint is POST /repositories/{repositoryId}/branches/{branchId}/nodes/search The payload is a JSON object containing a top-level property called "search" which wraps the elasticsearch DSL query. The JavaScript driver exposes this call on the Branch object using the searchNodes() methods. Examples: 1) Search for nodes containing the keyword "hello" in any property: req.branch(function (err, branch) { branch.trap(f
PHP Cookbook Getting Started To get started with the PHP driver, visit Gitana PHP Driver Page or the Github Page. It can be used in any composer php project. To install with composer from the command line: composer require cloudcms/cloudcms
Connecting to Gitana You can connect to Gitana with the php driver by providing a config array containing your keys, which can be obtained from a gitana.json file. It should look something like: {
"clientKey": "{your client key}",
"clientSecret": "{y
PHP Cookbook Getting Started To get started with the PHP driver, visit Gitana PHP Driver Page or the Github Page. It can be used in any composer php project. To install with composer from the command line: composer require cloudcms/cloudcms
Connecting to Gitana You can connect to Gitana with the php driver by providing a config array containing your keys, which can be obtained from a gitana.json file. It should look something like: {
"clientKey": "{your client key}",
"clientSecret": "{y
C# Cookbook Getting Started To get started with the C# driver, visit Gitana C# Driver Page or the Github Page. It is written with .NET Core and can be used in any compatible project. You can install the driver via the command line: dotnet add package cloudcms
or from within Visual Studio: Install-Package cloudcms
Or by adding this to your .csproj file (you may have to adjust the version): |
