[Home] - [Access to the platform] - [User management] - [DDS Config Manager] - [Bulletin App: Backend and Frontend] - [User Interface] - [Observations] - [Forecast Models] - [Static Layers] - [Events]
This guide explains how to configure and manage bulletin products through Django admin, then verify them in the operational editor.
It is organized around the two halves of every product: the schema, which defines what a bulletin contains, how it is initialized and what it produces, and the editors, which define who works on it and with which interface. No application-code editing is required for the standard configuration steps.
Conventions
Field names follow the admin models and may appear with spaces in the interface. YAML examples are editable text; preserve their indentation and exact identifiers. Training screenshots illustrate the resulting editor, and deployment-specific values are identified where needed.
MyDewetra Bulletin is a configurable system for producing recurring operational bulletins. Administrators define the structure, available tools and delivery rules in Django admin. Forecasters use the resulting bulletin editor to prepare each issue.
The family and its versions
A metaschema identifies a bulletin family, such as a national multi-hazard product. Its schemas are numbered versions of the definition. A schema describes the content fields, default values, workflow and outputs. Selecting a schema makes it the version used for new issues; selecting another version automatically deselects the previous one.
The bulletin and its editor
An instance is one real issue created from a schema. It contains the issue date, actual text, map values, status and generated files. Each instance remains linked to the schema version that created it.
An editor is a user-facing workspace for that product. Its roles control who can see it, and its capabilities control available actions. A detail editor configuration links that editor to a specific schema version and defines its tabs, widgets, permissions and previews.
| Object | Example | Purpose |
| Metaschema | Training CIMH | Groups versions of the same product. |
| Schema | Version 1.0 | Defines flood and wind maps, notes and a signature. |
| Initializer | DDS features plugin | Prefills a component from a data source when an issue is created. |
| Instance | The issue for a chosen date | Stores the values entered for that issue. |
| Editor | Training forecaster | Provides an interface for assigned roles. |
| Exporter | PDF Training | Creates a file using a print template. |
| Publisher | Training email | Sends content or links through a channel. |
One definition can support several views
Several editors can use the same schema while showing different hazards or granting different permissions. Reusing a mapset in two widgets also reuses its data: the widgets are views of the same component. Distinct hazards need distinct mapset components, even when they share the same geographical zones.
Open the admin address supplied for your deployment, usually ending in /admin/, and sign in through the configured account or portal. Confirm the environment and organization before editing records. The exact menu wording can vary with the installed version.
| Admin area or record | What you manage there |
| Bulletin meta schemas | Product families, ownership and the list of schema versions. |
| Bulletin schemas | Version settings, components and their initializers, flags, exporters and publishers. |
| Feature sets and warning level sets | Map zones and the available warning categories. |
| Bulletin editor groups | The connection between an editor group and a product family. |
| Bulletin editors | Editor roles, action capabilities and homepage configuration. |
| Detail editor configurations | Version-specific tabs, permissions, publishers and settings. |
| Bulletin instances | Issue dates, status, linked components, files and action history. |
Opening and saving a record
Access and ownership
Admin access and forecaster editor roles are separate. In the current portal integration, ordinary admin access uses the django-admin role; elevated access also requires the configured superuser role. Ordinary administrators see owned product records for their domain. Ownership fields may be read-only.
A missing product can therefore indicate the wrong domain or insufficient access. Ask your deployment administrator to check the account context before creating a duplicate. Schema, editor and instance fixture imports require superuser access in the current implementation.
The schema is the definition of a bulletin product. Everything in this part is configured on the metaschema, on a schema version or on records that a schema version uses, such as feature sets and warning level sets.
A schema version is complete when it defines the content fields, how they are prefilled, the workflow conditions, the files it produces and the channels that distribute them. Configure and test it before building the editors described in Part B.
Plan the bulletin content, geographical coverage, validity period and outputs before entering configuration. For a new product, create the family first and then its initial schema version.
| Field | Meaning and check |
| Selected | Activates this version for new issues. At most one version in the family can be selected; a family with none selected is not ready for normal creation. |
| Has range and Daysvalidity | When Has range is enabled, the end date is calculated from the issue date plus Daysvalidity. Verify the intended time coverage with a test issue. |
| Allow many | If off, the editor prevents creating another issue while an issue of that schema is open. Resolve the open issue before creating another. |
| Allow close with flags false | Controls the configured completion workflow. Keep it aligned with the required flags and test the close action. |
| Smart id template | Formats the issue identifier. Reuse a verified pattern and check a sample ID. Group id by controls the sequence grouping. |
| Timezone | Use the product’s required timezone. Check displayed dates and generated filenames around day boundaries. |
The schema list normally shows selected versions. To find older versions, choose the family in the Meta Schema filter or open the version links from its metaschema.
Changing a schema does not rebuild existing instance data. For structural changes, prepare a new version and matching detail editor configuration, then test a new instance. Section 15 describes the changeover.
Components are the data fields of the bulletin. Add them in the schema’s Bulletin Schema Components section and choose the required type. The editor widget and the print template will refer to each component by its Id string.
| Component type | Typical content | Configuration to check |
| TextSchema | Notes, discussion, signature | Template supplies the initial text; Language identifies its source language. |
| MapSetSchema | Hazard levels for zones and forecast times | Feature set, warning level set and map rows with forecast hours. |
| JSONSchema | Structured forms and values | The JSON structure and the matching form configuration. |
| RasterImageSchema | An image supplied for the issue | Image format and the configured initialization source. |
| DataPointsSchema | Values at stations or other points | Point set, variables, ordering and any thresholds. |
Stable component identifiers
Use short, descriptive identifiers such as flood_mapset, wind_mapset, notes_text and signature_text. An Id string must be unique within its schema version. It is a reference key, so spelling and case must agree wherever it is used.
For example, a rich text widget with schemas.text set to notes_text reads that TextSchema. A printed Schema text block must use the same tag. Changing only the label shown to the user does not change the underlying reference.
Defaults and automatic initialization
For manually authored text, put the starting value in Template. A signature can begin as “Duty Forecaster”; a notes field can start blank. Other components may initialize from a configured plugin or data source. Creating an issue can take time while those sources run.
Section 6 explains how to attach an initializer to a component, the available plugins and when initialization runs.
Optional translations
Text schemas can have translation rows with a target language, engine and optional template. Locked translations protect generated text from automatic overwrite. Translation services must be configured for the deployment, and translated operational wording still needs review.
A mapset combines geographical zones, a warning-level scale and one or more forecast times. The same FeatureSet can support several hazards, while each hazard keeps its own mapset and values.
Preparing a FeatureSet
The CIMH file barbados_boundaries.zip contains 14 features and includes fid, code and name columns. For this training file, the following mapping uses those existing columns:
{"fid": "fid", "code": "code", "name": "name"}
The automatic file import runs when a FeatureSet is created. Replacing the upload on an existing record is not a reliable reimport procedure. For revised boundaries, create and validate a new set, then use it in a new schema version.
Preparing levels and horizons
An initializer fills a component automatically from a data source or from another bulletin. When an issue is created, each component first receives its schema defaults and then runs its initializer, if one is configured. While initializers run, the issue is pending and the editor shows their progress and any warning or error.
Each component can have one initializer, configured inside the component row of the schema form in the Bulletin Component Initializer section. Choose Plugin initializer for new configurations. The older GeoJSON ingestion, Sentinel ingestion and DDS raster initializer types remain available for existing products.
Adding a plugin initializer
Available initialization plugins
The plugins below are general purpose. The Component column shows the component type each one supports (MapSetSchema, JSONSchema, RasterImageSchema or TextSchema); the plugin list in the form is filtered accordingly.
| Plugin | Component | What it does and main options |
| DDSFeaturesInitializer | Mapset | Reads a feature layer from a DDS and converts a numeric value per zone into warning levels. Set the DDS options, fid_column (the zone identifier in the layer), value_column and levels. Enable use_mapschema_hours to select the forecast lead time from each map’s hours, optionally shifted by mapschema_hours_offset. |
| RISICOInitializer | Mapset | Aggregates RISICO fire-danger model output from a DDS over the zones of a registered shapefile, using the most recent run of the last three days. Set dds_server, data_id, variable, level, shpname, shpfieldname (default name) and levels as value ranges. |
| WebAlertInitializer | Mapset | Imports hydraulic, hydrogeological or temperature criticality levels from a WebAlert service. Set webalert_base_url, webalert_user, risk_type, the zone code property in WebAlert (webalert_areas_property) and in the FeatureSet (bulletin_areas_property). Only map hours 0 (today) and 24 (tomorrow) are supported. |
| OtherMapSetInitializer | Mapset | Copies levels from the latest issue of another mapset with the same date. Set other_mapset as metaschema:version:id_string; must_be_closed uses closed issues only. maps_association pairs source and target hours (default: equal hours). If the FeatureSets differ, provide features_mapping or enable auto_feature_mapping; the highest severity wins where several source zones reach one target zone. |
| JSONFromDDSVectorInitializer | JSON | Selects a DDS vector layer and stores the attributes of its features as a list of rows. Set the DDS options and, optionally, columns to keep only some attributes. |
| GeoJSONIngestionPlugin | JSON | Loads a GeoJSON file from a URL or a server path. In path, $yyyy, $mm and $dd are replaced from the issue date, offset by days_after and days_before. An optional mask GeoJSON clips the loaded features. |
| RasterImageFromDDSPlugin | Raster image | Selects a DDS raster layer and renders it through the DDS map service, using the component’s bounding box, size, SRS and format. Optional background and foreground add map layers under or over the data. |
| RasterImageFromWMSInitializer | Raster image | Requests a PNG image from a WMS 1.3.0 service. Set wms_url, data_id (the layer name), optional credentials and query_params, whose values can use placeholders such as %date_iso% for the issue date. |
Some plugins are written for a single regional product. They are not described here.
Options shared by mapset plugins
Mapset plugins translate source values into the warning levels of the mapset. Each levels row selects a target severity from the component’s warning level set and states which source value produces it.
OtherMapSetInitializer can omit levels when both mapsets use the same warning level set.
DDS options
DDSFeaturesInitializer, JSONFromDDSVectorInitializer and RasterImageFromDDSPlugin select data from a DDS with the same set of options.
| Option | Meaning |
| dds_server | A DDS server registered in the backend configuration. |
| data_id | The DDS data or layer identifier. |
| days_before, days_after | Search window around the issue date for available data. The defaults are 10 and 1. |
| reference_time_filter | Optional filter on the data reference time: offset_hours from midnight of the issue date and tolerance_hours around that time. |
| forecast_lead_hours | Optional lead time, in hours, between the model run and the reference time. Leave it empty to disable the filter. |
| selectors | Optional name and value pairs that must match the DDS layer attributes. |
Conditional initialization and reinitialization
If a component has Init when flags, it is not initialized when the issue is created. It initializes when the last of those flags becomes true, for example after a preceding review is complete. Section 7 describes flags.
Reinitializing an existing component can replace entered values. Use that function only when the source, target issue and expected replacement are clear.
A configuration error, such as a missing required option or an unknown DDS server, stops initialization. Test a new or changed initializer in a training environment before selecting the schema version.
The normal issue lifecycle
An issue starts open. Initialization may temporarily make it pending. Forecasters complete the content and check previews, then close the issue. Closing runs the configured exporters and any publishers triggered by close. The publication action can subsequently run publishers triggered by publish.
Closing runs the exporters with Run on close in their Order, then the publishers with Run on close. If an exporter fails, the issue is reopened. A publisher failure is recorded in its publishing result and does not reopen the issue. Only a closed issue can be published.
| State or control | Operational meaning |
| Open | The issue is available for editing, subject to permissions and locks. |
| Pending | Background processing is underway. Wait for completion before proceeding. |
| Closed | Normal content editing has ended. Check generated files before dissemination. |
| Published | The issue has the published state. This alone does not prove successful delivery on every channel. |
| Session reservation | An active editing session may prevent another session from taking the same editing access. |
Flags support staged work
Schema flags define named workflow conditions. Each new issue starts with corresponding flag values set to false. Examples might represent a completed hazard review or a completed section, but the names and required sequence belong to the product configuration.
An exporter creates an output file for an issue. Files created on close are stored in the issue’s Exported files, where users can download them and publishers can reference them. Add exporters in the schema’s Bulletin Exporters section and choose one of two types.
Exporters run on close in ascending Order. Run on skip excludes an exporter from the automatic close export.
Adding a print exporter
| Setting | What to check |
| Id string | Must match previews[].exporter, such as pdf. |
| Client component | Must name a real registered print template. A typed name does not install a template. |
| Client options | Layout settings understood by that particular template. |
| Options | Print-service options. These are separate from Client options. |
| Print filename template | Use a tested naming pattern and verify the generated name and extension. |
| Has preview and Run on | Preview availability and automatic export timing are separate controls. |
Adding a plugin exporter
Shapefile exporter
ShapeFileExporterPlugin exports the zones of one FeatureSet as a zipped ESRI shapefile. Each zone keeps its fid, code, name and source attributes, and the exporter adds one column for each selected map.
| Plugin option | Meaning |
| featureset | The FeatureSet shared by the mapsets to export. |
| columns | One entry per output column. map selects a mapset and its forecast hours; column is the attribute name; value is a warning-level field such as severity or name, or meta.<field> for a value stored by the initializer. |
| filename | Base name of the files inside the ZIP. The default is shapefile. |
Shapefile attribute names are limited to 10 characters. Use short column names such as flood_d0 and wind_d1.
Filename templates
Print filename template and Filename template accept the placeholders below. Print exporters use the issue’s last modification time in the schema timezone; plugin exporters use the issue date. The same placeholders work in the headerTemplate and footerTemplate of a print exporter’s layout Options.
| Placeholder | Result |
| %year% | Four-digit year, for example 2026. |
| %month%, %day%, %hour%, %minute% | Two-digit values, for example 09. |
| %id% | Issue sequence number with three digits; %id:5% sets five digits. |
| %date%, %datetime% | 2026-09-15 and 2026-09-15 12:30:00. |
| %date::+1d% | Any placeholder can add an offset in days (d), hours (h), minutes (m) or seconds (s). |
For example, training_%date%_%id%.pdf produces training_2026-09-15_007.pdf. Verify the result on a closed test issue.
A publisher distributes bulletin information through a configured channel, such as email, SMS, Telegram or an API. Decide the recipients, message content, attachments or links, and trigger before enabling it.
| Publisher Run on | Meaning |
| close | Runs automatically during the close workflow, after the close exporters. Closing can therefore send messages. |
| publish | Runs when the bulletin publication action is performed. |
| request | Used by the explicit publisher request workflow. |
| skip | Excluded from the automatic close and publish trigger matching. It is not an access-permission control. |
New publishers default to skip. Set Run on explicitly once the publisher has been tested.
Publisher types
| Publisher type | Settings |
| Email publisher | Sender, Addresses, Subject template and Body template. Messages are sent through the deployment’s Mercurius mail service. |
| SMS publisher | Phone numbers and Body template. Messages are sent through the Mercurius SMS service. |
| Telegram channel publisher | Bot Token, Channel, Parse mode (plain, HTML or MarkdownV2) and Template. |
| API publisher | API endpoint. The issue is posted as JSON. For authentication, set auth_token in Options, with optional auth_header (default Authorization) and auth_prefix, such as Bearer. |
Message templates
Subject, body and Telegram templates use Jinja2 syntax. The variable bulletin holds the issue in a flat form: smart_id, date, dateto, is_open, is_published, exported_files and components keyed by component Id string. Text components expose text; JSON components expose value. Each key in Template data becomes an additional variable.
Subject: Bulletin {{ bulletin.smart_id }} of {{ bulletin.date }}
Body: <p>{{ bulletin.components.notes_text.text }}</p>
<p>{{ bulletin.components.signature_text.text }}</p>
Check the rendered message on a test destination. A template error is recorded as a publishing error for that channel.
Adding a publisher
Delivery results need their own check
PublishingStatus records show states including empty, draft, sending, sent and error, together with response and error information where available. The issue’s Is published field is a separate state: an individual publisher can record an error even when the issue is marked published.
Before retrying, check which channels already succeeded. A repeated send can deliver a duplicate message. Unpublish changes the bulletin’s publication state; it does not recall email, SMS or Telegram messages that recipients already received.
Each publisher runs independently. A failure is recorded in its own result and does not stop the following publishers.
Editors are the user-facing workspaces built on a schema. Everything in this part is configured on editor groups, editors and their detail configurations.
An editor defines who sees the product and which actions they can take. Its detail configuration binds it to one schema version and defines the tabs, widgets, component permissions, previews, publishers and settings dialogs. Several editors can serve the same schema with different views or permissions.
The editor group connects a family to its user-facing editors. Build the group and editor first, then create the version-specific detail configuration inside the editor form.
| Capability | What it permits |
| Can create | Creates a new issue, subject to the selected version and open-issue rules. |
| Can close | Closes an open issue through the configured workflow. |
| Can publish and Can unpublish | Changes publication state through the operational actions. |
| Can clone | Creates another issue from an existing issue when the workflow permits it. |
| Can delete | Allows issue deletion when permitted by its state. |
| Can change date | Allows date changes when the instance supports them. Also enable canChangeDate in the detail configuration options. |
Component permissions are a separate step
Save the detail configuration to create or synchronize its Permissions rows. Newly created rows have Can patch instance off by default. Turn it on for each component that this editor must save, then save again.
A visible field is not necessarily editable. A widget’s readonly setting affects the interface; Can patch instance is the server-side save permission. Check both. After adding a component or changing the bound schema, save and reopen the detail configuration and review every permission.
To create a review-only profile, reuse the family and schema but restrict the capabilities and component permissions. Validate it using an account with that profile’s roles.
The Configuration field on BulletinEditor controls the homepage or list of issues. It has a different purpose from the Configuration field on the detail editor. Paste the homepage YAML here, preserving spaces and indentation.
actions:
- edit
- download
- delete
- close
columns:
- is_open
- is_published
- timestamp
- last_modified
hasSettings: true
This is the homepage example supplied with the CIMH training. Actions lists the requested row actions; Columns selects status and date information. HasSettings requests the settings entry. The available controls still depend on permissions, configured settings and the issue state.
Save the editor, reload the bulletin application, and check the headings and row actions with the intended user role. A missing action can result from a capability or state restriction even when it appears in this YAML.
Open the detail configuration linked to the required schema version. Its Configuration field defines the editing workspace: tabs contain widgets, schemas connects widgets to stored components, and previews identifies available exporters.
| YAML | Purpose |
| tabs | The editor’s named sections and their layout. |
| components | The widgets shown inside a tab. |
| client_component | Exact installed widget name, including its module. |
| schemas | Maps a widget input, such as text or map, to a component Id string. |
| options | Widget-specific display or behavior settings. |
| previews | Preview labels and exporter Id strings. |
| settings | Settings dialog definitions linked to Available Settings records. |
A minimal text and map tab
tabs:
- name: Bulletin
layout: scroll
components:
- label: Notes
client_component: DynamicComponentsModule#RichTextComponent
schemas: {text: notes_text}
options: {}
- label: Flood maps
client_component: DynamicComponentsModule#MapSetComponent
schemas: {map: flood_mapset}
options: {shownMaps: [0, 24]}
previews:
- label: PDF Training
exporter: pdf
This example requires notes_text and flood_mapset on the bound schema, map hours 0 and 24, and an exporter whose Id string is pdf. It does not create those records. Save the configuration, enable the relevant Permissions rows, and test a new issue.
Use spaces for YAML indentation. Keep module names, key names and tags exactly as shown. Do not paste both blocks from the training settings.yaml file into one field: its EDITOR SETTINGS and EDITORDETAIL SETTINGS headings identify two different destination records.
Enable conditions and editing sessions
Two detail configuration fields connect the editor to the schema flags described in section 7.
Session completion and closing are different actions
An End session action can mark work complete and release the session without closing the bulletin. Use the button names and workflow supplied for the product. Avoid creating circular flag dependencies, such as requiring a flag to enter the only editor that can set it.
If another user has the session, coordinate with that user. Ask support to inspect a stale reservation rather than repeatedly opening competing sessions. Multiple editor profiles can serve the same bulletin, but simultaneous editing remains subject to the configured access locks.
The detail configuration references records defined on the schema. Each reference must resolve on the schema version bound to that detail configuration.
Previews
Each previews entry adds a preview with its label. Its exporter value must be the Id string of a print exporter on the same schema version with Has preview on, as described in section 8.
previews:
- label: PDF Training
exporter: pdf
A preview is generated on demand and is not stored. Preview generation is not a replacement for checking the stored final PDF after close.
Print layout settings dialog
If the deployment exposes the custom print layout editor, add an Available Settings record of type PrintExporterSettings, select the print exporter, and give it an Id string such as settings_print_layout. Add a matching settings entry to the detail YAML with the installed settings component.
The reference Custom Bulletin Editor end-user guide explains the visual layout workflow. Use it after the schema tags, map hours and exporter are correctly connected.
Publishers offered in the editor
In the detail configuration’s Publisher section, add each schema publisher that users of this editor should be offered, and configure its options. Enable Can publish on the editor when users need the publication action.
This section controls what the editor offers. Publishers with Run on close or publish still run automatically with those actions, whether or not they are listed here.
Editable recipient settings
If users should maintain email recipients, configure an EmailAddressesSettings record connected to the email publisher and a matching settings dialog entry. Restrict access to the appropriate editor roles. A preview entry, publisher entry and settings entry each reference different records.
This part applies to both halves of the configuration: monitoring real issues, versioning a product, a complete training exercise, troubleshooting and a quick reference.
Use the operational bulletin editor for normal create, edit, close and publish actions. These actions run the initialization, export and publication workflows. Django admin is useful for inspecting an issue and its related records.
Directly saving a lifecycle checkbox in admin is not equivalent to running Close or Publish. It can change the recorded state without executing the normal side effects. Use workflow actions for operational transitions and reserve direct record corrections for a controlled support procedure.
If a closed bulletin needs a correction, follow the organization’s reissue procedure. Where cloning is permitted, inspect the new issue’s date and all copied values before issuing it. Do not assume cloning refreshes external data.
Treat a schema version, its components, editor configuration and print outputs as a connected set. A new version can use the same logical tags while changing its structure, but every reference must resolve within that version.
Preparing a new version
The export formats
| Admin export | Typical use |
| Schema JSON | Preserves the selected schema records and the dependencies collected by the export. |
| Editor or detail configuration JSON | Preserves editor configuration records for review or transfer. |
| Bulletin instance ZIP | Contains fixture.json and exported files for the selected issue or issues. |
| Print layout export | Preserves visual layout settings from the custom print editor; it is not a complete product backup. |
Use the export button or selected-record action for the exact scope required. Name backups with the family, schema version and date. Keep them in the organization’s controlled storage.
Imports can update existing records matched by their identifiers and depend on the destination’s related records. Have an authorized administrator inspect the target and backup before import. Configuration fixtures do not by themselves install print templates, plugins, service credentials or external assets.
This exercise extends the CIMH material into one complete training product: flood and wind maps on the same Barbados zones, rich text notes, a plain text signature and a PDF. The names below are example choices for a training environment.
| Record | Training value |
| Metaschema | training-cimh-admin |
| Schema | Version 1.0; selected when ready for the test |
| FeatureSet | A new training set imported from barbados_boundaries.zip |
| Mapsets | flood_mapset and wind_mapset |
| Map hours | 0 and 24 on each mapset |
| Text components | notes_text and signature_text |
| Editor group and editor | CIMH training; CIMH training forecaster |
| Print exporter | Id string pdf; Name PDF Training |
Build the schema
Build the editor records
Create the editor group, forecaster editor and detail configuration for version 1.0. Assign the training role and enable creation and closing. Use the homepage YAML in section 11 and the complete detail YAML in section 17. Enable Can patch instance for all four components.
Paste this example into the detail configuration for the training schema. Each map widget displays both defined forecast hours. The two hazards share geography but save independent map values.
tabs:
- name: Hazards
layout: scroll
components:
- label: Flood
client_component: DynamicComponentsModule#MapSetComponent
schemas: {map: flood_mapset}
options: {shownMaps: [0, 24]}
- label: Wind
client_component: DynamicComponentsModule#MapSetComponent
schemas: {map: wind_mapset}
options: {shownMaps: [0, 24]}
- name: Text
layout: scroll
components:
- label: Notes
client_component: DynamicComponentsModule#RichTextComponent
schemas: {text: notes_text}
options: {}
- label: Signature
client_component: DynamicComponentsModule#SimpleTextComponent
schemas: {text: signature_text}
options: {}
previews:
- label: PDF Training
exporter: pdf
Optional print layout settings
If the matching settings module is installed, add the following top-level settings block after creating the PrintExporterSettings record described in section 13. Its Id string must be settings_print_layout and it must point to pdf.
settings:
- label: Print Layout
setting_id: settings_print_layout
client_component: >-
EditorSettingsComponentsModule#PrintLayoutSettingsEditorComponent
The folded YAML value after >- is one component name. If the installed deployment uses a different print template or settings interface, use its verified configuration. Save and reopen the detail form to check that the YAML and permissions persisted.
Connect the printed content
Run an issue through the whole workflow
Expected result
If a check fails, correct the corresponding configuration record and repeat the affected step. Use a new instance after structural schema changes; an existing instance does not automatically acquire new component data.
| Symptom | What to check |
| The admin product is missing | Confirm environment, domain and admin access. Ownership filtering can hide another domain’s records. |
| The forecaster cannot see the editor | Check editor Roles against the account’s actual roles, then refresh the application. |
| An old schema version is missing from the list | Choose the family in the Meta Schema filter or open its metaschema version links. The default schema list shows selected versions. |
| New issue is unavailable | Check Can create, the selected schema, a matching detail configuration and any existing open issue when Allow many is off. |
| A tab or widget is empty | Check YAML indentation, the exact installed client_component name and schemas mappings on the bound version. |
| The plugin list is empty or the options form is blank | Only plugins supporting the component type are listed. Save and continue editing after choosing a plugin so that its options form loads. |
| A field displays but cannot save | Check Can patch instance and readonly. Also check whether the issue is open, pending or reserved by another session. |
| Tomorrow is missing or repeats today | Check MapSchema hours and shownMaps. Hours 24 must exist and be selected where tomorrow is intended. |
| Map zones or labels are wrong | Check the FeatureSet, source-column mapping, loaded features and any widget filters or overlays. |
| A new field is absent from an older issue | Schema changes do not materialize new component instances into existing issues. Test a newly created issue. |
| Print Layout or recipient settings are missing | Check the Available Settings record, matching setting_id, installed settings component and the editor’s settings options. |
Useful information for support
Provide the environment, product family, schema version, editor name, issue ID and the exact action that failed. Include the time and visible error message, plus the affected component or exporter identifier. Redact credentials and unnecessary recipient details.
| Symptom | What to check |
| The issue stays pending or disappears after creation | Initialization may have failed. Ask support to inspect the initializer and backend logs before retrying repeatedly. |
| Initialization reports no data found | The source had no data for the issue date. Check the plugin’s date window and the source. With Fail if no data off, the issue keeps default values and shows a warning. |
| A component keeps its default values | Check that it has an initializer, that no Init when flags are pending, and the plugin options such as levels, column names and forecast hours. |
| Close is unavailable | Check Can close, issue state, the configured completion flags and any frontend option that hides Close. |
| The issue becomes open again after close | A close export or other close-processing step may have failed. Check the print service, exporter settings and logs. |
| Preview is unavailable | Check Has preview, the detail previews entry and the matching exporter Id string. |
| Preview works but no stored PDF appears | Check Run on close and the outcome of the close operation. A preview does not save a final exported file. |
| A shapefile or other plugin file is missing | Check the Plugin exporter’s Run on, Plugin options and the close outcome. A configuration error in the plugin reopens the issue. |
| The printed content is empty or wrong | Check the print template, tags and forecast hours against the issue’s schema version. Check that required assets are installed. |
| Published is true but a message was not received | Inspect the specific PublishingStatus, error and provider response. Publication state is not proof of delivery. |
| A close action sent a message unexpectedly | Review every publisher with Run on close before the next test or issue. |
| A retry sent duplicate messages | Check which publishers had already succeeded. Agree the intended retry scope before sending again. |
| Unpublish did not remove a received message | Unpublish changes the bulletin state. Already delivered messages remain with their recipients. |
A useful recovery sequence
Identify the affected issue, inspect its state and action history, then check component initialization, exported files and individual publishing results. Correct the cause before repeating the workflow. After a configuration repair, validate a test issue before returning the product to normal use.
Recommended configuration order
References that must match
| Configuration reference | Must resolve to |
| Editor group Meta schema | The family containing the intended schema versions. |
| Detail configuration Schema | The exact version used by the issues it edits. |
| components[].schemas.* | A component Id string on that schema version. |
| previews[].exporter | An exporter Id string on that schema version. |
| OtherMapSetInitializer other_mapset | A mapset written as metaschema:version:id_string. |
| Shapefile exporter columns[].map | A mapset and map hours using the exporter’s FeatureSet on that schema version. |
| settings[].setting_id | An Available Settings Id string on the detail configuration. |
| Map shownMaps values | Hours present in that mapset’s MapSchema rows. |