Pergapedia / SSP7
SMTX SupportSMTX Wiki
  • Introduction
  • Pergapedia / SSP7 Admin guide
  • Catalog
    • Typical use cases
      • Usage as Knowledge Catalog
      • Usage as Data Catalog
      • Usage as Service Catalog
    • Catalog Maintenance
      • Templates
        • Create a new template
        • Version management of templates
        • ACL (Access Control Lists)
          • Scopes
          • Add default ACLs
          • Remove All ACLS
          • ACL condition script examples
        • Set translation label for Publication request button
      • Parts (Fields)
        • Field types
        • Calculations
        • Field Validation examples
        • Field Visibility Examples
        • Field Filtering
        • Default value
      • Actors
      • Reusable content
      • Settings
      • General Settings
      • Roles
      • Javascript for Variables in processes
      • Action Forms
        • Add log entries for Action Forms
    • Service Maintenance
      • Services
        • Filter list of services
        • Duplicating services
        • Adding a new service
        • Service Details
          • General settings
          • Service Data
          • Contracts
          • Actors
          • Receivers
          • Targets
          • Support Groups
          • Relations
          • Requests
          • Quality Notes
          • Publication History
          • Documents
          • Log
          • Service Actions
        • Compare versions
        • Quality Notes
        • Service Changed flag
      • Approvals
      • Relations
        • Start service from service
      • Subscriptions
      • Outages
    • Public
    • Service Catalog API
      • Outbound REST API
        • Get Services
        • Get Service Details
      • Inbound SOAP calls
        • Create custom approval
        • Add log to service publish request
        • Add person to service person list
        • Add persongroup to service persongroup list
        • Delete service
        • Mark service publish request as in approval state
        • Process service publish request
        • Publish request set can be cancelled
        • Publish request set show in public
        • Remove person from service person list
        • Remove persongroup from service persongroup list
        • Remove support group from service
        • Update service field
        • Update service language field
        • Update template part datetime value
        • Update template part numeric value
        • Update template part text value
  • Fulfillment Platform
    • Admin Panel
    • General Settings
      • General
      • My Profile
      • Mail Settings
      • Login
      • Forms Setting
      • Workflow
      • Archive
      • Calendar Overview
      • Dashboard
      • Mobile Component
      • Ticketing
      • Webhooks
      • Goto
      • Search options
      • Application URL Settings
      • Address Book Settings
    • Dashboard
    • Categories
    • Topics
    • Forms
      • Fields-tab
      • Field: General Settings
      • Dynamic Value
      • Text (Area) Field
      • Yes : No Field
      • Upload file(s)
      • Date (Time) Field
      • Password Field
      • Read Only Display Field
      • Header
      • Tab
      • Section
      • Repeatable section buttons
      • Subform
      • Static HTML
      • Hidden Field
      • Selection Fields
      • Calculations
    • Processes
      • General Settings
      • Dynamic Field Mapping
      • Process Steps
      • Step Types
      • Logging
    • Datastore
      • Process interaction
      • Manage datastore entries via Webservices - Javascript
    • Tasks
    • Auto Forms
    • Adapters
      • Person Data
      • Web Services
    • Event triggers
    • Roles
    • Rolesets
    • Groups
    • Views
      • View Example 1
      • View example 2
    • Mail Templates
    • Layouts
    • Mail queue
    • Reporting
    • External Apps
    • My Items
    • Translations
    • Bulk Uploads
    • Help page
    • Goto
    • Search
    • Inbound Email
    • Reporting Dashboard
    • Ticketing
      • My Activities
      • Ticketing Views
      • External Integrations
    • Release Manager
    • Content Management Console module
    • SSP Studio
    • Persons & Accounts
    • Pools
  • Release Notes
    • Terms and Conditions
      • December 2024
    • Release 7.21.01
    • Release 7.21.03
    • Release 7.21.04
    • Release 7.21.05
    • Release 7.21.06
    • Release 7.21.07
    • Release 7.21.08
    • Release 7.21.09
    • Release 7.21.10
    • Release 7.21.11
    • Release 7.21.12
    • Release 7.22.02
    • Release 7.22.03
    • Release 7.22.04
    • Release 7.22.05
    • Release 7.22.06
    • Release 7.22.07
    • Release 7.22.08
    • Release 7.22.09
    • Release 7.22.10
    • Release 7.22.12
    • Release 7.23.01
    • Release 7.23.02
    • Release 7.23.03
    • Release 7.23.04
    • Release 7.23.05
    • Release 7.23.07
    • Release 7.23.08
    • Release 7.23.09
    • Release 7.23.10
    • Release 7.23.11
    • Release 7.23.12
    • Release 7.24.02
    • Release 7.24.03
    • Release 7.24.04
    • Release 7.24.05
    • Release 7.24.06
    • Release 7.24.07
    • Release 7.24.08
    • Release 7.24.09
    • Release 7.24.10
    • Release 7.24.11
    • Release 7.24.12
    • Release 7.25.01
    • Release 7.25.02
    • Release 7.25.03
    • Release 7.25.04
    • Release 7.25.05
  • Guides
    • Installation Guide
      • Scheduled Task installation
    • Upgrade Guide
    • LDAP Import
    • Training
      • Exercise : Create a new form
      • Exercise : Create a new Datastore Parameter
      • Exercise : Create a new Process
      • Exercise : Create a new Role
    • SubTopics in Topics
  • Pergapedia platform
Powered by GitBook
On this page
  • How to create Email Templates?
  • Standard templates
  • Action Step
  • Notification Step
  • Approval Step
  • Message
  • Request Additional Information
  • Request additional information answer
  • Custom Templates
  • Edit Custom Template
  • Dynamic Attachments

Was this helpful?

  1. Fulfillment Platform

Mail Templates

PreviousView example 2NextLayouts

Last updated 3 years ago

Was this helpful?

SSP 7 uses Mail templates for notification within processes. Most steps in a Process will send out a standard email to the selected Actor(s). Standard emails use a default template but you can also define custom email templates.

Modification of any standard email templates will automatically update all notification steps utilizing the updated templates. Custom configured templates will have to be maintained individually for each step containing notifications for all processes.

Its best practice to utilize mail templates where possible to ensure quick and easy updates.

The Email Templates screen is opened by clicking on the Templates link in Mail section in the Admin Panel.

clip0112

How to create Email Templates?

Find below print screen and explanation of how to create an email template:

  • Subject Line English : Fill in the Subject line to be used in this email.

  • Main Copy English : fill in the email body.

  • Subject Line & Main Copy other languages : fill in the appropriate values for the other languages, as set in SSP 7.

Standard templates

Action Step

An Action Step has the following Mail Templates:

  • Initial Email: This email is sent to the Actor when an Action Step is initiated.

  • Escalation level 1 Email: This email is sent to the escalation level 1 person in case the Actor of a process step has missed the defined deadline. The escalation person and the period of time (e.g. 10 days) after this email is sent are defined in the process step.

  • Escalation level 2 Email: This email is sent to the escalation level 2 person in case the Actor of a escalation 1 has missed the deadline. The escalation person and the period of time (e.g. 10 days) after this email is sent are defined in the process step.

  • Form sent back to requester Email: This email is sent to the requester in case additional information is required from the requestor and the form has been placed back in the drafts folder of the user.

  • Form changed Email: In case the original request form of a user has been altered during the process, the requestor is notified about that update with this email message

Notification Step

A Notification Step has one Mail Template: Initial Email: This email is sent to the Actor when an Action Step is initiated.

Approval Step

An Approval Step has six Mail Templates:

  • Initial Email: This email is sent to the Actor when an Action Step is initiated.

  • Decline Email: This email is sent to the Requester when this Step is not approved by the Actor(s).

  • Escalation level 1 Email: This email is sent to the escalation level 1 person in case the Actor of a process step has missed the defined deadline. The escalation person and the period of time (e.g. 10 days) after this email is sent are defined in the process step.

  • Escalation level 2 Email: This email is sent to the escalation level 2 person in case the Actor of a process step has missed the deadline. The escalation person and the period of time (e.g. 10 days) after this email is sent are defined in the process step.

  • Form sent back to requester Email: This email is sent to the requester in case that additional information or clarification to the request is required.

  • Form changed Email: In case the original request form of a user has been altered during the process, the requestor is notified about that update with this email message

Message

Message has one Mail Template: Initial Email: This email is sent to the Requester when a Message is filled in during a Ticket handled in the work flow.

Request Additional Information

"Request additional information" has one Mail Template:

Initial Email: This email is sent to the Requester when a "Request for Additional Information" is filled in during a Ticket handled in the work flow.

Request additional information answer

"Request additional information Answer" has one Mail Template:

Initial Email: This email is sent to the Actor when a "Request for Additional Information" is answered by the Requester, in during a Ticket handled in the work flow.

Custom Templates

Custom templates are used to define email messages that get regularly used in processes. Custom defined email templates are defined in the E-Mail templates admin panel and are referred to in process steps.

Please note that references used in custom templates should not be process specific, as these templates are used across multiple processes.

Filter : Use the search box and button to filter the list with email templates.

Edit Custom Template

When a new custom template is added or an existing Template is edited, the screen below is displayed:

Attachments

2 types of attachments can be added to an email defintion:

- Fixed : the attachment is always the same

- Dynamic : that attachment can be different based on parameters. The sources are : text files, PDF documents, CMC elements (Word or PDF)

Complete the following fields to define the attachments:

  • Add new fixed attachment : An attachment can be added to an email by clicking SELECT AND UPLOAD, locate the file on your PC or network. The attachment will always be included in the email message.

  • Add new Dynamic attachment : enter the name of the file to be generated & set the document location. Use the Dynamic field mapping to locate the definition of your PDF, text file or created CMC element (using previously entered fields). Click on ADD ATTACHMENT to add the file.

  • Subject Line English : Fill in the Subject line to be used in this email.

  • Main Copy English : Fill in the email body.

  • Subject Line & Main Copy other languages : Fill in the appropriate values for the other languages, as set in SSP 7.

Dynamic Attachments

The option of dynamic attachments is available within template emails and custom defined emails. Please note that PDF file generated within a process can only be send as an attachment in emails defined within the process generating the PDF files. Public mail templates can't use them.

Name: Here you can define the filename of the attachment. It is possible to use placeholder like #REPLACE-FORMFIELD-Lastname# for example. You need to define the file extension manually.

Document location: Set here a reference (URL or local path) to were SSP can find the attachment. Please note that the reference should be accessible for the server. If you want to include a generated PDF file, use the dropdown list and select Process. Under process you'll find the PDF file defined or a generic option to include the default PDF report.

clip0387

clip0388
clip0395
clip0376
clip0485
clip0486