Found 265 results for "branches actions"

The search executed in 0.00479462 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 16.65304

Gitana / 4.0 / Data Engine / Behaviors / Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 16.65304

Gitana / 3.2 / Guide / Guide / Branches

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t

Score: 14.995642

Gitana / 3.2 / Guide / Guide / Workspaces

Workspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th

Score: 11.99375

Gitana / 4.0 / Data Engine / Branches / Workspaces

Workspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th

Score: 11.99375

Gitana / 4.0 / User Interface / User Interface / Version Control

Version Control Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. It is inspired by Git and Mercurial which are popular source-control products within the software development world. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changesets. Transactions span multiple documents and full "units of work" are written into the changeset history w

Score: 10.2851095

Gitana / 3.2 / Guide / Guide / Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule 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 asso

Score: 10.186127

Gitana / 4.0 / Data Engine / Behaviors / Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule 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 asso

Score: 10.186127

Gitana / 4.0 / Getting Started / Working with Content / Branches

Branches Everything you do with content is done within a workspace. When you create content or modify content definitions, it is all done inside of a workspace. Workspaces are isolated from one another so that different teams can make changes to things without stepping on each other's toes. By default, there is a master workspace where everything happens. You can create new workspaces at any time. When you create a workspace, Cloud CMS remembers the point in time when the new workspace was creat

Score: 8.981443

Gitana / 4.0 / Data Engine / Branches / Overview

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t

Score: 7.7567606

Gitana / 3.2 / Guide / Guide / Releases

Releases 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: 7.0375385

Gitana / 4.0 / Data Engine / Releases / Overview

Releases 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: 7.0375385

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / actions

actions [ { "config": { "actions": { "create-content": { "title": "Create a New Content Instance" } } } } ]```

Score: 6.645282

Gitana / 4.0 / Developers / User Interface Customization / Contexts / actions

actions [ { "config": { "actions": { "create-content": { "title": "Create a New Content Instance" } } } } ]```

Score: 6.645282

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions

Actions Cloud CMS provides a large number of actions that can be bound to links sections within configuration blocks. This allows you to customize dropdowns, button toolbars and action links at various places within the user interface. It also provides a way for you to override action implementation classes for your own users. assign_access_policy change-password create_access_policy create_document delete_access_policies new_folder unassign_access_policy

Score: 6.57665

Gitana / 4.0 / Developers / User Interface Customization / Actions

Actions Cloud CMS provides a large number of actions that can be bound to links sections within configuration blocks. This allows you to customize dropdowns, button toolbars and action links at various places within the user interface. It also provides a way for you to override action implementation classes for your own users. assign_access_policy change-password create_access_policy create_document delete_access_policies new_folder unassign_access_policy

Score: 6.57665

Gitana / 3.2 / Guide / Guide / Branches / Actions

Actions 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: 6.5739107

Gitana / 4.0 / Data Engine / Branches / Actions

Actions 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: 6.5739107

Gitana / 3.2 / Guide / Guide / Releases / Actions

Actions 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: 6.460169

Gitana / 4.0 / Data Engine / Releases / Actions

Actions 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: 6.460169

Gitana / 3.2 / Guide / Guide / Scripting / Actions

Actions Properties There are no properties for this class. Methods execute Usage object execute() Arguments None Return Type Description object Examples Change the type of a Node In this example, we fire off the changeType action to change the type of a node to custom:thing. actions.execute("changeType", { "node": node, "type": "custom:thing" });

Score: 6.4574757

Actions

Actions Properties There are no properties for this class. Methods execute Usage object execute() Arguments None Return Type Description object Examples Change the type of a Node In this example, we fire off the changeType action to change the type of a node to custom:thing. actions.execute("changeType", { "node": node, "type": "custom:thing" });

Score: 6.4574757

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / document-actions

document-actions [ { "evaluator": "and", "condition": [ { "evaluator": "not", "condition": { "evaluator": "document-has-feature", "condition": "f:multilingual" } }, { "evaluator": "not", "condition": { "evaluator": "document-has-feature", "condition": "f:translation" } }, { "evaluator": "document-has-feature", "condition": "f:locale" } ], "

Score: 5.8875046

Gitana / 4.0 / Developers / User Interface Customization / Contexts / document-actions

document-actions [ { "evaluator": "and", "condition": [ { "evaluator": "not", "condition": { "evaluator": "document-has-feature", "condition": "f:multilingual" } }, { "evaluator": "not", "condition": { "evaluator": "document-has-feature", "condition": "f:translation" } }, { "evaluator": "document-has-feature", "condition": "f:locale" } ], "

Score: 5.8875046

Gitana / 3.2 / Guide / Guide / User Interface / Version Control

Version Control Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. It is inspired by Git and Mercurial which are popular source-control products within the software development world. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changesets. Transactions span multiple documents and full "units of work" are written into the changeset history w

Score: 5.069655