Voodoo Studio & Robot Version Management

Studio - Project Explorer: A "Activate Project" option has been added to the right-click context menu.

Studio - Code step: It has been ensured that the creation date is saved during versioning and the code step is shown when listing the versions.

Studio - Scenario design: An update file is created when a change is made to the scenario steps.

Studio - Export: Background operation, cancelling, tracking with progress bar features have been added.

Studio - Compilation: If the quit button is pressed during the compilation process, the compilation of the next steps is not started.

Studio - Scenario Design Screen: Visual record image insertion feature has been added. When the add image key is pressed, information is written on the screen, the default key is assigned as F11, it can be changed from the configuration file. When F11 is pressed, the picture on the screen is taken and added to the visual record.

Studio - Data Source: When adding a new record, if a row is not manually added to the data source (if the number of rows is zero), a row is added.

Studio - Visual Record: When the start visual recording button is pressed, the Studio is minimized and the countdown screen is displayed. After 5 seconds screen recording is started.

Studio - Debug/Code Step: If the code step for which breakpoint is added in the scenario list is saved in release mode, a warning message is displayed before the debug starts and it is indicated that it should be saved in debug mode.

Studio - Import: Background operation, cancelling, tracking with progress bar features have been added.

Studio - Project: Studio runs scenario change notification in case of project deletion, taking into account possible scenario changes.

Studio - Debug/Code Step: If the code step to which breakpoint is added in the scenario list is not compiled, it is indicated that it should be compiled first.

Studio - Welcome screen: Create project feature has been added.

Studio - Visual Record: Information tag has been added to the screen.

Studio - Scenario Design Screen: With the visual record addition feature, the visual record can be retrieved from this screen. The received record is added to the visual record associated with the scenario. If there is no visual record associated with the scenario, a visual record is created.

Studio - Added Welcome screen.

Studio - Data search step from the screen: Export / import / step copy / deploy structure customised. No image operation in synchronisation object; image is created in server directory during these steps and step registration.

Studio - Code step: System.xml and PostgreSQL database references were added in C# and VB.NET general templates. Version 3 of the templates has been released.

Studio - Code Editor Version Note: Multiple line note writing feature has been enabled.

Studio - Dashboard Step: The interface was changed; features such as active/passive, conditional flow, waiting time were activated.

Robot - Export Rest service added.

Robot - Added a structure that postpones the computer going to sleep and the screen switching off while the robot is running.

Robot - Service : During the transfer of a plan containing a large number of records, recording is performed with the feature of segmentation based on 1000 records.

Studio / Robot - Scenario synchronisation model: The scenario synchronisation mode can be selected according to the SynchronizationMode parameter in the config file. ( Enterprise / Standalone)

Studio / Robot - Encryption option has been added in the management of full-size screen images created at runtime.

Service - Added the ability to add a comment line to the config file. If the line starts with <!, it is treated as a comment.

Service - For database upgrade 3.0, it runs the database scripts given below in MySQL. If PostgreSQL is used, no script is executed; only the version 3.0.0.0.0 information is added to the database.

Service - The PostgreSQL database support has been added.

UC- Robot Service - License information is added when creating configuration information.

UC / Robot Service - Improved the structure showing the step image, added control for simultaneous access.

Robot - Fixed the mouse icon changing when hovering over the status change button.

Studio / Robot - Fixed the problem that the error message is not displayed if there is no plan in the add task step.

Studio - Compilation: Fixed an issue with the compilation screen staying in the background.

Studio - Scenario Copying: Incomplete display issue during project listing has been fixed.

Studio- On-screen data search step: Fixed the display of some controls when text validation is not enabled.

Service - When adding/updating to the MailcJob table, the body field is empty and related problems have been fixed in MySQL and Postgres databases.

Robot - Deploy: During the deployment process of a scenario that includes a code step during deployment, if there is dll in memory, the error is solved. The dll is unloaded and the process continues. If there is an access problem again, we wait and try back-to-back.

Studio - Code Step / CodeSight: Fixed an exception in code analysis if the step is closed without giving a parameter when the triggered function needs a parameter.

Studio - Code Editor Version Note: Version note update issue has been fixed.

Service - The problem of interpreting data pointers as null when inserting into MySql componentclasstemplate with release version has been fixed.

Studio - Language Options: Fixed a problem when restarting the application after changing the language.

Robot - CBS Step: New version resolved dll loading error when running step (CBSLoader.dll)

Studio - Code Step: Correction has been made so that when the name of the code step is updated, the name of the component of the step shown in the development perspective is also updated.

Studio - Robot / Rest Service step: Fixed the problem of accessing input parameters in the rest service step designed before version 2.1.11. Note: Since all parameters are in string type in versions before 2.1.11, they are transferred to the new structure as string.

Voodoo Service - Fixed the error caused by column validation during security check in MySQL layer.

Studio - Plan Management: Fixed an error when the UC ucPddUrl parameter is not defined.

VooDoo Service - Fixed the error in the Postgre database when updating in the application control step.

Voodoo Service: Issues with schema naming in the ComputationStepCurVers functions in MySQL and PostgreSQL layers have been resolved.

Robot: The Owin reference has been updated to version 4.2.2.

Robot: Errors occurring during directory checks at startup have been addressed.

Studio / Robot: The SharpZipLib reference has been updated to version 1.3.3.

Studio / Robot - In the Config section, the AppFlowClientCacheFolder parameter in the Config file is no longer used; the application is provided to decide this directory itself.

Studio / Robot - In scenario synchronisation, it has been enabled to synchronise the code step of the scenario synchronisation process via dataPlugin.

Studio / Robot - The code step was made to work by reading the dataPlugIn data from the synchronised data.

Studio / Robot: The Newtonsoft.Json reference has been updated to version 13.0.1.

Studio / Robot - All steps: The client synchronisation data model has been updated.

Studio / Robot: The BouncyCastle reference has been updated to version 1.8.9.

Studio / Robot: The log4net reference has been updated to version 2.0.10.

Studio - Code step, expression step: The code step, instead of the synchronous model, compiles with the data coming from the service.

Studio- All Scenario operations: Scenario synchronisation is integrated with the update structure.

Studio- Add task step: Corrections have been made to the English interface.

Studio - Development Perspective: The Find/Change window is automatically closed when the screen becomes inactive.

Studio - Plan Management: ID information is being recorded.

Studio - Compilation: The progress bar has been edited to more accurately reflect the status.

Service - The MySQL database has been updated according to the new naming standard.

Studio - Code step: Development perspective opening time optimised according to frequency of use.

Studio - Code step: Templates are listed in name order.

Studio - Import: In the code step, the data source ID data in the code expression is replaced with the ID data saved during import.

Studio - Import: In the expression step, the data source ID data in the code expression is replaced with the ID data saved during import.

Studio - Scenario Copying: If the script is copied to another project, the script name and expression name are replaced with the data sources and saved values.

Studio - Language Options: English interface has been edited.

Studio - Code Editor Project Properties: When parameters such as AllowUnSafe, Debug, NoStdLib, Optimisation are changed, the version of the component is upgraded. This has also been added as an information note in the project properties interface.

Studio - Debug / Code Step: The necessary infrastructure optimisations were made to run the debugged programs as a host under Windows service.

Setup - Changes have been made to VooDooDebuggerService, it is added to the service list during installation and removed during uninstallation.

Studio - Publish Scenerio: Interface adjustments have been made.

Studio - Manage Scenerio: Publish feature can also be accessed from this screen.

Studio - Debug / Code step: DebugTimeout has been added. It is applied for each debug command executed. Read from config file, default value is 30 seconds. If a debug operation exceeds this time, the debug operation is terminated.

Studio - Import : The step id data(s) in the code expression in the code step are replaced with step id data(s) during import.

Studio - Import : In the expression step, the step id data(s) in the code expression are replaced with the step id data(s) saved during import.

Studio - Debug / Code step: In the variable display screen, property and field information of complex types are listed. In special cases such as self-referencing, only this information is listed, the values are not displayed.

Studio - Application bring forward step: If the name or process is empty, it is not added to the list.

Studio - If the scenario consists of some steps (Application start step), it has been made optional to record a visual or associate it with the application.

Studio - Export/Import/Publish: Saving an image in the scenario has been made optional.

Studio - Export/Import/Publish/Deploy: Association with an application in the scenario has been made optional.

Studio - Some Steps: Application start, application control, application end, application bring forward, CBS, icm, keyboard key, clipboard, identification, windows screen setting, rest service, add task, pdf, zip, view data source, file ocr, expression, code, send email, listen to email, dialogue box, the requirement to have an image selected in the visual record when adding a step has been removed.

Studio - Export: Application start, application control, application end, application bring forward, cbs, icm, keyboard key, clipboard, identification, windows screen setting, rest service, add task, pdf, zip, view data source, file ocr, expression, code, send email, listen to email, dialogue box, can be exported if they are not associated with an image.

Studio - Import: Application start, application control, application end, application bring forward, cbs, icm, keyboard key, clipboard, identification, windows screen setting, rest service, add task, pdf, zip, view data source, file ocr, expression, code, send email, listen to email, dialogue box, can also be imported if they are not associated with an image.

Studio - Publish: Application start, application control, application end, application bring forward, cbs, icm, keyboard key, clipboard, identification, windows screen setting, rest service, add task, pdf, zip, view data source, file ocr, expression, code, send email, listen to email, dialogue box can also be published if they are not associated with an image.

Studio - Deploy: Application start, application control, application end, application bring forward, CBS, icm, keyboard key, clipboard, identification, windows screen setting, rest service, add task, pdf, zip, view data source, file ocr, expression, code, send email, listen to email, dialogue box can also be deployed if they are not associated with an image.

Studio - Scenerio copy: Application start, application control, application end, application brings forward, CBS, icm, keyboard key, clipboard, identification, windows screen setting, rest service, add task, pdf, zip, view data source, file ocr, expression, code, send email, listen to email, dialogue box, can also be copied if they are not associated with an image.

Studio - Manage Visual Recording: The component to be run while recording a visual recording is not mandatory, it can be left blank.

Studio - Visual Record: The application is not mandatory when recording a visual recording, it can leave it blank.

Studio - Import: CBS object unique value control has been taken to the business layer level and the import process has been optimized to work on Postgre base - MySQL.

Studio - Visual Recording: If the application is left empty, no application is run when visual recording is started.

Studio - Visual Record: While the visual recording images already exist, they can be re-recorded. In this case, the new images are added to the previously saved images.

Studio - Visual Record: After adding to the existing visual record, the synchronization data is deleted and the final version is displayed when you want to view it again.

Studio - Export: It has been made to support visual recording and no application.

Voodoo Studio - Main menu : “Window” ribbon bar group name changed to ‘Refresh’.

Voodoo Studio - Project explorer, plan explorer : Pressing “F5” on the open explorer refreshes the explorer content.

VooDoo Service - CBS Record: CBS_Key returns the same return value as MySQL Db layer in case of unique key constraint.

Voodoo Service: Base64 memory usage library has been reorganized.

Voodoo Service: Deploy commands have been adjusted to handle long data postings.

VoodooMySQLDAC: The BouncyCastle reference has been updated to version 1.8.9.

Studio, Robot - Screen Data Capture Step: Memory usage has been optimized.

Studio, Robot - Screen Data Search Step: Memory usage has been optimized.

Studio, Robot - Temporary Log Management: Memory usage has been optimized.

Studio - Selected Step Compilation: Performance optimised.

Studio - Plan Management: Trace features have been enriched.

Studio - Scenario compilation: Scenario compilation performance has been optimised.

Voodoo Service: Memory optimization has been performed for database large object (BLOB) operations.

Studio / Robot - License Check: Additional security requirements have been applied.

Studio / Robot - All Steps: Additional security requirements have been applied for image directory access controls.

Studio - Visual Recording Update: Additional security requirements have been applied.

Studio - CBS: Additional security requirements have been applied for running pages via URL.

Studio - Data Source Management: Additional security requirements have been applied for importing Excel and CSV content.

Studio - Log Password Decryption: Additional security requirements have been applied.

Robot - License Installation: Additional security requirements have been applied.

Studio - Diagram Viewing: Additional security requirements have been applied.

Robot - Image Service: Additional security requirements have been applied.

Robot - Log Service: Additional security requirements have been applied.

Studio: If the CBS resource names from the external scenario transfer conflict with the CBS resource names existing in the project, the external CBS resource will be saved with the new name and the relevant warning message will be shown to the user.

Studio: Bot ID can be obtained from the scenario parameters. Example: In the "Add Task" step, the Bot ID can be specified as "\par.ConfBotId\" so that the robot can create a job for itself.

Studio: Adjusted the data source usage in the "Screen Data Search" and "Screen Data Extraction" steps to be compatible with the "Scenario Import" process.

Studio: Added the ability to add text expressions to the text validation section in the "Searching Data from the Screen" step

Studio: Fixed the issue where records would be displayed incompletely if there were records without time information in the plan explorer tab.

Studio: Saving more than one "CBS Source" with the same name is prevented.

Studio: The error caused by the "Run CBS" step using the data source in the "Export Scenario" process has been fixed.

Studio: Errors that may occur due to type conversion in the "File OCR" step have been corrected.

Studio: The icon of the "Dialog Box" step has been changed and the problem with the "Export Scenario" process has been fixed.

Studio: In the "Export Scenario" process, a warning message will be received if there are no steps or visual records of the scenario to be transferred.

Studio: Date selection menu for "Date" type columns has been added to the data source.

Studio: A tooltip has been added to fully display long project and scenario names in the plan explorer tab.

Studio: Fixed an error when getting the number of clicks from the data source in the "Clicks" step.

Studio: PDD viewing in the "Plan Management" section has been updated so that it can be done via the browser.

Studio: Updated warning message regarding deletion of "CBS Source".

Studio: Updated the name of the PDD view button in the "Plan Management" section.

Studio: When using the same data source one or more times in the steps, the data source reference record is updated to be a single one.

Studio: The arrangement of scenario data source references has been updated in case a data source is used in the expression step.

Studio: Transactional functionality has been added to the registration rest service of the CBS step.

VooDoo Service: Some requests have been modified to work with post.

VooDoo Service: The dispatch mechanism in post requests has been optimized.

VooDoo Service: The structure that manages requests through Chunk has been optimized.

Studio: A trace structure has been added to the Application Close step.

Studio : Added tooltip to display project and scenario names that do not fit in the window in the project explorer.

Studio: The Text-In-Wild engine has been added to the File OCR step.

Studio: The error related to screen events encountered during visual recording has been fixed.

Studio: The error of database mismatch encountered during the import of scenarios containing the Database Command Sending step has been corrected.

Studio: Fixed the record deletion error encountered in the Database Management step.

Studio: Fixed an issue when Exporting/Importing scenarios where a data source is used in more than one code step.

Studio: The default maximum completion time for the File OCR step has been updated to 100 seconds.

Studio : The appearance of the "Clipboard" option of the data source selection field in the "Data Extraction from Screen" step has been edited for the English interface.

Studio : Transfer of data sources in Scenario Export/Import operations has been edited.

Studio : If the computer session is to be closed while the robot is running, this situation is recorded. If there is a scenario running on the robot, the operating system is informed that the session is not suitable to be closed.

VooDoo Service: Memory usage has been optimized for file encode/decode operations in the VooDoo Service.

Robot: Memory optimization has been performed for the image extraction function from PDF in the PDF step.

Studio : Fixed the problem of changing column locations when the data source changes in the Create Text Expression step.

Studio: Fixed an error where the file selection dialog box was displayed unnecessarily when using the open from file option during the Text Expression Creation step.

Studio : In the File OCR step, the file path field has been reorganized to accept file paths containing spaces.

Studio : Selecting debug and optimization features at the same time in the code step is prevented to avoid any errors.

Studio : When adding a CBS source, the CBS test operation can only be performed if the test URL is entered in the correct format.

Studio : The location of the EML file path field in the e-mail listening step has been edited.

Stuido : The information screens are now configured to become visible when hovered over the area and to be hidden after a certain period of time has passed.

Studio: A Debug mechanism has been introduced to the code development environment. The Debug environment includes functions such as run, step over, step into, step out, and set instruction pointer. It also features the ability to add breakpoints and watch variables.

Studio : Information screens for fields within steps can now be displayed by hovering over the field.

Studio: The error displaying an incorrect code template when attempting to update code steps within a scenario has been fixed.

Studio: Fixed an error that occurred when trying to select a visual region in a scenario where the visual flow has not yet been loaded.

Studio : The user will now be warned when trying to test without entering a valid URL in the add CBS resource step.

Studio: The issue of receiving a double warning message when attempting to test without filling in valid fields in the CBS source addition step has been resolved.

Studio: The error encountered when trying to remove a data source in the Text Value Creation step has been fixed.

Studio: The English interface of the 'Show External Work List' field has been edited.

Studio: The English interface of the Event Report field has been edited.

Studio : The English interface of the Match Method field in the ICM step has been edited.

Studio: The English interface of the Scenario Import step has been edited.

Studio: In the code step, a new infrastructure has been switched in order to work with codes that have more than one file.

Studio: In the code step, a constructor has been added to the PlanDataInstanceManager class for debugging purposes.

Studio : It has been ensured that the application can be closed safely while running Debug.

Studio: Titles of Process Design Documents (PDD) have been organized in the Plan Management screen.

Studio: The appearance of the Debug Status window has been adapted to the new design.

Studio: The appearance of the functional keys in the code step has been adapted to the new design.

Studio: The version selection screen in the code step has been adapted to the new studio design.

VooDoo Service: Additional trace structures have been added to REST services.

Studio: It is now possible to view process design documents (PDDs) created through the unified console from the plan management section of the studio.

Studio: The 'OutOfArray' error encountered when attempting to create a database connection definition has been fixed.

Studio: The 'VoodooMModelBase.dll cannot be opened' error encountered when using expressions or code step in a scenario, has been resolved.

Studio: Functions in the Expression step can now add help buttons at the 'Group', 'Expression', or 'Parameter' level to their designs using the required XML structure.

Studio: Fixed a tooltip issue in the step navigator in the main screen.

Studio: The views of the "Plan Definition," "Plan Schedule," and "Manage Data Source" tabs have been updated.

Studio: Fixed an issue that occurred during recording in the REST Service step.

Studio: Fixed an issue with the display of image selection controls when using the "Extract from Selected Region" option for "Subregion Analysis" in the "Screen Scraping" step.

Studio : Fixed the issue when the scenario diagram was wanted to be displayed before selecting the scenario visual record or adding a step.

Studio: Fixed an issue with form titles in database definition management.

Studio: The database-related steps within the scenario export and import features have been updated.

Studio: The appearance state of the main form was adjusted on the login screen.

VooDoo Service: The service robot is now configured to start in sessions other than RDP.

VooDoo Service: The Robot Health service is enabled in the enterprise version but set to passive mode in the community edition.

Studio: The runtime code editing version has been upgraded to v1.6.0.

Studio: In the login screen, if there is no user registration, the username box is displayed with the default username "Admin" and cannot be changed.

Studio: If there are no users on the login screen, a "Set Password" button is displayed. This button allows for the creation of a new user registration.

Studio: In database installations, if the user table is empty, users are prompted to create a new user account when they open VooDoo Studio.

Studio: The PDF step now includes a feature that automatically switches the step to an "unchecked" state in case of errors in the actions.

Studio: An additional check has been added to prevent saved database connection definitions from being deleted if they are being used in a scenario.

Studio: The "Publish Scenario" feature is now visible in both versions, but in the community edition, a message will be displayed indicating that this feature is exclusive to the enterprise edition.

Studio: The "Package Management" feature under the "Distribution" section on the main screen has been renamed to "Publish Scenario".

Studio: During the image extraction process in the PDF step, the destination directory can no longer be set as "root directory" or "program files".

Studio: The DAC (Data Access Component) text management has been reorganized according to the logic of code mixing.

Robot: Additional trace structure has been added to the robot maintenance service.

Robot: The "DeleteLocaleDbRecordsAndPreFramesAfterRelease" service in the robot maintenance service only deletes records in the local database, while the "Delete_Directories" service deletes all frames including preframe and ResultEndFrame.

VooDoo Service: Size adjustments have been made for the LRResponselength, Bodylength, and DocumentClassTemplate columns in the MaillCJob table.

Studio : In the PDF Step, a change was made so that the directory deletion operation during image export can now be optionally specified. The default value for the new PDF step when saved is set to "do not delete the directory". For previously saved steps, the default value is "delete the directory".

Studio: The feature of customizing HTTP headers in the REST service step has been added. If the Authorization header is defined in this field, the data defined here will be used for authentication instead of the data selected in the authentication.

Studio: The feature of specifying variable type while creating JSON input in the REST service step has been added.

Studio: A basic service has been written for publishing scenarios, and the enterprise version has the feature of publishing scenarios from the zip file.

Studio: The feature of copying scenario steps has been added.

Studio: The issue related to the waiting time in the Application Control step has been fixed.

Studio: Some modifications have been made in the English interfaces of Keyboard step, Document Table Recognition step and Bring Application step.

Studio: The message displayed on the login screen of VooDoo Studio when the user clicks the "Cancel" button has been removed, and the error occurring in this process has been fixed.

Studio : The System.Buffers.dll reference method in the expression steps has been converted to the core file reference model instead of the framework.

Studio: The English title on the main screen has been edited.

Studio: The "Publish Package" button on the main screen is visible in the enterprise version, while this button has been set to be hidden in the community version.

Studio: Conditional flows can now be expressed using the "end" keyword in English version and "son" keyword in Turkish version for the end of the flow.

Studio: Scenario references in the database can now be managed from the relevant tab.

Studio : In the database connection step, the reference relationship with the database object is added to the database during step registration.

Studio: If there is no previously registered user within VooDoo Studio, the user is prompted for a password during the startup screen to complete the registration process.

Robot : Optimized table creation in local database.

VooDoo Service: Additional trace has been added for more detailed detection of errors in Health Service.

VooDoo Service : Additional notification function about errors in VooDoo Health Service now provides more detailed information.

VooDoo Service : Default value assignment optimization has been implemented in data classes.

VooDoo Service : The TestQueueJSRequest and TestQueueJSRequestCheckResp functions have been improved for memory control and optimization.

Studio : Added ability to save scenario diagram in png format.

Studio : 'Open Step', 'Go To Successful Step' and 'Go To Unverified Step' functions have been added to the menu opened by right-clicking on the steps in the design screen.

Studio : Now the passive steps in the scenario diagram are written in strikethrough font.

Studio : Now, when you select an picture in the file open operation on the scenario diagram screen, the image opens with the default application on the computer.

Studio : Changes made in scenario steps are reflected in the scenario diagram in real time.

Studio : Now when you want to close the application, "Are you sure you want to exit the application?" question is asked.

Studio : Now the relevant node can be accessed even when the text of the node is changed in the scenario diagram.

Robot : After the application is opened, it minimizes itself.

VooDoo Service : If the service health service is closed and there is a remote open session, it operates the robot with this session.

VooDoo CodeSight : The 'ref'/'out' reference type information (if applicable) has also been added to the guide box that opens when writing function parameters.

VooDoo Service : Service cache management has been improved.

VooDoo Service : An error occurring during the recording of the code step has been fixed.

Studio : In the scenario design screen, by selecting the 'View in Diagram' option on the steps, the step is highlighted and displayed in the diagram.

Studio : Some properties (such as color and font) of scenario nodes in the scenario diagram can be customized on a node-by-node basis.

Studio : Changes made in the scenario diagram can be exported as an xml file and when imported again, the scenario diagram can be displayed with its modified structure.

Studio : In the 'Scenario Diagram' feature, a new diagram structure that works in harmony with the theme was introduced.

Studio : A column showing the step orders has been added to the first row in the scenario design screen.

Studio : The new messaging interface has been developed.

Studio : The order of tabs in screens such as Project, Application, CBS Management, and CBS Parameters has been organized.

Studio : Improved the recording time of the code step.

Studio : The step ID data has also been added to the scenario data and CBS references.

Studio : When a CBS object is selected and saved, the relationship between the scenario and CBS is automatically recorded in the references.

Studio : If an actively used CBS in the scenario is attempted to be deleted, the scenario name and (if applicable) step ID information is displayed and deletion is not permitted.

Robot : When the robot is turned on, if VooDoo Service is not active, it will activate automatically.

VooDoo CodeSight : Added Visual Basic intellisense.

VooDoo CodeSight : Added Intellisense property listing feature.

VooDoo CodeSight : Cache management added.

VooDoo CodeSight : The feature of displaying data source parameter alternatives added to the CheckIfExist, GetDataTable, GetCurrentDataDefinitionId, and SetDataTable functions

VooDoo CodeSight : The CodeSight feature can be turned off with a config parameter. If this parameter is not added to the configuration file, it will be on by default.

VooDoo CodeSight : During the process of reference validity verification, a check added to ensure that CBS objects used in the code are defined in the relevant project.

VooDoo CodeSight : Added enumeration feature to VooDoo code editor.

VooDoo Service : The feature of saving scenario reference data while recording the step added. Now these data can be saved in the DataScenarioEntity list while recording the step. Thanks to this feature, manual addition is only needed in special cases (such as global usage on a scenario basis).

VooDoo Service : The MailSend and CBS steps optimized.

VooDoo Service :Added a feature that automatically deletes scenario reference data (Scenario Data Entity) when deleting a scenario step.

VooDoo Service : In the CBS reference listing service, an error that occurred when a null value was received in the name field fixed.

VooDoo Service : The CodeComponent and CodeComponentTemplate items organized to work with mediumText.

VooDooCodeSight Technology is Added.

VooDoo CodeSight - Studio (Auto-Complete): Auto-complete feature after pressing the "Dot Key" is added..

VooDoo CodeSight - Studio (AutoFill): Autofill feature from cursor position by pressing "Ctrl-Space" key is added.

VooDoo CodeSight - Studio (Function Listing): The ability to show overloaded versions of the function with its parameters when calling a function is added.

VooDoo CodeSight - Studio (Data Source): If a function is called during autofill and the called function takes a data source parameter, and also the feature of importing and listing the relevant fields from the project, generating appropriate code is added.

VooDoo CodeSight - Studio (Data Column): If a function is called during autofill and the called function takes the parameters of the data column and also the feature of listing the relevant fields from the project according to the selected data source, generating appropriate code is added.

VooDoo CodeSight - Studio (CBS Step): If a function is called during autofill and the called function takes the parameters of the data column and also the feature of listing the relevant fields from the project according to the selected data source, generating appropriate code is added.

VooDoo CodeSight - Studio (Scenario Step): If a function is called during autofill and the called function takes the parameters of the data column and also the feature of listing the relevant fields from the project according to the selected data source, generating appropriate code is added.

Spelling corrections have been fixed in the English Interface.

Robot Config: "System Buffers" redirection is added.

Terminate Step: Sub Nodes are added under the Terminate Application tree and additional controls and traces are added.

VooDoo CodeSight - Studio: The path is updated as bin}VooDooCodeSight.

Robot: License Service fixed

Robot: Remove Service fixed

CBS Step Added

Studio, Robot : The ability to change the interface language has been added in the Tools menu.

Key step: Added key down to circle and up to circle.

Studio : Open developer perspective menu has been added to the frame menu on the scenario list on the scenario design screen.

Added database version upgrade module.

VooDoo Service: Infrastructure arrangement has been made.

VooDoo Service: Improved command invocation memory management.

VooDoo Service: Http get memory management style has been changed.

Keyboard key step : The text data control to be entered has been edited.

Scenario steps: Interface controls have been adjusted for post-process waiting time "wait-wait" changes.

Scenario design screen: Added additional control when viewing the step status in the step list.

Scenario design screen: Added the ability to move by selecting my name.

Button step : Added pre-keypress cooldown feature, default value is 0.

Button step: Left mouse down and left mouse up actions added.

PDF export to image : memory management has been improved.

Studio: Delete the old version of the code template and install the new version.

Infrastructure components have been upgraded to the new version

DAC command step: English interface has been edited.

Code step: VooDooCommonDAC.dll and VooDooDACRunner.dll dlls have been added to the references.

Code - Expression step: exceptions are detailed.

DAC command step: when the parameter is saved empty, that part is not opened again.

Setup : ConnectLoader.dll has been added under Setup\TemplateLibrary\Common in WinScp.dll setup.

Code step : ConnectLoader.dll, WinScp.dll added to references.

Expression step : ConnectLoader.dll, WinScp.dll added to references.

Code step: Template update feature has been added.

Studio - About screen: expression script and code script hash and file download updated via link and https.

Studio - Expression step: Control panel has been arranged to have 3 columns.

Studio - Robot : VoodooCommonDAC.dll, VoodooDACRunner.dll files are also checked for expression steps during system templates checks at application launch.

PDF step: If there is a target file to be compressed, it continues by deleting it.

PDF step: If an error occurs during compression, it copies the original file.

Studio - About screen: Key sizes have been updated in the Turkish / English interface.

Expression step: The special version of System.buffers.dll needed for Mailkit - Mimekit references has been added to the expression step references.

Setup : The relevant version of System.buffers.dll needed in the expression step has been added to the setup\templatelibrary\common folder.

Database steps added.

Code4 and Code5 fields have also been added to use

PlanInstanceManager: Added SetDataTable function.

Database definition: ConStr end-to-end encryption feature has been added.

Datasource definition: added control not to add fields with the same name.

Data source definition: Added ability to change defined data field type.

Added System.ServiceProcess.dll, System.Buffers.dll, System.Security.Cryptography.Algorithms.dll, System.Net.Requests.dll, System.Net.Http.dll and Microsoft.VisualBasic.dll dlls to expression step .

At the end of the plan, a structure that closes open database resources and performs memory control has been added.

Enabled use of Data Access Component objects in code step.

Datasource definition: added control not to add fields with the same name.

CronExpression field Adding task step Code2 field, but not Code2, has been fixed.

When adding the CronExpression field, the Manage schedule error in Studio has been fixed.

Improved memory usage.

Edited as picture quality transmitted by service.

Changed planDataInstanceProtectedManager instance management.

Data source definition: When the defined data field type is changed, if the existing defined content cannot be converted to the new content type, the error is displayed on the screen.

Reference from database code step: Data Access Component reference dlls are copied from setup directory to VoodooReference\DAC directory in directory control.

Setup: Copying Data Access Component directories to temp directory. If Studio or Robot cannot find the Codebase\Db\ directory at startup

Application run step: If an error occurs during execution, module, special component and parameter information is written in the message.

Studio : Design screen, project selection, application selection, visual record selection, plan selection, schedule selection, show schedule, run schedule, run scenario, select data source, select user, plan result, external work list, view event : In the list The delete feature with the del key has been turned off.

Setup: VC++ 2017-2019 dlls come in the corresponding application directory.

Setup: VC++ 2013 dlls come in the relevant application directory.

Studio : The design screen search buttons locations have been adjusted.

About : Script download keys are set to active/inactive instead of visible/invisible.

Expression step: If expression is selected in free expression and if the selected expression has validation defined, validation is not executed.

Expression step: It is possible to record without selecting an expression in free expression.

Expression step : Changed "create expression" button to "add expression".

Expression step: In Regular expression validation, if the control is visible, validation is done.

Interface Control Manager: Added description field to actions.

Interface Control Manager: Control, query possible actions feature button has been added.

Interface Control Manager: Added sequential control access feature.

Studio : The problem of searching by id and name in the design screen has been fixed.

Key, calendar, data list, document table recognition, data extraction from the screen, data search step from the screen: The problem with the step flow default value has been fixed.

Studio : Running as Administrator. It has been ensured that file copying problems that occur at the first boot do not occur.

Studio : Recognition parameters screen ocr engine iteration problem is fixed.

Studio : Adjusted additional controls in case of intended drag and drop.

Expression step: The problem that occurred during import has been fixed.

Expression step: Code editor features have been enriched.

Expression step: Added intellisense for VooDoo classes.

Studio : The design screen has been adjusted to fit 1920x1080.

Debug : Added additional check on variable representation.

About: English version has been edited.

Studio : Recognition parameters selection validations have been adjusted.

Interface Control Manager: Memory management in infrastructure has been arranged.

Interface Control Manager: Data entry objects have been edited.

Interface Control Manager: Workpiece model developed.

Interface Control Manager: Expanded the character capacity.

Code editor: Basic scripts for C# language have been added with tab tab.

Code editor: Added auto-completion feature for { and ( in C# language.

Document table recognition step: Added additional exception handling.

Code editor: Ctrl-I auto-indents.

Voodoo C++ : Infrastructure improvements have been made.

Voodoo .NET : Infrastructure improvements have been made.

Feature to listen to email box, import empty encrypted data when importing text box have been added.

When working with the new version VooDooCommonData, a data source id value is given in the code and expression step, and if the id value is not loaded in memory, then ArgumentException is thrown and the data source id value is written in the description.

If the script is disconnected from the data source used by a step other than the code and expression step, ArgumentException : "Data source not loaded, id : " ... error is received as a run-time error, even if the old version is run with VooDooCommonData.

Scenario design screen: Scenario steps can be sorted with drag and drop feature.

Compilation step: The screen turns off when the Enter key is pressed.

PDF image extraction action has been added.

Zip extraction step: If there are duplicate file names in the zip file, the feature of extracting the file by renaming has been added.

Robot : The ability to manually close the background form is blocked.

Robot : Task processing routine has been fixed.

PDF Step: Compress feature has been added.

Debug has been completed with basic features.

Zip step data source usage has been fixed.

Document table recognition step: The feature of matching region of interest from coordinates has been added.