Master Script Testing with RadishKit Parameter Management
Learn how to save and reuse script parameters for faster, more efficient Accela EMSE script testing workflows with RadishKit CLI.
Master Script Testing with RadishKit's Parameter Management
Testing Accela EMSE scripts often means running the same script multiple times with different parameters—whether you're debugging batch scripts, testing event handlers, or validating workflow logic. Manually entering parameters every time is tedious and error-prone.
RadishKit's intelligent parameter management system eliminates this friction by saving your test parameters and letting you reuse them instantly. In this guide, we'll show you exactly how to leverage this powerful feature.
What You'll Learn
How to test batch scripts with custom parameters
How to save parameter sets for instant reuse
How to test event scripts (ASA, WTUA, IRSA) with persistent parameters
Best practices for managing multiple parameter configurations
Batch scripts often require custom parameters like date ranges, record counts, or configuration values. RadishKit makes it easy to save and reuse these parameter sets.
Step 1: Test a Batch Script with Parameters
Let's say you have a batch script that needs custom parameters:
accli test Scripts/Batch/BATCH_BILLING_ASSESSFEES.js --batch
When you add the --batch flag, RadishKit prompts you interactively for parameters.
Step 2: Name Your Parameter Set (Optional)
First, you'll be asked if you want to name this configuration for easy identification:
? Would you like to name this parameter set? (yes/no): yes
? Enter a name for these parameters: Production Billing Jan 2025
Step 3: Enter Your Parameters
Next, you'll be prompted to enter key-value pairs:
Enter parameter name (or press Enter to finish): MaxSeconds
Enter parameter value: 120
Enter parameter name (or press Enter to finish): StartDate
Enter parameter value: 2025-01-01
Enter parameter name (or press Enter to finish): TestMode
Enter parameter value: true
Enter parameter name (or press Enter to finish):
[Press Enter to finish]
Step 4: Execute and Save
RadishKit executes your script with these parameters and automatically saves them to the RadishKit platform for future use.
Step 5: Reuse Saved Parameters
The next time you run the same command:
accli test Scripts/Batch/BATCH_BILLING_ASSESSFEES.js --batch
You'll see your saved parameter sets:
? Would you like to:
❯ Use saved parameters: "Production Billing Jan 2025" (2025-01-15)
Create new parameters
Edit saved parameters
Execute without parameters
Simply select your saved set and press Enter—no retyping required!
Part 2: Event Script Parameters
Event scripts (ApplicationSubmitAfter, WorkflowTaskUpdateAfter, InspectionResultSubmitAfter) require specific context like record IDs, workflow tasks, and statuses. RadishKit handles these elegantly.
Step 1: Test an ApplicationSubmitAfter (ASA) Event
For ASA events, you primarily need a record ID. You'll be prompted for it interactively:
accli test Scripts/Event/APPLICATIONSUBMITAFTER.js --event ASA
You'll be prompted:
? Enter record ID: PR2025-00123
RadishKit automatically saves the record ID for future use.
You can also pass the record ID directly to skip the prompt:
accli test Scripts/Event/APPLICATIONSUBMITAFTER.js --event ASA --record "PR2025-00123"
Step 2: Test a WorkflowTaskUpdateAfter (WTUA) Event
WTUA events require more parameters. You can start without any flags:
accli test Scripts/Event/WORKFLOWTASKUPDATEAFTER.js --event WTUA
You'll be prompted for all required parameters:
? Enter record ID: PR2025-00123
? Enter workflow task name: Building Review
? Enter workflow status: Approved
? Enter workflow date (YYYY-MM-DD) [2025-01-15]: 2025-01-15
? Enter workflow comment (optional): Test approval workflow
Step 3: Use Command-Line Parameters
If you know all the parameters upfront, pass them directly:
accli test Scripts/Event/WORKFLOWTASKUPDATEAFTER.js --event WTUA
RadishKit shows your saved parameter sets:
? Would you like to:
❯ Use saved parameters: Record PR2025-00123 - Building Review > Approved (2025-01-15)
Create new parameters
Modify saved parameters
Select the saved set and you're done!
Step 5: Test InspectionResultSubmitAfter (IRSA) Events
IRSA events work similarly but with inspection-specific parameters:
When saving parameters, use clear, descriptive names:
✅ Good:
"Production Billing - January 2025"
"Test Record PR2025-00123 - Approved Workflow"
"Building Inspection - Passed Scenario"
❌ Avoid:
"Test 1"
"Parameters"
"Temp"
Use Record-Specific Parameters
For event scripts, parameters are automatically grouped by record ID, making it easy to test the same record with different scenarios.
Edit Existing Parameters
You can modify saved parameters without recreating them:
accli test Scripts/Batch/MY_SCRIPT.js --batch
# Select "Edit saved parameters"
# Modify any value
# Save under the same or a new name
Archive Old Parameters
RadishKit stores your parameter sets in the cloud. You can archive old parameter sets that you no longer need to keep your workspace clean and focused on your current testing scenarios.
Part 4: Advanced Workflows
Combine with Safe Testing
All parameter testing uses RadishKit's safe-by-default rollback mode:
# Test safely (rollback)
accli test Scripts/Batch/BATCH_SCRIPT.js --batch
# When ready, commit changes
accli test Scripts/Batch/BATCH_SCRIPT.js --batch --commit
Non-Interactive Execution
For CI/CD or automation, provide all parameters via command line:
Parameters are stored securely in the RadishKit platform, making them accessible from any machine where you're logged in. This means:
Sync across devices: Access your saved parameters from your laptop, desktop, or any development environment
Team sharing: Share parameter sets with your team members automatically
Always available: No need to commit parameter files to version control
Team Collaboration
Team members invited to your agency project can use parameters created by other users in the project, making it easy to hand off development and testing tasks to other team members. This shared parameter library ensures everyone on the team has access to tested, validated parameter sets for common scenarios.
Quick Reference
Batch Script Commands
# Test with parameters (interactive)
accli test script.js --batch
# Test and commit
accli test script.js --batch --commit
# Run (commit by default)
accli run script.js --batch
Event Script Commands
# ASA (ApplicationSubmitAfter) - prompts for record ID
accli test script.js --event ASA
# Or pass record ID directly
accli test script.js --event ASA --record "RECORD_ID"
# WTUA (WorkflowTaskUpdateAfter) - prompts for all parameters
accli test script.js --event WTUA
# Or pass all parameters directly
accli test script.js --event WTUA --record "RECORD_ID" \
--task "Task Name" --status "Status"
# IRSA (InspectionResultSubmitAfter) - prompts for all parameters
accli test script.js --event IRSA
# Or pass all parameters directly
accli test script.js --event IRSA --record "RECORD_ID" \
--insp-id "INS_ID" --insp-type "Type" --insp-result "Result"
Next Steps
Now that you've mastered parameter management, take your workflow to the next level:
RadishKit's parameter management transforms script testing from a tedious, error-prone process into a smooth, efficient workflow. By saving and reusing parameters, you can:
Test faster with instant parameter recall
Test more reliably with consistent, repeatable configurations
Test smarter by organizing parameters by scenario
Stop retyping parameters and start testing with confidence. Your future self (and your team) will thank you!
