Found 327 results for "docs fields email"
The search executed in 0.00148113 seconds. That's fast.
|
Gitana / 4.0 / Data Engine / Content Models / ConnectorsConnectors You can create fields in your form which connect to your Cloud CMS content. This is done by configuring the Alpaca field's datasource to use CloudCMS via a connector. Example Suppose you have a type my:category and want to create a dropdown field to select category when creating another document. To do that, you would create a field in your form like this: { ... "category": { "type": "select", "dataSource": { "connector": true, "conf
Score: 16.418236
|
|
|
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: 12.76126
|
|
|
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: 12.76126
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Relator PropertiesRelator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as "relator properties". Consider a Store that sells Books. Books are written by Auth
Score: 12.332876
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Email NotificationEmail Notification Here is an example of a workflow model that sends an email when the workflow transitions into the node1 participant state. s { "id": "email-notification", "title": "Email Notification", "nodes": { "start": { "type": "start", "transitions": { "start": "node1" } }, "node1": { "type": "participant", "title": "Step One", "swimlane": "main", "trans
Score: 11.546745
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Email NotificationEmail Notification Here is an example of a workflow model that sends an email when the workflow transitions into the node1 participant state. s { "id": "email-notification", "title": "Email Notification", "nodes": { "start": { "type": "start", "transitions": { "start": "node1" } }, "node1": { "type": "participant", "title": "Step One", "swimlane": "main", "trans
Score: 11.546745
|
|
|
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: 8.857852
|
|
|
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: 8.857852
|
|
|
Gitana / 3.2 / Guide / Guide / FormsForms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des
Score: 8.595948
|
|
|
Gitana / 4.0 / Forms / CMS / OverviewForms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des
Score: 8.595948
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.35971
|
|
|
Gitana / 4.0 / Forms / CMS / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.35971
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / EmailEmail 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 Emails maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you the
Score: 7.814717
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / EmailEmail 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 Emails maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you the
Score: 7.814717
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / ConnectorsConnectors You can create fields in your form which connect to your Cloud CMS content. This is done by configuring the Alpaca field's datasource to use CloudCMS via a connector. Example Suppose you have a type my:category and want to create a dropdown field to select category when creating another document. To do that, you would create a field in your form like this: { ... "category": { "type": "select", "dataSource": { "connector": true, "conf
Score: 7.4938693
|
|
|
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: 7.2569065
|
|
|
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: 7.2569065
|
|
|
Gitana / 4.0 / Forms / API / Custom FieldsCustom Fields Alpaca has a pretty inclusive field library that you can use straight away. Fields are simply referenced by their type within your Alpaca forms configuration. If you don't provide specific field types to use, Alpaca guesses at sensible defaults for you. You can also create your own fields. Alpaca fields are object-oriented (essentially) so that you can extend existing fields, override methods and modify behaviors. The result is less work and a complete extensibility layer so that y
Score: 7.1403875
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / EmailEmail Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: { "templateKey": "abc" } Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik
Score: 6.976348
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / EmailEmail Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: { "templateKey": "abc" } Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik
Score: 6.976348
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / Email ProviderEmail Provider 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 Email Providers maintain a configuration that you can adjust or consult as you create, update and query for them. The following tabl
Score: 5.963857
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / Email ProviderEmail Provider 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 Email Providers maintain a configuration that you can adjust or consult as you create, update and query for them. The following tabl
Score: 5.963857
|
|
|
Gitana / 3.2 / Guide / Guide / Actions / Send EmailSend Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All
Score: 5.95088
|
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Send EmailSend Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All
Score: 5.95088
|
|
|
Gitana / 4.0 / Forms / Fields / Email FieldEmail Field The email field. Properties Title Email Description Email Field Type email Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attributes that will be added as DOM attribuets fo
Score: 5.885602
|