Is there an overview of all MessageTypes? E.g. what can I expect? And what do the other parameters do?
Best answer by Vincent Doppenberg
Hello René,
The TSFMessages header has not been documented because we assumed it would only be used by our own GUIs. With that said, Indicium can return the following MessageTypes:
IndiciumMessage. These are messages produced by Indicium and only contain a MessageID and NamedParameters.
ApplicationDbMessage. These are messages produced by tsf_send_message and only contain a RawMessage with the XML produced by that procedure.
TechnicalDbMessage. These are error messages produced by the database, for instance a primary key a violation. They contain a MessageID and NamedParameters.
The MessageID property can map to a message in the application model (you can define messages in the SF with their translations for various languages). The NamedParameters property is a JSON array containing JSON objects with the properties Key and Value. These parameters depend on the message but typically contain context information for the message, such as the name of the table the message applies to. The value of Key can be used in the translation, enclosed by brackets, like {table} and a GUI will replace that placeholder by the value of Value.
The TSFMessages header has not been documented because we assumed it would only be used by our own GUIs. With that said, Indicium can return the following MessageTypes:
IndiciumMessage. These are messages produced by Indicium and only contain a MessageID and NamedParameters.
ApplicationDbMessage. These are messages produced by tsf_send_message and only contain a RawMessage with the XML produced by that procedure.
TechnicalDbMessage. These are error messages produced by the database, for instance a primary key a violation. They contain a MessageID and NamedParameters.
The MessageID property can map to a message in the application model (you can define messages in the SF with their translations for various languages). The NamedParameters property is a JSON array containing JSON objects with the properties Key and Value. These parameters depend on the message but typically contain context information for the message, such as the name of the table the message applies to. The value of Key can be used in the translation, enclosed by brackets, like {table} and a GUI will replace that placeholder by the value of Value.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
