AutoStore: Konica Minolta iOption Script Language


Like most recent capture components in AutoStore 7, form behavior can be made to order with the Konica Minolta iOption capture component using a form script. When the script editor is launched, a Visual Basic .NET script template is provided.

Looking at the AutoStore Konica Minolta MFP capture component, which interfaces with Konica Minolta device using OpenAPI technology, you also get a .NET script template, so no loss there. However, the language of that template is in C#.

For those who have worked with the Konica Minolta MFP capture component in AutoStore, there are many reasons why you might prefer to continue developing form scripts in C# is preferred.

What ever the reason, you have the ability to write your form script with either the VB or C# or language in the Konica Minolta iOption capture component's script editor.

Here are the steps:
  1. In the AutoStore Process Designer, open the Konica Minolta iOption Capture Component.
  2. In the General tab, select an existing form, or select a Group or a Menu.
  3. Click on Add Form, and choose the Basic Form form option.
  4. Select the Enable Dynamic Form checkbox, and click Edit Script Code.
  5. The script editor is opened. The default script template is Visual Basic.
  6. Click on the Compilation menu, mouse over Languages, and select C Sharp.

Choosing the Konica Minolta iOption scripting language

It should be noted that form scripts between the Konica Minolta OpenAPI and the iOption capture components are not compatible. In particular, the device technologies are different, and the iOption uses a newer DataModel class, and there are differences in the event handlers.

Of course, any custom methods independent of device functionality should carry over just fine, but it should be expected that when moving from OpenAPI devices to iOption, it will likely mean that any existing scripts will need to be rewritten.

Which ever language you choose, happy scripting.

Cheers!

Comments

Post a Comment

Popular posts from this blog

VBScript: Ensure Backslash Folder Path

Image
To preface what could be regarded as a very small thing, I am reminded of a common turn of phrase concerning the amount of perspiration that should be afforded to the "stuff" belonging to a particular size-category, and pretty sure there was a book written about that topic. Not to come across as disagreeable, but rather to invite a little balance based on my own general observations over time, an increase in cost with things such as time, money, even relationships, can be avoided when the "small stuff" is given the regard that it deserves. One of these tiny details has to do with string variables that reference folder paths within a script. There are times when it is important that a defined directory for a particular folder should and must always end with a backslash. As an example: folderPath = "C:\Example"   Of course, it really is not very difficult to manually enter that backslash into the path. folderPath = "C:\Example\"
Read more

AutoStore: Create a Custom RRT

Image
Have you ever needed to dynamically create a custom RRT for an AutoStore process? In my previous post AutoCapture Default Date , I described my very first AutoStore script where the value of an  Invoice Date  field in an AutoCapture Vendor Invoices  form was assigned a default value of the day prior from the current date. This Invoice Date  needs to be part of the file name, however its format contains slash (/) characters that cannot be part of the file name. So, we'll use the AutoStore VB/JScript process component to create a new RRT that's more friendly. To do so, we'll look at how to do the following: Bring the existing Invoice Date  value into the script Reformat the Invoice Date  to a Windows-friendly file name Output the reformatted Invoice Date to a new custom RRT After adding the VB/JScript process component in between the capture component and the Send to Folder route component of the configuration file, we open the AutoCapture component to conf
Read more

AutoStore: Workflow Loop Example

Image
Regardless of the programming language, a looping-statement is a common declaration for iterating through collections of things, such as the items of an array, records selected from a database, elements within an XML file, or the files inside a directory. A recent AutoStore challenge was presented where a script was used to fetch data in a process that returned either one or many items. This was the easy part. However, each return record needed to be specific to an individual Route based on one of those items returned. Example Example1@email.com Example1/URL Example2@email.com Example2/URL Example3@email.com Example3/URL Although the captured document being processed would be common for all in the return, the recipient belonging to one of these unique records should not be aware of  nor  receive any of the information that would belong to a different recipient. Because an unknown number of return records would be expected, this presents a challenge due to the fa
Read more