creating a workflow to convert a file

Hey there,

I'm new to teamsite development. I'm just starting to work on it has have been given what seems to be a simple task. They have a csv file that, once published, needs to be read and imported into a mSQL table.

The currently developer showed me some of his scripts in iw-home/local/bin written in perl. It was recommended that I either use a job that runs at a pregiven time or create a task that runs with a special workflow.

Actually connecting and inserting into a database I realize can be done in perl and is beyond the scope of TeamSite/this form, but I'm a little confused at how to actually get the file.

I realize I could just grab the file from the staging area without having to interact with Teamsite at all, but if I wanted to use Teamsite's perl modules to check for the latest version of a particular file in a branch, how would I go about doing that and opening the file if it's not locked.

Also, where are the tutorials on this site specifically about making a workflow. Could I check for the existence of a new publication of a file in that workflow so I could process it?

Thanks
Sumit

Find more posts tagged with

Comments

Phanie

Also, where are the tutorials on this site specifically about making a workflow. Could I check for the existence of a new publication of a file in that workflow so I could process it?

Thanks
Sumit

Tutorials for workflow could be found at: http://devnet.interwoven.com/site.fcgi/techlib/48805

Also, want to mention one point here, we should have the Excel file in the TeamSite environment so that we can get the Latest Excel file evertime you are trying to have a new job with the workflow, we can then send the data to the Database this part can be done in many ways.

It would be nice if you provide us with environment details too.

---
Phanie

Tbag

Hi. Welcome to the wonderful world of TeamSite.

Cuz you're new, let me ask if when you said "once published" you meant "once a new Edition is created with that file" or if you meant "once OpenDeploy is used to deploy the file to your Prod server." I ask because the verb "publish" in a TeamSite context usually means "to cut a new edition."

In either case, the quickest & easiest way to do this might be to look at using DataDeploy, which is a built-in part of OpenDeploy. DataDeploy allows you to execute some arbitrary SQL while keeping all the connection ODBC setting stuff in a centralized place.

More to your questions, though, the "latest version of a file in a branch" is usually considered whatever is sitting in your branch's STAGING area (though this may depend on any business practices or workflow tomfoolery that may exist in your branch).

There's no "TeamSite perl module" to check for the latest version of a file in a branch, per se. You're just going to use a command line tool like "dir" or "ls" to see it and use the perl method "open(...)" to get the contents of the file. Your perl method won't care if there's a TeamSite lock or not on the file.

For help on making a workflow, check out the "Library" section of support.interwoven.com (you'll need an account) and grab the Workflow Developer's Guide.

Good luck!

nipper

Also not perl modules, but command line tools like iwattrib and iwrlog will provide a wealth of information, as will others.

Andy

Adam Stoller

...
In either case, the quickest & easiest way to do this might be to look at using DataDeploy, which is a built-in part of OpenDeploy. DataDeploy allows you to execute some arbitrary SQL while keeping all the connection ODBC setting stuff in a centralized place.
...

I'm not aware of DataDeploy being able to parse CSV files - I believe it primarily parses XML and TeamSite EAs.

There are likely a number of perl modules available for parsing CSV files - though if it's a CSV it's not that difficult to parse anyway - that along with Perl DBI generally works nicely - but you may have to build the particular DB's DBM module (which is not generally a trivial task - search the forums for details) If you can get past that it's usually not too difficult.