Knowledge Base Academy Community My Tickets

Home Knowledge Base Academy Community My Tickets

Fabric 8.2

Fabric 8.3 Fabric 8.2 Fabric 8.1 Fabric 8.0 Fabric 7.2 Fabric 7.1 Fabric 7.0 Fabric 6.5

Knowledge Base Using Translations in Fabric

Using Translations in Fabric

Translations can be used in the Table Population of an LU table, a Reference table or a Parser Map when a specific set of Data Transformation rules is required. Translations can also be used in any Fabric Project functions or Web Services.

Go to Project Tree > Logical Units > [LU Name].
Click Tables > [Table Name] > [Table Population]
Click the Objects tab in the right panel of the Table Population working area.
Click Translations and then click the Translation in the list. The list includes the Translation objects defined under the selected LU and under the Shared Objects.
Drag the Translation to the working area.
Connect the Translation’s Input and Output fields to the Table Columns, as follows:
- Translation Input fields can be either connected to the Source Object or other Fabric objects, attached to the Table Population like functions or Lookups.
- Translation Output fields can be connected either to the Target Object or other Fabric objects, attached to the Table Population like functions or Lookups.

How Do I Add a Translation to a Parser Map?

Go to Project Tree > Logical Units > [LU Name].
Click Parsers > [Parser Map].
Click the Objects tab in the right panel of the Parser Map working area.
Click Translations and then click the Translation in the list.
Drag the Translation into the working area.
Connect the Translation’s Input and the Output fields.
- Translation Input fields can be either connected to the Source Object, other Fabric objects or attached to the map like functions or lookups.
- Translation Output fields can be connected either to the Target Object, other Fabric objects or attached to the map like functions or lookups.

Translations can be used in any Project functions defined in Fabric.

Translations used in an LU function can be defined either on an Logical Unit or on a Shared Objects level.
Translations used in Web Services must be defined on a Shared Objects level. When editing a Java file, two built-in functions are available and displayed in the Objects tab.

Built-in Function	Description
getTranslationValues	Format	Map <String><String>(String translationName, Object[] inputs)
	Description	Returns the Translation’s Output parameters based on the Input parameter/s.
	Input	Translation input fields.
	Output	Translation output fields.
getTranslationsData	Format	Map<String,Map<String,String>>(String translationName)
	Description	Returns full Translation data based on the Translation name.
	Input	Translation name.
	Output	Translation data.

Go to Project Tree > Logical Units > [LU Name].
Click Tables > [Table Name] > [Table Population]
Click the Objects tab in the right panel of the Table Population working area.
Click Translations and then click the Translation in the list. The list includes the Translation objects defined under the selected LU and under the Shared Objects.
Drag the Translation to the working area.
Connect the Translation’s Input and Output fields to the Table Columns, as follows:
- Translation Input fields can be either connected to the Source Object or other Fabric objects, attached to the Table Population like functions or Lookups.
- Translation Output fields can be connected either to the Target Object or other Fabric objects, attached to the Table Population like functions or Lookups.

Go to Project Tree > Logical Units > [LU Name].
Click Parsers > [Parser Map].
Click the Objects tab in the right panel of the Parser Map working area.
Click Translations and then click the Translation in the list.
Drag the Translation into the working area.
Connect the Translation’s Input and the Output fields.
- Translation Input fields can be either connected to the Source Object, other Fabric objects or attached to the map like functions or lookups.
- Translation Output fields can be connected either to the Target Object, other Fabric objects or attached to the map like functions or lookups.

Translations can be used in any Project functions defined in Fabric.

Translations used in an LU function can be defined either on an Logical Unit or on a Shared Objects level.
Translations used in Web Services must be defined on a Shared Objects level. When editing a Java file, two built-in functions are available and displayed in the Objects tab.

Built-in Function	Description
getTranslationValues	Format	Map <String><String>(String translationName, Object[] inputs)
	Description	Returns the Translation’s Output parameters based on the Input parameter/s.
	Input	Translation input fields.
	Output	Translation output fields.
getTranslationsData	Format	Map<String,Map<String,String>>(String translationName)
	Description	Returns full Translation data based on the Translation name.
	Input	Translation name.
	Output	Translation data.