Download winshuttle transaction 10.1 - Previous versions
Looking for:
Download winshuttle transaction 10.1 |
Previous versions - Download winshuttle transaction 10.1
Download winshuttle transaction 10.1.Winshuttle Function Module: Installation - PDF Free Download
Unused fields from a web service are treated as blank fields and are uploaded to SAP wiping out existing values. Uses can choose to post data into SAP with a form using credentials of a pre-selected System post designer account.
Disabled fields can be recorded using GUI scripting mode to enable download of these values. The loop layout in excel sheets has been improved in case of multiple loops. The loops at same level with different identifier columns do not need to follow row indentation in the excel sheet. Upload time is available in seconds in the exported log to enable analysis of log data based on time to upload. If a scheduled task did not run, an email is sent to the users in the notification group stating the cause of failure.
Application instance closes automatically at the end of a scheduled run. Total time taken to run column is added to the log viewer. Undo-All button has been added to the mapper to undo all changes since last save. Tool tip in log viewer does not show full file path in case of linked file, with carry settings. Incorrect error message is displayed when user closes the excel application while it is running in addin.
Incorrect status message is seen when Run is stopped before finishing in German Locale. While running Linked files with carry settings using a secure license and second file run canceled at logon, next file auto runs when opened.
User is displayed as disconnected from the server in the status bar, even while the data is being uploaded when the sustained logon timeout limit has timed out. Application selection bar shows wrong script name on stopping linked file run. Toggle of already mapped fields to workbook to Read from SAP changes field mappings.
Index-based loops are provided for GUI scripting mode to allow appending data into grids and tables without the need of creation of a repeatable pattern. In GUI scripting mode, users can specify an if on index field condition to allow users to specify a row for updating other fields based on a key value. The program can now be completely re-sized, and flickering while navigating between different screens has been reduced.
A tracing option has been added in the options area to help customers resolve of program issues faster. The log viewer now gives details of scheduled runs that erred out and marks them for easy identification. Error handling has been improved for GUI scripting mode to return more descriptive and relevant messages in the log message column.
Validation and Review is supported on a Production System during a review process. Scheduler cannot send notification e-mails when case proxy authentication is required. Using an ALF that was created without a specified logon language, produces error messages in the log messages column when the script run even for successful updates. Log column overwrites mapped columns data without issuing a warning in case this column is mapped to line item field or is an identifier column.
It is not possible to add numbers [ Users cannot use more than fields in their scripts for upload or download. Users cannot see log messages, Error message, or Data downloaded messages if Excel spreadsheet is protected. On some Windows based environments, an entry point error is observed every time users try to access update page.
Clicking Cancel on non-existent date warning and then scheduling a run with correct specifications does not schedule and results in a Task already exists error. On French and German operating systems, an error occurs on specific rows filtered if script is run on Filtered rows.
When the network connection has been disrupted, an exception occurs when clicking Save while exporting a log. Exception occurs on network failure in between the running of a file.
Long text field and log field can be mapped to same Excel column value. An error occurs on editing and clicking on the outer loop of a nested loop or IF construct. Notes saved for previously disabled fields, disappear on reloading the file, even though the fields remain enabled. When upgrading from 2. Mismatching messages for views shown in data file document library.
A user does not get the admin role when group which has unique permissions is added in Admin Roles. User who is Team Site member is able to view data files of other users. Report showing licenses and usage Retain approval of files after migration Central Upgrade from Excel data files can be sent as an email attachment at the end of a scheduled run desktop scheduling.
Transaction Auto mapping is enabled for cell based mapping scripts. Validation error messages for the 'Validate' feature appear during design time in addition to Run. Users can copy rows from a construct within the same script and to a different script as well.
Validating a protected sheet with extended logging turned on, results in an error. Validation is always performed on the active sheet in the Add in irrespective of "Bind to Sheet" setting.
Error for an XML form with no upload fields does not come before the dynamic form is launched. For a Direct-based script, the fixed value fields are shown as valid input fields in the dynamic form. Read from SAP fields are not shown on the dynamic form as "Read only" fields.
Product name in the log header of the Excel file is not consistent when the script is run from Client versus when script is run from the add-in. Step by Step run modes are disabled in Excel add-in for the Enterprise mode. Not able to put if condition checking if the log column is empty, around the complete recording when Access is the data source.
Users are allowed to use internal e-mail servers to send scheduled run notification e-mails. Users are now allowed to use Extended Log with Validation.
It is now possible to select multiple values for a cell range using SAP values in the add-in for Excel. Auto logon with message server does not work as desired. The mapper preview takes a long time to upload when the add-in for Excel is enabled. An error is received after successful run of a transaction in the add-in for Excel on Russian locale. A misleading information message is shown when the user tries to assign an Excel column as a header ID for a loop.
An error message appears after a successful run if the data file contains a graphical object, such as WordArt and the Advanced Run option to close the Excel file after run is checked. Skip transaction if Empty with read from SAP fields does not give consistent results.
Long SAP transaction code overlaps the recording mode on the top panel. A misleading message is received on running a workbook marked as final. EndSession command is not able to release RFC sessions. In some cases, Virsa firefighter does not show the correct number of sessions that it can attach to. Log viewer shows incorrect details in the ROI details if the total time saved exceeds 24 hours.
Using Virsa firefighter logon, if no open sessions are present, the pop-up does not disappear when Cancel is clicked Users cannot use GUI scripting recording mode to record some transactions in CRM systems.
Skip screen if not found does not work as desired in step by step stop on errors mode. Auto logon does not work correctly when you log on using logon groups. In some cases, the Excel preview in the mapper takes more time to load if the add-in for Excel is enabled in the application options. Long text does not get recorded with some plant maintenance transactions for SAP release 4.
Long text recorded with Non batch with controls mode is not able to upload more than characters. When we try to run an Excel file with. Blank lines in saplogon. If there is no data in the loop items, the detail fields do not run. For some regional settings of the operating system, the logon pad shows OK button as disabled. For line items, transactionSHUTTLE tries to run on rows that do not have a line item identifier, but does not upload them successfully.
The subsequent files run on all the rows of the active sheet. For Fixed mapping type, it is not possible to set the value of a field to a blank. If not first transaction and IF first transaction does not work when Access is chosen as a data source.
Fixed value upload does not work correctly for long text fields. ROI details in the log viewer are not shown correctly for transactions with line items.
An error appears when we try to run on errors if the Excel version is and a color has been chosen under Error Management options to mark errors. On using step by step mode with GUI scripting, Excel remains in the foreground making the debugging difficult for the user.
Correct error message is not shown when we try to edit a nested loop and incorrectly set inner loop start row equal to outer loop start row.
An error comes up when we record long text in a non-applicable mode other than Non batch with controls or GUI scripting. An error occurs on applying a loop construct in an Access data source when either the header or the line items table does not have columns. An error occurs when we open an access data source with blank database and click on update mapping. A new Validate option allows users to validate their data file or script before actually uploading it.
Users working with EP logon will now be able to schedule script uploads. Generate support information is now available as a separate button in the help menu. Log viewer has additional information column for SAP username. A new color and prefix option has been added for fixed errors.
The status bar for the add-in has been separated from the Excel status bar to avoid masking of Excel status messages by the add-in. Recent files can now be viewed on the basis of last time they were used. Production server warning has been removed as the first screen.
End session command has been added in the editor to re-set SAP sessions after a specified number of transaction runs.
Mapper area has been increased to allow more space for script design. A data file can be archived to the archive data library once the data files reach a Run Completed state. The setting can be controlled from the server. If the process is not enabled on the server, SHUTTLEfiles will not require approval after a submission and will directly move to production. If not Run on Errors is not enabled from the server, users will not be allowed to make changes to error records and Run on errors for approved data files.
ROI details are now available on the reporting page. A new option has been provided on the licensing page to remove old licensing. The information for the number of days is truncated for ROI details. Date field is not correctly uploaded using MS Access as a data source. Number of records are not shown correctly in German version of the application.
Space is not accepted as a valid character with Contains operator for an if construct. Scheduler time format is not same as the system time format. Application needs to be restarted after extending an evaluation license in order to use the extended period. If the user specifies a list of email addresses in the E-mail Notification field in the Scheduler Wizard and enters the separator ; after the last e-mail, an error occurs. Line Items are not uploaded correctly if the common field for the header and the line item table name contains a space.
An IF construct applied on rows above the rows containing an if-else construct, results in improper placement. Run not Posted setting in the Advanced Run options is not functioning correctly. An error occurs on publishing an Excel data source file linked with an Access data source file. Write headers does not write header for Extended Log column.
On Validating an Access data source script, an error occurs when the if condition around the loop equates to false. Run on Errors does not work as expected if the data file is protected. Specify row for update does not work correctly if the field being updated is a check box or a button click. If you run a column mapping script on selected or filtered rows and then open a cell mapping script, an error appears. Filters do not work correctly for all options in the Expert mode in the mapper.
If on indexed field cannot be edited for a script with cell-based mapping. An error message appears if the Excel cell range used for importing a Validation list contains a single value.
If the "Application trace" setting is ON, the user will get a warning message indicating that the setting can result in a slower run. GUI scripting supports "Skip screen if not found" property. Excel data files can be sent as an email attachment at the end of a scheduled run. The number of files in the Recent Files list can be configured from the Application options. Default "Skip field indicator" can be set from the Application Options.
Log header information can be customized from the Header Log Details option. Advanced run option "Append timestamp to SAP log messages" appends time stamp to log messages returned in the data file. Validation log column is available as a field in the mapper and can be set during script design time and also from the run screen. If "Skip screen if not found" property has been set for non-applicable cases e.
Writing headers for cell based mapping has been enabled to allow users to create Excel forms in an untitled preview. Validation error messages for the "Validate" feature appear during design time in addition to Run.
The detailed line recording values appear at correct row in the untitled preview, next to the line identifier rows. A parent category and classification view is provided in the Direct script consumption screen. Users are allowed to copy rows from a construct within the same script and to a different script as well. Notes can be added to the mapper fields and screens for Direct based scripts. Some UI strings are not localized in all supported languages.
If an "If" condition around a loop evaluates to FALSE for a row, all expected transactions after that are not processed irrespective of the result of the "If" condition. Validating a protected sheet with extended logging on, results in an error. If a cell is mapped with multiple SAP fields, the Excel file Validation goes for entire loop row range. Space or tab in the header loop identifier results in inconsistent data upload.
Validation is always performed on the active sheet in the Add-in irrespective of "Bind to Sheet" setting. Validating a data file with line items on erred out records results in inappropriate log messages. Authorization check returns wrong values for function group authorizations for some users. The naming of log field for Access data source is inconsistent across different screens. Not able to put IF condition around the complete recording for log column is empty when Access is the data source.
Connection to SAP is not closed on cancelling a recording from the Recording properties screen until the user exits the application session. Loops indicator line is not displaying properly if manual additions are done to the mapper screen. Publish option is disabled when a template is downloaded and saved using "Save as" button instead of Save button.
An error occurs on clicking "Bind to sheet" or "OK" button on the publish dialog while the file is getting published. Notes are not properly saved for screen fields. UI issues are seen on "Open" and "if" icons on some locales. Cell mapping on the first row of the preview fails if the Spreadsheet gear option is turned off.
On a Citrix environment, users cannot launch application if the application options file has not been created due to user authorization problems. No way of changing loop type on switching from Cell based to Column based mapping. Uses can choose to post data into SAP with a form using credentials of a pre-selected System post designer account. Disabled fields can be recorded using GUI scripting mode to enable download of these values.
The loop layout in excel sheets has been improved in case of multiple loops. The loops at same level with different identifier columns do not need to follow row indentation in the excel sheet.
Upload time is available in seconds in the exported log to enable analysis of log data based on time to upload. If a scheduled task did not run, an email is sent to the users in the notification group stating the cause of failure. Application instance closes automatically at the end of a scheduled run.
Total time taken to run column is added to the log viewer. Undo-All button has been added to the mapper to undo all changes since last save. Tool tip in log viewer does not show full file path in case of linked file, with carry settings. Incorrect error message is displayed when user closes the excel application while it is running in addin. Incorrect status message is seen when Run is stopped before finishing in German Locale. While running Linked files with carry settings using a secure license and second file run canceled at logon, next file auto runs when opened.
User is displayed as disconnected from the server in the status bar, even while the data is being uploaded when the sustained logon timeout limit has timed out. Application selection bar shows wrong script name on stopping linked file run. Toggle of already mapped fields to workbook to Read from SAP changes field mappings. Index-based loops are provided for GUI scripting mode to allow appending data into grids and tables without the need of creation of a repeatable pattern.
In GUI scripting mode, users can specify an if on index field condition to allow users to specify a row for updating other fields based on a key value.
The program can now be completely re-sized, and flickering while navigating between different screens has been reduced. A tracing option has been added in the options area to help customers resolve of program issues faster. The log viewer now gives details of scheduled runs that erred out and marks them for easy identification.
Error handling has been improved for GUI scripting mode to return more descriptive and relevant messages in the log message column. Scheduler cannot send notification e-mails when case proxy authentication is required. Using an ALF that was created without a specified logon language, produces error messages in the log messages column when the script run even for successful updates.
Log column overwrites mapped columns data without issuing a warning in case this column is mapped to line item field or is an identifier column.
❿
Comments
Post a Comment