I have developed a custom workflow application that allows users to input field names into a workflow profile document, and this document does various processing for my workflow.
My question is this…Is is possible to display the form design to the user in the client using API or something. I saw a product called Integra for notes, and they were doing this but I have not been able to figure out how. The reason I want to do this is so the user can see the actual fieldnames in the form design and where they are located, so when they choose a field they know what they are choosing. I don’t want to just give them a list of fields to choose from using @docfields because sometimes field names are not that intuitive.
Any ideas?
Subject: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
Kris,
why don’t you let them pick the name, put put the list as ‘What they See’|notesfieldname
this way the user will see one this, but when you get it back you will have the readl notes field name to update the values with.
Subject: RE: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
You might be buying some serious lunches! 
Subject: RE: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
Good idea, that is actually exactly what I am doing now. There are only certain fields that I want them to see, so I am giving them a nice label and then the alias as a fieldname.
However, everytime they decide they want to add a new field I have to go into the design and update this field. I would rather just use @docfields, and then let them see the design of the form so that they know which field is which, thus no code updates.
Thanks for the response,
Subject: Create a config doc
Best way to do things like this where the field values available for choices change more than you want to change the design is to put the value list on a config document…
Dave
Chub Toad, LLC
Subject: RE: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
Kris,
Not if you kept the fields to display in a profile document - then you just have to modify the profile document - never do any design changes!
John
Subject: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
I know this is late in the process, but I really don’t see any reason to do anything but this.
Set the following on an action in the form…
Dim ws as New NotesUIWorkspace
Dim curDoc as NotesDocument
Set curDoc = ws.CurrentDocument.Document
Forall curItem in curDoc.Items
Call curDoc.ReplaceItemValue(curItem.Name, curItem.Name)
curDoc.SaveOptions = “0”
End Forall
Call ws.CurrentDocument.Reload
I suppose if you have a number of comboboxes, this will get awkward, but there’s even ways around that, if you’re particularly motivated.
Alternatively, you could set an Entering event on every field to echo it’s name to the status bar or something.
Subject: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
You could try changing the value of the $FormulaClass field on a view so that it displays design elements - the form design can be displayed in a Notes client to users by setting $FormulaClass to 4. Here’s how:
http://www.dominopower.com/issues/issue199908/design001.html
Note that although users will not be able to change the design a user with less than designer access is still viewing a design element (albeit minus any code) that they would otherwise not be able to see - there may be a security issue here.
hth
Subject: AND THE WINNER IS…FRANCISCO
I am a man of my word, I just followed the directions from the website you listed, and it actually worked. It’s gonna take a little bit of setup, but once I have it, its ON LIKE POPCORN. Francisco, send me your address to kking@tsys.com, and what you would like for your lunch, I will send your gift certificate in the mail.
Thanks,
KRIS
Subject: RE: AND THE WINNER IS…FRANCISCO
Kris,
You are a generous and noble fellow but I’m afraid I couldn’t possibly accept your kind offer.
The credit is ultimately due to Mr. Velasco and any contributions I make on LDD - in my real name as well as the fictional Bond baddie alias used here - aim to be of an altruistic nature.
I’m simply glad the link helped and hope you have ‘fun’ with it.
Best Regards
Francisco
Subject: RE: AND THE WINNER IS…FRANCISCO
Well thanks again,
This is a really cool feature to add, and my mind is running wild with ideas. I was almost ready to give up when I didn’t get a response in the R5 forum.
Have a good weekend,
Kris
Subject: RE: AND THE WINNER IS…FRANCISCO
I am still very crious as to why exactly you needed the fields to be visible to the user in your workflow… I have designed custom workflow for years, so I have a good idea of the general requirements behind workflows; and yet I don’t see why you would need this. I am wondering if perhaps a deeper analysis of your need wouldn’t yeld a possibly completly different way to achieve the same final result.
Let me know
I’d be curious to understand! 
Good luck though
Nicolas Abesdris
Quintessence e-solutions Inc.
Subject: RE: AND THE WINNER IS…FRANCISCO
If his workflow engine is abstracted to allow business users to define their own query criteria for workflow actions, they might need field names for @formula evaluations.
Subject: RE: AND THE WINNER IS…FRANCISCO
Yes, I see what you mean.
Still, I’d be curious to know exactly the parameters; Perhaps there would be a way to handle this without a 3rd party product.
For instance, once could put on the form the name of the fields next to the label, so that users would know what to input.
Or better, maybe there is a way to build pick lists made of the correct field values, so that it is not required to be a “designer” in order to use it…
Just my 2 cents; i Guess i have spend too many years as a Notes Analyst: the (infamous) “And WHY do you need this, exactly?” question is always the very first that pops into my mind…
grins
Cheers!
Nicolas Abesdris
Quintessence e-solutions Inc.
Subject: RE: AND THE WINNER IS…FRANCISCO
It doesn’t have to be that complicated. See my script code in this thread for a simple way to display the field names.
Subject: RE: AND THE WINNER IS…FRANCISCO
Nathan,
Just checked your solution in this thread: a very nice bit of code!
Simple, elegent, and it does the job without the need for additional access. I like it!

Nicolas Abesdris
Quintessence e-solutions Inc.
Subject: ATTENTION ALL GURUS: I WILL BUY YOU LUNCH IF SOMEONE CAN FIGURE THIS OUT.
I would create a new copy of the form and instead of fields put their names as fields. You can make them “clickable” to add the actual value into your selection. This is probably the best solution if the form is not changed often or if there are not too many fields in the form.
You can also use solution suggested by Michael Sloan and show the actual form in “read” mode.
Subject: *Out of curiosity, why not just buy Integra for Notes if it does the job?
Subject: RE: *Out of curiosity, why not just buy Integra for Notes if it does the job?
Because my company doesn’t have unlimited budget like yours I guess. I said that Integra contains the feature I need but it also has much more stuff that I don’t. I don’t think its feasible to pay thousands of dollars for one feature, when I can just write it myself.
Subject: RE: *Out of curiosity, why not just buy Integra for Notes if it does the job?
It’s not about “unlimited budgets”, it’s about cost trade-offs. Is your time and effort “free”? It may be, depending on how costs are computed in your organisation. The choice boils down to where the money is spent – do they buy an off-the-shelf product that does what they wan and comes with support, or do they spend what can amount to more money developing a solution in-house that can make a critical asset (that would be you) unavailable for other projects.
Frankly, as an internal developer who was budgetted as “overhead”, it always irked me that management would let projects pile up and lead times wind way into the future while I was kept busy devloping some subset of a shrinkwrapped solution that actually would have been cheaper and more effective in the long run.
And that’s what Ben was on about.