Process Discovery

https://youtu.be/qHyu-vamzBQ

Knowledge Sharing - performance issue and a fix for LogonExpert The following performance issue has been found in v19.5.x and might be even relevant for earlier versions (not verified yet): If an unattended robot is defined in Console without credentials, the robot will “pause” for full two minutes (!) before every task run.It was due to an issue with LogonExpert that had a timeout of two minutes in case it tried to “unlock” the session when no credentials were set in the machine. This was solved as part of LogonExpert v7.9 that was released two weeks ago.We recommend to upgrade the LogonExpert version for Unattended customers running 19.5.x:https://ln2.sync.com/dl/f69a60530/vre5xnid-2ricuefh-hqg4m2v9-c4h3e2hc LogonExpert can be upgraded separately from the Kryon sol

Please note that starting v20.3 the default minimum level of log writes in clients (Robot/Studio) will be changed from “Verbose” (=All levels) to “Information”. That means that all the debug log writes from Robot/Studio will not be written to SEQ by default.We already got reports and confirmation from a customer (Wyndham) that this change causing a significant improvements in the client side performance (memory, disk IO) for version 19.5.x. In case you want to change back the Robot/Studio config to write also debug level, do the following: In the “config” sub folder (of the Robot/Studio), open serilog.json to edit, and –Replace the line"LevelSwitches": { "$controlSwitch": "Information" },with the line"LevelSwitches": { "$controlSwitch": "Verbose" },

For customers that are experiencing issues with LogBeat logging, and increasing DBlogs: R&D suggested the next changes as work around untill we have permanent solution: 1) C:Program FilesKryon Robot20.3.0.28LogBeatLogBeatConfig.json   "BatchCount": "1000", "RetentionRunningIntervalMinutes": "30", 2) C:Program FilesKryon Robot20.3.0.28Configserilog.json   "LevelSwitches": { "$controlSwitch": "Verbose" },   -> Change the value to Warning  Please monitor and update with the results.

 Watch this video created by Eyal Zamir:https://kryonsystems.atlassian.net/wiki/spaces/AT/pages/998539265/SEQ   

In the cases, if the customer is not inclined to use outlook for sending emails: there is an alternative way to send an email by Using Kryon Rest API or curl Advanced commands. With these AC an email can be sent by using a third party company that provides such services. e.g. the integration of SendGrid.com or other similar service providers and Kryon Rest API/ Curl AC will give you an alternative option to send emails.Special thanks to @Darren Cheng​ for his support on this.

To add a new user to the Aerobase is possible also with using CMD. Simply run the below command with CMD: bin/add-user-keycloak.[sh|bat] -r master -u -p  

Workaround for the Whitelist / Blacklist special sign issueKnowledge share by Ziv @Theo Charles Schmidt-Zimmermann​  help @Ziv Ilan​  find a bug in PD versions 20.1 and 20.2 with adding URLs with special characters (“-“ for example) to the applications list. In the meantime you can use the following workaround to add URLs with special signs to your black/white list –Add the relevant URL without the special sign Download and install DB Browser for SQLite - https://sqlitebrowser.org/dl/ - an open-source tool which is very friendly to use Open the orchestrator.sqlite file from the following path - %programdata%KryonOrchestrator Go to Browse Data and select Persistence from the drop-down Go to the relevant tenant and to the relevant list and add the special sign – 

Knowledge shared by Oren With the introduction of the new ConsoleX, a few more services were added to the list of Kryon RPA Server services.Before I will explain on each one, I will note that the list of services is expected to keep grow as we are switching to Micro Services architecture. The new services will be installed of course only if you select to install ConsoleX.In the next version we plan to remove one or two redundant services of the old Console in case the new ConsoleX is installed (this change did not make it to the upcoming v20.3 release). A few terminology explanation before we continue:FE – Front End, the UI of a web application, AKA “Client application”. Runs on a web hosting engine, like NginX.BFF – Backend for Front End – the server side

Install SEQ on a separate machineKnowledge shared by Oren A few people have asked me how to install SEQ on a separate machine, with all the configuration that are required for Kryon.So we have prepared an installation kit for you that wraps SEQ original installation kit, and also configures everything that the RPA / PD installation does. http://jfrog.kryonsystems.com:8081/artifactory/Common-Installation-Resources/Kryon_SEQ_Wrapper/dev/Kryon_SEQ_Wrapper.exe This installer knows to handle cases that SEQ is already installed, upgrade of SEQ, etc. Currently the installer UI is poor, we will improve it for next versions.

SSL/TLS certificatesKnowledge shared by Oren This knowledge sharing article will cover:Crash course on SSL/TLS Certificates Lessons learned from last week installation How v20.3 installation kit will make our life easier with certificates The following explanation is in my own words.This topic is very complicated, I personally learn new things all the time, so I tried to simplify the explanation in the price of being not so accurate here. What is the difference between SSL and TLS?It is the same thing actually. SSL is the old standard name, and TLS is the new standard name. SSL counts today as very not secured,but everyone are still using this name as it was the first.The latest version of TLS is 1.2 . before it there were TLS 1.0 and 1.1, both counts as not secured anymore.There is a new version of TLS going to be

"Breaking compatibility without breaking it" for WebAPI with the new ConsoleX (v20.3+)Shared by Oren With the release of ConsoleX, as you all know and anticipating, we are moving from IIS to Nginx.This move include both the Console itself and our Web API (Add Task). The purpose of this post is to share knowledge on how we are going to “break” the compatibility together with providing instructions how to “fix the break” to allow customers the time to adjust to the new change. I recommend that when preparing the 20.3 upgrade plan – to map which customers are using WebAPI and communicate this change is coming.The documentation of all of this is still very rough, so keep that in mind. So what has been broken:1. We dropped the support for repeats for Add Task. That means that each call to Add task will create only one task. No more option to create multiple tasks

Updated guide on how to use the toolkit with PD

 (Knowledge shared by Oren) We don’t officially support, for a very long time now, exporting wizards from old version (for example 19.1 or 5.25) and import into a new version (for example 19.5). We defined it a long time ago as out of scope of testing and development, as this situation should not happen in customer environment. Technically the import process might end successfully, but there could be issues inside the wizards.Some wizards might imported successfully without any issues, and some don’t, so please avoid doing it on customer environment. But more important –when upgrading a customer environment from old version – never plan to install a new DB and then importing the wizards from the old version! Always do the upgrade on the original DB (with the wizards) or on a duplication of the original DB. If you think it is important we will support suc

 Knowledge shared by Oren I understood that some of the people that install 19.5.1 avoid using the feature of generating Robot/Studio MSI wrappers because it take 2-3 minutes more time in the installation.As a result – they use the EXE version of the client EXE setup, configure the appSettings and LogBeat manually, make sure to copy the config files to every client machine, and then throw on the customer IT to keep copy this settings files.It sounds to me not so productive. One more important thing that you probably don’t know – if the FQDN of the server is being provided to the client installation, it will know to automatically configure the “Trusted domains” settings in IE, and save you yet another 1-2 hours trying to understand why the SSO does not work. So I ask you – ALWAYS create the client MSI. ALWAYS. For future version we will create in addition to the MSI files also batch file for the EXE

Hi there, community members! This week we are introducing you with Elise Marx! ? Elise joined Kryon in November 2018, and she is a Global Manager of Business Development. She grew up on a farm in a small town in Connecticut and moved back to raise her children there. She is located in between Boston and NYC! The first product she heard about in Kryon is Process Discovery, when she was interviewing and learning about Kryon. It was what she was most excited about and why she joined the team- isn't that cool?! This is what excites Elise about RPA: "I have the fortunate perspective of not only being a technology sales person but also being on the customer side of purchasing and implementing technology as well. When I think about RPA and all of the areas that can be automated and optimized so that the work force can ultimately be more efficient and successful - that is exciting to me!"  Here's a

Knowledge Sharing - Audit trail for SEQ login:shared by Oren We’ve been asked (by a customer) if SEQ keeps audit log for login to SEQ itself (when authentication is enabled of course).See below the answer. On a side note – please avoid addressing SEQ support directly. It is a sensitive point in our license agreement with them.For any questions that should be addressed to SEQ, send them to Oren and Aviad.

Kryon IaaS - How to use itKnowledge shared by Oren This item will get you familiar with our IaaS Jenkins jobs, so you will be able to manage your own machines in our cloud, for example to test Ldaphelper, etc. In General:Here is the main link to all Jenkins IaaS Jobs:http://jenkins.kryonsystems.com:8080/job/IAAS/(you need to connect to VPN first). Our IaaS allows you to create and manage your own VMs in AWS (and also in Azure, but it is less used).(The below instructions refers to AWS machines only.) General notes:Each machine that you will create will be automatically shutdown on 20:00 Israel time, and will be terminated 48 hours after it was last shutdown.You can start it every day, and by that keep it alive.There are also two (ne

 See HERE the recorded webinar.Add comments / questions if you have any

How did we solve "RPA DB failed to populate" issue in BGL with 19.5.1Knowledge share by Oren Configuration: Single machine, user password, SQL express 2017 was installed manually on the same machine, no TLS.The symptom:Installation completes, RPA DB is empty, Authentication DB is populated correctly.Digging into logs, found the following error: SqlSearch: Executing SQL query 'SELECT CAST(HAS_PERMS_BY_NAME(QUOTENAME('Keycloak'), 'DATABASE', 'ANY') AS VARCHAR)'. Server='PEG-RPAAPPDEV02', Instance='SQLEXPRESS', Database='', User='sa'. Will place results in property 'ab_sql_db_exists'SqlSearch: Error 0x80004005: Failed to initialize connection to Server='PEG-RPAAPPDEV02SQLEXPRESS', Database='', User='sa'. SSL Security error.SqlSearch: Error 0x80004005: Failed connecting to databaseCustomAction SqlSearch returned actual error code 1603 (note this may no

Justin Kruse, RPA Lead at LTCG: “We recognize the huge value that Kryon ProcessDiscovery™ delivers in conjunction with RPA, and we’re certain that our working relationship with Kryon will help us to boost our digital efficiency quickly and easily.” Read the full story here: http://bit.ly/370vsFN

Keycloak / AerobaseKnowledge shared by Aviad KeycloackKeycloak is an open source Identity and Access Management solution aimed at modern applications and services. It makes it easy to secure applications and services with little to no code.Keycloak supports login with (SSO). Keycloak also supports login with username/password In order to integrate Keycloak with Windows Active Directory we need to (In Kryon case):Integrate with LDAP, which means that user accounts will be provisioned from LDAP server. Add service principal for "HTTP" service (with Keytab File). For example if your Keycloak server will be running on www.mydomain.org you may need to add principal HTTP/www.mydomain.org@MYDOMAIN.ORG assuming that

See here training content added by Aviad to confluence. Aviad is updating it all the time, so follow it.https://kryonsystems.atlassian.net/wiki/spaces/RndKB/pages/880607994/Aerobase+-+DraftLogin with Kryon domain user

Except using visual recognition which is opening the outlook then visually selecting the specific email, copying and pasting it to the respective folder, the following basic Vb-script can be used with the "Run Script" advanced command to save the messages as well as carry out more actions in a faster and smooth way. The .txt file of the code is attached. <<< ***Set outlook = createobject("outlook.application")Set session = outlook.getnamespace("mapi")session.logon 'optional to useolMSG = 3Set objMailbox = session.Folders("Insert your email address here")Set objFolder = objMailbox.Folders("Inbox").Folders("Important") 'this reperesents Inbox/Important folder For Each m In objFolder.itemsIf m.unread Thenm.SaveAs "C:UsersKryonDesktopEmailSource.msg", olMSGend ifNext session.logoff 'optional to use Set outlook = NothingSet CaseTitle = Nothing

If you encountered issues with fail/stuck Jenkins job, during VM deployment/start/termination and etc. Follow next steps (Deploy VM example):Find your own run:Click on build number (see: Jenkins1) Browse to Parameters: (see: Jenkins2) Here you may find all the information about parameters that triggered the job: (see: Jenkins3) Browse to Console Output for logs: ((see: Jenkins4) In the logs you have several milestones:                                                             i.     VM creation (not in Domain): (see: Jenkins5)                                                            ii.     Add VM to DNS: (see: Jenkins6)                                                           iii.     Prerequisites tool installations: (see: Jenkins7)                                                           iv.     Chrome installation: (see: Jenkins8)