Installation
uPerform installation requires administrative permissions on the local workstation. The installers are only available in English (US). uPerform requires the Microsoft .NET framework.
Languages Supported
The uPerform user interface and published content supports the following languages: Bulgarian, Catalan, Chinese (PRC), Chinese (Taiwan), Croatian, Czech, Danish, Dutch (Belgium), Dutch (Netherlands), English (US), English (UK), Finnish, French (Canada), French (France), German, Greek, Hungarian, Indonesian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Spanish, Swedish, Thai, and Turkish.
Published content can also be created in Arabic.
Author Citrix Usage
Authors can use uPerform from a 32-bit or 64-bit Terminal Server to support the generation of content. uPerform has been tested against XenServer 7.5/Virtual apps and Desktops 7.1808. uPerform does not support application publishing, remote applications, or web gateways from a Terminal Server. The Citrix server performance will depend on other applications in use on the Citrix server, as well as the number of planned concurrent uPerform authors. In order to optimize recording in a Citrix environment, uPerform and the target application must be presented to the user from the same server and contain the same settings.
Workstation Environments
End User Workstations
End user workstations support viewing of content generated by uPerform. The requirements are based on tested configurations with all software installed locally.
To view video included in courses, the video viewer (browser, plug-in, or device) used to view the course must meet the requirements for any video files included in courses. Prior to enabling a given video format in your template, ensure your chosen viewer supports that video format.
For optimum performance, viewing published simulations or courses over a low bandwidth connection is not recommended.
Rapid Recorder Workstation
Rapid Recorder workstations support only the recording of content. The requirements are based on tested configurations with all software installed locally.
Author/Administrator Workstations
Author or administrator workstations support the generation of content using the uPerform Editor component. The requirements are based on tested configurations with all software installed local.
Workstation Requirements |
End User |
Author Admin |
---|---|---|
1.5 GHz processor minimum; 2.5 GHz recommended |
X |
X |
8 GB RAM minimum; 16 GB RAM recommended |
X |
X |
2 MB Video card with 16 million colors at 1024 x 768 resolution |
X |
|
8 MB Video card with 16 million colors at 1024 x 768 resolution |
|
X |
Windows 10 (Desktop mode) |
X |
X |
Windows 11 |
X |
X |
(USGCB) v1.2 |
X |
X |
Microsoft Edge® to view content |
X |
X |
Mozilla Firefox® 42 or newer to view content |
X |
X |
Google Chrome™ 47 or newer to view content |
X |
X |
Safari 11 to view content |
X |
X |
Microsoft Office® to view content |
X |
X |
Microsoft Office 2016 to import Microsoft Office PowerPoint content into eLearning courses |
|
X |
Adobe Acrobat Reader® XI, DC 2015 to view PDF output |
X |
|
Apple iPad® running iOS 8.1 or higher to view content |
X |
|
Android device running v4.1 or higher to view content |
X |
|
JAWS® for Windows v12-18 |
X |
|
Microsoft .NET Framework v3.5 and v4.5.2 |
|
X |
Microsoft Visual C++ Redistributable Package v14.40.33810 (x64) and (x86) |
|
X |
Microsoft Windows Automation API 3.0 |
|
X |
Java Access Bridge for Windows 2.0.2 or higher for Java Runtime Environments 1.5 and later if recording Java-based applications |
|
X |
250 MB allocated to roaming profile |
|
X |
Microphone to record audio while recording |
|
X |
A server connection to submit tasks and check-in/out documents |
|
X |
Visual J# Redistributable Package v2.0 |
|
X |
Microsoft server speech voices v10 or v11, or other 32-bit SAPI5 compliant voice(s) installed if publishing files that use text-to-speech functionality |
|
X |
Learning Management Systems (LMS)
Capturing Simulation and Course Assessments
Published simulations and courses can be imported into any Learning Management System (LMS) that conforms to AICC 2.2, SCORM 1.2, or SCORM 2004.
Simulation and course assessment tracking can be performed directly within the uPerform Server. Assessment tracking must be enabled on the project and within the template.
uPerform uses Package Exchange Notification System (PENS) 1.0.0 to announce the location of content packages for delivery of courses to a Learning Management System (LMS). Simulations and courses support the following SCORM and AICC elements:
Learning Management System (LMS) Communication
SCORM 1.2 |
|
---|---|
Lesson Status (cmi.core.lesson_status) Lesson Location (cmi.core.lesson_location) Suspend Data (cmi.suspend_data) Raw Score (cmi.core.score.raw) Min Score (cmi.core.score.min) Max Score (cmi.core.score.max) Session Time (cmi.core.session_time) Progress (rwd.progress_measure) Completion threshold (rwd.completion_threshold) Simulation Mode (rwd.sim_mode)
|
Interactions (cmi.interactions)
|
SCORM 2004 |
|
Completion Status (cmi.completion_status) Success Status (cmi.success_status) Lesson Location (cmi.location) Suspend Data (cmi.suspend_data) Raw Score (cmi.score.raw) Min Score (cmi.score.min) Max Score (cmi.score.max) Scaled Score (cmi.score.scaled) Session Time (cmi.session_time) |
Interactions (cmi.interactions)
|
AICC |
|
Lesson Location (Core.Lesson_Status) Lesson Status (Core.Lesson_Location) Suspend Data (Core_Lesson) Raw Score (Core.Score) Session Time (Core.Time) |
|
User Management
User Authentication
uPerform can be configured to work with multiple authentication models. The following solutions have been tested. uPerform will work with customers to configure non-tested authentication solutions as needed.
- Basic authentication
- Security Assertion Markup Language (SAML 2.0) using Single-Sign-On
Recording
uPerform can record and document most 32-bit and most 64-bit Microsoft Windows or web-based applications, provided that the Windows or web-based application has been developed using Windows accessibility standards.
General recording of browser-based applications can be done in any supported desktop browser. For best results, Microsoft Edge or Google Chrome are the recommended browsers. For named in-application help connectors, recording requires the uPerform browser extension for Microsoft Edge or Google Chrome . If recording such applications in other browsers, recording quality may be reduced and you must manually enter context information into the uPerform document. For use with the general web application connector, automatic capture of context information occurs with Microsoft Edge, Google Chrome, or Firefox browsers.
In-Application Help
uPerform can provide in-application help for software applications.
The primary method for providing in-application help is through uPerform’s web connectors which can be deployed by direct integration in web applications or through extensions for Google Chrome and Microsoft Edge browsers.
Some in-application help solutions use the existing help functionality built into the software application, and require the software application to provide a method to direct context information to an external system when the user requests help. In these cases the comprehensiveness of the uPerform solution directly correlates to the comprehensiveness of the help functionality built into the software application.
The table below identifies applications for which uPerform has been tested from a recording and/or in-application help perspective. If a specific help solution exists for a given application, the table entry identifies the nature of the solution.
Business Application |
Recording |
In-Application Help Method |
---|---|---|
SAP GUI for Windows 8 |
X |
Help Launchpad for SAP Basis levels 700, 730, 740, 750 and 751 |
SAP HTML GUIs 7.x based on corresponding ITS/WAS with SAP application server |
X |
Help Launchpad for SAP Basis levels 700, 730, 740, 750 and 751 |
SAP CRM 7 Web Client |
X |
configuration |
SAP SRM 7 Shopping Cart |
X |
configuration |
SAP BI Platform 4.2 – Web Intelligence |
X |
|
SAP SuccessFactors |
X |
Browser extension for Chrome or Edge |
SAP Fiori |
X |
Browser extension for Chrome or Edge |
SAP Personas v3.0 |
X |
|
Oracle E-Business Suite 12 (Java applet) |
X |
configuration |
Guidewire Policy Center, Claim Center, and Billing Center – version 10 |
|
Browser extension for Chrome or Edge |
Any Infor application running in Ming.le |
|
Infor Ming.le connector via browser extension for Chrome or Edge |
Infor CSF and SM |
X |
Infor CSF and SM connector via browser extension for Chrome or Edge |
Infor LN |
X |
Infor LN connector browser extension for Chrome or Edge |
Infor M3 |
X |
Infor M3 connector browser extension for Chrome or Edge |
Infor HMS |
|
Infor HMS connector browser extension for Chrome or Edge |
HTML applications running in Google Chrome™ |
X |
browser extension
|
HTML applications running in Microsoft Edge |
X |
browser extension |
HTML applications running in Mozilla Firefox® |
X |
|
API
uPerform has an external API available, which enables change notification messages to be generated by any third-party application. In order to access the API, the third-party application must be able to authenticate against uPerform using Basic authentication.
System Landscape Registration
uPerform can optionally be registered in the SAP System Landscape Directory (SLD). Running the SLDRegistration.exe installation will configure uPerform to be registered automatically within the SLD. Registration will occur after each reboot of the server and every 12 hours after that to ensure the SLD remains current. In order for the registration to be processed in the SLD the latest Component Repository should be installed. If the latest Component Repository has not been installed, please review SAP Note 669669 for the minimum requirements.
Supported Environment Retirement Process
Third-Party Platforms
- We will support a technology platform until the end of mainstream support for that product as determined by the manufacturer of the software (Microsoft, etc.) in new releases of our software.
- We are not able to support a technology platform after the end of extended support as dictated by the manufacturer of the software (Microsoft, etc.) in new releases. However, users may be able to continue to use these retired platforms with previous releases of our software.
- If a new version of our software is released within 12 months of the announced end of extended support for a technology platform, we may choose not to support it for a new release of our software.
Browsers
- Chrome, Edge and Firefox: We will support each Chrome version until it is no longer supported by Google. We will support each Edge version until it is no longer supported by Microsoft. We will support each Firefox version until it is no longer supported by Mozilla. Due to the higher frequency of new releases of these browsers, we may not be able to support a specific browser version throughout the lifecycle of a full release of our software.
- Safari: We will support each Safari version until the end of mainstream support as determined by Apple.