Popup Data entry form outside of TeamSite

Don't know if I recall seeing something like this, but is there a way to have a TeamSite form popup via a web / email link to allow for data entry? If so, what is the needed url trigger?

Once submitted, the form will process through TeamSite as specified in the Workflow we have..

Would like to see something like this without requiring users to have to Log into TeamSite to fill in a form. (Submitters would not have approval or deployment capabilities - just data entry only).

Teamsite 6.7, Win

Find more posts tagged with

Comments

Adam Stoller

Don't know if I recall seeing something like this, but is there a way to have a TeamSite form popup via a web / email link to allow for data entry? If so, what is the needed url trigger?

Once submitted, the form will process through TeamSite as specified in the Workflow we have..

Would like to see something like this without requiring users to have to Log into TeamSite to fill in a form. (Submitters would not have approval or deployment capabilities - just data entry only).

Teamsite 6.7, Win

In general - if a user has any interaction with the content stored within TeamSite, they must be registered TeamSite users and they will have to login to TeamSite somewhere along the way (though perhaps with SSO that requirement might not exist).

Some folks have conjured up ways to have forms in email that submit information in a structured manner to a "system" mail address, the mailbox of which is processed by a daemon / service that is owned by someone who does have TeamSite access, and through which the structured information is transferred into the appropriate place within TeamSite - however this is a very non-trivial thing to set up IMO, so unless you absolutely, positively, need this kind of functionality - I wouldn't try venturing down this path.

A somewhat more elegant approach is to enable non-expiring authentication (Nipper can probably fill you in on that ;-) such that once authenticated once (or twice, as email tends to use a different cookie than direct from the desktop), the authentication should never been required again (from that client machine, assuming nothing changes on the server to invalidate it)

A more elegant approach can probably be achieved with SSO (single-sign-on), which is covered somewhat in the manuals, but which is supposed to be easier to enable once 6.7.1 SP1 comes out (caveat: it comes with a development price on it - as most of your pre-existing Perl scripts and PTs will have to be completely re-implemented as I understand it)

Migrateduser

Thanks for the reply... Email may not work because it would be too messy. I want to be able to utilize some visual format fields to allow the contributor to format their entries. So straight text from email entries would require having to touch each entry received.

I did recommened a ColdFusion form to DB approach, and have TS create the dcrs from the db with datadeploy - but management wants it all to be done with TS... Problem is that there would be a number of contributors spreadout within my organization nationwide, and they do not have access to this TS branch - just their own branch. What about implementing a shared branch, any issues or insights there?

This is a low use data form at this time (maybe 5 to 20 submissions per month). So it may not be worth spending a lot of time and resources to develop a complex routine.

In your last comment, you said something about TS 6.7.1 and that existing Perl Scripts and PTs will have to be completely re-implemented? What do you mean by that and why would this be the case. If so, we definately need to know about this - it could be a BIG technical and time support issue. Could you elaborate more on this?

Thanks again for the reply. I look forward to other ideas that may be possible

Adam Stoller

Thanks for the reply... Email may not work because it would be too messy. I want to be able to utilize some visual format fields to allow the contributor to format their entries. So straight text from email entries would require having to touch each entry received.

I did recommened a ColdFusion form to DB approach, and have TS create the dcrs from the db with datadeploy - but management wants it all to be done with TS... Problem is that there would be a number of contributors spreadout within my organization nationwide, and they do not have access to this TS branch - just their own branch. What about implementing a shared branch, any issues or insights there?

This is a low use data form at this time (maybe 5 to 20 submissions per month). So it may not be worth spending a lot of time and resources to develop a complex routine.

A shared branch shouldn't be too much of a problem unless you have to deal with very disparate time zones and need to take into account downtime for backups and such.

If they have their own branches, you could also implement some sort of iwat trigger or workflow process that would copy the files from one branch into the other.

There are probably other ways of handling it - but hey, you gotta do some thinking about it here ;-)

In your last comment, you said something about TS 6.7.1 and that existing Perl Scripts and PTs will have to be completely re-implemented? What do you mean by that and why would this be the case. If so, we definately need to know about this - it could be a BIG technical and time support issue. Could you elaborate more on this?

PLEASE read the CONTEXT of my comment.
The issue with PTs and Perl scripts only applies if you are attempting to utilize SSO with 6.7.1 SP1's non-OS-user feature (admittedly, I left that out of the original context).

I am not (currently) aware of any significant changes needed if you are not planning to use the non-OS-user feature.

I could try to provide more detail - but it would be largely assumptions on my part based on discussions held at this year's GearUp this past May in San Francisco - and I'm hoping that they'll do a good job of documenting the pros/cons/etc. when SP1 is released.

cute_guy

Don't know if I recall seeing something like this, but is there a way to have a TeamSite form popup via a web / email link to allow for data entry? If so, what is the needed url trigger?

Once submitted, the form will process through TeamSite as specified in the Workflow we have..

Would like to see something like this without requiring users to have to Log into TeamSite to fill in a form. (Submitters would not have approval or deployment capabilities - just data entry only).

Teamsite 6.7, Win

Moorechi,

Are looking for something like there should be link in your website and when the customer clicks on the link the TeamSite data entry screen should be poped up and when the content is saved, then the html content generated should sent thro' a workflow process and deployed to your web server?

If yes, you can have a look at the content center URLs, which does NOT require user to navigate to the workarea and create the content.However it does require a valid TeamSite user id created for the user in the server.

Migrateduser

Yes, I think this is what we are looking for.

However, I am not able to see the URL in Content Center that I can put on our website to link to the form we want to use. Where would I find it in CC center?

Migrateduser

Moorechi,

Are looking for something like there should be link in your website and when the customer clicks on the link the TeamSite data entry screen should be poped up and when the content is saved, then the html content generated should sent thro' a workflow process and deployed to your web server?

Just an idea.
Why not have a web form that calls a cgi in the iw-bin folder.
the cgi transforms the form data to a valid dcr and triggers the workflow.
Will be a lot more work then being able to use a dct directly though.

rajani_interwove

Moorechi,

Have you come up with any solution for your problem?

gorka_esnal

Then,

is there any URL to show a datacapture form directly?

ISCBorisB

Then,

is there any URL to show a datacapture form directly?

Yes. Interwoven® User Interface Customization Guide, Chapter "Using URL Commands", File URL Commands, Command "edit".
If your user does not have valid IWAUTH cookie system will prompt him to log in

Migrateduser

Thanks for the follow up. Due to other priorities, the need for this type of form has been put on the back burner, but will definately take a look at it soon.

ISCBorisB

Thanks for the follow up. Due to other priorities, the need for this type of form has been put on the back burner, but will definately take a look at it soon.

Hi moorechi. That was actually a reply to somebody else request. I never do follow-ups for the threads that are not my own.