How to verify if file path entered exists or not

In the DCT's i want to verify whatever file (can be .dcr, image, pdf, .html etc) browsed or even the name of the file entered exists or not. Is there some way to check this. Any help will be appreciated.

Find more posts tagged with

Comments

kaalraa

In the DCT's i want to verify whatever file (can be .dcr, image, pdf, .html etc) browsed or even the name of the file entered exists or not. Is there some way to check this. Any help will be appreciated.

On the first thought, use the method CallServer and write an cgi script which can be called from. Within that cgi file... use formapi object to gather the values of the DCT and then play around Smiley Happy

Migrateduser


if (-e "hello.txt")
{ 
  #proceed with your code
}

nipper

In you example, a DCR, then you have to run a call server event. That will be a pain.

If you can do it in the TPL, then you can use the perl -e flag. I am doing something similar with directories and making them if they do not exist.

Migrateduser

In you example, a DCR, then you have to run a call server event. That will be a pain.

If you can do it in the TPL, then you can use the perl -e flag. I am doing something similar with directories and making them if they do not exist.

I would think that doing it in the TPL would be too late. A user should be alerted before submitting to workflow. Plus, how will you alert the user that the attachment doesn't exist?

kaalraa

Had replied as per query... which says to verify from a DCT. There are numerous of other places (which were not asked) from which we can check whether a file exists or not.

In you example, a DCR, then you have to run a call server event. That will be a pain.

If you can do it in the TPL, then you can use the perl -e flag. I am doing something similar with directories and making them if they do not exist.

chetansethi

I second taalgaard opinion that it would be too late to do in TPL. The user should be alerted while saving the file itself.
We are using call server to test and it works, and it is not much of a pain, it is just one line in DCT and a few lines of CGI code as per your requirements.

npuri

I will like to thank you all for the replies...that is right i want to include some validation in DCT itself to verify if file exist....I got the process from your replies - is to use callserver method and use some cgi script..but it will be very helpful if some examples anyone can provide as in how to use callserver and extract parameters or items in DCT in CGI script...thanks in advance

ravio

..but it will be very helpful if some examples anyone can provide as in how to use callserver and extract parameters or items in DCT in CGI script...

This is documented very well in the manuals and includes examples and sample code.
Refer - Forms Publisher FormAPI Developers Guide

kaalraa

If you find the word 'callserver' on devnet then also you will get a lot of threads dealing with the same.

Still need any specific issue related help... just be here anytime.

I will like to thank you all for the replies...that is right i want to include some validation in DCT itself to verify if file exist....I got the process from your replies - is to use callserver method and use some cgi script..but it will be very helpful if some examples anyone can provide as in how to use callserver and extract parameters or items in DCT in CGI script...thanks in advance

Migrateduser

Here's some of my code (it's a mess, but works). It's not specific to your request and there's alot of extra stuff, but should have enough in it for you too pick apart.

runFileName is the function that you should be looking at below, it has a call to it, you'll have to follow the breadcrumbs and figure it out.

The first line on the perl file is specific to Windows and you may have to change it if you run Solaris, etc.

Migrateduser

taalgaard is being a nice person.

Seriously, there's enough documentation on this and if you're versed in Perl, it should take you 20 minutes -- far less time than waiting for peoples' responses, most of which would just be recommendations to "do it yourself."

Dave

Adam Stoller

Seriously, there's enough documentation on this and if you're versed in Perl, it should take you 20 minutes

... and if you're not versed in Perl - pick up a book:

It may take you a bit longer - but the reward for learning it pays high dividends (IMO).

Migrateduser

I have this one myself.

http://www.amazon.com/gp/product/0072129506/002-7502823-9472041?v=glance&n=283155

fred_sanford

I'm a devout O'Reilly fan. But, the only time I've strayed is for my favorite Perl book

Adam Stoller

I have this one myself.

http://www.amazon.com/gp/product/0072129506/002-7502823-9472041?v=glance&n=283155

There are thousands of Perl books out there - I mention the O'Reilly ones specifically for introductory purposes and because they are well written - even to the point of being enjoyable to read (which you can't say about a lot of technical books). I'm sure there are many alternatives (such as the one you referenced) - but I guess I'm a bit of a stickler for the "original" ;-)

Migrateduser

List of perl tutorial that are shiped with most perl distributions

perldoc perlreftut - Mark's very short tutorial about references
perldoc perldsc - data structure complex data structure struct
perldoc perlrequick - Perl regular expressions quick start
perldoc perlretut - Perl regular expressions tutorial
perldoc perlboot - Beginner's Object-Oriented Tutorial
perldoc perltoot - Tom's object-oriented tutorial for perl
perldoc perltooc - Tom's OO Tutorial for Class Data in Perl
perldoc perlbot - Bag'o Object Tricks (the BOT)
perldoc perlstyle - Perl style guide
perldoc perlcheat - Perl 5 Cheat Sheet
perldoc perltrap - Perl traps for the unwary
perldoc perldebtut - Perl debugging tutorial
perldoc perlopentut - tutorial on opening things in Perl
perldoc perlpacktut - tutorial on pack and unpack
perldoc perlthrtut - tutorial on threads in Perl
perldoc perlothrtut - old tutorial on threads in Perl
perldoc perlxstut - Tutorial for writing XSUBs

Note: Commands are in bold face in the above list.