Found 235 results for "features geolocation"
The search executed in 0.001528616 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / FeaturesFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 18.67846
|
![]() |
Gitana / 4.0 / Data Engine / Aspects / OverviewFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 12.672797
|
![]() |
Gitana / 3.2 / Guide / Guide / Features / GeolocationGeolocation QName: f:geolocation Indicates that this node supports geolocation properties. This feature provisions the node with a loc property that contains two sub-properties - lat and long. { "properties": { "loc": { "type": "object", "title": "Geolocation Details", "properties": { "lat": { "type":"number", "title": "Latitude", "minimum": -180, "maxim
Score: 10.813244
|
![]() |
Gitana / 4.0 / Data Engine / Aspects / GeolocationGeolocation QName: f:geolocation Indicates that this node supports geolocation properties. This feature provisions the node with a loc property that contains two sub-properties - lat and long. { "properties": { "loc": { "type": "object", "title": "Geolocation Details", "properties": { "lat": { "type":"number", "title": "Latitude", "minimum": -180, "maxim
Score: 10.813244
|
![]() |
Gitana / 3.2 / Guide / Guide / General / Geolocation ServicesGeolocation Services Cloud CMS provides geolocation information look up services that can be used to determine geographic information for a given IP address or set of coordinates. In many places, Cloud CMS automatically utilizes these geolocation services for you. In places where geolocation information is stored on your content instances, geolocation data can automatically be looked up and applied using Cloud CMS features. In addition, you can invoke the API directly to look up geolocation info
Score: 10.704097
|
![]() |
Gitana / 4.0 / Data Engine / General / Geolocation ServicesGeolocation Services Cloud CMS provides geolocation information look up services that can be used to determine geographic information for a given IP address or set of coordinates. In many places, Cloud CMS automatically utilizes these geolocation services for you. In places where geolocation information is stored on your content instances, geolocation data can automatically be looked up and applied using Cloud CMS features. In addition, you can invoke the API directly to look up geolocation info
Score: 10.704097
|
![]() |
Gitana / 3.2 / Guide / Guide / Content ModelingContent Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste
Score: 9.172916
|
![]() |
Gitana / 4.0 / Data Engine / Content Models / OverviewContent Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste
Score: 9.172916
|
![]() |
Gitana / 4.0 / Data Engine / Content Models / Default PathsDefault Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":
Score: 7.9690475
|
![]() |
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: 6.630544
|
![]() |
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: 6.630544
|
![]() |
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Add Features
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 6.6195745
|
![]() |
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Add Features
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 6.6195745
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-features-list-item-actionscontent-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i
Score: 4.4082937
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-features-list-item-actionscontent-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i
Score: 4.4082937
|
![]() |
Gitana / 3.2 / Guide / Guide / Content Modeling / Default PathsDefault Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":
Score: 3.509128
|
![]() |
Gitana / 4.0 / Data Engine / General / OverviewGeneral Custom Domain Name Geolocation Services
Score: 3.4742079
|
![]() |
Gitana / 3.2 / Guide / Guide / GeneralGeneral Custom Domain Name Data Lists Geolocation Services Locking
Score: 3.4580886
|
![]() |
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @expand@expand Fetches a list of content instance by first extracting a set of node id values from properties of a node. Useful when using _relators in a parent node and you wish to load all the resulting associated nodes in a single Dust tag. Parameters parameter required description list lost of nodes key JSON "path" to the property containing the ID of the record to fetch type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1
Score: 2.5742598
|
![]() |
Gitana / 4.0 / Developers / Application Server / Tags / @expand@expand Fetches a list of content instance by first extracting a set of node id values from properties of a node. Useful when using _relators in a parent node and you wish to load all the resulting associated nodes in a single Dust tag. Parameters parameter required description list lost of nodes key JSON "path" to the property containing the ID of the record to fetch type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1
Score: 2.5742598
|
![]() |
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @queryOne@queryOne Supports all of the same mechanics as the @query tag but keeps only the first result. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relativ
Score: 2.4394531
|
![]() |
Gitana / 4.0 / Developers / Application Server / Tags / @queryOne@queryOne Supports all of the same mechanics as the @query tag but keeps only the first result. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relativ
Score: 2.4394531
|
![]() |
Gitana / 4.0 / Forms / Fields / Number FieldNumber Field The number field. Properties Title Number Description Number field Field Type number 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 at
Score: 2.140535
|
![]() |
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @query@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr
Score: 2.0169616
|
![]() |
Gitana / 4.0 / Developers / Application Server / Tags / @query@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr
Score: 2.0169616
|