Appearance
Workspace tools
Three small Studio screens that are not designers: the Application Launcher, the Calendar and the Master Data of Localization. They are operational pages; what they show is not authored or versioned content.
App Launcher
Where to find it
Workspace > Navigation > App Launcher.
What it shows
A live preview of every application of the workspace as a launcher tile, built from the fields of each application's Details tab (see Applications and Features): icon, colour, badge text, sequence and category. One tile is shown per application name, preferring the published version and otherwise the highest version.
Views
| View | Description |
|---|---|
| Grid | The runtime application tile block, exactly as end users see it. |
| List | A plain list of the same applications. |
| Category | Applications grouped by their Category field. |
When both tiers exist, the Platform tier is listed apart from the Solution tier.
Changing what appears
The launcher has no settings of its own. Change an application's Sequence (lower first), Category, Badge text or Tier on its Details tab.
Calendar
Where to find it
Workspace > Navigation > Calendar.
What it shows
A month grid of events from two sources: native events that people create here, and events contributed by modules that ship a calendar contribution, for example leave, holidays and training. Contributed events are read only. Only native events can be edited or deleted. The grid loads the visible month plus the month before and after.
Event fields
| Field | Description |
|---|---|
| Title | Required. The Save button is disabled while empty. |
| Description | Optional. |
| Category | meeting (default), task, deadline, reminder, leave, holiday, training, birthday, other. Each has its own colour. |
| Start, End | Date and time. A new event defaults to 09:00 to 10:00 on the clicked day. |
| All day | An all-day event. |
| Visibility | private by default. The scope controls who else sees the event. |
| Recurrence rule | Optional recurrence expression (API field recurrenceRule). |
Select a day to create an event; select a native event to edit it.
API
| Action | Endpoint |
|---|---|
| List events in a range | GET /api/v1/authoring/calendar/events?from=&to= |
| Create | POST /api/v1/authoring/calendar/events |
| Update, delete | PUT, DELETE /api/v1/authoring/calendar/events/{id} |
Calendar synchronisation with outside calendars is provided by the calendar sync endpoints and connectors; see Integrations.
Master Data (Localization)
Where to find it
Workspace > Solution > Localization > Master Data.
What it does
Maintains the lists that every language, locale, time zone, date format, time format, currency and week-start picker reads. Preferences, the workspace localization defaults and the runtime locale widget all read these lists; none of them has a hard-coded list.
Tabs and fields
One tab per list: Language, Locale, Timezone, Date Format, Time Format, Currency, Week Start.
| Field | Description |
|---|---|
| Code | The value stored, for example en-IN, Asia/Kolkata, INR. |
| Label | The text shown in pickers. |
| Sort | Order within the list; lower first, ties broken by code. |
Rows can be added, edited inline, deactivated and deleted. A deactivated row stops being offered but stays for existing values.
API
GET /api/v1/localization-master-data/catalog returns the catalogue pickers use; GET, POST /api/v1/localization-master-data/entries and PUT, DELETE .../entries/{id} maintain it. The effective values for a user come from GET /api/v1/localization/effective, and the workspace defaults from GET /api/v1/localization/tenant-defaults. See also Add translations.
Related
Applications and Features, Navigation Designer, Users and Access: Preferences.