Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hello,I am trying to set up an integration to post a document to a folder in iManage. This integration requires the request body to be multipart/form-data, and to pass through the document to be uploaded and the document "profile" which contains information which will be added to the document on the iManage side.below is how the integration is set up in postman:
And this is how I have set up my integration (second screenshot showing the expression I have built for the profile part):and this is the error I am getting: Would anyone have an idea of where I am doing things incorrectly? It would seem to me as though the content type is not passed through properly, as seen by the content type field in the header section of the httpResponse.Thank you
Discussion posts and replies are publicly visible
Looks good for me and I did similar integrations in the past. Without more details of the actual error on the other side, this becomes a pure guessing game.
Can you talk to the OPS team at the iManage side?
Should be able to, but have you seen or heard of successful integrations between Appian and iManage?
Not that I am aware of, but a multipart form post is not exactly platform specific in any way.
Does the API expect the profile part to be JSON?
These are extracts of the API documentation, doesn't specify unfortunately, it would seem like JSON should be fine?
Well, in the config, the part "profile" also seems to be a file. That might make a difference. A JSON string in an application/json part is something different than a JSON file using some other content type.
so should I try to create a JSON file, and then pass that along with the actual file in the appian request body configuration?
You could try many things, but without talking to the API team, this can become a very long and tedious trial&error session.
Thank you, will try that approach and will also try to reach the API team.
UPDATE: I have since been able to get this to work and the solution is quite simple here is what I have done:
Below are screenshots of the listed changes:
Great to hear that. I would have expected that Appian does the JSON conversion automatically when setting the type to JSON.