Templates and versions
The content of each message, versioned, with the approval that released it.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
Each template as a versioned record with its content, the message type it serves, and the validate → approve → publish sequence that releases a wording change — so what a customer received can be established afterwards.
What has to exist first
- Reads
- staffCommTemplatesList
- Actions
- staffCommTemplateSave
- staffCommTemplateValidate
- staffCommTemplatePublish
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.