Serendipitous Cerebration – Part (X = 5-2) of (X+2)

Once we got what we felt was all of the needed information from the client as to their expectations and requirements.  We formulated a solid battle plan, sharpened our keyboards, and forged ahead with a spirit steeled on the principle of “Rat’s Head, Ox’s Neck”.

DA PROJECT CONFIGURATION
What we need to see happen first is to be able to recognize the appropriate screens, in this case PeachTree’s   AP and AR Invoice Screens and map them in ILINX Integrate.

Here is an example of one of the PeachTree screens.  Both the AP and AR screens are very similar.  The 2 main differences are the screen header and one of input fields.  The screen Headers is how we plan on differentiating between the screens

 

 

 

 

 

 

 

 

 

 

 

Configuration for these screens is pretty straight forward and we built basic applications using the “Windows” Connectors seen in the sample below “Project 1”.

 

 

 

 

 

 

To finish off the screen configurations we need to tell ILINX Integrate how to differentiate one screen from another.

 

 

 

 

We do this by using the Window Finder tool.  Drag and drop style selection of screens with the “Flash” button to show you if you have the proper elements/screens selected.

 

 

 

 

 

 

 

Verify that Integrate sees the proper screen by using the “Flash” button.  Now we have screens that flash when tested using the selection tool, time to select the fields from the invoice applications that we need to pull values from.

 

 

 

 

On both screens we need to capture the values entered into the” Customer ID” field.  Click the Identify Field button, and using the Info Editor select the field.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Rinse and repeat with the other fields that need to be identified as well, for AP adding the “VendorID” and “Invoice No.” for AR.  For those of us that are following along in your books, you should end up with something akin to this.

 

 

 

 

 

 

 

OK, this is what we have completed in this project already; configured “Windows” applications, recognized individual PeachTree screens, and input fields configured.  Now that the screens are identified and the entry fields have been configured, it’s time give the screens a job or “Task” to do.

 

 

 

 

 

 

 

 

 

We are accessing the content in ILINX Content Store via a URL that takes in parameters to retrieve stored images in Content Store.  So add a Web “URL Task” here.

 

 

 

 

 

 

 

 

 

At some point, technology will advance to the point that when building Integrate projects the program will read your mind to configure the tasks and events.   Current projections estimate this feature will be available in an underground version of ILINX Integrate v6.02×10²³.  Until that time, we will have to use the old tried and true method, entering in your configuration settings using the mouse and keyboard.  At this time if you feel the need to be a bit closer to version v6.02×10²³, as opposed to the current build v611, configure using input devices engineered after 1995.

 

 

 

 

 

 

 

 

 

&

 

 

 

 

 

 

So with our fancy, or not so fancy, I/O enter in the following…

 

 

 

 

 

*Parts of the URL redacted to protect the innocent.

If you look closely in the top URL, you will notice 2 portions of the URL follow this format, ${SomeParamater}.   Each value entered into the URL in this format creates an input parameter that can be mapped to one of the fields we configured earlier.  The example above is for the AR configuration and we placed the ${PramCustomer} & ${PramInvoice} into the URL where we want the values read from the PeachTree Invoice to be entered.

 

 

 

 

 

The last Item that we need to add to the screens is an “Event”.

 

 

 

 

 

 

 

Apparently the developers knew in advance how “Cool” this project would be and named the Event we wanted appropriately.

 

 

 

 

 

 

 

 

 

 

We have our “KoolButton” action added with a name that gives some indication as to what function is to take place when pressed.  When this project is running & one of the configured PeachTree screens is opened, a free floating button will appear on the screen.

 

 

 

Click the button and BAM, ILINX Integrate is opened in a browser window and begins searching for the corresponding document in the image repository.  Now we can hit the “Green Arrow” to run & test the application.

 

 

 

 

 

 

Warning: Testing can be hazardous.  Green Arrow can hit back!

 

 

 

 

 

 

 

 

Once testing has confirmed everything is up to par, do a final save of the Project’s .kap file.  In our next installment, we will review the deployment process and finally delve into realm of Serendipitous Cerebration and how it became a factor in this project.  TTFN.

 

Co Authors: Random Kurt-Patrick Duncan McParks & John Hart
ImageSource Inc.

Serendipitous Cerebration (Part 2 – Project Planning)

Serendipitous Cerebration as a problem solving technique can only be applied in the rare cases when normal logical troubleshooting has failed.  As much as we hate to admit it, when all logical problem solving avenues have been exhausted and our troubleshooting prowess to a flummoxed state of tentation, this is when we begin to enter the realm where serendipitous cerebration hides in dark, dank crevasses.  In reviewing this project, our hopes are that you can see how the process of Serendipitous Cerebration can develop.

The Project was to integrate a line of Accounting Software (PeachTree) to an Imaging Document Repository (ILINX®Content Store).  The purpose for the integration was to speed the process of document retrieval.  We selected ILINX Integrate to work as a gangplank stretching out from the PeachTree Galleon to the ILINX Content Store docks for the transferring of cargo, Account Payable and Account Receivable (AP and AR) Customer and Invoice Numbers for a seamless document look up.  The mechanism for initiating the document retrieval process will be a set of floating pop up buttons, one for AP & one for AR.  So when an end user opens an invoice in PeachTree, the type of invoice is recognized and prompts a “Magic Button” to materialize like a Superhero to save the day (think Batman and gadgets, cause gadgets are cool.  Unfortunately this has no real relation to this project).  One button press and clickety-clack you’re looking at the requested document in a browser window.

 

 

 

Once we understood what the involved components were, what the final expected behavior of said components should be, and set our timelines, and formulated a plan of attack, we were ready to get started on the construction phase.  So please stay tuned for the next thrilling installment in this 5 part series!

 

Co Authors: Random Kurt-Patrick Duncan McParks & John Hart
ImageSource Inc.

Serendipitous Cerebration (Part 1)

I recently worked on a team tasked with a software integration project that connects invoices from between some Accounting software to ILINX®  Content Store.  The integration software was used for pulling invoice values from both our AP and AR invoices for modifying the image indices for the stored content in ILINX Content Store.  Following a series of patches for Windows, Content Store, and the accounting software, Murphy’s Law began rearing their ugly heads and the integration solution in place that retrieved and updated indices flat quit working.

Most of the issues resolved themselves in short order, but ONE issue – the ability to read one field.  We were able to connect and pull values from every other field on the Accounting form.  To complicate issues more, 2 of the fields from the invoices are used to identify the proper document in Content Store and the broken field was one of these.  Trying to isolate the cause of the issue quickly started feeling like wrestling with a squamous Kimono dragon bent on devouring as much time and resources as a large Monitor lizard can muster.

A couple of techs, multiple attempted connector types, some choice language, and a forehead sized dent in my keyboard later it connected and started pulling.  After all of the hair pulling and frustration I’m left with one of those moments when things started working for no reason and continued to function as originally expected, and while you still need to determine what happened you’re just too ecstatic that the software is no longer harassing you with error messages.

I’d never advise using Serendipitous Cerebration as a preferred method of problem solving.   In fact, if Serendipitous Cerebration is your preferred method of problem solving, chances are there is a lot of floundering around before isolating the issue down to a workable solution.  Which is why I’m guessing that most of us try and not go that route, but I’d bet that there are not many techs out there that have had similar moments when, out of the blue, an issue seemingly resolves itself and all you want to do is jump up and start cheering before attempting to figure out what really corrected the issue.

Please check back for the Part 2 of this 5 part blog on 9/30/11!

 

Co Authors: Random Kurt-Patrick Duncan McParks & John Hart
ImageSource Inc.