You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A robust script editor (and interactions editor) is important to setup a multi path, robust campaign with lots of possible paths for texters to take.
The current setup setup supports multi path interactions, but can often get convoluted and time consuming to step.
Context
The current script editor is a little convoluted at times, with multiple warnings, loads of custom fields, and now with campaign variables all of them adding up into a complex view.
Parts of the backend can also be cleaned up and refactored to better handle character encoding, and converting all UI elements to MUI v4 and moving to a functional component removing any UNSAFE_ methods.
Goals and Non-Goals
Main Goals:
Better support for loads of variables + campaign variables
Better support for attaching attachments, with size warnings and mime type warnings
Better support for warnings
Non Goals (for a later time):
Rethink the interactions section
Milestones
Milestone 1:
UI / UX Design diagrams
Milestone 2:
Implementation and testing
Existing Solution
Proposed Solution
Alternative Solutions
Testability, Monitoring and Alerting
Cross-Team Impact
Open Questions
Detailed Scoping and Timeline
The text was updated successfully, but these errors were encountered:
Overview
A robust script editor (and interactions editor) is important to setup a multi path, robust campaign with lots of possible paths for texters to take.
The current setup setup supports multi path interactions, but can often get convoluted and time consuming to step.
Context
The current script editor is a little convoluted at times, with multiple warnings, loads of custom fields, and now with campaign variables all of them adding up into a complex view.
Parts of the backend can also be cleaned up and refactored to better handle character encoding, and converting all UI elements to MUI v4 and moving to a functional component removing any
UNSAFE_
methods.Goals and Non-Goals
Main Goals:
Non Goals (for a later time):
Milestones
Milestone 1:
UI / UX Design diagrams
Milestone 2:
Implementation and testing
Existing Solution
Proposed Solution
Alternative Solutions
Testability, Monitoring and Alerting
Cross-Team Impact
Open Questions
Detailed Scoping and Timeline
The text was updated successfully, but these errors were encountered: