Configure Email Conversations

V10.5

Overview

Email conversation is a type of case-related conversation supported in Cora Orchestration. You can enable and configure the Email conversation type for a Solution, which allows users to compose and send ad-hoc emails from within the forms, and display case-related incoming and outgoing emails.

The To, Cc, and Bcc fields in the email composer display names of the recipients, and the users can add new email addresses to the address book in the system directly from the To, Cc, and Bcc fields.

Starting from V10.5,  in the email composer you can now search for an email address or a name in the in the To, Cc, and Bcc recipients fields and the system fetches and suggests the email address from the address book for auto completion.

Configure email conversation type through the Conversations View

1. In the Administration site, open the Solution from the list.
2. In the Solution Components section, click Conversations View.
3. In the Conversation View window: 
   1. Select the Email conversation type to enable for the Solution.
   2. Add status change handlers for event handling.
      For details, see the Configure conversation item events for the event handling section in this article below.
   3. Add Email Settings.
      For details, see the Email settings section below.
      
      

Email settings

Configure email conversation type through the Email Composer

1. In the Administration site, click and open a Solution from list.
2. In the Solution Components section, click Email Composer.
3. In the Email Composer window:
   1. Add a valid default "Address - From" email address.
      This address is used when no From address(es) is provided while calling the Email Composer. An invalid address displays an error. 
   2. Add valid "Addresses - To" email address(es) for recipients' auto complete selection.
      This list is used for the To, Cc, and Bcc fields and is managed and displayed as a grid where you can add, edit or delete email addresses.
   3. Add "Email Templates".
      These templates help user standardize an email format and are created as a Cora SeQuence expression.
      You can also edit and delete existing templates.
      You need to have the master workflow configured to use its properties like activities, variables, and metadata in the message body and subject. The workflow properties are displayed on the right panel.
   4. Add "Email Signatures".
      These signatures help user standardize an email signature.
      You can also edit and delete existing email signatures.

Configure Email Sender job

With Email Composer, you need to configure an Email Sender JES job to send emails. The emails are sent asynchronously. 

1. Go to, Administration > Global Settings > Jobs Management, and click Add Job.
2. Select Email Sender as the job type.
3. Click Create.
4. Edit the Job tab, as required.
5. On the Command tab, add:
   1. Fetch Batch Size: Number of emails to be included in a single batch.
      The batch includes emails in the "InQueue" state, or in the "Sending" state for longer than Abandoned Timeout.
   2. Abandoned Timeout: Time to allow a conversation item to remain in the "Sending" state before it is considered as "abandoned", and ready to be fetched again by the job.
   3. Polling Interval: Time to wait between each database query to fetch conversation items with the "InQueue" state and abandoned emails.
   4. SMTP Connection Name: Name of the SMTP connection to use. It is defined in the General tables > SMTP connections. (for versions previous to V9.8.3.)
      OR
      Email Sending Connection Name: Name of the connection to use for email sending. (for V9.8.3 and later.)
   5. Max. Retry Count: Number of retries to run before abandoning the batch and failing the job.
   6. Max Retry Interval: Time to wait between consecutive retries of the same email.
   7. Email Time to Live (TTL): Time for an email conversation item to stay in the "InQueue" state before moving to the "Sending" state.
   8. Send Emails with Custom Email Headers: Optional. Custom headers to be added to the emails sent from the Conversation View. Default is blank.
6. On the Advanced tab, define the job execution schedule.
7. Click Finish.

Adding incoming emails to the Conversations View through built-in command

To add incoming emails directly from an Email Listener to Conversations View in your workflow:

1. Add a Built-In Command activity.
2. In Category, select Case Operations.
3. In Commands, select Create Incoming Email from Email Listener.
4. Click Next.
5. Click EmailListenerToIncomingEmail item.
6. Clear IsNull check box.
7. Expand EmailListenerToIncomingEmail item. 
8. Click the MailMessage parameter and assign Email Listener's email value.
   For example, {ListenerName}.Email.
9. Click the WorkflowInstanceId parameter, and assign the master workflow value of the workflow where you want to display the email conversation item.
10. Click the CreatedByUserId parameter, and assign a value to display the user who created the email conversation item.
11. Click Finish.

To add incoming emails to Conversations View manually, you can use the Create Conversation Item built-in-command.

1. Add a Built-In Command activity.
2. Select Case Operations > Create Conversation Item.
3. Click Next.
4. Add the following command parameters:
   • workflowInstanceId: the master or the sub workflow id.
   • conversationItemState: should be Incoming, but can be any state.
     For details, see this article.
   • ConversationItem: EmailConversationItem
     • From
     • To
     • Cc
     • Bcc
     • Subject
     • Priority: Sets the priority of the email conversation. Value can be High or Normal.
       Available for V9.6 and later.
     • Content Type
     • Body
       Example: IIF({EmailListenerActivityName}.Email.HasBodyHtml, {EmailListenerActivityName }.Email.PreviewBodyHtml, {EmailListenerActivityName }.Email.BodyText)
     • Attachments
       File name example: {Listener1}.Email.AllAttachments.Last().FileName
       AllAttachments combines the email attachments and the msg/eml file that was created by the Email Listener.
   • createdByUserId: the current user executing the built-in command.

4. Click Finish.

Use Email Composer in Cora SeQuence forms

You can add Email Composer in your forms, in the following two ways:

• Add Conversations View control to get all the email functionalities.
  For more details, see this article.
  
  
• Manage the Email Composer controls independently, through Client API within the forms.
  For details, see the section below.

Manage Email Composer through client API

1. Add or edit a form or task activity in a workflow.
2. Add the following script to the form source.

    <script type="text/javascript">
      function OnNewMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          windowTitle: 'New Message',
          from: "absd1@gmail.com,apgd@gmail.com",
          to: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          cc: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          bcc: '',
          template: 'SignatureTemplate',
          subject: 'Email Composer Subject',
          priority: 'high',
          signature: 'ben sign alias',
          body: 'Hello',
          //disabledFields: ['from', 'cc', 'bcc', 'template', 'subject','signature']
          disabledFields: ['signature']
        };
        var uniqueId = SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnExistingMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          uniqueId: "F8C8FC17-86E4-40F9-85CC-C1555DA47A94"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnReplyMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          replyToId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnForwardMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          forwardedFromId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }
    </script>

Language support

Localization of Email conversation type is supported by default.
For details on multilingual configuration, see this article.

Conversation component is translated according to form's Globalization settings:

• if Localizable = False, use the Language activity definition
• if Localizable = True, use the user's language

For general client API information on all conversation items including Email Composer, see the Conversations View client API section in this article.

For Email Composer, you can use the following args object parameters:

Configure state triggered workflows

You can configure the system to initiate a specific workflow and perform an action when a conversation item changes to a specific status.

For details, see this article.

V9.7 and V10.4.x

Overview

Email conversation is a type of case-related conversation supported in Cora SeQuence. You can enable and configure the Email conversation type for a Solution, which allows users to compose and send ad-hoc emails from within the forms, and display case-related incoming and outgoing emails.

The To, Cc, and Bcc fields in the email composer display names of the recipients, and the users can add new email addresses to the address book in the system using the To, Cc, and Bcc fields in the email composer.

Configure email conversation type through the Conversations View

1. In the Administration site, open the Solution from the list.
2. In the Solution Components section, click Conversations View.
3. In the Conversation View window: 
   1. Select the Email conversation type to enable for the Solution.
   2. Add status change handlers for event handling.
      For details, see the Configure conversation item events for the event handling section in this article below.
   3. Add Email Settings.

Configure email conversation type through the Email Composer

1. In the Administration site, click and open a Solution from list.
2. In the Solution Components section, click Email Composer.
3. In the Email Composer window:
   1. Add a valid default "Address - From" email address.
      This address is used when no From address(es) is provided while calling the Email Composer. An invalid address displays an error. 
   2. Add valid "Addresses - To" email address(es) for recipients' auto complete selection.
      This list is used for the To, Cc, and Bcc fields and is managed and displayed as a grid where you can add, edit or delete email addresses.
   3. Add "Email Templates".
      These templates help user standardize an email format and are created as a Cora SeQuence expression.
      You can also edit and delete existing templates.
      You need to have the master workflow configured to use its properties like activities, variables, and metadata in the message body and subject. The workflow properties are displayed on the right panel.
   4. Add "Email Signatures".
      These signatures help user standardize an email signature.
      You can also edit and delete existing email signatures.

Configure Email Sender job

With Email Composer, you need to configure a JES job to send emails. The emails are sent asynchronously. 

1. Go to, Administration > Global Settings > Jobs Management, and click Add Job.
2. Select Email Sender as the job type.
3. Click Create.
4. Edit the Job tab, as required.
5. On the Command tab, add:
   1. Fetch Batch Size: Number of emails to be included in a single batch.
      The batch includes emails in the "InQueue" state, or in the "Sending" state for longer than Abandoned Timeout.
   2. Abandoned Timeout: Time to allow a conversation item to remain in the "Sending" state before it is considered as "abandoned", and ready to be fetched again by the job.
   3. Polling Interval: Time to wait between each database query to fetch conversation items with the "InQueue" state and abandoned emails.
   4. SMTP Connection Name: Name of the SMTP connection to use. It is defined in the General tables > SMTP connections. (for versions previous to V9.8.3.)
      OR
      Email Sending Connection Name: Name of the connection to use for email sending. (for V9.8.3 and later.)
   5. Max. Retry Count: Number of retries to run before abandoning the batch and failing the job.
   6. Max Retry Interval: Time to wait between consecutive retries of the same email.
   7. Email TTL: Time for an email conversation item to stay in the "InQueue" state before moving to the "Sending" state.
6. On the Advanced tab, define the job execution schedule.
7. Click Finish.

Adding incoming emails to the Conversations View through built-in command

To add incoming emails directly from an Email Listener to Conversations View in your workflow:

1. Add a Built-In Command activity.
2. In Category, select Case Operations.
3. In Commands, select Create Incoming Email from Email Listener.
4. Click Next.
5. Click EmailListenerToIncomingEmail item.
6. Clear IsNull check box.
7. Expand EmailListenerToIncomingEmail item. 
8. Click the MailMessage parameter and assign Email Listener's email value.
   For example, {ListenerName}.Email.
9. Click the WorkflowInstanceId parameter, and assign the master workflow value of the workflow where you want to display the email conversation item.
10. Click the CreatedByUserId parameter, and assign a value to display the user who created the email conversation item.
11. Click Finish.

To add incoming emails to Conversations View manually, you can use the Create Conversation Item built-in-command.

1. Add a Built-In Command activity.
2. Select Case Operations > Create Conversation Item.
3. Click Next.
4. Add the following command parameters:
   • workflowInstanceId: the master or the sub workflow id.
   • conversationItemState: should be Incoming, but can be any state.
     For details, see this article.
   • ConversationItem: EmailConversationItem
     • From
     • To
     • Cc
     • Bcc
     • Subject
     • Priority: Sets the priority of the email conversation. Value can be High or Normal.
       Available for V9.6 and later.
     • Content Type
     • Body
       Example: IIF({EmailListenerActivityName}.Email.HasBodyHtml, {EmailListenerActivityName }.Email.PreviewBodyHtml, {EmailListenerActivityName }.Email.BodyText)
     • Attachments
       File name example: {Listener1}.Email.AllAttachments.Last().FileName
       AllAttachments combines the email attachments and the msg/eml file that was created by the Email Listener.
   • createdByUserId: the current user executing the built-in command.

4. Click Finish.

Use Email Composer in Cora SeQuence forms

You can add Email Composer in your forms, in the following two ways:

• Add Conversations View control to get all the email functionalities.
  For more details, see this article.
  
  
• Manage the Email Composer controls independently, through Client API within the forms.
  For details, see the section below.

Manage Email Composer through client API

1. Add or edit a form or task activity in a workflow.
2. Add the following script to the form source.

    <script type="text/javascript">
      function OnNewMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          windowTitle: 'New Message',
          from: "absd1@gmail.com,apgd@gmail.com",
          to: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          cc: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          bcc: '',
          template: 'SignatureTemplate',
          subject: 'Email Composer Subject',
          priority: 'high',
          signature: 'ben sign alias',
          body: 'Hello',
          //disabledFields: ['from', 'cc', 'bcc', 'template', 'subject','signature']
          disabledFields: ['signature']
        };
        var uniqueId = SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnExistingMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          uniqueId: "F8C8FC17-86E4-40F9-85CC-C1555DA47A94"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnReplyMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          replyToId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnForwardMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          forwardedFromId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }
    </script>

Language support

Localization of Email conversation type is supported by default.
For details on multilingual configuration, see this article.

Conversation component is translated according to form's Globalization settings:

• if Localizable = False, use the Language activity definition
• if Localizable = True, use the user's language

For general client API information on all conversation items including Email Composer, see the Conversations View client API section in this article.

For Email Composer, you can use the following args object parameters:

Configure state triggered workflows

You can configure the system to initiate a specific workflow and perform an action when a conversation item changes to a specific status.

For details, see this article.

V9.5

Overview

Email conversation is a type of case-related conversation supported in Cora SeQuence. You can enable and configure the Email Composer component for a Solution, which when added to a workflow instance, allows users to compose and send ad-hoc emails from within the forms.

The Email Composer component coupled with Conversations View, helps display case-related incoming and outgoing emails.

Configure Email Composer

1. In the Administration site, click and open a Solution from list.
2. In the Solution Components section, click Email Composer.
3. In the Email Composer window:
   1. Add a valid default "Address - From" email address.
      This address is used when no From address(es) is provided while calling the Email Composer. An invalid address displays an error. 
   2. Add valid "Addresses - To" email address(es) for recipients' auto complete selection.
      This list is used for the To, Cc, and Bcc fields and is managed and displayed as a grid where you can add, edit or delete email addresses.
   3. Add "Email Templates".
      These templates help user standardize an email format and are created as a Cora SeQuence expression.
      You can also edit and delete existing templates.
      You need to have the master workflow configured to use its properties like activities, variables, and metadata in the message body and subject. The workflow properties are displayed on the right panel.
   4. Add "Email Signatures".
      These signatures help user standardize an email signature.
      You can also edit and delete existing email signatures.

Configure Email Sender job

With Email Composer, you need to configure a JES job to send emails. The emails are sent asynchronously. 

1. Go to, Administration > Global Settings > Jobs Management, and click Add Job.
2. Select Email Sender as the job type.
3. Click Create.
4. Edit the Job tab, as required.
5. On the Command tab, add:
   1. Fetch Batch Size: Number of emails to be included in a single batch.
      The batch includes emails in the "InQueue" state, or in the "Sending" state for longer than Abandoned Timeout.
   2. Abandoned Timeout: Time to allow a conversation item to remain in the "Sending" state before it is considered as "abandoned", and ready to be fetched again by the job.
   3. Polling Interval: Time to wait between each database query to fetch conversation items with the "InQueue" state and abandoned emails.
   4. SMTP Connection Name: Name of the SMTP connection to use. It is defined in the General tables > SMTP connections.
   5. Max. Retry Count: Number of retries to run before abandoning the batch and failing the job.
   6. Max Retry Interval: Time to wait between consecutive retries of the same email.
   7. Email TTL: Time for an email conversation item to stay in the "InQueue" state before moving to the "Sending" state.
6. On the Advanced tab, define the job execution schedule.
7. Click Finish.

Adding incoming emails to the Conversation View through built-in command

To add incoming emails directly from an Email Listener to Conversations View in your workflow:

1. Add a Built-In Command activity.
2. In Category, select Case Operations.
3. In Commands, select Create Incoming Email from Email Listener.
4. Click Next.
5. Click EmailListenerToIncomingEmail item.
6. Clear IsNull check box.
7. Expand EmailListenerToIncomingEmail item. 
8. Click the MailMessage parameter and assign Email Listener's email value.
   For example, {ListenerName}.Email.
9. Click the WorkflowInstanceId parameter, and assign the master workflow value of the workflow where you want to display the email conversation item.
10. Click the CreatedByUserId parameter, and assign a value to display the user who created the email conversation item.
11. Click Finish.

To add incoming emails to Conversations View manually, you can use the Create Conversation Item built-in-command.

1. Add a Built-In Command activity.
2. Select Case Operations > Create Conversation Item.
3. Add the following:
   • workflowInstanceId
   • conversationItemState: should be Incoming, but can be any state.
   • createdByUserId

4. Select the type as Email Conversation Item, and add the following command parameters:
   • From
   • To
   • CC
   • BCC
   • Subject
   • Priority: Sets the priority of the email conversation.
     Example: EmailConversationItemPriority Priority = "High"
     NOTE
     Available for V9.6 and later.
   • Body
     Example: IIF({EmailListenerActivityName}.Email.HasBodyHtml, {EmailListenerActivityName }.Email.PreviewBodyHtml, {EmailListenerActivityName }.Email.BodyText)
   • Attachments
     File name example: {Listener1}.Email.AllAttachments.Last().FileName
     AllAttachments combines the email attachments and the msg/eml file that was created by the Email Listener.

Use Email Composer in Cora SeQuence forms

You can add Email Composer in your forms, in the following two ways:

• Add Conversations View control to get all the email functionalities.
  For more details, see this article.
  
  
• Manage the Email Composer controls independently, through Client API within the forms.
  For details, see the section below.

Manage Email Composer through client API

1. Add or edit a form or task activity in a workflow.
2. Add the following script to the form source.

    <script type="text/javascript">
      function OnNewMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          windowTitle: 'New Message',
          from: "absd1@gmail.com,apgd@gmail.com",
          to: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          cc: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          bcc: '',
          template: 'SignatureTemplate',
          subject: 'Email Composer Subject',
          priority: 'high',
          signature: 'ben sign alias',
          body: 'Hello',
          //disabledFields: ['from', 'cc', 'bcc', 'template', 'subject','signature']
          disabledFields: ['signature']
        };
        var uniqueId = SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnExistingMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          uniqueId: "F8C8FC17-86E4-40F9-85CC-C1555DA47A94"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnReplyMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          replyToId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnForwardMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          forwardedFromId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }
    </script>

Language support

Localization of Email conversation type is supported by default.
For details on multilingual configuration, see this article.

Conversation component is translated according to form's Globalization settings:

• if Localizable = False, use the Language activity definition
• if Localizable = True, use the user's language

For general client API information on all conversation items including Email Composer, see the Conversations View client API section in this article.

For Email Composer, you can use the following args object parameters:

Available email states

V9.4.1

Overview

Email Conversation type is a part of reusable components added to Cora SeQuence. The Email Conversation type uses the Email Composer to allow users compose and send ad-hoc emails from within the forms. Email Composer component in the Conversations View component helps display the incoming and outgoing emails.

Configure Email Composer

1. In the Administration site, click and open a Solution from the list.
2. In the Solution Components section, click Email Composer.
3. In the Email Component window, 
   1. Add a valid default "Address - From" email address.
      This address is used when no From address(es) are provided while calling the Email Composer. An invalid address displays an error. 
   2. Add valid "Addresses - To" email address(es) for recipients' auto complete selection.
      This list is used for the To, Cc, and Bcc fields, and is managed and displayed as a grid where you can add, edit or delete email addresses.
   3. Add, edit or delete email templates.
      These templates help user standardize an email format, and are created as a Cora SeQuence expression.
      You need to have the master workflow configured to use its properties like activities, variables, and metadata in the message body and subject. The workflow properties are displayed on the right panel.
   4. Add, edit or delete email signatures.
      These signatures help user standardize an email signature.

Configure Email Sender job

With Email Composer, you need to configure a JES job to send emails. The emails are sent asynchronously. 

1. Go to, Administration > Global Settings > Jobs Management, and click Add Job.
2. Select Email Sender as job type.
3. Click Create.
4. Edit the Job tab, as required.
5. On the Command tab, add:
   1. Fetch Batch Size: Number of emails to be included in single batch.
      Batch includes emails in "InQueue" state, or in "Sending" state for longer than Abandoned Timeout.
   2. Abandoned Timeout: Time to allow a conversation item to remain in "Sending" state before it is considered as "abandoned", and ready to be fetched again.
   3. Polling Interval: Time to wait between each database query to fetch conversation items with "InQueue" state and abandoned emails.
   4. SMTP Connection Name: Name of the SMTP connection to use. It is defined in the General tables > SMTP connections.
   5. Max. Retry Count: Number of retries to run before abandoning the batch and failing the job.
   6. Max Retry Interval: Time to wait between consecutive retries of the same email.
   7. Email TTL: Time for an email conversation item to stay in the "InQueue" state.
6. On the Advanced tab, define the job execution schedule.
7. Click Finish.

Adding incoming emails to the Conversation View through built-in command

You can use the Create Conversation Item built-in-command to insert incoming emails into the Conversations View. 

1. Add a Built-In Command activity.
2. Select Conversation Operations > Create Conversation Item.
3. Add the following:
   • workflowInstanceId
   • conversationItemState: should be Incoming, but can be any state.
   • createdByUserId

4. Select the type as Email Conversation Item, and add the following command parameters:
   • From
   • To
   • CC
   • BCC
   • Subject
   • Body
     Example: IIF({EmailListenerActivityName}.Email.HasBodyHtml, {EmailListenerActivityName }.Email.PreviewBodyHtml, {EmailListenerActivityName }.Email.BodyText)
   • Attachments
     File name example: {Listener1}.Email.AllAttachments.Last().FileName
     AllAttachments combines the email attachments and the msg/eml file that was created by the Email Listener.

Use Email Composer in Cora SeQuence forms

You can add Email Composer in your forms, in the following two ways:

• Add the Conversations View: With this you get all of the email functionalities.
  For more details, see this article.
  
  
• Manage the Email Composer controls independently, through Client API within the forms.
  For details, see the section below.

Manage Email Composer through client API

1. Add or edit a form or task activity in a workflow.
2. Add the following script to the form source.

    <script type="text/javascript">
      function OnNewMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          windowTitle: 'New Message',
          from: "absd1@gmail.com,apgd@gmail.com",
          to: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          cc: "john.smith@genpact.digital,mack.ben@pnmsoft.com",
          bcc: '',
          template: 'SignatureTemplate',
          subject: 'Email Composer Subject',
          signature: 'ben sign alias',
          body: 'Hello',
          //disabledFields: ['from', 'cc', 'bcc', 'template', 'subject','signature']
          disabledFields: ['signature']
        };
        var uniqueId = SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnExistingMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          uniqueId: "F8C8FC17-86E4-40F9-85CC-C1555DA47A94"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnReplyMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          replyToId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }


      function OnForwardMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          forwardedFromId: "18C01D1F-2947-4CDB-BE0E-3056598ECFFA"
        }
        SEQComponents.Email.open(parameters);
        args.set_cancel(true);
      }
    </script>

For general client API information on all conversation items including Email Composer, see the Conversations View client API section in this article.

For Email Composer, you can use the following args object parameters:

• args.detail.parameters.windowTitle: Specifies the title of the Email Composer window.
• args.detail.parameters.from: Specifies the list of email addresses a user can select from. This parameter overrides the pre-configured From email address. The first item is set as the default From address.
• args.detail.parameters.template: Applies a selected template.
• args.detail.parameters.signature: Applies a selected signature template.
• args.detail.parameters.to: Adds a list of To addresses.
• args.detail.parameters.cc: Adds a list of Cc addresses.
• args.detail.parameters.bcc: Adds a list of Bcc addresses.
• args.detail.parameters.subject: Specifies the email subject. The subject is overwritten if an email template is set.
• args.detail.parameters.body: Specifies the email body. The body is overwritten if an template is set.

Available email states

V9.4

Overview

Email Conversation type is a part of the case management reusable components added to Cora SeQuence. The Email Conversation type uses the Email Component to allow composing and sending ad-hoc emails from within the forms, and the Conversation Component helps display the incoming and outgoing emails.

Configure Email Composer

1. In the Administration site, click and open a Solution from the list.
2. In the Solution Components section, click Email Component.
3. In the Email Component window, 
   1. Add a valid default "Address - From" email address.
      This address is used when no From address(es) are provided while calling the Email Composer. An invalid address displays an error. 
   2. Add valid "Addresses - To" email address(es) for recipients' auto complete selection.
      This list is used for the To, Cc, and Bcc fields, and is managed and displayed as a grid where you can add, edit or delete email addresses.
   3. Add, edit or delete email templates.
      These templates help user standardize an email format, and are created as a Cora SeQuence expression.
      You need to have the master workflow configured to use its properties like activities, variables, and metadata in the message body and subject. The workflow properties are displayed on the right panel.

Configure Email Sender job

With Email Composer, you need to configure a JES job to send emails asynchronously. 

1. Go to, Administration > Global Settings > Jobs Management, and click Add Job.
2. Select Email Sender as job type.
3. Click Create.
4. Edit the Job tab, as required.
5. On the Command tab, add:
   1. Fetch Batch Size: Number of emails to be included in single batch.
      Batch includes emails in "InQueue" state, or in "Sending" state for longer than Abandoned Timeout.
   2. Abandoned Timeout: Time to allow a conversation item to remain in "Sending" state before it is considered as "abandoned", and ready to be fetched again.
   3. Polling Interval: Time to wait between each database query to fetch conversation items with "InQueue" state and abandoned emails.
   4. SMTP Connection Name: Name of the SMTP connection to use. It is defined in the General tables > SMTP connections.
   5. Max. Retry Count: Number of retries to run before abandoning the batch and failing the job.
   6. Max Retry Interval: Time to wait between consecutive retries of the same email.
   7. Email TTL: Time for an email conversation item to stay in the "InQueue" state.
6. On the Advanced tab, define the job execution schedule.
7. Click Finish.

Add Email Composer to Cora SeQuence forms

You can add Email Composer in your forms, in the following two ways:

• Add the Conversations View
  With this you get all of the email functionalities. For more details, see this article.
  
  
• Manage the Email Composer controls independently through Client API within the forms.

Manage Email Composer through client API

1. Add or edit a form or task activity in a workflow.
2. Add the following script to the form source.

<script type="text/javascript">
      function OnNewMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          title: 'New Message',
          from: "johnk@genpact.com;",
          to: "mark.smith@genpact.digital;john.smith@pnmsoft.com",
          cc: "jack.fellow@genpact.digital",
          bcc: '',
          template: 'rat',
          subject: 'Email Composer Subject',
          body: '',
          //disabledFields: ['from', 'to', 'cc', 'bcc', 'template', 'subject']
        };
        var messageId = SEQForms.EmailComposer.open(parameters);
        args.set_cancel(true);
      }
      function OnExistingMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          messageId: <Guid>,
          template: "rat"
        }
        SEQForms.EmailComposer.open(parameters);
        args.set_cancel(true);
      }
      function OnReplyMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          replyToId: <Guid>,
          subject: 'Email Composer Subject',
          template: 'rat'
        }
        SEQForms.EmailComposer.open(parameters);
        args.set_cancel(true);
      }
      function OnForwardMailButtonClientClicking(sender, args) {
        var parameters = {
          wfId: '<%= { wf.WorkflowInstanceId } %>',
          forwardToId: <Guid>
        }
        SEQForms.EmailComposer.open(parameters);
        args.set_cancel(true);
      }
    </script>

For general client API information on all conversation items including Email Composer, see the Conversations View client API section in this article.

For Email Composer, you can use the following args object parameters:

• args.detail.parameters.windowTitle: Specifies the title of the Email Composer window.
• args.detail.parameters.from: Specifies the list of email addresses a user can select from. This parameter overrides the pre-configured From email address. The first item is set as the default From address.
• args.detail.parameters.template: Applies a selected template.
• args.detail.parameters.to: Adds a list of To addresses.
• args.detail.parameters.cc: Adds a list of Cc addresses.
• args.detail.parameters.bcc: Adds a list of Bcc addresses.
• args.detail.parameters.subject: Specifies the email subject. The subject is overwritten if an email template is set.
• args.detail.parameters.body: Specifies the email body. The body is overwritten if an template is set.

Adding incoming emails to the Conversation View through built-in command

You can use the Create Conversation Item built-in-command to insert incoming emails into the Conversations View. 

1. Add a Built-In-Command activity.
2. Select the category as Conversation Operations and command as Create Conversation Item.
3. Add:
   • workflowInstanceId
   • conversationItemState: should be Incoming, but can be any state.

4. Select the type as Email Conversation Item, and add the following command parameters:
   • From
   • To
   • CC
   • BCC
   • Subject
   • Body
     (example: IIF({EmailListenerActivityName}.Email.HasBodyHtml, {EmailListenerActivityName }.Email.PreviewBodyHtml, {EmailListenerActivityName }.Email.BodyText))
   • Attachments

Available email states