using multipart/form-data to post document to iManage

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:

• Removed the "content-type" header entirely, this is automatically set by Appian when you set the request body to be in multipart/form-data format
• when giving the profile attributes in JSON format, in the expression rule the entire JSO needs to be wrapped in an a!toJson()
• reduced the numbers of parameters in the profile part (I have only kept the required ones), while having the other parameters will not cause an error, for simplicity's sake I have trimmed them down

Below are screenshots of the listed changes:

UPDATE: I have since been able to get this to work and the solution is quite simple here is what I have done:

• Removed the "content-type" header entirely, this is automatically set by Appian when you set the request body to be in multipart/form-data format
• when giving the profile attributes in JSON format, in the expression rule the entire JSO needs to be wrapped in an a!toJson()
• reduced the numbers of parameters in the profile part (I have only kept the required ones), while having the other parameters will not cause an error, for simplicity's sake I have trimmed them down

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.