...
Default templates will be stored in sunbird middleware(learner service) and configuration for the template will be stored as form config. Default template can also be configured at the installation time using Form API's.
Below is the sample template configuration for different content review workflows stored in form service.
Publish
{
"request": {
"type": "notification",
"action": "publish",
"subType": "email",
"data": {
"templateName": "publishTemplate"publishedTemplate",
"action": "publish",
"fields": [{
"body": "Congratulations! The content that you had submitted has been accepted for publication. It will be available for usage shortly. <br> <br><b> Content <br><br><b>Content Type: </b>{{Content type}}<br> <b> Content Title<br><b>Title: </b>{{Content title}}<br> <b>Content Link<br><b>Link: </b>{{Content link}}<br>",
"subject": "Congratulations, your content is live! Content Type: {{Content type}}, Title: {{Content title}}",
"logo": "https://dev.open-sunbird.org/assets/images/sunbird_logo.png"
}]
}
}
}
Request Changes
{
"request": {
"type": "notification",
"action": "requestChanges",
"subType": "email",
"data": {
"templateName": "requestChangesTemplate",
"body": "Congratulations! The content that you had submitted has been accepted for publication.It will be available for usage shortly. <br> <br><b> Content Type: < /b>{{Content type}}<br> <b> Content Title: </b>{{Content title}}<br> <b>Content Link: </b>{{Content link}}<br>",
"subject": "Congratulations, your content is live!",
"logo": "https://dev.open-sunbird.org/assets/images/sunbird_logo.png"
}
}
}
...