Found 187 results for "releases actions"
The search executed in 0.001642291 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / ActionsActions 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.605349
|
![]() |
Gitana / 4.0 / Data Engine / Behaviors / ActionsActions 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.605349
|
![]() |
Gitana / 3.2 / Guide / Guide / 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: 15.392597
|
![]() |
Gitana / 3.2 / Guide / Guide / WorkspacesWorkspaces 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: 12.775231
|
![]() |
Gitana / 4.0 / Data Engine / Branches / WorkspacesWorkspaces 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: 12.775231
|
![]() |
Gitana / 3.2 / Guide / Guide / RulesRules 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.148642
|
![]() |
Gitana / 4.0 / Data Engine / Behaviors / RulesRules 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.148642
|
![]() |
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: 10.039483
|
![]() |
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: 10.039483
|
![]() |
Gitana / 4.0 / Data Engine / Releases / OverviewReleases 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: 9.53298
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / releases-contextreleases-context [ { "evaluator": "context-project", "config": { "releases-context": { "items": [ { "key": "project/releases", "title": "Releases", "header": true, "order": 10000, "items": [ { "key": "project/releases/calendar", "title": "Calendar", "uri": "#/projects/{projectId}/releases/calendar", "iconClass": "fa fa-angle-r
Score: 7.4853454
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / releases-contextreleases-context [ { "evaluator": "context-project", "config": { "releases-context": { "items": [ { "key": "project/releases", "title": "Releases", "header": true, "order": 10000, "items": [ { "key": "project/releases/calendar", "title": "Calendar", "uri": "#/projects/{projectId}/releases/calendar", "iconClass": "fa fa-angle-r
Score: 7.4853454
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Samples / Releases Menu ItemReleases Menu Item In Cloud CMS, Releases describes the ability for the product to allow multiple branches to be forked, merged and scheduled for automatically promotion of content to a live environment. It offers scheduled publishing, conflict detection and offers an ideal solution for editors to coordinate the delivery of content in situations where multiple editorial efforts may be running concurrently. When Releases is enabled for a Project, a Releases menu item shows up in the left-hand men
Score: 6.676202
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Samples / Releases Menu ItemReleases Menu Item In Cloud CMS, Releases describes the ability for the product to allow multiple branches to be forked, merged and scheduled for automatically promotion of content to a live environment. It offers scheduled publishing, conflict detection and offers an ideal solution for editors to coordinate the delivery of content in situations where multiple editorial efforts may be running concurrently. When Releases is enabled for a Project, a Releases menu item shows up in the left-hand men
Score: 6.676202
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / actionsactions [ { "config": { "actions": { "create-content": { "title": "Create a New Content Instance" } } } } ]```
Score: 6.6245
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / actionsactions [ { "config": { "actions": { "create-content": { "title": "Create a New Content Instance" } } } } ]```
Score: 6.6245
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / ActionsActions 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.557212
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / ActionsActions 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.557212
|
![]() |
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: 6.555466
|
![]() |
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: 6.555466
|
![]() |
Gitana / 3.2 / Guide / Guide / Releases / 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: 6.4437575
|
![]() |
Gitana / 4.0 / Data Engine / Releases / 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: 6.4437575
|
![]() |
Gitana / 3.2 / Guide / Guide / Scripting / ActionsActions 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.4392014
|
![]() |
ActionsActions 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.4392014
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / document-actionsdocument-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.8669925
|