flat space issue...

Jime0726

hi, i know there is a workaround to avoid saving documents into flat space by doing something along the lines of adding a custom field to the dialogs and hiding it (and obviously there's a lot more too it)...but i was wondering if anything has been written that we have not seen yet that would involve something like the following scenario:

a document usually winds up in flat space when it is copied from the worklist, because when you right click on the document, click copy, it opens the dialog first. When you look at the "location" field it just displays the DB and not the folder where the document is stored, so when the user clicks OK on the profile to save it as a new document, that document is now in flat space. is it possible to mark that "location" field required and clear it out when the dialog is open to force the user to search for the correct folder and populate it?

jny

hi, i know there is a workaround to avoid saving documents into flat space by doing something along the lines of adding a custom field to the dialogs and hiding it (and obviously there's a lot more too it)...but i was wondering if anything has been written that we have not seen yet that would involve something like the following scenario: a document usually winds up in flat space when it is copied from the worklist, because when you right click on the document, click copy, it opens the dialog first. When you look at the "location" field it just displays the DB and not the folder where the document is stored, so when the user clicks OK on the profile to save it as a new document, that document is now in flat space. is it possible to mark that "location" field required and clear it out when the dialog is open to force the user to search for the correct folder and populate it?

Documents are always stored in a flat space. In fact documents are never rooted to a folder. Unlike files stored in the system directory, the WorkSite documents - which essentially are server objects with a corresponding physical file stored in the file server - are never rooted to any one folder. The documents "contained" in the folder are merely pointers (references) to the objects which are stored in the database/flat space.

If you would like to enforce the import destination to be a folder when inside the profile dialog, then you may explore the possibility of catching the PreOnOK event to keep the dialog open when the end-user has selected a database. Prompt them to select a folder. This implies that you would need to (1) check that the newprof.nrs (which is also fired for Copy) can return a handle to the source document, so that you know it's a copy - because a new document import will not have the source document to return - and (2) check that the import location is database.