My goal is to validate whether system‑provided parameters supplied by Identity Security Cloud are correctly populated and rendered in email templates, prior to using them in production.
Some of these parameters are only populated by the ISC system itself at runtime, and reproducing the actual trigger conditions that generate them is difficult and time‑consuming.
Because of this, I would like to test the email content without having to reproduce the original trigger events.
I initially tried the email test feature in the UI, but noticed that some system parameters are not rendered correctly in that test output.
As a next step, I attempted to use the Send Test Notification API via Postman, explicitly setting parameter values in the request payload. However, this also did not allow me to validate how certain system/global parameters are rendered in the final email.
Given this context, I would like to ask:
-
Is there a supported or recommended way to validate email templates that rely on system‑generated parameters, without reproducing the original trigger conditions?
-
Are there best practices for testing or previewing how ISC‑provided parameters are populated in emails (for example, via a specific test mechanism, workflow, or alternative approach)?
The ultimate objective is to verify the final email output (including system parameters) before production use, while avoiding the need to recreate complex trigger scenarios.
Any guidance or recommended testing approach would be greatly appreciated.
-Nandika
