Opening a document using OpenCmd command

Hi there,

I want to open a document using the OpenCmd command in the IManExt.dll.

I've got this code "executing" but not opening the document. Is something missing? Can anybody provide me with some sample code? :-)

Language: C# Platform: ASP.NET 2.0 Worksite ver: 8.2

oDoc = (IManDocument)oWorkArea.Worklist.ItemByIndex(1);

OpenCmd openc = new OpenCmd();

ContextItems ci = new ContextItems();

NRTDocument Document;
Document = (NRTDocument)oDoc;

ci.Add("NRTDMS", myDMS);
ci.Add("SelectedNRTDocuments", oDoc);
ci.Add("ParentWindow","");
ci.Add("IManExt.OpenCmd.NoCmdUI", "");
ci.Add("IManExt.OpenCmd.Integration", true);

openc.Initialize(ci);

openc.Update();

openc.Execute();

Thanx
E

PS. I am new to the Worksite libraries :-)

Find more posts tagged with

Comments

jny

Hi there,

I want to open a document using the OpenCmd command in the IManExt.dll.

I've got this code "executing" but not opening the document. Is something missing? Can anybody provide me with some sample code? :-)

Language: C# Platform: ASP.NET 2.0 Worksite ver: 8.2

oDoc = (IManDocument)oWorkArea.Worklist.ItemByIndex(1);

OpenCmd openc = new OpenCmd();

ContextItems ci = new ContextItems();

NRTDocument Document;
Document = (NRTDocument)oDoc;

ci.Add("NRTDMS", myDMS);
ci.Add("SelectedNRTDocuments", oDoc);
ci.Add("ParentWindow","");
ci.Add("IManExt.OpenCmd.NoCmdUI", "");
ci.Add("IManExt.OpenCmd.Integration", true);

openc.Initialize(ci);

openc.Update();

openc.Execute();

Thanx
E

PS. I am new to the Worksite libraries :-)

You cannot use this command object to open a document in its native app from within the context of a Web app. This command is implemented to be used by Desktop application. The command looks to the native machine to checkout the document to its associated WorkSite portable path, then open it from there. When you run this command inside your ASP code, the command will execute successfully if the imanext.dll is registered on the calling machine (which is your IIS server in this case). But, it will also checkout the document to the server's portable path - not the browser machine - and open the document from that path.

If you're only interested in opening the document in read-only mode, you may want to call GetCopy (IManDocument) to download the file then use external methods to open it up from within a browser.

SteveClements

Hi,
Did you ever get the file to open in asp.net c#?

I am in your situation now, new to Worksite and their Interop.

I have looked at the webservices, but dont see much more than viewing...got the doc paths with the objects returned but how do I open them?

jny

Hi,
Did you ever get the file to open in asp.net c#?

I am in your situation now, new to Worksite and their Interop.

I have looked at the webservices, but dont see much more than viewing...got the doc paths with the objects returned but how do I open them?

The IWovServices Web Methods are wrapper functions around the iManage.dll API's. This object model exposes low-level calls; thus it does not provide any mechanisms to handle client-side operations, namely opening a document. Using the WebServices, you can only get back the document object. It is up to you to download the contents of the document file to open it in your browser or the document's native app.

SteveClements

The webservices dont seem to get much use, just doing a search on the service names brings nothing back. Even their webcast is such poor quality its impossible to understand what they are saying.

Would you recommend to use the COM API?

I have having problems with simple things like GetFolderContents returning no documents, but no error. And where do I get the ID's from in the first place?

What is the best practice for opening the docs over the web? I see IW have a smooth process where something is downloaded and auto opened...is there no URL I can pass a doc object ID to which will do the same? Would you create the NRL pointer file on the fly and give the user that to download?

Thx for you help with this! Much appreciated!!

Steve

jny

The webservices dont seem to get much use, just doing a search on the service names brings nothing back. Even their webcast is such poor quality its impossible to understand what they are saying.

Would you recommend to use the COM API?

I have having problems with simple things like GetFolderContents returning no documents, but no error. And where do I get the ID's from in the first place?

What is the best practice for opening the docs over the web? I see IW have a smooth process where something is downloaded and auto opened...is there no URL I can pass a doc object ID to which will do the same? Would you create the NRL pointer file on the fly and give the user that to download?

Thx for you help with this! Much appreciated!!

Steve

I see that you've submitted to Devsupport this similar request. I'll address your questions in detail there. I will then post the answers here when the Devsupport case comes to fruition.

The WSW team uses a proprietary ActiveX contol (or set of controls) to download documents and do integrated check-out's.

There might be some ways to build an URL to open the document in the browser from within the WSW app.

Let's continue this via the DevSupport case. This latter part of your questions will require me to get some input from the WSW team as this is the presentation layer code that isn't equipped for me to address. Of course, if someone from the WSW team happens to monitor this Forum, they might just help address it here.

guido1

Using the service supplied with WSW 8.2 you can perform a search and return the resulting document(s) as a byte stream.

Your client that consumes the service could read the byte stream and save it to the local disk, then perform whatever operation you prefer to open the document in its native app.

SteveClements

The webservices just dont seem complete, for example the document name/description is not returned. Which seems crazy, unless its in another place?

SteveClements

mistake post - wrong place Smiley Happy

Migrateduser

Hi,
I got an ASP.Net application, I need to open the document in DeskSite if it is installed on the client machine, else open it in the Worksite Viewer (assuming it is installed on every client machine). This is something I have seen on Desksite, when right click and select "Send Nrl/Url". But still it open the document only in Worksite Viewer.
My requirement is when the user click the Button or Link on the ASP.Net page, they should be navigate to the document, containing folder on the DeskSite. So they can make changes on the document inside Desksite itself.
Could anyone tell me is this possible or not.
Cheers.
Gihan.

jny

Hi,
I got an ASP.Net application, I need to open the document in DeskSite if it is installed on the client machine, else open it in the Worksite Viewer (assuming it is installed on every client machine). This is something I have seen on Desksite, when right click and select "Send Nrl/Url". But still it open the document only in Worksite Viewer.
My requirement is when the user click the Button or Link on the ASP.Net page, they should be navigate to the document, containing folder on the DeskSite. So they can make changes on the document inside Desksite itself.
Could anyone tell me is this possible or not.
Cheers.
Gihan.

I'm not too certain I understand what you're describing here. It looks like you're trying to launch DeskSite (if it's installed on the same machine on which your aspnet app is running) and to expand the folder to which the document is contained, when the document link (inside your app) is selected by the end-user. Is that correct? Or something else?

You may want to include screen shots of the use case to illustrate your point if I haven't hit it on the nail yet.

Migrateduser

Hi Jny,
Thanks for your reply. Yes that's exactly what I want to do. You got it right.
Cheers.

jny

Hi Jny,
Thanks for your reply. Yes that's exactly what I want to do. You got it right.
Cheers.

Unfortunately, that isn't possible. While, in theory, you may launch any executables, including DeskSite, using ShellExec method, there isn't an entry point to programmatically expand and focus on any one specific node from within DeskSite.

If ultimately you're attempting to take the user to a WorkSite Client, so that they can perform different operations on the document profile itself, you may do so via WorkSite Web link, specifically the GetDoc URL. This URL should take the user to the documet's edit options panel inside WSW for them to carry on with their tasks on the document. This implies that you have WorkSite Web Component installed. If not, then I don't see a way of accomplishing your objective.

Migrateduser

Using the service supplied with WSW 8.2 you can perform a search and return the resulting document(s) as a byte stream.

Your client that consumes the service could read the byte stream and save it to the local disk, then perform whatever operation you prefer to open the document in its native app.

Hello,

I am trying the same thing, consume IWOVServices in ASP.Net / C#. I am trying to call the GetDocuments method. It returns me an error - Object reference not set to an instance.

My code:

string error = string.Empty;
IWOVServices obj = new IWOVServices();
obj.PreAuthenticate = true;
obj.Credentials = new NetworkCredential("username", "password", "domain");

GetDocumentsInput docInput = new GetDocumentsInput();

docInput.ObjectIDs = new string[2];

docInput.ObjectIDs.SetValue("!nrtdms:0:!session:IWAPPRIC:!database:TestActive:!document:2292216,1:", 0);

docInput.ObjectIDs.SetValue("!nrtdms:0:!session:IWAPPRIC:!database:TestActive:!document:2292075,1:", 1);

docInput.OutputMask = OutputMask.DocumentContent;

docInput.OutputProfile = new imProfileAttributeID[1];
docInput.OutputProfile.SetValue(imProfileAttributeID.imProfileCreateDate, 0);

GetDocumentsOutput docOutput = obj.GetDocuments(docInput);
if (docOutput.Errors.Length == 0)
{
Document[] outputDocs = docOutput.Documents;
for (int i = 0; i < outputDocs.Length; i++)
{
Document opDoc = outputDocs;
byte[] byteArray = opDoc.Content;
}
}
else
{
error = docOutput.Errors[0].Message;
}

return error;

guido1

margorilla,

The WorkSite web service implementation is fine, however your code logic is wrong.

Following your call to GetDocuments you have the following statement:
[size=2][size=2][/size][/size]if (docOutput.Errors.Length == 0)
[size=2][size=2][/size][/size]
[size=2][size=2]This logic will generate an "Object reference not set.." exception if docOutput.Errors is null, which it is because your call to the GetDocuments web method was in fact successful.[/size][/size]
[size=2][size=2][/size][/size]
[size=2][size=2]Your logic should read:[/size][/size]
if (docOutput.Errors == null)
{ /* successful */
else
{ /* unsucessful */ }