Maintaining and expanding OTIS SMS

Expanding for new legal issues

• 1. Creating triage in Guided Navigation
  • 1.1. Steps to create Dialogues & Segments
    • 1.1.1. Step 1
    • 1.1.2. Step 2
    • 1.1.3. Step 3
    • 1.1.4. Step 4
    • 1.1.5. Step 5
    • 1.1.6. Step 6
    • 1.1.7. Step 7
    • 1.1.8. Step 8
• 2. Creating case acceptance webform
  • 2.1. Create a webform
    • 2.1.1. Required fields
    • 2.1.2. Optional fields
  • 2.2. Populate the webform
  • 2.3. What submissions get used
• 3. Create a rest export for the case acceptance
  • 3.1. Creating the REST Export
    • 3.1.1. Path settings
    • 3.1.2. Format
    • 3.1.3. Fields
    • 3.1.4. Filter Criteria
    • 3.1.5. Sort Criteria
    • 3.1.6. Pager
    • 3.1.7. Saving
  • 3.2. Sample REST Export
    • 3.2.1. Admin interface for view
    • 3.2.2. Sample Data Export
  • 3.3. Next Steps
  • 3.4. Backing up and restoring a view
    • 3.4.1. To backup a view
    • 3.4.2. To restore a view
• 4. Updating Twilio for new legal issue
  • 4.1. Step 1: Update functions
    • 4.1.1. Update the “get process” function
    • 4.1.2. Update the “”validate process” function
  • 4.2. Step 2: Update the Studio Flow
• 5. Twilio token updates
• 6. SMS etransfer failures

Demographic taxonomy terms

Taxonomy terms for gender, race, ethnicity, etc, that are used in the SMS application, are stored in functions rather than pulled from the website.

Any change needs to be made in both the relevant otis-load and otis-validate functions. Each demographic term has its own pair of functions (for example, otis-load-genders and otis-validate-genders).

 if (event.langcode == null || event.langcode == 'en') {
   marital.push('Single','Married','Divorced','Separated','Widowed');
   marital.push('Other', 'Prefer not to respond');
 }
 else {
  marital.push('Soltero','Casado','Divorciado','Separado','Viudo');
  marital.push('Otros', 'Prefiero no contestar');
}

Todo

Replace this with API calls to the website.