generalForm.addField(OfferProps.NAME, Fields.string()
.label("offers.fields.name")
.order(1000)
.required()
.translatable())
The Broadleaf Admin can be used to manage field level translations for translatable entities.
Enabling translation admin capabilities is done by declaring the field or view as translatable in
the metadata. The example below shows a field being constructed with metadata. The last function
call to translatable()
lets the admin know this field should participate in translation mode.
Example
generalForm.addField(OfferProps.NAME, Fields.string()
.label("offers.fields.name")
.order(1000)
.required()
.translatable())
Note
|
See Data Translations for more information on making an entity translatable. |
If an entity supports translations, then you can engage translation mode in the admin and make the edits directly on the chosen entity.
Once, in translation mode, the translatable fields will be editable. The diagram belows shows an example. Translation changes are saved, promoted, approved, and deployed just like other field changes in the admin. Notice that the non-translatable fields still show in translation mode but are not editable.