Centralize Reusable Workflow Code, Fix Question JS in New Experience & Member Level Ups

Happy Friday, Community! This week brought workflow code management questions, a critical New Survey Experience JavaScript bug fix, and lots of community level ups!

Congratulations to

• ​@laveenacrasta for reaching Level 1
• ​@policyandresearch  for reaching Level 2!
• ​@Seray for reaching Level 2!

Big recognition to our milestone achievers:

• ​@Sachin Nandikol earned the 100 Answers badge
• ​@TusharDalwani hit 100 Comments

Also welcoming first-time contributors: ​@zzhelyazkov, ​@JustHereBrowsing, ​@ritacisecurity, ​@kev, ​@Juan Sebastián Bonilla, and ​@JohnR  have all earned First Comment and First Conversation badges.

You’re building the community!

Share your community achievements and earn an extra 50 points! 

Centralize Reusable Code Across 70 Surveys — A member is managing ~70 identical workflows and wants a single source of truth instead of duplicating JavaScript in each Code Task. Community suggesting web services/APIs instead of embedding code directly. See the approaches.

XM Directory Lite Users: Upvote Unsubscribe Support — If you're using XM Directory Lite and need mailing list unsubscribe functionality, upvote EV-4918 to restore the feature. Add your vote.

Question JS Breaking in New Survey Experience — Switching languages causes Question JavaScript to fail: addOnReady receiver becomes page-level (questionId undefined), breaking selectors and question-scoped methods. Detailed bug report with reliable workaround: capture questionId on first pass and use QuestionInfo/QuestionData.getInstance. See the fix.

Experience Transparency — Share you real-world implementations of Experience Transparency for website reviews. Jump in with your ideas.

Huge props to ​@kim_t who returned to a 5-year-old post with a clarification! 

Subscribe to Week in Review and get it delivered every Friday morning—perfect with your coffee, tea, or whatever keeps you energized.