Tools tab of Process Runner DB

This section describes how to configure the options on the Tools tab. You can configure the settings that affect the visual style and other settings for the different technologies of Process Runner DB.

This section contains the following topics:

• Application
• Tool
• Other
• SAP GUI Utility
• Control Panel Settings/Control Panel Cloud Settings
• Visual Style
• Reset

Application

This section describes how to use the options in the Application section.

• Options
• Collective Run

Options

This section contains information about the different options in the Options window.

• Enterprise Settings
• Updates/Backup
• Other
• Path
• Colors
• Transaction
• Scripting
• Data Extractor

Enterprise Settings

The enterprise applications brings productivity and agility while providing simplified data management, collaboration, publishing, reporting, governance, and monitoring capabilities. This section contains the following topics:

• Control Panel
• EShare
• Dashboard
• Enterprise Application Configuration File

Control Panel

Control Panel stores data in Microsoft Access or SQL Server in the backend and increases the efficiency of Process Runner DB and SAP system. The web-based interface of Control Panel enables easy monitoring and control by IT or SAP administrators to instantly define and implement usage policies across users, systems, and processes without changing SAP security or access.

To configure the options on the Control Panel tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.
2. In the Enterprise Settings > Control Panel tab, select Enable Control Panel

   

   .
3. From the Connection Type drop-down list, perform the following:
   • To enable web-based Control Panel for on-premises usage, select Service Configuration.
     • To import and use the existing EShare enterprise settings for the configuration of Control Panel, perform the following steps:
       1. Select Import Configuration Details. The ControlPanel config file dialog box appears.
       2. Browse and select the ControlPanelConfig.icf file. The configuration information is automatically populated in the appropriate fields.
     • To configure Control Panel using a web service, perform the following steps:
       1. URL: Enter the URL of the Control Panel instance.
       2. In Credentials for your web service url, select one of the following options:

          Use default: Indicates that the default credentials are used to connect to Control Panel. The User Name and Password options are not available for this option.

          User defined: Indicates that the domain user name and password that are used to connect Control Panel.

          Note: Ensure that you get the required details from your Control Panel administrator.

       3. Select Test Connection. The configuration details are verified.
       4. To reduce the average time to access Control Panel server for frequent actions, select Enable Control Panel Cache. The copies of actions performed for the first time in Process Runner DB are stored on your computer and thus the average time to access the Control Panel server is reduced.
   • To use the Cloud Hub Control Panel, select Process Runner Cloud.

4. Select Apply and then OK. The changes are saved.

EShare

This topic describes how to configure the options of the EShare tab.

You can use the EShare functionality to configure EShare through a web service, a database connection or a cloud and save the Process file in the centralized location. You can also use the feature to import and use the existing enterprise settings of EShare from a configuration file (.icf) to your computer.

To configure the options on the EShare tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.
2. On the Enterprise Settings > EShare tab, select Enable EShare.

   

3. To import and use the existing EShare configuration, perform the following steps:
   1. Select Import Configuration Details. The EShare Config file dialog box is displayed.
   2. Browse and select the EShareConfig.icf file. The configuration information is automatically populated in the appropriate fields.
4. To configure EShare, in Connection Type, select one of the following options: 
   • Select Service Configuration. Enter the following details and test the connection:
     • URL: Indicates the URL of the EShare instance.
     • Use default: Indicates the default credentials are used to connect EShare. The User Name and Password options are not available for this option.
     • User defined: Indicates that the domain user name and password that are used to connect EShare.

     Note: Ensure that you get the required details from your EShare administrator.

   • Select Database Configuration. Enter the following details and test the connection:
     • Database Server name or IP: Indicates the host name or IP address of the computer on which EShare is installed. Specify the port number if you do not use 1433 as a default value and a comma after the IP address or hostname. For example, specify 199.xx.yy.xxx, 11111.
     • Database Name: Indicates the name of the EShare database.
     • Authentication Mode: Indicates the authentication mode that must be used to connect to EShare. For SQL Server Authentication, user name and password are also required.
   • Select Process Runner Cloud to opt for Eshare in Cloud Hub.
5. To enforce case-sensitive user name comparison while logging in to the EShare server, select Case-sensitive windows user name comparison.
6. Select Apply and then OK. The changes are saved.

Dashboard

Dashboard enables you to view graphically how Process Runner DB is used within your enterprise. You can view reports, metrics and key performance indicators (KPIs).

To configure the options on the Dashboard tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.
2. On the Enterprise Settings > Dashboard tab, select Enable Dashboard.

   

3. Optionally, select Copy from EShare. The configurations of the EShare tab are copied to Database Setting of the Dashboard tab.

Note: Copy from EShare is available only when EShare in the Options window is selected.

4. To import and use the existing Dashboard settings for configuration of EShare, perform the following steps:
   • Select Import Configuration Details. The Dashboard Config file window appears.
   • Browse and select the DashboardConfig.icf file. The configuration information is automatically populated in the appropriate fields.

   Note: The configuration information about Dashboard is displayed in the different boxes of Database Setting or Service Setting. You must get the DashboardConfig.icf file from your Dashboard administrator.

5. To configure Dashboard using a web service or database connection, perform the following steps:
   1. If you select Service Configuration in Connection Type, enter the following details, and test the connection:
      • URL: Indicates the URL of the Dashboard instance.
      • Use Default: Indicates that the default credentials are used to connect to Dashboard. The User Name and Password options are not available for this option.
      • User Defined: Indicates that the domain name and password are used to sign in to Dashboard.

      Note: Ensure that you get the required details from your Dashboard administrator.

   2. If you select Database Configuration in Connection Type, enter the following details, and test the connection:
      • Database Server name or IP: Indicates the host name or IP address of the computer on which Dashboard is installed. Specify the port number if you do not use 1433 as a default value and a comma after the IP address or host name. For example, 199.xx.yy.xxx,11111.
      • Database Name: Indicates the name of the Dashboard database.
      • :Authentication Mode Indicates the authentication mode that must be used to connect to Dashboard. For SQL Server Authentication, user name and password are also required.
   3. Select Test Connection. The configuration details are verified.
6. In Upload Timing, select one of the following options:
   • Manually: Indicates that the records are uploaded manually.
   • End of Each Run: Indicates that the record are uploaded automatically after the successful run of the Process file.
   • On Exit: Indicates that if an error occurs in the first collective file run, then Process Runner DB logs the error in a log file and continues the run of the other files in the collective run.
7. Optionally, to upload only the new records that eliminates the replication of the records, select Upload New Records Only.
8. Select Apply and then OK. The changes are saved.

Enterprise Application Configuration File

This section describes how to export the configuration details of enterprise applications.

Ensure that you are on the computer where you have configured the enterprise applications to work with Process Runner DB. You must export the configuration file that can be sent to other Process Runner DB who can import the configuration and start working with Enterprise Applications.

To export or import enterprise configuration file,

1. In Process Runner DB, select Tools > Options. The Options window appears.
2. On the Enterprise Settings > Tools tab, select Export. A zip file named InnoweraEnterpriseConfig.zip is created with the configuration details.

   

3. To import the configuration details, each user who wants to use the file must perform the following steps:
   1. Obtain the InnoweraEnterpriseConfig.zip that was created as described in step 2.
   2. Place the file on desktop and start Process Runner DB. Process Runner DB detects the InnoweraEnterpriseConfig.zip and the user is prompted to import the settings.
   3. Select Yes in the confirmation dialog box. The configuration file and the compressed file, InnoweraEnterpriseConfig.zip, are automatically removed from the desktop.

Updates/Backup

This section describes how to use the options on the Updates/Backup tab to get the latest updates of Process Runner DB and enable the automatic process of backing up Process files, Stat files, and log files.

To configure options in Updates/Backup tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.

   

2. Select the Updates/Backup tab and perform the following options:
   • Disable future version file check: Indicates that no warning messages are displayed when you open a Process file in an older version of Process Runner DB that was created in a later version of the product.
   • Disable SAP version check on run: Indicates that Process Runner DB does not check for SAP version automatically when it is started.
   • Auto update file version: Updates your file version to the latest version automatically.
   • Disable sample file refresh: Disables the refresh of sample file version.
   • Notify to install updates: Sends notification to install the latest update.
   • Automatically create backup of Process DB file when saving: Stores the backup of Process files automatically in My Documents\Innowera\Backup folder. Optionally, you can also select Auto backup of Process DB file when saving from schedule/command prompt/smart eshare run.
   • Automatically backup Log and Stat file When starting Process Runner DB: Stores the backup of Log and Stat files automatically in My Documents\Innowera\Backup folder. Optionally, you can also select Auto backup Log and Stat files when starting from schedule/command prompt run.
3. Enter a value in the Create new Log and Stat file when it box to automatically create new Log and Stat file when the file reaches the specified size.
4. Select OK. The details are saved.

Other

The topic describes how to configure the options of the Other tab.

To configure the options on the Other tab,

1. In Process Runner DB, select Tools > Options > Other tab. The Other tab window appears.

   

2. Select Suggest this Logon Shortcut file and then select a logon shortcut file from the dropdown list. The selected logon shortcut file is displayed during the recording of a transaction, which eliminates the SAP logon step and speeds up your recording process.
3. In No. of recent files to display, enter the number of recent files that must be displayed in My Dashboard > Recent File List.
4. In Context Sensitive help (F1), to open help, select Online Help and it displays the most updated help directly from the insightsoftwaredocumentation website.
5. To use the NetWeaver RFC library to communicate with SAP, select iNETConnector setting.
6. To generate the application log for help from the insightsoftware support team, select Application Log.
7. In Mapper Setting, select the following:
   • Display Mapping type: Indicates the display for the mapping type.
     • Icon Only: Displays only the icon in the dropdown list that is displayed in the Mapping Type column.
     • Icon with caption: Displays only the icon with the relevant text in the dropdown list that is displayed in the Mapping Type column.
   • Auto hide side bar when in mapper: Hides the sidebar displayed when the Mapper tab is activated; you can get a complete detailed view of Mapper.
8. In Reset messages, select the following:
   • Time to show the message: Sets the custom time for automatic timeout messages.
   • Reset messages to default: Resets all timeout & saved response (do not ask again) messages to default.
9. In File Operation Setting, select the following:

   Note: File operation using is an advanced file operation setting and should not be used without instructions from the insightsoftware support team.

   • Compress Process File: Compresses every Process File globally. After successful download and installation of Process Runner Enterprise, if any existing Process File (which are created in Process Runner 20084.20.132.21677 or earlier versions) is opened with Process Runner Enterprise, that file is upgraded and compressed. Thereafter those Process Files run into compatibility errors when opened in Process Runner 2008 4.20.132.21677 and earlier versions.

     To make the Process File compatible with Process Runner DB 2008, disable the Compress Process file option in Process Runner Enterprise edition. This setting can be performed on the individual Process Files by disabling the Save Process file with Compress format option in the Save As Options tab.

10. To close the application if it is idle for specified time period, select Exit Application when idle.
11. In Display Setting, select the following:
    • Disable Display Scaling on High DPI settings: Disables the automatic display scaling when on High DPI settings.
    • Do not show "Wait" dialog on run: Does not show the Wait dialog on run.
12. Select Apply and then OK. The changes are saved.

Path

The topic describes how to configure the options of the Path tab for Process Runner DB, Process File, and database files.

To configure the options on the Path tab,

1. In Process Runner DB, select Tools > Options > Path. The Path tab window appears.

   

2. On the Path tab, select the working folder for the following:
• Process Runner DB: Saves the Process Runner Application Files (iLogon, Process Files, Log & Stat ) to the specified location instead of \\My Documents\Innowera, which is the default location.
• Process Files: Saves the Database Data File to the specified location instead of \\My Documents, which is the default location.
• Log & Stat File: Saves the Log & Stat Files to the specified location instead of \\My Documents\Innowera\Other, which is the default location.
• Creating Temp File: Changes the temporary folder path and it is also known as the working folder.
• GUI Execution folder: Saves the GUI execution to the specified location instead of \\ProgramData\Innowera\Process Runner\GUI Temp, which is the default location.
• Temporary folder: Changes the temporary folder path.
• Ready-to-Run download template folder: Downloads and saves the ready-to-run templates to the specified location instead of \\My Documents\Innowera\Online Samples, which is the default location.
3. Select Apply and then OK. The changes are saved.

Note: Select Defaults to revert to the default settings.

Transaction

This topic describes how to configure the options of the Transaction tab. These settings are applied to all the SAP systems globally.

To configure the options on the Transaction tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.

   

2. On the Transaction tab, in the Transaction Settings section, select one of the following options:
   • Use Standard RFM: Indicates that standard RFM methods of SAP are implemented in Transaction technology for all the SAP Systems.
   • Use Extended RFM: Indicates that the customized RFM methods of Process Runner are implemented in Transaction technology for all the SAP Systems. To get the Name of Extended Function, please create a support case on Salesforce.
3. To transform the messages that SAP returns in Process Runner DB to custom messages, in the SAP Return Message Settings for Transaction and RFM/BAPI section, select the following options:
   • Active: Indicates that the messages returned by SAP are activated.
   • Suppress: Indicates that the messages returned by SAP are suppressed.
   • Display this message in DS: Indicates the custom message that is displayed when the ID and message number matches. When Process Runner DB encounters the message ID that must be transformed, the custom message is displayed instead of the original message along with the following details:
     • Id: Displays the SAP message ID.
     • No: Displays the SAP message number.
     • Status: Displays the status when the ID and message number matches. For example, error message or information message.
4. If the message you want to customize is not listed in the table, you can add the message by entering the ID, Number, return message, and status. The values can be found in the status and log column after you run the file.
5. In the Advanced Transaction Settings section, select the following options:
   • Transaction Update mode: Indicates how updates in SAP are done. By default, it is set to synchronous.
   • Get Fields from SAP mode:Indicates that the fields must be fetched in SAP mode
   • Use default screen size: Indicates that the application uses the default screen size. You can use this option if you are running this file on different computers or if you are sharing this file. Your transaction recording looks the same on computers even if they have different resolutions when the file is run.
   • Use screen size based on my system: Indicates that the application uses the screen size as set on your computer.
   • Output XML trace for Transaction: Generates a detailed trace file of the various operations performed for the transaction.
   • Save Excel Report as per file extension: Saves the Excel report according to the file extension.

Note: To update the Use Standard RFM and Use Extended RFM settings for a specific SAP system, go to <SAPSystemName> > Properties > Transaction Settings from Connector for SAP .

6. Select Apply > OK. The details are saved.

Note: Select Defaults to revert to the default settings.

Scripting

This topic describes how to configure the options of the Scripting tab.

To configure the options on the Scripting tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.

   

2. On the Scripting tab, in Multiple Logon Setting - What to do when you are already logged on, select any of the following:
• Create new session from existing logons:Process Runner DB creates a new session from existing logons. Select this option only if you know how updates are done in SAP.
• Continue with new Logon terminating any other existing logon (You may loose any unsaved changes):Process Runner DB terminates the existing logons and the unsaved work in the SAP sessions is lost.
• Continue with new logon, without ending any other logon (will not loose any work but may violate SAP licensing agreement in production environment):Process Runner DB initiates a new SAP GUI session and does not close any existing session. SAP license agreement generally does not allow dual logons to the same computer with the same user ID in a production environment. All such logon activity is generally monitored. Check with your administrator if this is an appropriate option for your production system.
• Stop and do nothing:Process Runner DB stops and stays idle.
3. In Other Scripting Setting, select the following:
   • Suppress Scripting Errors and Prompts while running:Process Runner DB suppresses scripting errors and prompts during the run.
4. Select Apply and then OK. The changes are saved.

Note: Select Defaults to revert to the default settings.

Data Extractor

This topic describes how to configure the options of the Data Extractor tab. These settings are applied to all the SAP systems globally.

To configure the options on the Data Extractor tab,

1. In Process Runner DB, select Tools > Options > Data Extractor. The Data Extractor window appears.

   

2. To stop all subsequent calls if a data dump is encountered, select Stop all the subsequent calls on the first short dump.
3. To implement standard RFM methods of SAP for Data Extraction for all SAP systems, select Use Standard RFM. Select one of the following options:
   • Auto Method: Indicates that the standard method is used.
   • Method 1 - BBRT: Is optional and is used if the standard method fails.
   • Method 2 - RT: Is used when both the standard method and Method 1 fails.
4. To implement extensively customized RFM methods of Process Runner for data extraction for all SAP systems, select Use Extended RFM. Perform the following:
   • Name of Extended function: Enter Y_PROCESS_RUNNER_DE in the text box.
   • Reset settings for packed numbers: Select only if instructed by insightsoftware and if you are using the SAP OSS note.
5. To set the total width of records extracted using extended RFM, enter the number in the Record width text box. The default row width for standard RFM is 512.

Note: To update the Use Standard RFM and Use Extended RFM settings for a specific SAP system, go to <SAPSystemName> > Properties > Data Extractor Settings from Connector for SAP .

6. Select Apply and then OK. The changes are saved.

Note: Select Defaults to revert to the default settings.

Colors

This topic describes how to configure the options of the Colors tab that helps you identify the various fields and values on the Mapper tab.

To configure the options on the Colors tab,

1. In Process Runner DB, select Tools > Options. The Options window appears.

   

2. On the Colors tab, in Mapping Types, set the color for the following fields:
   • DS To SAP: Indicates the row in Mapper where Mapping type is DS To SAP.
   • SAP To DS: Indicates the row in Mapper where Mapping type is SAP To DS.
   • Fix Value: Indicates the row in Mapper where Mapping type is Fix Single Value.
   • Constant: Indicates the row in Mapper where Mapping type is System Value.
3. In Row Block Types (Only for BAPI/RFM), set the color for the following fields:
   • Fix Multiple Value: Indicates the row in Mapper where Mapping type is Fix Multiple Values.
   • Fix Block: Indicates the row in Mapper where Block Type is Fix Block.
   • On Change: Indicates the row in Mapper where Block Type is On Change.
   • Blank Row: Indicates the row in Mapper where Block Type is On Blank Cell In Column
4. In Other, set the color for the following fields:
   • Background: Indicates the background color in Mapper.
   • Disabled Row: Indicates the inactive rows in Mapper.
   • Screen Row: Indicates the screen rows in Mapper (Only for Transaction).
5. Select Apply and then OK. The changes are saved.

Note: Select Defaults to revert to the default settings.

Collective Run

Process Runner DB retains a default behavior of executing a single process file at a single instance. This behavior can be configured to achieve execution of multiple process file in a single instance. The Collective Run window allows to manage these process files by letting users to add, order, modify and delete the process files.

The following table represents the influence of each field and option of the Collective Run window.

Create New Collective Run

This topic describes how to create a collective run that enables you to run multiple Process files in a single instance of Process Runner DB.

To create a collective run,

1. In Process Runner DB, select Tools > Collective Run. The Collective Run window appears.
2. Select New. The Create New Collective Run window appears.

   

3. In the Create New Collective Run window, perform one of the following:
   • To add files that are available on your system, select Add File > Local.
   • To add files that are available in a central location, select Add File > EShare.
4. In Logon Shortcut Settings, select Use this Logon Shortcut file to activate a specific logon shortcut file for execution related to collective run file and select one of the following options:
   • For all files: Indicates that all the Process files of the collective run are run with the selected the logon shortcut file.
   • For files with no Logon Shortcut: Indicates that the Process files that are not allotted any logon shortcut file are run with the selected logon shortcut file.

   Note: If you do not select Use this Logon Shortcut file and also no auto logon file is set for the individual files, then a logon pop-up dialog appears before each Process file is run.

5. In Validation Settings, select Validate existing files before Run to activate or deactivate the validation of each Process file in the collective, and select one of the following options:
   • Stop if file is missing: Indicates that the run is terminated in case of missing file.
   • Stop on first error: Indicates that the run is terminated in case of first error.
6. In Other Settings, select Close last file after Collective Run execution ends to close each Process file individually and instantly after its run.
7. Select Save. The collection of files is saved in My Documents\Innowera\Collective Runs\ (filename).icr and the file for collective run is created.

Tool

This topic describes how to use the options in the Tool section in Process Runner DB. This topic contains the following topics:

• Commander
• Autofix Tool

Commander

To run the scheduled processes in Process Runner DB, it takes a bit of time to open and close Process Runner DB instance for each scheduled process. To overcome this insightsoftware has introduced Commander in Process Runner DB. The Commander offers centralized monitoring and execution control for various processes. The Commander is based on MSMQ technology to bring reliable and fail-safe performance for process execution. Using Commander you can execute all the scheduled processes in one instance of Process Runner DB one by one.

Note: Message Queuing (MSMQ) must be installed on the computer.

To execute all the scheduled processes,

1. In Process Runner DB, select Tools > Tool > Commander. The Commander window appears.

   

2. In the Commander window, perform the following as required:
   • Start: Executes all the scheduled processes in one instance of Process Runner DB.
   • Pause: Pauses the execution of any scheduled processes in the grid. The pause action can be reversed using Start button.
   • Options: To configure the settings of Commander as follows:

     Option	Description
     Maximum Number of Process Runner DB Sessions	Usually Commander helps for the quick execution of Process files. In case when a file is being executed in Process Runner DB, the Commander initiates a new session of Process Runner DB and executes the scheduled process file in opened session. Users can set the number of parallel instances (of Process Runner DB) that can be allowed for execution of Process Files. insightsoftware provides maximum amount of 6 instances for Process Runner DB as far as extension in the same is separately requested. Set the number of Instances from the text-box of this option
     Launch at Startup	Select this option to instruct windows operating system to start the Commander at the start-up of the system.
     Launch Commander when Schedule	Selecting this option will start the Commander before the execution time of Scheduled Process File

   • Select All: Selects all the jobs that are queued-up in the process-grid of the Commander.
   • Executing: Displays only the jobs that which are being executed currently.
   • Finish Execution: Displays the jobs which are concluded for its execution.
   • Error: Displays the jobs which encountered an error during its execution.
   • Skipped: Displays the jobs which were skipped for its execution.
   • All: Enables all the preceding filters and display all the jobs.
   • About: Displays the About window of Commander.
3. Select OK to save the settings and exit the commander window.

Autofix Tool

The AutoFix Tool allows the users to auto-fix the settings of the system to the state which are relevant for effortless and smooth consummation of insightsoftwareproducts without disturbing the normally required environment for the organization.

To automatically fix the settings of Process Runner DB,

1. In Process Runner DB, select Tools > Tool > Autofix Tool. The Autofix Tool window appears.

   

2. Select Auto Fix for the following options:

• Excel Setting: Helps to automatically fix Excel related settings that are essential for running insightsoftware products.

  Note: You must contact insightsoftware Support for modifying any group of settings.

  • Required folder to be run Process Runner Products in logoff Mode: Restores the required settings for selection of the essential folder to run insightsoftware products in offline mode.
  • Required setting for convert Excel File to PDF using COM method for service user (Non Interactive User): Fixes the settings to its default values that are required to convert Excel file to PDF using COM method for a service or non interactive user.
• SAP GUI Setting: Fixes the errors and retains default state of Process Runner DB or GUI Script technology.
  • Disable "Notify when a GUI Script opens connection and attaches to SAP GUI" for current user: Bypasses the prompt that is displayed when a GUI Script connection is established with SAP GUI for the current user.
  • Disable launch of SAP GUI instance while process file recording or execution for current user: Regains the access of Process Runner products to run in log off mode for the current user.
  • Disable "Notify when a GUI Script opens connection and attaches to SAP GUI" for all user: Bypasses the prompt that is displayed when pro GUI Script connection is established with SAP GUI for all the users.
  • Disable launch of SAP GUI instance while process file recording or execution for all user: Restores the required SAP GUI Security Settings to run Process Runner products in log off mode for all the users.
  • Disable "Notify when a GUI Script opens connection and attaches to SAP GUI" for service user: Bypasses the prompt that is displayed when a GUI Script connection is established with SAP GUI for a service or non interactive user.
  • Disable launch of SAP GUI instance while process file recording or execution for service user: Regains the access of Process Runner products to run in log off mode for a service or non interactive user.
• EP/SSO Setting: Helps to autofix several EP/SSO related settings. Select the following option:
  • Enable Process Runner Products EP/SSO compatible with IE 11: Restores the required default settings that will enable the EP/SSO of Process Runner Products with Internet Explorer 11.
• IE 9 Setting: Helps to restore default settings that are essential for playback of Process Runner DB videos on Internet Explorer 9. Select the following option:
  • Enable Video compatible with IE 9 (For Process Runner Only): Adjusts the settings Internet Explorer 9 settings for being compatible with Process Runner DB videos.

Other

This topic describes how to use the options in the Other group to perform certain tasks in Process Runner DB.

To configure the Other group options,

1. In Process Runner DB, select Tools > Other. The Other group of options appears displayed.
2. Select Minimize on Run. The Process Runner DB window is minimized during the execution of process file.
3. Select Disconnect from SAP. The current SAP session is ended.

SAP GUI Utility

This section contains the following topics:

• SAP GUI Scripting Spy
• Enable SAP GUI History

SAP GUI Scripting Spy

This topic describes how to configure the SAP GUI Scripting Spy option for debugging and duplication. Each SAP screen has its own screen ID that you can view using scripting spy. This option also allows you to select and view properties of an UI element by directly clicking it. It displays the complete hierarchy of the object that you select.

Note: The SAP GUI Scripting Spy option is not related to the Process files.

To configure the Scripting Spy option,

1. In Process Runner DB, select Tools > SAP GUI Scripting Spy. The SAP GUI Scripting Spy window appears.
2. Select Refresh/Get GUI session. The list of the selected object hierarchies in another SAP instance is refreshed. The GUI session details are also displayed. If no SAP GUI sessions are found, a prompt to log in to the SAP system is displayed.

   Note: Only the sessions having SAP GUI Scripting enabled are supported.

3. Select Load. The following GUI session details are loaded:
   • Connection Property: The fields Connection ID, Description, ConnectionString, and Session ID display the connection property details.
   • Property: The fields ID, Name, Text, Type, and subtypes Container Type and Changeable display the property details.

   

4. Select Start Debug. The SAP GUI appears.
5. To capture the properties of an object, select it. For example, if you want to get the property values of Material field of MM02 transaction, point to the Material field.

   

6. Expand the session IDs. The hierarchical list of the object is displayed.

   

7. Select Stop Debug. The debugging is stopped.

Enable SAP GUI History

This topic describes how to use the Enable SAP GUI History option to update the SAP GUI local history settings and view the location of the saved history.

To configure Enable SAP GUI History settings,

1. In Process Runner DB, select Tools > SAP GUI Utility > Enable SAP GUI History. The captured history is saved in the default location.
2. To view the saved history location, perform the following steps:
   1. Open SAP Logon and select Options from the dropdown list. The SAP GUI Options - SAP Logon window is displayed.
   2. Expand Local Data and select History. The location of saved history is displayed under Directory for Input History:.

   

   Note: The file is saved in the SAPHistory <UserName> format. To open the file, contact your SAP BASIS administrator.

Control Panel Settings/Control Panel Cloud Settings

This topic describes how to configure the Control Panel Settings or Control Panel Cloud Settings options in the Tools tab. The Control Panel Settings or Control Panel Cloud Settings section is displayed only if you have selected Enable Control Panel under Tools > Options > Enterprise Settings > Control Panel tab.

• After selecting Enable Control Panel, if you have selected Service Configuration in the Connection Type drop-down list, the Control Panel Settings section appears.

  To configure Control Panel Settings,

  1. Select Clear Cache. The cache stored on the local computer is cleared by Process Runner DB now and the average time to access the Control Panel instance is reduced.

     Note: If you are restricted to use any Processes, the option to send access request is displayed. If you try to use the same Process before the access request is approved, an error message is displayed indicating that the request has been already sent to the Control Panel administrator and is waiting for approval. After the request is sent, the option to send a reminder is available only if you clear the control panel cache or restart the Process Runner instance.

• After selecting Enable Control Panel, if you have selected Process Runner Cloud in the Connection Type drop-down list, the Control Panel Cloud Settings section appears.

  1. Select Clear Cloud Cache. The cache stored on the local system is cleared by Process Runner DB.

Visual Style

This topic describes how to use various themes to modify the appearance of Process Runner DB user interface.

To use the Visual Style options,

1. In Process Runner DB, select Tools. The Visual Style options along with other groups of options are displayed.
2. Select a single theme from Standard, Bonus, and Theme options. The GUI of Process Runner DB is modified.

Reset

This section contains information about how to reset the different tools using the Apply Reset option and perform tasks, such as adding authorized computers or clearing the temporary cache, using the Utility option.

Apply Reset

This topic describes how to reset the settings for different tools in Process Runner DB. For example, if you run into an issue with the layouts, you can reset the layout to its default settings.

To reset the settings,

1. Save and close all Process Files.
2. In Process Runner DB, select Tools > Reset > Reset. A drop-down list appears.
3. Perform any of the following steps:
   • Select Reset Layouts and confirm to reset the layout.
   • Select Reset Toolbars and Menus and confirm to reset the toolbars and menus.
   • Select File Association and confirm in the Process Runner DB dialog to reset the Process Files associated with Process Runner DB.
   • Select Refresh Ready-to-Run template and confirm in the Update Samples Confirmation dialog to reset the ready-to-run template samples.

Utility

This topic describes how to use the various options in Utility, such as Proxy Settings and Clear Innowera Temp.

To use the various options in Utility,

1. In Process Runner DB, select Tools > Utility. A dropdown list appears.
2. To clear temporary files and improve the performance, select Clear Temp.
3. To add or delete an authorized computer in Process Runner DB, perform the following steps:
   1. Select RDP Computer Setting. The Authorized RDP Computers Setting window appears.
   2. To add an authorized computer to RDC Computers List, enter the name or IP address of the computer and select Add. The computer is added to the RDP list and you can access Process Runner DB from the computer.

   Note: The total numbers of RDP Computers that you can add to RDP Computers List depends on your Process Runner DB license.

   3. To delete an authorized computer in Process Runner DB, select Delete. The Access Key to Delete RDP Computer window appears. Perform the following steps:
      1. Enter the access key to delete the RDP computer from Process Runner DB. To get the access key, send an email to mag-innoweralicense@insightsoftware.com with the computer ID of the RDP computer.
      2. Select OK.
4. To configure proxy settings, perform the following steps:
   1. Select Proxy Settings. The Proxy Settings window appears.
   2. Select any of the following:
   • Default: Indicates that the proxy server is not installed in the same network as Process Runner DB.
   • User Define: Indicates that the proxy server is installed in the same network as Process Runner DB.
   • Enter the following details:
     • Proxy IP/URL: Indicates the IP address of your proxy server.
     • Port: Indicates the port number.
     • User name: Indicates the name that is used to sign in to the proxy server; user name is provided by the network administrator.
     • Password: Indicates the password that is used to sign in to the proxy server; password is provided by the network administrator.
   3. Select Test. The configured settings are validated.
5. To view the status of the tasks, select Start Task Manager. The Windows Task Manager window appears.