Found 320 results for "docs fields control"
The search executed in 0.002087237 seconds. That's fast.
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 1.9603487
|
|
Gitana / 3.2 / Guide / Guide / API / PaginationPagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver
Score: 1.9537967
|
|
Gitana / 4.0 / Data Engine / API / PaginationPagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver
Score: 1.9537967
|
|
Gitana / 4.0 / Forms / API / FunctionsFunctions General Usage The general usage of Alpaca is one where you pass a JSON object into the $.alpaca method to inspire the rendering of your form. The general usage follows a structure like this: $("#id").alpaca({ "data": {}, "schema": {}, "options": {}, "postRender": function(control) { } }); This will use the information provided by schema and options to render a form containing data into the DOM element with ID id. Once the form has finished rendering, the postRender
Score: 1.9494652
|
|
Gitana / 4.0 / Forms / Fields / Upload FieldUpload Field The upload field provides a mechanism that enables end users to upload one or more files to a server endpoint and have references to those files stored in the JSON of your form. For example, you may have an array of files in your JSON consisting of filenames to assets that are uploaded to your server - something like: { "title": "My Files", "files": [{ "filename": "/folder1/folder2/file3.jpg" }, { "filename": "/folder1/folder2/file4.pdf" }] } This fi
Score: 1.9336089
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / AndAnd This section describes features that are coming in 4.0 The and condition lets you perform a logical AND operation across multiple sub-conditions. Configuration { "type": "and", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products so long as it is of type my:article. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["co
Score: 1.8819509
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / FeatureFeature 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.8819509
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 1.8819509
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ
Score: 1.8819509
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / OrOr This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c
Score: 1.8819509
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / PathPath 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.8819509
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / AndAnd This section describes features that are coming in 4.0 The and condition lets you perform a logical AND operation across multiple sub-conditions. Configuration { "type": "and", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products so long as it is of type my:article. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["co
Score: 1.8819509
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / FeatureFeature 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.8819509
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 1.8819509
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ
Score: 1.8819509
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / OrOr This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c
Score: 1.8819509
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / PathPath 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.8819509
|
|
Gitana / 4.0 / Forms / Fields / Integer FieldInteger Field The integer field. Properties Title Integer Description Image Field Type integer Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attributes that will be added as DOM attri
Score: 1.8776388
|
|
Gitana / 4.0 / Forms / Fields / Zip Code FieldZip Code Field The zipcode field. Properties Title ZIP Code Description Provides a five or nine-digital US zipcode control with validation Field Type zipcode Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a k
Score: 1.8776388
|
|
Gitana / 4.0 / Forms / API / Conditional DependenciesConditional Dependencies Alpaca extends JSON Schema's dependencies capabilities by allowing you to define conditional dependencies where dependencies are only valid based on conditional value matches with other fields. This lets you get more precise with your dependency management. If you want to go further and wire together completely custom form inter-dependencies that have little or nothing to do with the underlying JSON Schema definition, take a look at Alpaca's support for observables and e
Score: 1.8702874
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Container HooksContainer Hooks This page describes the configuration of HTTP hooks that can be wired into your container orchestration framework to facilitate container lifecycle events (such as shutdown). Lifecycle Hooks Your container orchestration framework likely supports the ability to signal a running API container when one of the following occurs: A container has finished starting up. A container is about to be shut down. In the Kubernetes world, there are two lifecycle hooks (postStart and preStop). Th
Score: 1.8676767
|
|
Gitana / 4.0 / Forms / API / LookupsLookups Alpaca provides abstractions for forms, fields, connectors and other types so as to provide a consistent and easy-to-use interface. This interface lets you find other objects in the JSON structure and plug in function handlers that make decisions by drawing from values of other fields. Every field that renders fundamentally receives an ID. The ID is a dynamically assigned value of no particular significance other than that it is unique. Typically, it is something like alpaca123. Each fie
Score: 1.8552501
|
|
Gitana / 4.0 / Forms / Fields / Token FieldToken Field The token field. This provides an implementation of the Bootstrap TokenField plugin on top of a text field to allow for autocomplete and typeahead tokens in a comma (or alternative separator) delimited string. For full documentation on the options available for the Bootstrap Tokenfield plugin, see: http://sliptree.github.io/bootstrap-tokenfield For full documentation on the options available for the Twitter Bloodhound Suggestion engine, see: https://github.com/twitter/typeahead.js/bl
Score: 1.8290609
|
|
Gitana / 4.0 / Forms / Fields / Any FieldAny Field The any field. Properties Title Any Description Any field. Field Type any Base Field Type control Schema Property Type Default Description enum array List of specific values for this property Options Property Type Default Description name string Field Name. showMapOnLoad boolean sort function Defines an f(a,b) sort function for the array of enumerated values [{text, value}]. This is used to sort enum and optionLabels as well as results that come back from any data sources (for select a
Score: 1.8097806
|
|
Gitana / 4.0 / Forms / Fields / Email FieldEmail Field The email field. Properties Title Email Description Email Field Type email Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attributes that will be added as DOM attribuets fo
Score: 1.7955859
|