Found 246 results for "docs fields editor"
The search executed in 0.001955076 seconds. That's fast.
How do I run custom validation before something is deleted?Cloud CMS provides several ways to run validation ahead of deletion. There are many use cases where this employed - such as: Preventing an Image from being deleted when it is being referenced by a live Web Page Preventing a required sub-object from being deleted Preventing something from deleted when one or more other things are referencing it or depend on it in some way Here are a few approaches which are commonly used: ## Content Model Dependencies We implement link validation via the graph. S
Score: 0.85028887
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / ScriptsScripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/
Score: 0.8246598
|
|
Gitana / 4.0 / Data Engine / Content Models / ScriptsScripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/
Score: 0.8246598
|
|
Users, Identities and SSO with Cloud CMSOne of the really interesting use cases for Cloud CMS is that of maintaining users across multiple domains while having those users share a common identity context. A common identity context allows an authentication session to transition seamlessly (via an authentication swap) from one user to the next. It also allows for properties (such as username, email, password or other custom user properties) to automatically synchronize across all of the user identities that are part of the context. Here
Score: 0.7772536
|
|
Gitana / 3.2 / Guide / Guide / Cookbooks / Go CookbookGo Cookbook Getting Started To get started with the Go driver, visit the Github Page or Package Page to view the source code, tests and basic usage examples. You can install the driver via the command line: go get github.com/gitana/cloudcms-go-driver Connecting to Cloud CMS There are two ways to connect with the Go driver: By finding a gitana.json file in your working directory, or by providing a config configuration. // Connect to CloudCMS using gitana.json in working directory session, err :=
Score: 0.74524736
|
|
Gitana / 4.0 / Developers / Cookbooks / Go CookbookGo Cookbook Getting Started To get started with the Go driver, visit the Github Page or Package Page to view the source code, tests and basic usage examples. You can install the driver via the command line: go get github.com/gitana/cloudcms-go-driver Connecting to Gitana There are two ways to connect with the Go driver: By finding a gitana.json file in your working directory, or by providing a config configuration. // Connect to Gitana using gitana.json in working directory session, err := clou
Score: 0.74524736
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / RegistrationRegistration Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} The minimum registration flow looks like this: The application collects the user's email The application creates an Registration object. It stores t
Score: 0.72526395
|
|
Gitana / 3.2 / Guide / Guide / Applications / Public Services / Registration FlowRegistration Flow One of the more frequent flows that an application must achieve is that of registering a user. Cloud CMS already provides registration support. The application service convenience method shown below make it a little easier to register users for your web application by letting you predefine: The Custom Domain Name where new users will be created. The Email Provider to be used to send emails to new users. The Registrar where new tenants will be created (optional). The Domain User
Score: 0.72526395
|
|
Gitana / 4.0 / Data Engine / API / Data Types / RegistrationRegistration Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} The minimum registration flow looks like this: The application collects the user's email The application creates an Registration object. It stores t
Score: 0.72526395
|
|
Gitana / 4.0 / Data Engine / Platform / Applications / Public Services / Registration FlowRegistration Flow One of the more frequent flows that an application must achieve is that of registering a user. Cloud CMS already provides registration support. The application service convenience method shown below make it a little easier to register users for your web application by letting you predefine: The Custom Domain Name where new users will be created. The Email Provider to be used to send emails to new users. The Registrar where new tenants will be created (optional). The Domain User
Score: 0.72526395
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / Authentication GrantAuthentication Grant Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au
Score: 0.7157726
|
|
Gitana / 4.0 / Data Engine / API / Data Types / Authentication GrantAuthentication Grant Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au
Score: 0.7157726
|
|
Product Releases - GitanaProduct Releases - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and c
Score: 0.6448271
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / ContextsContexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi
Score: 0.6398537
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / ClientClient Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Configuration Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you t
Score: 0.6398537
|
|
Gitana / 4.0 / Developers / User Interface Customization / ContextsContexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi
Score: 0.6398537
|
|
Gitana / 4.0 / Data Engine / API / Data Types / ClientClient Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Configuration Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you t
Score: 0.6398537
|
|
Gitana / 3.2 / Guide / Guide / WorkflowWorkflow In explaining workflow, let's first take a look at the following things: Workflow Models Workflow Instances Workflow Tasks Workflow Payload Resources Workflow Comments Workflow History Item Workflow Events Workflow Event Handlers A workflow model is a definition of a workflow consisting of a full set of instructions on how content should be routed between participants or activities on its way toward completion. A workflow model is kind of like a blueprint describing the sequence of step
Score: 0.63479316
|
|
Gitana / 4.0 / Data Engine / Workflow / OverviewWorkflow In explaining workflow, let's first take a look at the following things: Workflow Models Workflow Instances Workflow Tasks Workflow Payload Resources Workflow Comments Workflow History Item Workflow Events Workflow Event Handlers A workflow model is a definition of a workflow consisting of a full set of instructions on how content should be routed between participants or activities on its way toward completion. A workflow model is kind of like a blueprint describing the sequence of step
Score: 0.63479316
|
|
Gitana / 3.2 / Guide / Guide / User Interface / ReleasesReleases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab
Score: 0.59759736
|
|
Gitana / 4.0 / Forms / API / ViewsViews When Alpaca runs, the very first thing it does is sort out which view implementation it will use to render the schema and options that you provide. A view implementation consists of an ID and an implementation class. The implementation class serves as a reference object that Alpaca uses to determine things along the way such as: which template to render for a given form, container or control type what CSS classes to inject into rendered elements what callback behaviors to run against rende
Score: 0.59759736
|
|
Gitana / 4.0 / User Interface / User Interface / ReleasesReleases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab
Score: 0.59759736
|
|
Gitana / 3.2 / Guide / Guide / Command Line / Transfer CommandsTransfer Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: export content from Cloud CMS as an Archive import content into new Cloud CMS environments using that Archive Archives consist of ZIP files that store a full capture of the exported content. Archives may consist of an entire snapshot export or they may be partial (spanning date ranges or changeset ranges in the case of Repositories). The Cloud CMS Transfer Services make
Score: 0.597383
|
|
Gitana / 4.0 / Developers / Command Line Interface / Transfer CommandsTransfer Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: export content from Cloud CMS as an Archive import content into new Cloud CMS environments using that Archive Archives consist of ZIP files that store a full capture of the exported content. Archives may consist of an entire snapshot export or they may be partial (spanning date ranges or changeset ranges in the case of Repositories). The Cloud CMS Transfer Services make
Score: 0.597383
|
|
Gitana / 3.2 / Guide / Guide / Cookbooks / JavaScript 2.0 CookbookJavaScript 2.0 Cookbook Getting Started To get started with the JavaScript driver, please visit the Gitana JavaScript 2.0 Driver Page. This JavaScript driver, in contrast to the Gitana JavaScript 1.0 Driver, fully supports ECMAScript promises, which makes it easier to seamlessly integrate with your javascript apps. Connecting to Cloud CMS You can connect and then use this driver in three different but equivalent ways: Async / Await Promises Callbacks Async / Await const cloudcms = require("cloud
Score: 0.56057656
|