Found 505 results for "docs fields json"
The search executed in 0.001570699 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Content Model Builder / Create A New Content TypeCreate A New Content Type In the Content Model Builder, you can create a new Content Type. Click button "Create Content Type" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and the new content model will open in the Content Model Builder: As you can see there are two tabs -- "UI" and "JSON". Cloud CMS provides you with two ways to build in the content type builder. If you are an editor and fancy building it with simple actions like drag and drop, UI build
Score: 1.1415591
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Content Model Builder / Create A New Content TypeCreate A New Content Type In the Content Model Builder, you can create a new Content Type. Click button "Create Content Type" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and the new content model will open in the Content Model Builder: As you can see there are two tabs -- "UI" and "JSON". Cloud CMS provides you with two ways to build in the content type builder. If you are an editor and fancy building it with simple actions like drag and drop, UI build
Score: 1.1415591
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Definitions / Content Type DefinitionContent Type Definition A content type defines a type of content that your content workers generally create, edit and publish. For example, an article or a press release might be considered to be a content type. The content type defines the schema, properties, behaviors and everything to do with a specific kind of content. You then set about creating instances of that content type. These are sometimes referred to as content instances. Instances are instantiations of a type. All content instances
Score: 1.1324965
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Definitions / Content Type DefinitionContent Type Definition A content type defines a type of content that your content workers generally create, edit and publish. For example, an article or a press release might be considered to be a content type. The content type defines the schema, properties, behaviors and everything to do with a specific kind of content. You then set about creating instances of that content type. These are sometimes referred to as content instances. Instances are instantiations of a type. All content instances
Score: 1.1324965
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-associations-list-item-actionscontent-model-associations-list-item-actions [ { "config": { "content-model-associations-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/associations/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/associations/{{_qname}}/json", "iconClass": "fa fa-code" }, { "
Score: 1.1165828
|
|
|
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: 1.1165828
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-types-list-item-actionscontent-model-types-list-item-actions [ { "config": { "content-model-types-list-item-actions": [ { "key": "edit-properties", "link": "/#/projects/{{project._doc}}/model/types/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/types/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-instances",
Score: 1.1165828
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-associations-list-item-actionscontent-model-associations-list-item-actions [ { "config": { "content-model-associations-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/associations/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/associations/{{_qname}}/json", "iconClass": "fa fa-code" }, { "
Score: 1.1165828
|
|
|
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: 1.1165828
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-types-list-item-actionscontent-model-types-list-item-actions [ { "config": { "content-model-types-list-item-actions": [ { "key": "edit-properties", "link": "/#/projects/{{project._doc}}/model/types/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/types/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-instances",
Score: 1.1165828
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Definitions / Feature DefinitionFeature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO
Score: 1.1118519
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Definitions / Feature DefinitionFeature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO
Score: 1.1118519
|
|
|
Gitana / 4.0 / Forms / API / Data SourcesData Sources Alpaca supports lazy loading of data from remote locations via data sources. Data sources are supported by a limited number of field types - including select, radio and checkbox fields. To use a data source, specify the dataSource option for your field. The dataSource option can be any of the following: a set of datasource array elements directly supplied or a list of text items that will be converted to a data source array. an object consisting of key/value pairs to be used to gene
Score: 1.1113641
|
|
|
Gitana / 4.0 / Forms / Fields / Country FieldCountry Field The country field. Properties Title Country Description Provides a dropdown selector of countries keyed by their ISO3 code. The names of the countries are read from the I18N bundle for the current locale. Field Type country Base Field Type select Schema Property Type Default Description enum array List of field value options Options Property Type Default Description allowDefaultNoneSelected boolean This is used for required fields, where by default no "None" option is available. En
Score: 1.1113641
|
|
|
Gitana / 3.2 / Guide / Guide / Branches / ActionsActions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat
Score: 1.1086717
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / ReferencesReferences Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally
Score: 1.1086717
|
|
|
Gitana / 4.0 / Data Engine / Branches / ActionsActions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat
Score: 1.1086717
|
|
|
Gitana / 4.0 / Forms / CMS / ReferencesReferences Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally
Score: 1.1086717
|
|
|
Gitana / 4.0 / Developers / Frameworks / cURLcURL Guide and References for connectivity to Cloud CMS Connecting to Cloud CMS From a command prompt, the curl command can be used to execute API calls to Cloud CMS. Connecting to the Cloud CMS API requires API Keys from your Cloud CMS project. This is done by default for the sample project. You can find these by going to Manage Project and clicking API Keys in the left hand menu. Several examples of using curl are available in our Gitana SDK For example, reading a node can be done with the fol
Score: 1.0989566
|
|
Advanced Content Modeling options (example)Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem
Score: 1.0957091
|
|
|
Gitana / 3.2 / Guide / Guide / Features / Deployment ConfigDeployment Config QName: f:deployment-config The Deployment Config feature lets you describe settings that should be considered by one or more Deployment Handlers during deployment. These settings may describe things such as a mappings of deployed content to file system paths. When a node is deployed, if it has the f:deployment-config feature on it, then that feature may instruct the Deployment Handler about how to deploy. Configuration The f:deployment-config feature is utilized by the followin
Score: 1.0937698
|
|
|
Gitana / 4.0 / Data Engine / Aspects / Deployment ConfigDeployment Config QName: f:deployment-config The Deployment Config feature lets you describe settings that should be considered by one or more Deployment Handlers during deployment. These settings may describe things such as a mappings of deployed content to file system paths. When a node is deployed, if it has the f:deployment-config feature on it, then that feature may instruct the Deployment Handler about how to deploy. Configuration The f:deployment-config feature is utilized by the followin
Score: 1.0937698
|
|
|
Gitana / 3.2 / Guide / Guide / Actions / Web HookWeb 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.0915618
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Web HookWeb 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.0915618
|
|
|
Gitana / 3.2 / Guide / Guide / 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.0894103
|