I need to pass as parameter a document to a rule, however, it will only work in a interface. When in a portal url, it throws an error `at function a!httpformpartcheckvalue_appian_internal [line 37]: The function a!httpFormPartInputToFormPart is unavailable.`
rule!test( token: local!token, id: ri!id, valorPrevisto: local!value_for_payment, file: local!uploaded_file[1] )
I've been debugging and I am sure that's because of uploaded_file. I would like to share my component to please get some insights from you
a!fileUploadField( label: "Please, upload a file:", labelPosition: "ABOVE", fileDescriptions: "excel", target: cons!CE_UPLOADING_FOLDER, maxSelections: 1, value: { local!uploaded_file }, saveInto: { local!uploaded_file, if( a!isNullOrEmpty(local!uploaded_file), { a!save(local!currentFormStep, 1), a!save(local!variant_value_for_payment, 0) }, null )
Just to remind, in a interface, that's 100% fine, but when that comes to a portal... I believe it doesn't have access to the folder of the `target` or something like. Hope you guys will help me one more time, so we'll both make contributions for the community. Thanks in advance
Discussion posts and replies are publicly visible
Hi Silas B. Ferreira ,
Since its portal, you cannot use the local!uploaded_file directly. Use the a!submitUploadedFiles() to get the file into appian.
Since its saying error in a!httpformpartcheckvalue_appian_internal, So I am assuming that the rule is an integration. So my suggestion would be start a process using a!startProcess() on button click and use a!submitUploadedFiles in the button also to get the file in to appian folder and then call the integration inside process model using call integration node.
Sri Ram Kaja Are you sure it's possible to use process models inside Portals?
Silas B. Ferreira said:possible to use process models inside Portals?
a!startProcess(), specifically, does work. At least, for the most recent several versions of Appian.
Nice, thanks for the information
By the way, this error makes so weird to be given only in a portal but not in a interface. I was developing a process model with a start form, then I came back to the same point I was before. Because I discovered portals won't accept a process model replacing an interface
A process model with a start form would not be a valid thing to use in a portal. Portal pages can be a single interface only. The start process node would be used *only* to pass information from the portal to a process for the sake of persisting information or kicking off related processes/tasks/etc, but none of that involves a process with a start form.