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; } } }

COPY command change in WorkSite 8.0 SP1

RussWilmott

Until the latest SP1 upgrade, whenever a user performed a copy operation the New Profile nrClass field was naturally defaulted to the Class of the source document.
However this functionality has now been changed.
Refering to the technote below, it states that the user does not see the values on the Enhanced dialog because they need to select the DETAILS button, but Author, Class and SubClass all appear on the SaveAs dialog (provided they are selected in the registry).
When a copy command is used the New Profile dialog is displayed anyway.
So, can we please have at least a registry setting to insert the Class field when copying, otherwise users are going to choose a different Class that will be wrong.

Russ

COPY command change in WorkSite 8.0 SP1
________________________________________________________________________________________________ Technote Number: 62005-1227
Category: Informational
Product: 8.0 SP1
Created: 06/17/2005
Last Modified: 06/17/2005
________________________________________________________________________________________________

Introduction:
Changes to the COPY commands were implemented with WorkSite 8.0 Service Pack 1. Invoking a COPY operation, such as such as Copy and Open, will no longer pre-fill the document profile information.

Information:
The design change was made to better support Matter Centric implementations and the use of the Enhanced Dialogs. The basic premise is that the target document is new content, and therefore it should be treated the same as an import.

When the Enhanced dialogs are in use today, the user does not see the values that are being applied to the profile unless they select the DETAILS button. In such an environment it is dangerous to add values for the user that they may not be expecting.

Find more posts tagged with

Comments

jny

There are two ways to do this. One is to set class field in newprof.nrs. Another way is to add class field to folder properties, assuming that the new document will be saved in a folder and it will be inherited by the new document.

RussWilmott

That's good news.

I'll use NewProf.nrs, but could you tell me how do I get the Class of the source document that is being copied so that I can set the Class of the destination document to be the same?

Thanks

Russ

jny

The ContextItem "SelectedNRTDocuments" returns the source document (the one from which to copy) but since this cannot be returned when in scripting (due to the returned values being in a safearray) you would need to pass it to a COM helper object to get the value successfully.

Once you have the document object through SelectedNRTDocuments ContextItem, you may then query for the Class (off of the document object). See code example below.

[VB]
===================================================================
' Example of a COM Helper Object source code;
' assuming the proid is "SampleFetchContextItems.Helper".

Option Explicit

Private m_Context As IMANEXTLib.ContextItems
Private m_Class As Variant

Public Property Let ContextItems(ByVal vNewValue As IMANEXTLib.ContextItems)
Dim rpSelectedNRTDocuments() As IManage.NRTDocument
Dim objDoc As Object
Dim iCountOfSelectedNRTDocuments As Integer
Dim strClass As String

Set m_Context = vNewValue

If Not m_Context Is Nothing Then
' the documents that the user has selected

' If an attempt is made to retrieve an item from the context items
' collection which does not exist, an exception is thrown. Ignore this
' exception and keep running.
On Error Resume Next

' Extract the selected documents from the context items. They are stored
' under the name "SelectedNRTDocuments".
rpSelectedNRTDocuments = m_Context("SelectedNRTDocuments")

' Check to see if an array of selected documents were retrieved from the
' context items.
If Not IsEmpty(rpSelectedNRTDocuments) Then

' Obtain a count of the documents that the user has selected.
iCountOfSelectedNRTDocuments = UBound(rpSelectedNRTDocuments) - _
(LBound(rpSelectedNRTDocuments) - 1)

' Determine if there are documents selected.
If iCountOfSelectedNRTDocuments > 0 Then
Set objDoc = rpSelectedNRTDocuments(0)
strClass = objDoc.Class.Name
PutClass strClass
End If
End If
End If
End Property

Public Property Get Class() As Variant
Class = m_Class
End Property

Private Sub Put Class(ByVal vNewValue As Variant)
m_Class = vNewValue
End Sub
===================================================================

[NewProf.nrs]
===================================================================
' Ex// calling helper object from script
Option Explicit

Sub NewProfileDlg_OnInitDialog(obj)
dim myobj, sClass
set myobj = CreateObject("SampleFetchContextItems.Helper")
myobj.ContextItems = Context
sClass = myobj.Class
msgbox sClass
End Sub
===================================================================

williamp

Cool but this does not work.

jny

Cool but this does not work.

It should as it had been tested through and through.

You may even try getting a handle to the source document object via the new profile dialog. Since it's a copy op, the NRTDocument Property of the dialog may return the source doc.

[NewProf.nrs]
==================================================
Option Explicit

Const nrClass=8

Sub NewProfileDlg_OnInitDialog(obj)
dim srcdoc, sClass
on error resume next
set srcdoc = obj.NRTDocument

if not srcdoc is nothing then
obj.SetAttributeValueByID nrClass, srcdoc.Class.Name, true
end if
End Sub
==================================================

williamp

I've tried the script in different ways and it throw errors on my end. Having an issue with NRTDocument.

jny

I've tried the script in different ways and it throw errors on my end. Having an issue with NRTDocument.

What are the different ways? The NRTDocument Property of the dialog will not return an object - and will probably throw an error - if you're attempting to query for it in an import op. This is suitable only for copy because the property returns the source document. Whereas in import, there isn't a document object created yet to return; the document object is created only after the dialog goes away so the earliest possible time you can get the imported document object reference is by catching the PostOnOK event and using the "ImportedDocument" ContextItem, like so:

' ~ inside PostOnOK event function ~
Dim importeddoc
set importeddoc = Context("ImportedDocument")

williamp

The error throws when I use the Copy command.

jny

The error throws when I use the Copy command.

Would you show me your script, and the use case steps to encounter the error?

williamp

I am using the script you provided above.

jny

I am using the script you provided above.

ok, but what is the use case step that you used against the script. would you copy-n-past the script here anyway with those use-case steps? also, let me know the version of WorkSite this is.

williamp

It the same that you provided above.

jny

It the same that you provided above.

Show me the steps you use in running the script.