Naming Convention

‌Cinchy is built as a simple, business user friendly application. This means that you should use business friendly terms to name your tables and columns. For example, you want to name a column “Full Name” rather than full_name, fullName, fName etc.‌‌

Domains

‌Domains essentially act as folders to be able to organize your data. Generally you will want to split domains by business lines (ex. Sales, Marketing, Human Resources, Product Development). The key thing is to keep it consistent so users have a general idea where to go to find information.‌‌

Descriptions

‌You can add descriptions to your tables and columns. Descriptions allow other users to use data in a more self-serve fashion, and also helps prevent misunderstandings of the meaning of your data.‌‌

Table descriptions are shown in the My Network screen, and will show up in search as well.‌‌

Translate API

Translation API

POST <Cinchy-URL>/API/Translate

Pass in a list of literal GUIDs, along with a language and region. If translations are found in that language, they will be returned.

Request Body

{
  "data": {
    "button.create": {
      "translation": "Create",
      "language": "en",
      "region": "US",
      "defaultText": false
    },
    "button.cancel": {
      "translation": "Cancel",
      "language": null,
      "region": null,
      "defaultText": true
    },
    "button.favorite": {
      "translation": "Favourite",
      "language": "en",
      "region": "CA",
      "defaultText": false
    },
    "button.delete": {
      "translation": "button.delete",
      "language": null,
      "region": null,
      "defaultText": false
    }
  }
}

Logic

If the translation exists in the language and region specified, it will be returned.

If the translation exists in the language but not the specified region, it will still be translated and returned.

If the GUID exists but it is not available in the specified language, the default text in the Literals table will return.

If the GUID does not exist or you do not have permission to it, it will return the GUID back as the translation.

System Tables

There are 3 tables in Cinchy to provide language support. [Cinchy].[Literal Groups], [Cinchy].[Literals], and [Cinchy].[Literal Translations].

Literal Groups

This table can optionally be used to group the translations. The default Cinchy strings belong to the Cinchy literal group. We recommend you create one literal group per applet or UI so you can retrieve the full list of GUIDs required for that page/applet easily.

Literals

This table defines all the strings that you want to translate.

Default Text

String that displays if no translation is found for the language specified.

GUID

GUID used to refer to the literal. A UUID will be generated by default, but can be overrode using the Guid Override field to something more human-readable.

Literal Group

As mentioned above, this can be used to group your strings so they can be easily retrieved. Note that this is a multi-select so you can use a single literal for multiple applets (including using the default Cinchy literals and translations for custom applets).

Literal Translations

This is the table where the translations are stored.

Translated Text

This is the translated string that is returned.

Literal

This is the literal the translation is for.

Language and Region

A language must be specified for a translation. Region can also be optionally specified for region specific words (ex. color vs colour).