Hello and welcome to the demonstration for RPI’s Yoga Link. Yoga Link is a browser extension meant to integrate web based ERPs with web based ECM clients.
Yoga Link has two major pieces of functionality. Number one is to scrape information from your ERP and apply that information to document index information in your ECM client. Number two is to scrape information from your ERP and perform a look-up into your ECM client to find and retrieve documents.
First, I’m going to demonstrate these two pieces of functionality. Then I’m going to show a bit about how it works. What you see on the screen are two things. On the left is a document opened in work flow in RPI’s Yoga Docs. A front end for perceptive content. I have an invoice open ready for keying into my ERP. On the right you see a basic invoice entry screen in our Lawson sandbox environment.
For the sake of this demonstration, I’ve already keyed in the necessary invoice information including vendor, invoice number and amount.
To scrape the data from my Lawson screen and apply it to my document, I simply hit the keyboard keys ‘alt’ and ‘l’ at the same time. You will notice the information quickly transposed over into the respective fields in Yoga. You see vendor id invoice number, vendor name and other information. Then I can route the document onto the next step in the process and move on.
Now, a day later, I, as an A.P. clerk, am viewing this invoice record inside of Lawson and want to find the associated image. I can simply execute ‘alt’ plus ‘s’ on my keyboard and Yoga Link will launch another browser tab and perform a search for this record. You can see it automatically retrieves the invoice image and displays it for me. I can review index information or eForm content.
Now, a little bit about how this works. Yoga Link dives directly into the html in the browser to fetch the necessary information. Mapping the fields can be done by using the inspection built into the browser’s development tools.
In front of me I have another invoice open in Yoga and a slightly different invoice entry screen that has not been trained yet. I’m going to map the company field from Lawson to Yoga. First I need to know what the field i.d. is for company and Lawson. I right click and inspect. Navigate the page’s html tree to where the company field is highlighted. I need to note the field i.d, in this case, underscore F eight.
I then perform the same steps in Yoga. Here I can inspect the field directly. Yoga is very straightforward in that fields one through five have the same i.d. The custom properties use the custom properties unique i.d. from Perceptive Content.
I then open the extension. Give it a new unique name. Save the configuration, and I find that the i.d. of the field in Lawson on the left side, _F-8 and I specify the i.d. of the target field under ‘target field.’ This is field one.