nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workspace Templates

System

Two Questions;

1. When adding a document search folders to a workspace template is there a way to limit it to search only within the workspace (as it does if created from FileSite).

2. When I check the box "Automatically generate email address for folders created from this template" on a template and then generate a new workspace from the template the resulting email address is workspace_value.workspace_value.[dbname]@....

Anyone have any ideas .... ?

Thanks.

Find more posts tagged with

Comments

Migrateduser

We've managed to achieve this by running a SQL /DTS Job after the Workspace creation job has completed. But this is only to be attempted if you happy with accessing the database directly.

jny

1. When adding a document search folders to a workspace template is there a way to limit it to search only within the workspace (as it does if created from FileSite).

[jny] In your search parameters collection, add the workspace id to the search attributeID nrContainerID to do search-within.

2. When I check the box "Automatically generate email address for folders created from this template" on a template and then generate a new workspace from the template the resulting email address is workspace_value.workspace_value.[dbname]@....

[jny] I'm not clear on this question. Would you elaborate?

dabird

While daz' solution works, I'd like to point out that IWOV highly discourages modifying the database tables directly. This is a prime example of an enhancement request for WorkSite Web. We don't know what the product's limitations are until we get feedback from our customers, and if you're modifying database tables to achieve some functionality, then we'll never get your feedback. As a developer on the WorkSite Web team, I encourage both of you to submit an enhancement request for this feature. It seems like a fair request. We do listen to your requests, and we do try hard to get them into a future release.

To submit an enhancement request, go to http://worksitesupport.interwoven.com/, and click on New Feature request link.

As for the email address, is the value on the resulting workspace literally "workspace_value", or are you using that as a placeholder to represent that the value is copied from the workspace? Which version of WorkSite Web are you using?

Migrateduser

I'd be more likely to submit a enhancement request if I actually got some feedback. To date, I've submitted 4 requests, and apart from the initial confirmation, I've heard nothing further.

While I'm sure you review and evaluate them, and the then act on the relevant ones....from a customer perspective, enhancement requests seem to simply drop into a "black hole". The tendency is to believe that if you don't hear anything then nothing is going to happen....

Enhancement Request: Feedback on Enhancement Requests. Smiley Very Happy

On this issue specifically, I was surprised to find that when you add a search folder to a Workspace template that it didn't make it container specific by default - especially as FileSite does this. I'm more inclined to treat it as a defect. We had to implement the 'fix' at the last minute (ie a few days before a rollout) when we realised what the problem was.

regards
Darryl.

dabird

Hi Darryl,

Thank you for your honesty in pointing out necessary improvements in our enhancement request system. I have forwarded your last post to the appropriate management team. Please understand that our feature sets/bug fixes for upcoming releases are planned and locked months before the release is published. So you may submit an enhancement request for the current product release, but you may not see it until several releases later. However, when many customers report the same enhancement request, that usually gets noticed by the management team because it indicates that we may have a design flaw in our product.

I'm sorry that you have had problems with enhancement request submissions in the past. If you'd like, send me a private message with the enhancement request numbers and I will follow up on them for you.

Lastly, I was unaware of the inconsistency between FileSite and WSW with respect to this feature. You're right: since FileSite provides it, but WSW does not, this should be a bug rather than a feature request. Please submit this as a bug for WSW. Do you know if DeskSite behaves like FileSite or WSW?

Thanks for your feedback.

dabird

Hi everyone,

Boy, I sure feel embarrased on this one. Today I was reviewing some code and I noticed that we actually have implemented searching within a workspace created from a template in 8.1. All you have to do is add the workspace template as the container id. When we create workspaces from the template, when the container id matches the moniker for the template, we replace the template's moniker in the container id field with the moniker for the new workspace.

This was actually reported as defect #30320, which was provided as part of the 8.1 release. This should be listed in the Release Notes on the WSW installation CD.

Hope this helps everyone who is using complex SQL modifications to do this!

Migrateduser

You can also do this automatically with the WorkSpace Builder:

http://www.docauto.com/WorkSpace_Builder.htm

jlopez

1. Example: if you have a unique identifier at the Workspace level, lets say Matter# in Custom2 or a combination of 1 or more, as Custom1->client# and Custom2=Matter# then : in the Search Folder criteria set Custom1= %workspace_value%
and Custom2=%Workspace_value%

when the Workspace is created and the Search folder is created in the Workspace it will replace the values with those from the created workspace. I believe this is what you want to do if I understand correctly.

2. There is a technote explaining the way an e-mail address is generated on the support site for worksite. If you create Workspace thorugh code/api you can also customize the way the e-mail address is created.

hope this helps .......

dabird

2. When I check the box "Automatically generate email address for folders created from this template" on a template and then generate a new workspace from the template the resulting email address is workspace_value.workspace_value.[dbname]@....

FYI: This has been reported as a bug in WSW 8.1. We will fix this in 8.2. This is reproducible when you have a template folder whose document profile has client/matter fields that contain "%workspace_value%". This is not an issue if the template folder's default profile has "inherit all metadata" checked.

Migrateduser

Today I was reviewing some code and I noticed that we actually have implemented searching within a workspace created from a template in 8.1. All you have to do is add the workspace template as the container id. When we create workspaces from the template, when the container id matches the moniker for the template, we replace the template's moniker in the container id field with the moniker for the new workspace.

This was actually reported as defect #30320, which was provided as part of the 8.1 release. This should be listed in the Release Notes on the WSW installation CD.

Sorry, I may be being thick here.... but how do you specify this on a search folder when you're setting up a template in Worksite Web? I don't see 'container' as a search option?

regards
Daz

dabird

Sorry, I may be being thick here.... but how do you specify this on a search folder when you're setting up a template in Worksite Web? I don't see 'container' as a search option?

regards
Daz

You need to make sure that the container field is in your role's search profile.
1. Login to WSW as an admin.
2. Go to Manage | Document Search Profiles.
3. On the profile that is used in your role, click the Action button and then Properties.
4. Select an available field. Scroll through the list of search fields until you find the container field.
5. Save your profile.
6. Repeat for all profiles if you want the container field availabe to all profiles.

Migrateduser

Thanks, I've got that far, but when I edit the template, and then try and change the properties on the search folder, I add %workspace_value% to the container field, but when I click OK - I get a "No object for moniker" and it won't accept %workspace_value% in the field?

dabird

Thanks, I've got that far, but when I edit the template, and then try and change the properties on the search folder, I add %workspace_value% to the container field, but when I click OK - I get a "No object for moniker" and it won't accept %workspace_value% in the field?

The feature requires that the value in the field be set to the template's moniker, not "%workspace_value%". When you save the search folder, iManage.dll is trying to perform a search, which is why you are getting the forementioned error.

Migrateduser

Excellent - thank you for your help, and discovering this new fix! I can get rid of part of my nasty SQL now.

kind regards
Daz