Hi Templaters -
I'm new at templating (couple of weeks), so excuse any obviously stupid questions. I'm working on 5.5.2 Solaris.
I'm building my 1st template project and want, for this project, to hide as much of the user interaction with the datacapture template as possible. Other than user validation, I don't want these users to know that TeamSite is running the show. Here's the scenario I'm trying to achieve:
The user clicks on a desktop link that points to an existing .htm page that was generated with templating (using a URI fashioned like this:
http://tsserver.nike.com/iw/webdesk/edit?vpath=/default/main/intranet/supplychainTraining/WORKAREA/templatingProject/test.htm). They're not going to generate any new pages, or do a 'save as' - they're only going to use this template to update an existing page. Since they're not generating any new pages, there's no need for either the Generate or Save As buttons, and I'd like to eliminate them. From looking in Devnet, I assume that the only way to do this is FormAPI.
Once the user has finished updating the dcr in the dct and is happy with the preview, I'd like them to press 'close' or 'save and close' and then have the workflow take over from there. If possible, I'd like it to eliminate any prompts about regenerating or submitting the file. Once again, I believe that this is only possible through using FormAPI.
Now comes the workflow portion. Since I can force the user to start the session by editing the previously generated .htm file, which then brings up the source dcr in the datacapture template, how do I get the workflow to recognize the .htm file rather than the dcr when close / tt_data is invoked? From what I've seen so far, the workflow has a handle to the dcr, not the .htm I started with. If it had the handle to the .htm, I could just run an iwregen against the .htm and be done with it.
Summarizing the implied / stated questions above:
Is it true that I can eliminate the Generate and Save As buttons from the 5.5.2 datacapture template using FormAPI? (samples helpful here)
Can I eliminate ALL post-close prompts using FormAPI? (samples helpful here, too!)
How can the workflow most easily run an iwregen on the .htm file that I originally started editing (rather than the dcr it seems to have a handle on)?
Any help is greatly appreciated!
Thanks,
Wally Box
Nike
