Found 505 results for "docs fields json"
The search executed in 0.002193033 seconds. That's fast.
Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fieldsdocuments-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },
Score: 5.5827837
|
|
Gitana / 3.2 / Guide / Guide / Cookbooks / Content Modeling CookbookContent Modeling Cookbook Getting Started To get started with Content Modeling, please visit the Content Modeling Page. Code Samples Here are some code samples of common data structures to help you get started. Array of strings An array of strings. Definition: "prop1": { "type": "array", "items": { "type": "string" } } Form: "prop1": { "type": "array", "items": { "type": "text" } } An Object An object with two properties. Definition: "articleAvailability
Score: 4.881765
|
|
How to limit the fields that come back in a queryQuery API calls like http://api.cloudcms.com/docs#!/node/post_repositories_repositoryId_branches_branchId_nodes_query support a parameter named _fields which defines an object specifying the node properties you want to include in the result set for matching nodes. For example in the following query I want the title, subTitle and slug fields returned: { "_type":"my:article", "_fields":{ "title":1, "subTitle":1, "slug":1 } } The result set would look something like the
Score: 4.4846106
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / ReferencesReferences References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la
Score: 3.825622
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Consumer of all ContentConsumer of all Content This section describes features that are coming in 4.0 JSON { "title": "Consumer of all Content", "statements": [{ "action": "grant", "roles": ["consumer"] }] }
Score: 3.4765058
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Consumer of all ContentConsumer of all Content This section describes features that are coming in 4.0 JSON { "title": "Consumer of all Content", "statements": [{ "action": "grant", "roles": ["consumer"] }] }
Score: 3.4765058
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Editor of all Content in SpanishEditor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }
Score: 3.4585278
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Editor of all Content in SpanishEditor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }
Score: 3.4585278
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Manager of all Content in a FolderManager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }
Score: 3.4526765
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Manager of all Content in a FolderManager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }
Score: 3.4526765
|
|
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.3713017
|
|
Is there a programmatic way to add more content to workflows?There is a programmatic way to add more content to workflows once they're in-flight. However, once the workflow is in-flight, the workflow process instance isn't the correct place to add things. Instead, you'd want to add new content to a workflow task. Essentially, a workflow is made up of a series of tasks. When the workflow transitions from one node to another in the workflow model, it instantiates a new task and the task holds the state (and references to documents) for that phase of the wor
Score: 3.3650582
|
|
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: 3.0108387
|
|
REST based access callsThe authentication mechanism in Cloud CMS is OAuth 2.0. While you can use any of the flows, the easiest one to begin with is "password". We've outlined a basic example here using Advanced REST Client to show our API-first platform in action. First, from your Cloud CMS platform home page, navigate to "Manage Platform" and select the "API Keys" section to list all available projects for remote access: If you have no keys for your project then create a new "Application" from "Manage Platform" and t
Score: 2.9988797
|
|
How to Retrieve content by their document library pathYou can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo
Score: 2.9811773
|
|
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: 2.926595
|
|
Gitana / 4.0 / Forms / API / CallbacksCallbacks 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: 2.902632
|
|
Gitana / 4.0 / Getting Started / Working with Content / FormsForms Cloud CMS provides a forms engine that instantly renders user interface forms on top of your content models. As your content models change, forms are automatically updated to provide an intuitive and easy-to-use editorial experience. Forms automatically calibrate for the most common web controls including text, numbers, text areas, drop downs, radio buttons, checkbox elements and nested fields (arrays, sub-objects). Cloud CMS integrates the powerful, open-source Alpaca.js Forms Engine so t
Score: 2.8586898
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / Web FormsWeb Forms Cloud CMS provides an forms engine that instantly renders user interface forms on top of your content models. As your content models change, forms are automatically updated to provide an intuitive and easy-to-use editorial experience. Forms automatically calibrate for the most common web controls including text, numbers, text areas, drop downs, radio buttons, checkbox elements and nested fields (arrays, sub-objects). Cloud CMS integrates the powerful, open-source Alpaca.js Forms Engine
Score: 2.840684
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Embed Media In CKEditor / Advanced Usages / Extra AttributesExtra Attributes In addition to common attributes like width, height and id, you might need extra attributes for your embedded media HTML tag. For example, you probably hope to have attributes like title and creator: CloudCMS allows you to add extra attributes that best suit your need with some simple configurations. Add JSON Configurations for Extra Attributes Navigate to Manage Project --> Editors --> Embedded Media Editor. Check Enable Additional Attributes and two JSON editors will pop up. W
Score: 2.7979455
|
|
Gitana / 4.0 / User Interface / Embedded Media / Advanced Usages / Extra AttributesExtra Attributes In addition to common attributes like width, height and id, you might need extra attributes for your embedded media HTML tag. For example, you probably hope to have attributes like title and creator: CloudCMS allows you to add extra attributes that best suit your need with some simple configurations. Add JSON Configurations for Extra Attributes Navigate to Manage Project --> Editors --> Embedded Media Editor. Check Enable Additional Attributes and two JSON editors will pop up. W
Score: 2.7979455
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / dataview-subcontextdataview-subcontext [ { "evaluator": "context-dataview", "config": { "dataview-subcontext": { "items": [ { "key": "dataview", "title": "Data View", "header": true, "order": 1000, "items": [ { "key": "dataview/view", "title": "View", "uri": "#/projects/{projectId}/dataviews/{reportId}", "order": 100 },
Score: 2.7973273
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / dataview-subcontextdataview-subcontext [ { "evaluator": "context-dataview", "config": { "dataview-subcontext": { "items": [ { "key": "dataview", "title": "Data View", "header": true, "order": 1000, "items": [ { "key": "dataview/view", "title": "View", "uri": "#/projects/{projectId}/dataviews/{reportId}", "order": 100 },
Score: 2.7973273
|
|
Gitana / 4.0 / Forms / API / Recursive ReferencesRecursive References Alpaca tracks references when looking up schema and options information so as to avoid circular loops. A circular loop happens when a child schema points back to a parent schema. If the reference is a hard reference (meaning that Alpaca must resolve a schema before it can proceed with rendering), then process of resolving the total document schema will never complete. One example of a circular reference might be a box object with a property called contains. The contains prop
Score: 2.7897139
|
|
Gitana / 4.0 / Forms / API / DependenciesDependencies JSON Schema provides support for dependencies as a means for describing dependencies between fields. Using dependencies, you can establish that property2 should be supplied when property1 is supplied. Alpaca supports both JSON Schema v3 and v4 syntax for declaring dependencies. We recommend using JSON Schema v4 syntax. In JSON Schema v4, a single dependencies block within the container object stores key/values which consist of the ID of the property (key) and an array of property ID
Score: 2.7790132
|