Problem and Solution - DAPI.CreateNode() returns Could not create path

Hi there,

This time I am posting both the problem and the fix. Before anyone asks why I was creating a node using DAPI.CreateNode() let me assure everyone that I was using llNode.NodeCreate() which is the supported way. I merely isolated the llNode.NodeCreateSubclass() as the place where the problem was occurring. I searched the KC for my error message 'could not create path' in various forums, but none had my problem. I was creating a document object in a standard folder. Only when I did the unthinkable and edited the NodeCreateSubclass() to stick some debug in it, did I stumble upon the problem. My previous node alloc statement was trying to allocate the node with an Undefined name. If development is listening, this should spawn an error as technically your DAPI node should always have at least a name.

In case anyone is wondering what I'm doing (and I'm relaying this because I wouldn't mind hearing how others have gotten around the problem), I'm trying to create a request handler that uploads a document to a drop-box folder. This request handler runs in an AJAX call silently from within a form. The response is a JSON string which gives the DAPI ID of the just created node. This is all a workaround so I can submit a form that triggers a workflow, and be able to script an event to copy or move the just created document into the workflow's attachment folder. This is the critical missing functionality of forms that cause workflows to launch. Incidentally, if anyone else has had to solve this problem, I'd like to know your workaround, and from OT, I'd like to know if there is any out-of-box solution for making the document upload to attachments and the form submission all exist on the same page.

-Hugh Ferguson

Find more posts tagged with

Comments

Appu_Nair

“This is all a workaround so I can submit a form that triggers a workflow, and be able to script an event to copy or move the just created document into the workflow's attachment folder.”

There are 2 methods that I know and have used to do this. First the iFrame method published by OT .Since you are an experienced livelinker even if one or 2 of my steps from memory is incorrect you will be able to figure that one

Method 1 –Iframe method.

Create Workflow with attachments folder defined
Add a form template to it
Make the form start this workflow bypassing the start step
When adding form tell the painter you want to see “Display attachments”
Export the template and create a IFRAME element containing wfattach url or something similar to it. There are plenty of examples in the KB.I belive it has to be the last form element.I am not sure if it is apopup it works it has to be in line.
This functionality is broke unless a specific patch is there in 9.7.1.

If all goes according to plan when the form is submitted you should see a wide area in the iFrame resembling the attachments weblingo . You add the document and start the workflow and it will be there. The aesthetics will be far from impressive but it works.You cannot really test if attchments is there or not as the file uplaod is not testable by javascript methods or I don't know how to do it.

Method 1 –Programming method.

I create a form template /definition whatever the customer wants
In the exported view I throw in a file upload control.
I change the form submission to my RH.
When the form is submitted I get the passed in record and the file as well.
I see in my module's INI the workflow I need to start for this
I start the workflow and add the document as well.
I tell user the wf has started and this is the id or something similar.

Not sure how the JSON method works.I would like to see a simple example if possible.

Hugh_Ferguson

Quoted anair@alitek.com on 2011-12-23 11:56:

Method 1 –Programming method.

I create a form template /definition whatever the customer wants
In the exported view I throw in a file upload control.
I change the form submission to my RH.
When the form is submitted I get the passed in record and the file as well.
I see in my module's INI the workflow I need to start for this
I start the workflow and add the document as well.
I tell user the wf has started and this is the id or something similar.

Not sure how the JSON method works.I would like to see a simple example if possible.

My approach is similar to your programming method in that it involves a request handler on the back end. I have been using jQuery, and found a jQuery extension on line that adds a control to a file input element. I got this one here:

https://github.com/jfeldstein/jQuery.AjaxFileUpload.js

What I did next (and since this is jQuery, you will need to import the jQuery library. If you don't know jQuery, this methodology is not the best), is I added a script to my javascript of the form

$("#myUploadInputID").ajaxfileupload({
      'action': '/yourlivelinkurl/livelink.exe',
      'params': {
        'func': 'your.requesthandler'
      },
      'onComplete': function(response) {
        // your ajax should somehow encapsulate ID of document you uploaded, grab it

$("#idOfFormVariableToHoldDocID").val( [ID of document from response]);
}

}

Then in your workflow you would need an event script that moves the document into the attachments. Another reason I'm using this approach is that my form will launch a master workflow that will call sub-workflows, and I want the sub-workflow's attachment folder to get the document as a document object and not as an alias or a copy.

-Hugh

Appu_Nair

Thanks I have done simpler jquery that takes a LiveReport and makes it hyperlinked so was very impresssed by its capabilities.I will try your approach as well soon.

Hans Stoop

I did something like that. IIRC this is what I did:

I created a custom attribute type that displays the standard file-upload on the form.

On submit of the form it stores the document in some configured place and stores as field value the objid.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Freitag, 23. Dezember 2011 16:05
To: eLink Recipient
Subject: Problem and Solution - DAPI.CreateNode() returns Could not create path

Problem and Solution - DAPI.CreateNode() returns Could not create path

Posted by hughf@ca.ibm.com (Ferguson, Hugh) On 12-23-2011 09:59

Hi there,

In case anyone is wondering what I'm doing (and I'm relaying this because I wouldn't mind hearing how! others have gotten around the problem), I'm trying to create a request handler that uploads a document to a drop-box folder. This request handler runs in an AJAX call silently from within a form. The response is a JSON string which gives the DAPI ID of the just created node. This is all a workaround so I can submit a form that triggers a workflow, and be able to script an event to copy or move the just created document into the workflow's attachment folder. This is the critical missing functionality of forms that cause workflows to launch. Incidentally, if anyone else has had to solve this problem, I'd like to know your workaround, and from OT, I'd like to know if there is any out-of-box solution for making the document upload to attachments and the form submission all exist on the same page.

-Hugh Ferguson

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center