- *BASICS*
- The Knox Ecosystem
- Samsung Knox Portal
- General Knox Support
- Knox Licenses
- *FOR IT ADMINS*
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- White paper
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Introduction
- Get started
- Features
- Register resellers
- Add an admin
- Create profiles
- Google device owner support
- MDM compatibility matrices
- Device users
- Activity log
- Enroll and unenroll devices
- Configure devices
- Provide KME feedback
- Use the Knox Deployment App (KDA)
- Recover Google FRP locked devices using KME
- Role-based access control (RBAC)
- Release notes
- FAQs
- Troubleshoot
- KBAs
- Knox Configure
- Mobile
- Wearables
- Shared Device
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQs
- Troubleshoot
- Knox Manage
- Introduction
- How-to videos
- Get started
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- FAQs
- KBAs
- Knox E-FOTA
- Introduction
- White paper
- Knox E-FOTA One
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQs
- Troubleshoot
- KBAs
- Migrate from Knox E-FOTA Advanced to Knox E-FOTA One
- Knox E-FOTA Advanced
- Knox E-FOTA on MDM
- Samsung Care+ for Business
- *FOR RESELLERS*
- Knox Deployment Program
- *FOR MANAGED SERVICE PROVIDERS*
- Knox MSP Program
Keystroke output
Knox Capture sends scanned data to business apps as keystrokes, imitating the way a user manually enters data using a keyboard.
To review an example of setting keystroke output rules, refer to IT admins: Getting started with Knox Capture - Step 5: Set keystroke output rules.
Overall formatting
Refer to the following settings to modify scanned data and format its output:
Setting | Description | Options | Default |
Send Enter character as | Sets the output format for all existing and appended Enters |
Key event—Sends Enter as a key event. String—Sends Enter as ASCII Line Feed 0x0A. Both String and Key event—Sends Enter as ASCII Line Feed 0x0A and key event. None—Sends no output for Enter. |
None |
Send Tab character as | Sets the output format for all existing and appended Tabs |
Key event—Sends Tab as a key event. String—Sends Tab as ASCII Horizontal Tab 0x09. Both String and Key event—Sends Tab as ASCII Horizontal Tab 0x09 and key event. None—Sends no output for Tab. |
None |
Send Carriage Return character as | Sets the output format for all Carriage Returns |
Key event—Sends Carriage Return as a key event. String—Sends Carriage Return as ASCII Carriage Return 0x0D. Both String and Key event—Sends Carriage Return as ASCII Carriage Return 0x0D and key event. None—Sends no output for Carriage Return. |
None |
Send ASCII Control characters as | Sets the output format for ASCII characters 1-31 |
Key event—Sends ASCII codes 1 through 31 as key events String—Sends ASCII codes 1 through 31 as strings. Both String and Key event—Sends ASCII control characters in both string and key event formats. None—Sends no output for ASCII control characters. |
String |
Send ASCII Printable characters as | Sets the output format for ASCII characters 32-126 |
Key event—Sends ASCII characters 32-126 as key events. This is useful when a text input field, like a password input, requires key events for validation and does not accept pasted strings. String—Sends ASCII printable characters as strings. Both String and Key event—Sends ASCII printable characters as both strings and key events. None—Sends no output for ASCII printable characters. |
String |
Key event delay |
Sets the delay in milliseconds that Knox Capture will wait before sending a key event like Tab. Note: String data transmits faster than key events, which can cause synchronization problems. Use this setting to inject a pause after each key event before sending string data to ensure an application receives the scanned barcode data in the correct order. |
[0, Int32 max value] |
0 |
Basic data formatting
Refer to the following basic data formatting information to create rules to add prefixes, suffixes, and append Tab or Enter characters to scanned barcode data before output.
NOTE - If appending a Tab or Enter key to the data output, you must also select an output option in the Send Tab as or Sent Enter as settings above.
Setting | Description | Default |
Prefix to data | Prepends a string of characters to the beginning of the scanned data. | Blank |
Suffix to data | Appends a string of characters to the end of the scanned data. | Blank |
Append Tab character | Appends a Tab (ASCII Horizontal Tab character, 0x09) to the end of the scanned barcode data to automate actions like moving to the adjacent cell in a spreadsheet. | OFF |
Append Enter character | Appends an Enter (ASCII Line Feed character, 0x0A) to the end of the scanned barcode data to automate actions like submitting a form. | OFF |
Send as Hex | Sends the data in hexadecimal format. | OFF |