1 | User logs into HTG Translator | HTG Translator

2 | Dashboard shows translation modules and options | HTG Translator

3 | API fetches source strings for selected resource type | HTG Translator API

4 | User edits and saves translations via UI | HTG Translator

5 | Translations stored using appropriate POST API | HTG Translator API

6 | Translations published using publishModules API | HTG Translator

7 | Translated content reflected in applications or modules | Target Applications (Email, Forms, UI, etc.)

- Event: Translator or admin logs into the HTG Translator system.

- System: HTG Translator

- APIs:

- Authentication callback: GET /api/idp/htgtranslatorfl/auth/callback

- Logout: POST /api/idp/htg-translator/logout

- Load modules: GET /api/providermgmt/getModules

- Event: User selects a translation module (e.g., Static Text, Dropdowns).

- APIs:

- Static Text: GET /api/providermgmt/SourceString?resourceType=STATIC_TEXT

- Dropdown: GET /api/providermgmt/SourceString?resourceType=DROPDOWN

- Error Messages: GET /api/providermgmt/SourceString?resourceType=ERROR_MESSAGES

- Page Title: GET /api/providermgmt/SourceString?resourceType=PAGE_TITLE

- Message Templates: GET /api/providermgmt/SourceString?resourceType=MESSAGE_CENTER_TEMPLATES

- Response Example:

{ "id": 101, "sourceText": "Submit", "resourceType": "STATIC_TEXT", "language": "en", "translation": "Soumettre" }