Found 136 results for "actions webhook"
The search executed in 9.32717E-4 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: 21.77515
|
![]() |
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: 21.77515
|
![]() |
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: 16.620665
|
![]() |
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: 16.620665
|
![]() |
Gitana / 3.2 / Guide / Guide / PoliciesPolicies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. These policies will trigger behaviors whe
Score: 9.770313
|
![]() |
Gitana / 4.0 / Data Engine / Behaviors / PoliciesPolicies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. These policies will trigger behaviors whe
Score: 9.770313
|
![]() |
Gitana / 4.0 / Data Engine / Content Models / BehaviorsBehaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b
Score: 9.634146
|
![]() |
Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Events ExampleEvents Example This workflow model demonstrates how you can use events in various ways. This workflow model is provided as an kind of reference for how handlers can be set up. It isn't intended to be particularly useful or functional beyond its purpose as a demonstration. { "id": "events", "title": "Events Example Model", "nodes": { "start": { "type": "start", "transitions": { "start": "node1" } }, "node1": {
Score: 7.853938
|
![]() |
Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Events ExampleEvents Example This workflow model demonstrates how you can use events in various ways. This workflow model is provided as an kind of reference for how handlers can be set up. It isn't intended to be particularly useful or functional beyond its purpose as a demonstration. { "id": "events", "title": "Events Example Model", "nodes": { "start": { "type": "start", "transitions": { "start": "node1" } }, "node1": {
Score: 7.853938
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / actionsactions [ { "config": { "actions": { "create-content": { "title": "Create a New Content Instance" } } } } ]```
Score: 6.6281705
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / actionsactions [ { "config": { "actions": { "create-content": { "title": "Create a New Content Instance" } } } } ]```
Score: 6.6281705
|
![]() |
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.560871
|
![]() |
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.560871
|
![]() |
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.5591884
|
![]() |
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.5591884
|
![]() |
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.4474487
|
![]() |
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.4474487
|
![]() |
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.442764
|
![]() |
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.442764
|
![]() |
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: 6.437051
|
![]() |
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: 6.437051
|
![]() |
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.8699026
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / 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.8699026
|
![]() |
Gitana / 3.2 / Guide / Guide / Content Modeling / BehaviorsBehaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b
Score: 4.8048
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-item-actionsdocuments-list-item-actions [ { "evaluator": "document-is-favorite", "config": { "documents-list-item-actions": [ { "key": "favorite", "iconClass": "fa fa-star", "action": "remove-from-favorites", "order": 9000 } ] } }, { "config": { "documents-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/documents/{{document._doc}}/properties",
Score: 4.776344
|