Dates and advanced configuration
The module/feature dialog edits a complete mutable configuration. Saving replaces all mutable fields, so preserve the values you intend to keep.
Field reference
| Field | Rule | Example |
|---|---|---|
| Code | Select from the offered module/feature catalogue | The approved module code |
| Enabled | Stored on/off choice | Enabled for a planned rollout |
| Effective from | Optional start; empty means open-ended | Approved future start time |
| Effective to | Optional end; must not precede start | Planned end of a temporary feature |
| Advanced configuration (JSON object or null) | Valid JSON object or null; not an arbitrary scalar or array | null when no documented configuration is required |
The dialog displays the browser's time zone. Local date/time entries are converted to instants for the server. Confirm the displayed zone before coordinating a rollout across offices; a user's browser zone is not necessarily a Care facility's medication-scheduling zone.
Example: planned rollout
Ali prepares a future module start for an agreed local time. Before that time, Configured enabled may be Yes while Within configured period and Available now are No. Do not repeatedly toggle the module to fix an intentional future start. After the start, refresh and inspect dependencies/entitlement if runtime availability is still false.
JSON examples
Use null when the capability does not require a configuration payload:
null
An empty object is syntactically different:
{}
Do not invent settings such as allowAllUsers or assume the backend consumes arbitrary keys. Use only a module's documented schema and approved values. Valid JSON syntax is not proof that the settings achieve an operational result.
Save failure
| Message/situation | Recovery |
|---|---|
| End precedes start | Correct the date order |
| Invalid configuration | Correct JSON syntax/type without discarding intended settings |
| Server rejects save | Read its message; the dialog preserves the draft |
| Someone changed the row meanwhile | Refresh the latest version and reconcile approved changes |
| Save succeeds, runtime unavailable | Recheck entitlement, dates and dependencies |
Configuration details expose Created/Updated timestamps, actors and version metadata. Use them to reconcile changes; they are not a full business approval record.