thinkwise-software-factory-messages

Create a msg row with a purpose-based msg_id, severity, and msg_location_id, then add one transl_object_transl row per application language using type_of_object 4. For choice messages, add msg_option rows with response_type and status codes, then wire the caller via SQL, a task confirmation, or a process flow action.

Call the tsf_send_message subroutine with msg_id, parmtr_string, and abort_ind parameters. Build the parameter XML with for xml path('text') so special characters are escaped, and pair an aborting call with an explicit rollback and return since abort does not roll back transactions automatically.

Configure msg_error_code, msg_regular_expression, and priority on a msg row so the engine error is captured and replaced with localized text. Give business-specific captures a lower priority number than the generic base-model captures at priority 100, and anchor the specific constraint name in the regex.

A msg_option's translated label is keyed by its bare msg_option_id, not scoped by msg_id, so every message using the option id yes shares one translation row. Editing it changes the label everywhere; create a distinct msg_option_id like yes_continue when a message needs its own wording.

Use a show_msg process action and capture the status_code output into a process variable via the pre-seeded process_action_modeler_fixed_output row, then branch with decision actions on the numeric status codes. For a simple binary yes/no message, the last_process_action_successful step condition is sufficient.

Avoid popups for routine feedback, successful saves, and Defaults or Layouts logic that fires frequently, since interrupting dialogs train users to dismiss them unread. Use panel or snackbar locations for non-blocking status, and reserve popups for errors, warnings, and choices that genuinely require attention.