Memsource Integration

Business perspective: Memsource Integration

1. Business Summary

OAuth login, project & TM creation, file analysis, deliverables retrieval against Memsource.

2. Business Value

Automation of TM-driven workflows.

3. Users / Stakeholders

PMs, engineers.

4. Workflows

  • MemSourceController::login() requests/refreshes a token (cached in memsource_users, valid until token_datetime).
  • Token tied to user and brand.
  • addTmsProject, uploadTmx, deliverables.

5. Sub-Features

  • Token caching.
  • Brand-scoped credentials.

6. Business Rules

  • Falls back to hard-coded admin credentials in some paths (Risk).
  • Token reused while token_datetime > now().

7. Data Entities

MemsourceUser (memsource_users), MemSource projects/TMs (external).

8. Entry Points

  • mem_source/* actions.
  • TMS controller integration points.

9. Inputs & Outputs

  • Inputs: credentials.
  • Outputs: tokens, projects, analyses, deliverables.

10. Integrations

  • Memsource API.

11. Calculations / Logic

  • Token TTL handling.

12. Status Lifecycle

  • Token valid/expired.

13. Permissions

  • PMs/engineers, brand-scoped.

14. Reports & KPIs

  • Memsource sync success.

15. Risks & Observations

  • Hard-coded fallback credentials.
  • 120-sec sleeps in TMS controller.

16. Source Code Evidence

  • app/Controller/MemSourceController.php (~3,650 LOC).

← Deep dives index