-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Adapt Program Notification Template to new API [DHIS2-17502] #1394
base: master
Are you sure you want to change the base?
Conversation
@@ -2861,3 +2861,64 @@ See an example payload below: | |||
} | |||
``` | |||
|
|||
## Program Notification Template | |||
|
|||
The Program Notification Template feature enables you to create message templates that can be triggered by various types of events. These templates, including both the message and subject, will be dynamically translated into actual values and sent to a configured destination. Depending on whether the notification recipient is external or internal, each template will be transformed into either a `MessageConversation` object or a `ProgramMessage` object. These intermediate objects will only contain the translated message and subject text. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are the intermediate objects? Is that important for users to know?
] | ||
} | ||
|
||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
newline
@@ -2861,3 +2861,64 @@ See an example payload below: | |||
} | |||
``` | |||
|
|||
## Program Notification Template | |||
|
|||
The Program Notification Template feature enables you to create message templates that can be triggered by various types of events. These templates, including both the message and subject, will be dynamically translated into actual values and sent to a configured destination. Depending on whether the notification recipient is external or internal, each template will be transformed into either a `MessageConversation` object or a `ProgramMessage` object. These intermediate objects will only contain the translated message and subject text. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these templates metadata?
If so we would not need to add Retrieving and deleting Program Notification Template
apart from a parameters table for the ones we add on top of the CrudController. It would be enough to add something like
Since working lists are metadata refer to metadata on how to create, update and delete metadata.
No description provided.