ASG-Studio 6.3 Release Notes

ASG-Studio installer is enhanced to support direct upgrade without uninstalling your earlier versions. This enhancement is available to upgrade from ASG Studio versions 6.1 and above to 6.3. See, Upgrade ASG-Studio.

Composite Webservice Datasource: Allows composition of different webservice methods that perform individual operations. See, Create Composite Webservices Datasource.

Also a set of new composite webservice APIs are available that can be used to set memory variables. See, Composite Webservice APIs.

Server Script APIs: A set of new Server Script APIs are available to execute various functions including database queries. See, Server Script APIs.

Form Validations: UI controls are enhanced with Form Validations options that helps to submit a form only when the specified validations are satisfied.

Button Menu: A new Button Menu control is added to provide menu with an interaction that navigates to another view.

Preview: You can now see the saved changes by refreshing your Preview window. You must refresh only from the home page of your application. Previously, you needed to click Preview every time you saved the UI model to see the updates.

Pack: The Pack functionality is enhanced to package your UI model and enable preview option with increased speed.

Custom HTML: The Custom HTML control is renamed to Block Custom HTML and enhanced to support Construct View Frames.

Block Controls: New Block controls are available that can be used as customized UI controls to support various selectors associated with custom HTML.

Process model is enhanced to support various functionality using APIs in the custom scripts. You can now add the custom scripts that include APIs in Script Task and On Before and On After options in any other tasks in the process model. See, Process Services APIs.

Datasource Commands Automation: Provides Datasource Commands Automation activity to execute a webservice method that is available in the specified datasource. You can use these activities to connect to a datasource and execute a webservice method. See, Datasource Commands Automation.

SAP Automation: Added SAP Automation activity group that contains activities designed to connect to SAP client and efficiently automate tasks or work within that SAP client. These activities are generally used to log into SAP client, run a transaction, perform element action, and log out from SAP client. See, SAP Automation.

Recorder Actions Automation: Added Recorder Actions Automation activity that enables you to easily capture the user actions in a web application and translates them into sequences. You can modify these recordings to easily replay and reuse them in as many other recorder action activities as you need. You can record user actions in a web application only using Google Chrome web browser. See, Recorder Actions Automation.

A set of new Log APIs are provided to add additional log messages at various levels such as INFO, DEBUG, WARN, and ERROR. See, Log APIs.

1. Variable suggestion to be displayed irrespective of preceding or succeeding text present in any RPA activity field.
2. In Web Automation, Web Element Action, the Get Matching Elements should be used only with Find Elements By (Any Locator) as Search Type. You can now use List as Search Type in Web Automation, Web Element Action.
3. When user modifies Excel File path in Debugger Window, Excel was not set to Foreground.
4. Logs in Debugger are overlapped when scrolled within Debugger panel.
5. OCR configuration window is closed when clicked outside OCR screen.
6. Multiple Email attachments was not processed in Send Email and Compose Email activities.

1. Issue: Sync option does not auto refresh the expanded section in project.
   Workaround: Collapse the section and expand again for the changes to take effect
2. Issue: When I import a project for second time after deleting the same project that is previously imported, on click of Save or Pack, the error message is displayed as "Code Generation Failed." This issue occurs only when you delete an imported project and again import the same project.
   Workaround: After importing the project you must navigate to each of the project resource such as datasource, UI model, process model, RPA model, and app roles, select the values in each field again and then save the project.

1. Issue: Where pack routing is used, the values in the UI fields are not updated after the page reload in Preview.
   Workaround: Delete the browser cache and launch the Preview again.
2. Issue: External CSS and My Styles in UI model causes cache issue.
   Workaround: If styling changes are not reflected in the canvas or in the preview, delete browser cache and apply the styles again.
3. Issue: In an imported project, if the UI model uses external CSS, external JS, or image files the preview does not look as expected and as designed using the external files.
   Workaround: Select the external files again in UI Model and save to reflect the changes.
4. Issue: When you import a project into ASG-Studio 6.0/6.1/6.3 from a previous version, the app view icon is not applied to the existing UI model though the corresponding image file is available in the project.
   Workaround: This issue occurs only with the imported projects. The image file will be available in the project after the import but does not automatically apply to the UI Model visual designer. Open the project that you imported and navigate to UI Models. Open the UI Model and select the image from the App View Icon drop-down to use as app view icon. Click Save. The app view icon is applied to the UI model.
5. Issue: When you save or pack the UI Model, the operation takes approximately 2 to 3 minutes. While the save or pack operations are in progress you cannot perform any other operations. This issue occurs based on the number of UI controls and design aspects of your UI model and the size of your app.
   Workaround: It is recommended not to perform any other operation on the UI model while saving the UI model is in progress. If saving or packing the UI model continues for long time, you can choose to click Clean to stop the current build process and then Save the UI model again. Do not attempt to exit ASG-Studio or stop the ASG-Studio service while the UI model is saving. Any such attempt may lead to loss of your updates to UI model.

1. Issue: The imported project does not retain the decision model selected in the decision task of process model.
   Workaround: Select the decision model in the decision task of process model, enter the values as required and save.
2. Issue: The loop back from one user task to another user task does not work.
   Workaround: Do not directly loop back from user task to user task. Insert a manual task between the two user tasks and loop back via the manual task.
3. Issue: The imported project does not display the Form in Inbox.
   Workaround: After importing the project, open the process model and update the User Task. You must reselect the Form and add List of References in user task and save the process model.

1. Issue: The RPA automation activities that have Window Name or Choose Window property set to Current Window will not work.
   Workaround: The value of Window Name or Choose Window must be enclosed in [ ]. If you have specified Current Window as Window Name or Choose Window, you must modify the value from Current Window to [Current Window].
2. Issue: If you start executing a bot and then close the ASG Bot Engine, the RPA visual designer remains in processing state.
   Workaround: Save the bot, refresh the RPA visual designer window in your browser and run the bot again.
3. Issue: In Desktop Automation, when you try to rearrange the Click Element Action Key Value in the properties panel of Windows Element Action, the items do not move as expected.
   Workaround: Delete the list and add the Action Key Value set again based on your requirement.
4. Issue: When running a bot with Excel Automation activities, sometimes an InteropService error occurs.
   Workaround: Close all Excel spreadsheets open in your machine before executing a bot with Excel Automation activities.
5. Issue: When you run a bot with Word Automation activity, the action is not executed and a Word document does not open.
   Workaround: Rerun the bot and check if the Word document is opening.
6. Issue: If you are expanding the Sub Process activity in the visual designer, the activities encapsulated in the Sub Process sometimes can overlap or expand. The connector and sequence of the activities do not appear.
   Workaround: Expand and collapse the sub process shape.
7. Issue: When you run a bot, you might see that the log messages are not fetched, and the bot is continuously in processing state, even after all the activities are executed.
   Workaround: Close RPA Model window in ASG-Studio. Restart RPA Bot Engine and refresh ASG-Studio window.

1. When your process app is executed in ASG-Zenith Portal the Priority and Due Date values entered in the app interface do not work. This issue occurs in all the process apps and the values entered in the fields designed for Priority and Due Date are not passed to the process model.
2. Where pack routing is used, the routing does not work if the target UI model is not previewed at least once.

1. The Process Model can contain only Script Tasks and End Event in the sequence flow going out of the Timer Boundary Event.
2. The Process Model which contains a loop back task may result in memory hogging in ASG-Zenith Portal (SaaS) and causes server restart. Users may experience a downtime of the app access during this period.
3. In Process Model User Task if Assignee is set to Role, the Inbox notifications does not display message body.

1. RPA bots function correctly only with Office 2016 or higher version. You might see an error when using the earlier versions of Office.
2. When you are using Run Macro activity in Excel Automation, you must save the macro file under the path: C:\Users\<username>\Documents\.
3. OCR Automation activity for extracting information from the indicated user interface element or image supports the Windows display scale set to 100% only.
4. In Read Email activity of Email Automation, if you have selected the Search by From Address option in the Search Type field, the data from emails with CC and BCC fields are not extracted.
5. The analytical log messages for Web Element Screenshot, Perform OCR, and Read Email activities are not displayed.