Recently I dove into the Localization Framework, noticed some new tables, made some incorrect initial assumptions, and came out with an understanding of the table structure that I could not find consolidated on the documentation site.
|LRITM||Localization Requested Item||sn_lf_requested_item|
You might think as I did that this data model aligns to request fulfillment with LFTASK the same as SCTASK, LRITM as RITM, and LP as REQ however this is incorrect.
Localization Projects (LP)
Are groupings of multiple requested items (LRITM). Localization Projects are assigned to a group with the localization_manager role and “assigned to” a member of the group to manage this effort. This table extends the task table directly. Localization Projects are not required in localization fulfillment.
Localization Framework > My Projects
Localization Requested Items (LRITM)
Can be added to a project to allow fulfillers to translate items in bulk. Localization Requested Items can be added to a project after they are created and does not need to be done during creation. The Localization Requested Item does not extend task and links through the document id to the target artifact record (knowledge, catalog item, VA topic, etc). Localization Requested Items link to Localization Tasks for translation and are not assigned or actioned directly.
Localization Framework > My Requested Items
Localization Tasks (LFTask)
Are actionable tasks per target language for localization fulfillers with the actions being “Verify Translations” and “Translate”. Localization Tasks directly extend the task table and are related to Localization projects. Localization fulfillment and approval is well documented in the links below.
Localization Framework > My Tasks
For those that like a picture, here is a representation of the tables and corresponding relationships.