1

I am trying out a mashup of Alfresco and ProcessMaker. I intend to use Alfresco's document management capabilities over ProcessMaker.

Here is the scenario:

A user fills up a form in ProcessMaker and a file is uploaded in Alfresco.

I followed the wiki in this link. The problem is that, my result variable is always false. I also checked my input. I am able to access Alfresco via the address I provided, but it still does not work. I also ensured that the file exists in my directory.

Is there a way I can check (probably from logs or console) the error being returned by Alfresco or ProcessMaker so I can continue?

  • Alfresco is installed in a Japanese version of Windows 7.
  • Alfresco version is 4.2.c.
  • Process Maker version is 2.0.45.
Braiam
  • 1
  • 11
  • 47
  • 78
nmenego
  • 846
  • 3
  • 17
  • 36

3 Answers3

3

I have no experience with ProcessMaker, but here's a couple of things you can try to investigate your issue:

  • inspect the network traffic between ProcessMaker and Alfresco (e.g. with Wireshark) to see if there's any hint available in the HTTP responses from Alfresco
  • enable DEBUG logs on Alfresco side
  • as far as I can see, ProcessMaker users Alfresco CMIS REST APIs to implement its triggers. Have a look at class.pmAlfrescoFunctions.php in ProcessMaker and try the calls yourself with some REST client (e.g. curl, Chrome REST console, htty)

This should give you an idea of what's going wrong in your case.

UPDATE

After reading that the Japanese language pack changed a folder name from "Sites" to "/サイト", and double checking the Alfresco triggers code, it's indeed the case that localized versions of Alfresco are not supported OOTB by ProcessMaker, which hardcodes "Sites" in its CMIS queries.

While the workaround provided by @nmenego would be enough in most cases, I opened a bug to ProcessMaker to let them know of the limitation.

Community
  • 1
  • 1
skuro
  • 13,414
  • 1
  • 48
  • 67
  • Very valid points. I checked all of these points, but for my case, all is well. I have added my answer because for my case, it was what solved the issue. The debug logs in Alfresco as well as the network traffic between the two systems are both OK. – nmenego Mar 07 '13 at 01:31
1

I discovered that the problem was in the encoding used by my installed Alfresco. Instead of the default folder /Sites, the default directory was /サイト (sites in Japanese). Apparently, upon installation, the names of the default folders are translated to Japanese.

What I did was I added a folder named /Sites, and it all works now. Of course, the points pointed out by skuro are all valid as well.

nmenego
  • 846
  • 3
  • 17
  • 36
  • IIRC that's an ancient bug, I had troubles with it like three years ago... I forgot to ask, which version of Alfresco are you using? – skuro Mar 07 '13 at 06:49
  • I added the versions of Alfresco and ProcessMaker to the original question in case other people encounter this problem. Also, if I could be so bold to ask a favor from you @skuro to edit original tags and add processmaker, since I do not have enough reputations to do so. Thanks! – nmenego Mar 07 '13 at 07:37
  • Tag added. Apparently the Alf version you're using is pretty new, I'll see if there's any problem on the side of localizations... – skuro Mar 07 '13 at 11:00
  • 1
    Ok, the problem is indeed in ProcessMaker: the PHP file I linked above hardcodes "Sites" in a couple of places, so that when you localize your Alfresco instance the integration falls apart. – skuro Mar 07 '13 at 12:04
0


We just confirmed that this is a bug in the ProcessMaker connector triggers for Alfresco, thank you for reporting it.

I've just opened ticket 11003 in ProcessMaker's Main Support Portal for the developers to work on fixing it.

Please register for free in ProcessMaker's Main Support Portal in order to follow up on the resolution of this bug.

Best regards,

Arturo A. Robles
Customer & Partner Support Manager
Colosa Inc. - ProcessMaker

Arturo A. Robles
  • 1