botserver/templates/hr/employees.gbai/employees.gbdialog/search-employee.bas

PARAM searchterm AS STRING LIKE "John" DESCRIPTION "Name, email, or employee number to search for"

DESCRIPTION "Searches for employees in the HR system by name, email, or employee number."

IF searchterm = "" THEN
    TALK "What would you like to search for? You can enter a name, email, or employee number."
    searchterm = HEAR
END IF

IF searchterm = "" THEN
    TALK "I need a search term to find employees."
    RETURN
END IF

TALK "🔍 Searching for employees matching: " + searchterm
TALK ""
TALK "To search the employee database, I'll look through the records for you."
TALK "You can search by:"
TALK "• Full name or partial name"
TALK "• Email address"
TALK "• Employee number (e.g., EMP2024-1234)"
TALK ""
TALK "💡 Tip: For best results, use the exact employee number if you have it."

SET BOT MEMORY "last_search", searchterm
Looking at this diff, I can see it's a comprehensive documentation update and code refactoring focused on: 1. Adding new documentation pages to the table of contents 2. Restructuring the bot templates documentation 3. Changing keyword syntax from underscore format to space format (e.g., `SET_BOT_MEMORY` → `SET BOT MEMORY`) 4. Updating compiler and keyword registration to support the new space-based syntax 5. Adding new keyword modules (social media, lead scoring, templates, etc.) Refactor BASIC keywords to use spaces instead of underscores Change keyword syntax from underscore format (SET_BOT_MEMORY) to more natural space-separated format (SET BOT MEMORY) throughout the codebase. Key changes: - Update Rhai custom syntax registration to use space tokens - Simplify compiler preprocessing (fewer replacements needed) - Update all template .bas files to use new syntax - Expand documentation with consolidated examples and new sections - Add new keyword modules: social_media, lead_scoring, send_template, core_functions, qrcode, sms, procedures, import_export, llm_macros, on_form_submit 2025-11-30 10:53:59 -03:00			`PARAM searchterm AS STRING LIKE "John" DESCRIPTION "Name, email, or employee number to search for"`

			`DESCRIPTION "Searches for employees in the HR system by name, email, or employee number."`

			`IF searchterm = "" THEN`
			`TALK "What would you like to search for? You can enter a name, email, or employee number."`
			`searchterm = HEAR`
			`END IF`

			`IF searchterm = "" THEN`
			`TALK "I need a search term to find employees."`
			`RETURN`
			`END IF`

			`TALK "🔍 Searching for employees matching: " + searchterm`
			`TALK ""`
			`TALK "To search the employee database, I'll look through the records for you."`
			`TALK "You can search by:"`
			`TALK "• Full name or partial name"`
			`TALK "• Email address"`
			`TALK "• Employee number (e.g., EMP2024-1234)"`
			`TALK ""`
			`TALK "💡 Tip: For best results, use the exact employee number if you have it."`

			`SET BOT MEMORY "last_search", searchterm`