Currency ISO code options across CDP, Chat, and mobile
Context
A client reported that currency options were disabled on the website, while the mobile application already handled ISO code options. The work was split across backend, CDP and Chat frontend, and mobile:
- BE: TF-3574
- FE — CDP Create, Details, and Edit: TF-3573
- FE — Chat Customer Profile: TF-3576
- Mobile CRM: TF-3575
- Mobile Chat: TF-3581
The tasks were queued for Sprint 2, with engineers invited to pick them up after completing their current tickets.
Notes
- Giovanni Massimiliano (Jovi) picked up the CDP frontend work.
- Azani Ramadhan accepted the Chat frontend work.
- The backend will still provide CRUD capabilities for currency data, allowing a dedicated currency API to be used by future features if needed.
- Mobile CRM was still waiting for regression work. The discussed release timing was around the end of July, followed by the next mobile work queue around early August.
- Recent CRM releases did not use a beta rollout. A percentage rollout may be possible, but the team agreed to follow the normal release mechanism for this change.
Decisions / changes
- Currency options will be supplied by the backend.
- Consumers will read the currency options directly from
field_properties, following the same general approach as channel and status options, instead of requiring another API call. - The currency data remains under the existing number field with currency subtype. It is not a new
top-level field; the implementation may add a property within the
field_propertiesobject. - The backend will retain dedicated currency CRUD support for potential future use.
- The approach minimizes frontend and mobile changes and avoids adding another required API call.
Follow-ups
- Giovanni Massimiliano (Jovi): implement the CDP frontend changes in TF-3573.
- Azani Ramadhan: implement the Chat Customer Profile frontend changes in TF-3576.
- Maulana Ghozi Humama / BE: implement backend-managed currency options and currency CRUD in TF-3574.
- Mobile team: deliver TF-3575 and TF-3581 through the regular mobile release queue; the stated timing was approximately late July to early August.