Found 561 results for "gitana 4.0 forms api templates-example3-control-text"

The search executed in 0.002464208 seconds. That's fast.

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Data Store

Data Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val

Score: 1.8861998

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Feature

Feature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],

Score: 1.8861998

Can your CMS do this?

This is not going to be a list of features in Cloud CMS, that to be honest, you righfully expect in a CMS: API, versioning, workflow, Content model, Content entry forms,.. For a bit of fun, I started thinking “what really makes Cloud CMS better than your CMS” embracing my school boy mentality. 1. SaaS and/or On-Premise Cloud CMS is avaible as a SaaS product and OnPremise. Docker containers have allowed us to distribute the Cloud CMS product easily for On-Premise/Private Cloud installation. Whils

Score: 1.8837156

Gitana / 3.2 / Guide / Guide / User Interface / Security / Add a User to a Project

Add a User to a Project Option 1: Create User in the Tenant At Platform level, select 'Member' (left nav) and '+Create User' - Enter the values on the forms and 'Save'. Result: User is now created. Note: The new user will not be able to see any projects when they login the new user will be seen in the Tenant members list and will be available to be added as an 'existing user' to any project Second Step is to add the user to a Project Select Members (left Nav) -> add existing user. - select the u

Score: 1.865685

Gitana / 4.0 / User Interface / Security / Add a User to a Project

Add a User to a Project Option 1: Create User in the Tenant At Platform level, select 'Member' (left nav) and '+Create User' - Enter the values on the forms and 'Save'. Result: User is now created. Note: The new user will not be able to see any projects when they login the new user will be seen in the Tenant members list and will be available to be added as an 'existing user' to any project Second Step is to add the user to a Project Select Members (left Nav) -> add existing user. - select the u

Score: 1.865685

Gitana / 4.0 / Forms / API / Callbacks

Callbacks Alpaca provides several places where you can hook in callbacks. Events - events are raised when the user interacts with fields. You can register callbacks to handle these events, adjust field state or other operations. Observables - each field maintains an observable that you can subscribe to. Subscribing to an observable means that you're listening for changes to its value. You can also use observables to interrogate and find values of fields within namespaces. This lets you find valu

Score: 1.844394

Gitana / 4.0 / Forms / API / Ordering

Ordering The default rendering engine that Alpaca utilizes will render your fields in the order that they are described within your schema. {% raw %} {% endraw %} Use the order option to specify rendering order The precise order of properties can be configured using the order option. {% raw %} {% endraw %} Use a Template to layout fields See Templates for more information on using custom templates to take full control over the layout of your forms.

Score: 1.8308735

Gitana / 4.0 / Data Engine / Overview

Data Engine The Gitana Data Engine provides the foundation on which everything runs. Note Here is a note! Here is a test of an important admonition blocK: Important Be wary of visitors bearing gifts!!

Score: 1.8037801

Gitana / 4.0 / Getting Started / Working with Content / Overview

Working with Content You can put any kind of content into Cloud CMS. Things like desktop files (Word documents, PDF files, images, audio files and video) are no problem. However, the real power of Cloud CMS begins when you begin to model content type definitions and features to wrap around that content. A content type is a type of thing, such as an Article or a Press Release. You define content types in the same way that you might define a word in the dictionary. You give it a name and then you

Score: 1.8032372

Gitana / 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica Set

MongoDB Replica Set The MongoDB Replica Set kit defines an environment with a 3 node MongoDB replica set and two Cloud CMS environments running against it The configuration files for this kit can be found in the Gitana SDK Running Start the mongo servers first and then initialize the cluster: docker login --username {docker-username} --password '{docker-password}' docker-compose up -d mongodb1 mongodb2 mongodb3 Initialize the replic set. only have to do this once since the mongo servers persist

Score: 1.7417736

Gitana / 3.2 / Guide / Guide / User Interface / Projects / Create a Project

Create a Project You can create as many projects as you would like within Cloud CMS. Each project provides a collaborate space for your team. You use this collaboration space to: Work on content together Design your content schema, properties and forms Invite users into teams and assign roles and responsibilities Approve content and make it available on your web site or mobile app And much more. There are multiple ways to create a project. For example, you can: Create a Project from scratch -Cre

Score: 1.7261987

Gitana / 4.0 / Forms / API / References

References This page shows examples of using JSON schema $ref markup to reference definitions and other structures within your JSON schema definition to generate more complex and nested schema documents. The $ref convention used by Alpaca builds on top of JSON schema and allows for the $ref value to identify a URI to a remote resource. It also allows you to point to JSON structures within the current document, enabling re-use. Alpaca extends $ref by allowing for additional loaders such as a dict

Score: 1.7261987

Gitana / 4.0 / User Interface / Projects / Create a Project

Create a Project You can create as many projects as you would like within Cloud CMS. Each project provides a collaborate space for your team. You use this collaboration space to: Work on content together Design your content schema, properties and forms Invite users into teams and assign roles and responsibilities Approve content and make it available on your web site or mobile app And much more. There are multiple ways to create a project. For example, you can: Create a Project from scratch -Cre

Score: 1.7261987

Gitana / 3.2 / Guide / Guide / Content Modeling / Content Model Builder / Extend Field Templates

Extend Field Templates If you find the existing field templates still limited to your need, Modules allow you to add your own field template. In the following sample, we added a field template that provides a Summernote WYSIWYG editor. Default CKEditor WYSIWYG: Customized Summernote WYSIWYG: Get the code here in the SDK: https://github.com/gitana/sdk/tree/master/ui/modules/content-model/content-model-field

Score: 1.719011

Gitana / 4.0 / Data Engine / Content Models / Content Model Builder / Extend Field Templates

Extend Field Templates If you find the existing field templates still limited to your need, Modules allow you to add your own field template. In the following sample, we added a field template that provides a Summernote WYSIWYG editor. Default CKEditor WYSIWYG: Customized Summernote WYSIWYG: Get the code here in the SDK: https://github.com/gitana/sdk/tree/master/ui/modules/content-model/content-model-field

Score: 1.719011

Gitana / 4.0 / User Interface / Overview

User Interface Documentation Welcome to the User Interface Documentation Gitana provides a full user interface that your editorial team and managers use to create, manage and deliver content to the business, applications and web sites. The user interface is secure, role-based and customizable, allowing your development team to cater the editorial experience to the exact needs of end users. Add-ons Embedded Media Modules Projects Security User Interface Workflow

Score: 1.719011

Gitana / 4.0 / Getting Started / Overview

Getting Started Welcome to the Getting Started Guide. In this guide, we walk through some of the high-level concepts and the general ideas of the Gitana Platform. This guide keeps things pretty light. It provides an overview and then lets you dive into other parts of the documentation for greater detail. To start off, select one of the sections below: Working with Content Navigating the User Interface Using your Data Platform Publishing Workflow

Score: 1.7092743

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Path

Path This section describes features that are coming in 4.0 The path condition allows you to constrain a policy statement so that it applies to content nodes that exist at a matching path. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "path", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to all content in the path

Score: 1.6945747

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Reference

Reference This section describes features that are coming in 4.0 The reference condition allows you to constrain a policy statement so that it applies to entities that match a given Reference. This condition supports regular expressions, allowing you to focus in on a single Reference or wildcard expressions within an Reference. In Cloud CMS, a Reference is a string that uniquely locates an item within the system. It takes on a structure that looks like one of the following: {type}://{platformId}

Score: 1.6945747

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Path

Path This section describes features that are coming in 4.0 The path condition allows you to constrain a policy statement so that it applies to content nodes that exist at a matching path. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "path", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to all content in the path

Score: 1.6945747

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Reference

Reference This section describes features that are coming in 4.0 The reference condition allows you to constrain a policy statement so that it applies to entities that match a given Reference. This condition supports regular expressions, allowing you to focus in on a single Reference or wildcard expressions within an Reference. In Cloud CMS, a Reference is a string that uniquely locates an item within the system. It takes on a structure that looks like one of the following: {type}://{platformId}

Score: 1.6945747

Gitana / 4.0 / Getting Started / Working with Content / Versioning

Versioning Cloud CMS provides you with content repositories that are powered by a changeset versioning model. Changeset Versioning It has been around for awhile and has become extremely popular since it enables you to work unimpeded, fully distributed and without any of the headaches of file locking. Changeset Versioning: The Basics lot like a transparency (from the old transparency projector days). This is a see-through sheet of plastic that you write on with one of those Sharpie pens. The proj

Score: 1.6875347

Gitana / 3.2 / Guide / Guide / Actions / Web Hook

Web Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca

Score: 1.6758687

Gitana / 4.0 / Data Engine / Behaviors / Actions / Web Hook

Web Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca

Score: 1.6758687

Gitana / 3.2 / Guide / Guide / API / Data Types / Platform

Platform Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreTypeId

Score: 1.655797