Skip to main content
H
Hardy_S1-Visitor
1-Visitor
February 1, 2018
Question

Use the CLI for updating a field with rich text content longer than 8191 characters

  • February 1, 2018
  • 1 reply
  • 1493 views

We are using the CLI (im.exe) for updating a rich text field with content we maintain in another system (SharePoint).

e.G.

"C:\Program Files (x86)\Integrity\IntegrityClient10\bin\im.exe" editissue --richContentField=Status="Some content ..." 1234567

This works well in a nutshell, also with inline images in the HTML, that we parse out and add as attachments.

We create the .cmd files programatically and are looking into further automating the approach.

We are facing the following limits restrictions and are wondering if they can be overcome:

  1. the windows cmd interpreter has a limit of 8191 characters. Someting our content is longer than that and we cannot update this issue with the CLI. Are there any known workarounds for that?
    Good solutions would be an "Append" command or the option to read all parameter data from a file, e.g:
    im.exe" editissue --richContentField=Status= c:\contentfile.txt 1234567.
    IS any of this supported somehow?
  2. When adding attachments, only local or UNC paths seem possible. Is there a way to get the file from a Web Server address instead?
  3. If we cannot resolve issues 1,2 we would like to use the webservice in client side JavaScript. The limits don't seem to exist there. I see big issue though: Each SOAP call requires username and password and our API endpoint is served bei http. unsecure. We will not ask the user for password in our unprotected javascripts for these credentials and we would not store them or not transmit them through unsecure channels.
    Is there functionality of Javascript libraries available that can integrate with windows authentication - like IM.exe is able to? Any other options for implementing a secure web service integration?

1 reply

A
awalsh5-Regular Member
5-Regular Member
February 1, 2018

There is currently no way to use a file for input for a rich text field.  There's also no way to give an attachment location using a URL. Both of these are good ideas. 

For #3: I can't find a way to give a default user for connecting with web services. 

Would using the Java or C API be an option? For either, you can specify a default API user in the properties files, and use this user rather than giving credentials when connecting via the API. You can Impersonate other users so that actions still happen as them. 

Terms & ConditionsAccessibility statement