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

Context items for Custom3LookupCmd

David_ISA

Hi,

Does anyone know what context items i need to set when using the Custom3LookupCmd command?
I've looked everywhere and can't find any reference to what the required context items are.
The code i'm using is listed below.
Thanks in advance.

Dim MyLookup As IMANEXTLib.Custom3LookupCmd
Dim pContextItems As IMANEXTLib.ContextItems

Set MyLookup = New IMANEXTLib.Custom3LookupCmd
Set pContextItems = New IMANEXTLib.ContextItems

pContextItems.Add "ParentWindow", Me.hWnd
[What other context items do i need ??]

MyLookup.Initialize pContextItems

If MyLookup.Status = nrActiveCommand Then
MyLookup.Execute
End If

Set MyLookup = Nothing
set pContextItems =nothing

Find more posts tagged with

Comments

jny

IManExt.SelectionDlg.Object ContextItem is necessary so that WorkSite knows to which server/database to assicate the lookup list.

[VB]
pContextItems.Add "IManExt.SelectionDlg.Object", pSess.PreferredDatabase
' A valid pointer to an NRTDatabase or NRTSession object

Darbus

After we use the Execute() method of the Custom3LookupCmd, how do we return the lookup dialog's selected data?

Private Sub btnKnowledgeType_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnKnowledgeType.Click

Dim KnowledgeTypeLookup As New IMANEXTLib.Custom6LookupCmd
Dim contextKnowledge As New IMANEXTLib.ContextItems
Dim db As IManDatabase

db = mSess.Databases.ItemByName("Knowledge")

contextKnowledge.Add("ParentWindow", Me)

contextKnowledge.Add("IManExt.SelectionDlg.Object", db)

KnowledgeTypeLookup.Initialize(contextKnowledge)
KnowledgeTypeLookup.Update()

If KnowledgeTypeLookup.Status = KnowledgeTypeLookup.Status Or CommandStatus.nrActiveCommand Then
KnowledgeTypeLookup.Execute()
'Me.txtKnowledgeType.Text =

End If

End Sub

jny

After we use the Execute() method of the Custom3LookupCmd, how do we return the lookup dialog's selected data?

Private Sub btnKnowledgeType_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnKnowledgeType.Click

Dim KnowledgeTypeLookup As New IMANEXTLib.Custom6LookupCmd
Dim contextKnowledge As New IMANEXTLib.ContextItems
Dim db As IManDatabase

db = mSess.Databases.ItemByName("Knowledge")

contextKnowledge.Add("ParentWindow", Me)

contextKnowledge.Add("IManExt.SelectionDlg.Object", db)

KnowledgeTypeLookup.Initialize(contextKnowledge)
KnowledgeTypeLookup.Update()

If KnowledgeTypeLookup.Status = KnowledgeTypeLookup.Status Or CommandStatus.nrActiveCommand Then
KnowledgeTypeLookup.Execute()
'Me.txtKnowledgeType.Text =

End If

End Sub

This is documented in the manual, Creating Custom Commands in WorkSite: Hijacking Commands: Hijacking a Lookup Button...below Table 11:

Returning the Selected Value to the Form

Your command can return the selected value back to the form using the following name-value pair in the ContextItems collection:

Name: IManExt.SelectedString
Type of Value: String

The form will look for the value stored under this name in the ContextItems collection. If it finds a string, it will stick that string in the corresponding edit field in the form.

When returning multiple selections, the string should consist of a list of items delimited by commas.

The Creating Custom Commands in WorkSite.pdf is distributed with the WorkSite iToolkit 8.x, stored in the iHelp folder under the SDK's unstalled path.

Darbus

Thank you very much. That was the context item string I was looking for. Thanks for the info on the document too.

izogi

This is documented in the manual, Creating Custom Commands in WorkSite: Hijacking Commands: Hijacking a Lookup Button...below Table 11:

Returning the Selected Value to the Form

Your command can return the selected value back to the form using the following name-value pair in the ContextItems collection:

Name: IManExt.SelectedString
Type of Value: String

The form will look for the value stored under this name in the ContextItems collection. If it finds a string, it will stick that string in the corresponding edit field in the form.

When returning multiple selections, the string should consist of a list of items delimited by commas.

To revive this thread, does this definitely work with custom3 commands that return multiple selections? I'm trying to figure out if there's a bug, or if I'm just doing something wrong.

I've created a custom command for Custom3 that pops up my own custom dialog. It works perfectly with the New Profile and Edit Profile dialogs -- the string that it leaves in the "IManExt.SelectedString" Context Item gets inserted into the dialog's Custom3 field as it should.

I can't seem to get it to work with the Find dialog, however. Even if I return a string that's *not* comma-separated, the Custom3 text box in the Find profile dialog still remains blank.

Here's a cut-down test case with the .Execute() method of my custom command, written in C#:


        public override void Execute()
        {
            System.Windows.Forms.MessageBox.Show("The command is definitely running");
            this.Context.Add("IManExt.SelectedString", "MS-1-1");
            this.Context.Add("IManExt.Refresh", true);
        }

If I use this with the Edit Profile dialog (for instance), then on clicking the popup button next to Custom3, I first get the dialog to confirm the command is definitely running, then the text "MS-1-1" is inserted into the text box.

If I use this with the Search Dialog, then on clicking the popup button next to Custom3, I first get the dialog to confirm the command is definitely running, but the text box for custom3 remains blank. Smiley Sad

I'm presently running this inside Desksite 8.2.598.

I guess I have a couple of specific questions:

* Should I be plugging the text into a different context variable for it to be returned to the Find dialog?
* Is there a length limit on the string that can be returned? We have roughly 20,000 strings in the validation table for that field (which my dialog shapes into a nice tree shape), and it's possible that people might want to search for large sets or subsets of them at a time. Even if I padded it with wildcards to encompass larger groups, I think the comma-separated search string could easily get quite long.

Another issue I've noticed on the side is that the documented Boolean context item called IManExt.SelectionDlg.MultipleSelection doesn't seem to be getting passed to my custom dialog as far as I can tell. If I try to look it up, I simply get an exception. (I even iterated through the names of every ContextItem in the collection being passed to the command, and nothing looked similar.) It's not as difficult a problem for me at this point, though, since I can work around it by using different custom command wrappers for the different dialogs.

Thanks for any help.
Mike.

Extract Year.zip