Transcript:

Speaker 1:
…essentially you have your standard workflow queues, whatever it is that the end user has permissions to see. We can open these queues, load the document, load any existing annotations, view the forms, any properties, and then also apply annotations and save and route those annotations.

Very simple, very used to what everyone is used to seeing. All of the views for the workflows, for the views themselves, are all just based off of the ImageNow permissions. I think that kind of covers it.

I’ll go back real quick because we did have those audio issues and just once again, we are not charging for Yoga. You do need to have integration server transaction packs which can be purchased from your Lexmark account executive and we can help you understand what level of transaction pack that you need.

As far as the installation of Yoga is concerned, we can provide you with all of the information on how to install it and you can certainly install it yourself. If you prefer, that is something we can assist you with.

We do have quite a few questions so let me take a look and see what other of questions we have. The underlying technologies that are used, it’s predominantly HTML5 is the front end and then we are using some bootstrap and some node.js.

Another question, “Is the pull of available workflows also dynamic, why is there not a workflow section like the view section?” We didn’t feel that there was actually a need to actually have a separate workflow section because you’re going to see all of your workflows up here.

Accounts payable in this instance is the actual workflow and AP detail entry and AP header entry are the available queues to that user. Yes, everything is dynamic, so when I log into Yoga, it’s going to pull all of the workflows that that user has access to, and all of the queues that the user has access to and then also utilize those workflow views.

I have another question, “Does this work with 6, 7?” It does require version 7.13 because that is the version of the API that we’re utilizing.

I do apologize to everyone for the rough audio that it sounds like we were having.

“Can this open images from a workflow queue?” Yes, absolutely, so under accounts payable that is what we’re looking at here our workflow queues and then we are actually opening the image. In this case, we had loaded in some fake invoices but whatever image it is that you need, we are able to open.

Someone asked if this was built from Perceptive Experience? This is not built off of the Perceptive Experience framework. This is a completely separate framework that we created.

“Are we planning on adding new features?” Yes, we will absolutely add new features. You can always submit those and request them. Based on the demand for those new features, we may add them. Another option that we will be giving clients is the ability to sponsor a feature.

If there’s a feature that you really want and is really a customization, what we’ll do is tell you what it would cost to sponsor that feature and then we’ll actually include that feature in the next release.

Another question, “Can Yoga integrate with a legacy system? Can we add a button that opens Yoga and passes in a document ID to open a specific document?” That is a great question, Yes, absolutely. If you are utilizing an ERP system, Lawson or Peoplesoft or ebusiness suite or any system where you an place a button that can generate that dynamic URL like you might do presently with WebNow, yes, we can absolutely just open up Yoga through that URL the same way that you’re doing it with possibly WebNow, presently.

As far as the mobile experience is concerned, we have not optimized this for mobile. That being said, it works really well on a tablet but it is not been optimized for iPhones or anything like that. With that being said, that is something that we will be doing in the future but at this point in time we simply haven’t made that optimization yet.

There are some questions around, “What else differentiates this from WebNow, from Functionality other than Java?” I think it’s kind of based on an organization’s requirements. What we tried to do with Yoga is make it as simple as possible. What that means that it doesn’t necessarily have every feature that you could possibly imagine but instead it has the features that you truly need for your day to day processing and routing of AP documents and HR documents and legal documents.

Especially when it comes to having approvers that aren’t necessarily super heavy users of ImageNow but instead are people that occasionally need to approve an invoice or approve an HR document. Rather than needing to have thick clients or needing to worry about supporting specific browsers, we’re able to allow them to easily launch these documents from an email or from a third party ERP system.

There’s a question around, “Isn’t the latest version of Perceptive Content HTML 5 that doesn’t require Java?” I believe that maybe you’re referring to Perceptive Experience. Yes, there is another web client that Lexmark has released that thus far we haven’t seen a ton of or have a ton of experience with called Perceptive Experience. That does require that you own the WebNow licenses in order to utilize Perceptive Experience. It does utilize those Image Now, WebNow common license.

One other thing that I would mention in terms of the installation. As of now, our messaging is, we’ll show you how to install it and you can go about it yourself, or we can do it for you and we’ll charge you. The reality of it is that this is a new platform for us and we do want to work with you.

If this is something that your organization is interested in using, we will absolutely assist you with the installation at this point in time and no, we will not charge you right now.

Someone else asked, “Is there a basic front end product that just loads the similar features like views, workflow, etc. without major development?” Yes, that is what I’m showing you right here. This can be installed extremely quickly and we just have to hook it up to your integration server at which point in time we are going to automatically begin authenticating against your Perceptive Content environment. We are automatically going to use the user’s credentials to authenticate that user against Perceptive Content to see what workflows and what views they have access to and to pull back those items that they have that they have access to.

Once again, this does require version 7.13. If you have not upgraded to 7.13 you will need to wait until that upgrade occurs. That is something that we can assist you with, certainly contact me. Once again, my contact information is right down here. For those of you asking how to move forward as the next step, the best thing to do is to send me an email at that email address.

Another question around filters, yes, yes you can utilize filters within Yoga.

“Can you upload files or scan into Yoga?” No. Not at this time. We are working on that piece of it but at this point in time it’s truly meant for the viewing, the annotating, the coding, and the routing of documents.

There are some questions around the transaction pacts. Definitely shoot me an email. I would be happy to discuss transaction packs a little bit more with you and what you need to own in terms of Lexmark licenses.

“Will we provide assistance with questions during the installation?” At this point in time, yes absolutely. We want to help everyone to install it and to make sure that this is successful for you. Yes, absolutely we will assist with installations right now.

There’s a question, search features. “Can you build your own searches on the fly?” Once again, the views and the workflow views are based off of what exists in ImageNow. You are not building anything within Yoga, you are actually utilizing the same views that you have built within ImageNow or Perceptive Content. If you want to build a new view, you would just build that right within Perceptive Content and it’s going to show up.

Can the eForm still trigger iScripts through true data etc.? That’s an excellent question and the answer to that is yes. The eForms will still continue to function as they possibly do.

“Is it possible to do linking using Yoga?” No, not at this time. We are not presently supporting any linking.

Someone else asking, “Does it works on versions higher than 7.13 such as 7.15?” Yes Yoga will operate on version 7.13 and higher.

Someone else has asked, “Since this is brand new I assume no company has used it yet?” That is correct. This is the first day we are releasing it, the first day we are offering it. That’s why we will, at this point in time, assist organizations with installing it free of charge and work directly with you.

There’s a question around, “Will we potentially change the cost model from free to a charge in the future?” We do not have any intentions of that, obviously things can always change but no, that is certainly not our intention. Our intention is to continue to grow our client base.

Someone else asks, “Help me understand more how this is beneficial?” They are already on image 7.13 how can this benefit them? The main way that this can benefit just about any organization is for deploying this to those users that are not your; this is not for your AP entry, your AP processors right now. It’s always best for them to continue to use the thick ImageNow client because that’s how you’re going to link, that’s how you’re going to do those things.

This is really beneficial for those people that have to approve those AP invoices or those people that have to approve those HR documents. They really just want to be able to click a link, open a document, see it and approve it. We don’t want to have to dictate browsers for.

“Are there any issues with opening folders?” No, folders are part of this release. We can absolutely open folders.

“Can you route documents through workflow?” Yes, once again, I’ll show what it looks like. If I open up one of my documents, once it loads I’m going to have access to route to any of the workflow queues that this user has permission to route to. I can apply annotations, I can modify, assuming I have the right permissions to modify, and then I can save and route.

These are the queues that this particular user that I am logged in on has permissions to route to. Again, based off of your existing permissions within ImageNow. You’re not setting any permissions within Yoga. If I have the ability to route within ImageNow to this cue then I can route to that cue within Yoga.

“Through scripting will we be able to link to documents within Yoga?” I guess that depends on what you really mean by that question. For instance, you could have what’s called within queue scripts. Maybe I am just entering into Yoga a vendor ID into the form and then we’re pulling back data from third party databases, yes, we can definitely do that.

The other way that we can do scripting is through the eForm. If you presently have scripts within your eForms, we can continue to pull that data. For instance, this validate button, if I were to put in the data for this eForm the validate button would continue to work. Nothing has changed there, we are displaying the real eForm and the scripts behind it do work.

Again, yes it can open folders and the documents within them.

Another question here, “What measures are in place to protect and secure information?” This is not taking any information outside of ImageNow. Our perceptive content, all of your security, that all still continues to live within Perceptive Content. Your data does remain secure within Perceptive Content.

Yes, it is compatible with version 7.15. There is not a maintenance fee as long as you will maintain it on your own. We will continue to release updates. We will continue to send those updates out to everyone that is using Yoga. We will not charge for that. If at any point in time you want us to assist with updating Yoga or doing any more complex integrations we will charge you for our time then but no there is no maintenance fee, there’s none of that.

The only caveat that you could end up with a cost is Integration Server action packs that you may have to purchase from Lexmark.

“Will RPI work with me to customize this to fit my business?” Yes, absolutely, we can absolutely create custom versions. Generally what we’re calling that is a sponsored feature. The reason that we’re referring to that as a sponsored feature is once we create a customized version for you, we want that customization to continue to live in all of the upgrades that we do. If we create something special for you for let’s say your version 7.13 or 7.15, and then we have the next version of Yoga come out, we want that continue to live. Yes, we can absolutely do sponsored feature requests and then we will release those in the next version.

There’s a question around, “Can eForms be printed in full from within Yoga? That’s a good question. I would think that they could be because they are just living in a browser, but definitely something we could look into and if it doesn’t already exist in full that might be a great example of where we might have a sponsored feature request where we could create the ability to perform that.

Correct, it is version 7.13 and up. So 7.13, 7.14, 7.15, all of those versions are supported and should continue to be supported into the future. If at any point in time there are changes in the API as in, the API calls are deprecated to utilize, we will update Yoga to work with those features.

Will documents with a file type other than TIF open in the same way? Will there be thumbnails for each page? Yes, there will be thumbnails, I’m not sure of the exact list of document types that were are supporting right now but is definitely the vast majority of document types. Other than very one-off document types, we do support them all.

There another question around whether or not we have clients already Beta testing this? No, we do not. Today is our release of our Beta and so no, we don’t have other clients Beta testing it. We are looking for clients to Beta test.

Once again, no Yoga does not require any user licenses. The only license that it requires is that integration server transaction pack in order to make those API calls back to ImageNow.

A demo of opening Yoga from another app. I do not have that demo at this point in time but really it’s just a matter of structuring the URLs, so that’s certainly something I could put together very quickly to show you what a structured URL would look like.

“Does Yoga require its own server?” No, it does not necessarily require its own server, though as a best practice we generally do recommend that various web applications are each on a separate server.

Sorry guys, if I miss your questions there are a ton coming in and I’m trying to get through them. If I don’t understand the question I will certainly reach out and touch base with you to better understand it and make sure we get it answered.

There’s a question on, “Does all the annotations work?” Yes. We’re not simply just creating annotations then throwing them in. Any annotations to my understanding should work. If you have a specific use case that you want to verify once again, please feel free to email me. There’s my email address below.

We always send out a follow up email following all of our webinars, you can respond to that email or respond to the invitation.

Again, no licensing costs on Yoga. Asking about how it compares to licensing of WebNow? WebNow and ImageNow utilize combo licenses. We do not utilize any client licenses. It works off of API calls to ImageNow.

Another question around any browser, any version, any client requirement? Really it should work on any browser, any version, assuming you’re using a modern browser. We do not support IE6 or the older browsers that don’t support HTML 5.

There’s a question around, “Can we brand it?” That is a good question and we’ve has discussions about it and probably the way we plan on treating branding is that that would be an add-on. The reason that it’s an add-on is part of the reason we are giving away Yoga is that we want to continue to have more and more of our brand out there. Branding it is something that we would have to discuss on a one off basis.

There’s another question, I’m not sure I understand. “Does this tool replace the need for WebNow and the troublesome requirement for Java?” Yes, it does replace the need for WebNow and the requirement for Java. There is no front end Java used here. What you see is HTML 5 bootstrap, no JS, all modern technologies.

Another question about customizations and branding. I think we can have all of those conversations a little more one-off in what we can do.

Additional security concerns with the Yoga layer. We have built it to be secure but that being said, it is in Beta. I would’t recommend exposing your ImageNow environment out to the internet using Yoga or anything else, honestly. No, we do not believe there to be any security concerns. That’s part of the reason we designed it to use the native ImageNow authentication.

I’m having a lot of questions around servers specs. I can’t answer that. I’m not quite technical enough to tell you exactly what we need in terms of server specs. That will of course, have a lot to do with your volume and how many users you have using it.

Question around modifying index files. Yes, assuming that the user has the proper permission, you can modify index values, custom properties, and the eForm.

Question around integrating your ERP directly into Yoga. Yes, you can certainly embed links into your ERP that open a document in Yoga. That is definitely an option. Any time you can generate that dynamic URL then you can easily open it within Yoga.

“We have a large amount of viewers that only need to approve invoices, view employee files etc. Seems like a good solution to the issues with end user clients that have Java related issues presenting them from viewing documents in Lawson.” Exactly. That is a perfect example.

“Is Yoga actually a replacement for WebNow?” That goes back to what your use case is for WebNow, but for the vast majority I would say, yes, absolutely.

Some questions around differences between Yoga and the Thick client. One of the main difference right now is just the capture ability. If you have users that are capturing documents, I would always recommend that they remain on the thick client. Linking is the other thing, if you’re linking to third party applications through learn mode, you would want those users to continue to use the thick client.

Again, with licensing when a user logs into Yoga with licenses used on the ImageNow site, no client licenses are used on the ImageNow side. The integration server transaction pack is what’s used because it’s an API call so that’s what we’re utilizing.

“Any specific software need to be on client devices? No, just any sort of modern day browser, Chrome, Firefox, Safari, modern versions of Internet Explorer.

There s a question around email/attach feature. No, there is again no way presently to attach documents in Yoga.

File size limitation and how many pages can be displayed. Nothing that we have ran into yet but certainly something that we would be more than willing to test with you to make sure it works for your environment.

What we have tweak forms to display nicely in Yoga. For the most part I think the answer to that is no, right? I’m  guessing that you’re referencing the way that forms currently work within form server. The way that forms are display within Yoga are actually the way that they’re displayed in ImageNow. No, you should not have to tweak forms to display them within Yoga.

Another question is, “Only one transaction pack used per user in Yoga or how does that work?” It’s something that I would want to speak with you and your Lexmark account executive about. Transaction packs are actually based on the number of API calls. You could theoretically have only one transaction pack and have 100 different approvers that use the one transaction pack because they only go in and approve invoices on a more rare basis. No, you do not necessarily need a transaction pack per user. You can have multiple, multiple users that are operating off of one transaction pack.

“Can we invent buttons in Lawson that will be able to display the docs in Yoga similar to WebNow?” Yes, absolutely, we can call documents from Lawson straight into Yoga bypassing that dynamic URL the same way you’re doing in WebNow. Yup, we can absolutely do that.

I believe I answered if not all of the questions, almost all of the questions. I may have skipped over a couple but with that being said, absolutely feel free to reach out. You can email me here. You will also receive a follow up email from us or email the response to the original email invitation that you received.

Anything that I can do to help answer questions, I’m certainly here to do. For those that are interested in installing Yoga and utilizing it while we are still in this, what we’re calling version .9 Beta release, we will absolutely work with you to get Yoga installed and working in your environment, as we would like client references.

Definitely, please reach out to me if you have any interest whatsoever. With that being said, I really appreciate everyone’s time today and please let me know any way that I can help, whether it’s with Yoga or with any of your other Perceptive Content, Capture, or Cofax, KTM needs. Please reach out and thanks so much and have a great day.