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×1023.  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×1023, 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.

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

  1. The survey did what social media couldn’t: It
    showed us, systematically and scientifically, what they wanted
    to know about how to do surveys, and what they DIDN’T want
    to know. An example of such strategy would be to dominate the search results from Google, build some links, find some
    highly profitable niches, extract lots of commission,
    and attract lots of traffic from different search engines.
    On the internet, your email signature is the
    equivalent of your business card.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s