Copy This To That

Recently I saw a post in OT Forum that caught my eye What prompted me to write this is because the OT experts also advised using some other mechanisms (XML WF Extensions and use of WR). Now, normally I like to code as well as any other user in Livelink a.k.a Content Server so why this post is because I remember when OT announced the Item Handler and Item Reference(yes they are different) several years ago I believe when Tammy Jakubowski(now GCI) was the WF Product Manager at OpenText.It was downright confusing but did it work in complicated situation boy it did. So I also asked the same questions why would you need WF Attributes and Form attributes in the workflow because they both do the same thing. But this user kept telling me that Business Workspaces apparently has a WF Step that creates BWS’s and it would only work with WF Attributes and they didn’t want their users to see the WF Interface

I replied with a simple OOB implementation where I used a simple throwaway hardcoded documents inside my WF Attachments map and using two Item Handlers Copied what a user entered in a Form Value to a Category to the throwaway Object and using a second step copied that Category Values onto a WF Attribute.

I later explained to the user in a series of simple screencaps how one would do this as that user needed hand-holding and I find the OT Online Documentation horrendously confusing 🙂

General Help Series 5 – Form Templates,Web Forms


Forms as the name implies is a object where you can capture input and store them in livelink  . The exact methods are only going to serve as what you design your forms to be.I wrote this because a user was asking about this in the KB

Main Attributes: Forms can be made to work only by installing the “Forms Module”,which in turn will give you a Form Template sub type(230). This serves as the straw man for your data requirements.

Installation of WEB FORMS will give you HTML form capability like wise if you install PDF Forms it will give you that capability.

Forms is used extensively in delivering a awesome user experience,however the form template code is very busy and in efficient as it will add unwanted(literally thousands of lines of javascript ) so anything you can do to optimize javascript you can do that. In the course of your work you will create a Form Template,create HTML Views so that user experience can be controlled via javascript logic,thousands and thousands of examples full forms etc in the KB.

In a article where I put earlier where we all were active in communities at one point

I find that a OT moderator putting my exact lines as I replied in a post


Little has changed although the product from Patrick Vitali called “Answer Modules” has out rightly taken of the tedium of developing in forms.

Every Which way a Form can be used“”

Almost all organizations will need  data in forms to be reported so use SQL as storage.If you keep it at default it could go as version files which is not parsable by a SQL tool nor will it have header info(you won’t know which field is which). Users using the Transmittal product usually get bitten by the fact that most of the work in transmittals revolve around forms and if you don’t make it SQL storage you will never be able to report on it.Actually on my first project installing transmittals I bungled and then I looked under the covers to understand it.Even now there is no mention in any guide saying change forms to SQL storage.A recent help to a assoc

You can very greatly experience a users’ livelink workflow experience by chnaging the process to use FORMS while maintaining the business logic of the workflow

Advanced Topics in Forms/Workflows

This I put here  and only if you know Oscript is this of any useadvanced Topics in Forms workflows