Hi everyone,
We're trying out Portals on a Community Edition. We've set up a test form on an interface, DSE, web-api, connected system, and integration. Portal publishes, works, looks good.
But on a Community Edition environment, how do I get an import customization file that's needed for the Portal to save info from the test form? The usual ways https://docs.appian.com/suite/help/22.1/Managing_Import_Customization_Files.html#download-a-template-file aren't available in the Community Edition. As I understand, I can't save info from the Portal to my data store without it.
Many thanks,
Uel
Discussion posts and replies are publicly visible
Last week there was a similar conversation here. I suggest to contact Appian.
Thanks Stefan. I did email and there reply:
Hi Uel, Unfortunately, we are unable to help with project specific issues, but you are welcome to post questions as discussion posts on Community or take courses on Academy Online. Additionally, here is the link to our Documentation. Best,Appian Community Edition Support Team
Hi Uel,
Unfortunately, we are unable to help with project specific issues, but you are welcome to post questions as discussion posts on Community or take courses on Academy Online. Additionally, here is the link to our Documentation.
Best,Appian Community Edition Support Team
Thank you so much for this tip alex.ladue.
The second option requires the plugin "Content Tools" to be deployed.
Yes it does require the plugin "Content Tools" to be deployed, but I believe that is automatically deployed to Community Edition sites.
Brilliant :) Thanks alex.ladue we'll give that a try and then report back.
Hi Alex,Thanks for the confirming this approach. This is exactly what I have done. I am however getting another (very strange) error when calling the web api, i.e. `The System Has Encountered an Error - HTTP Code: 500`.
Expression evaluation error [evaluation ID = #####:####] at function a!buttonWidget [line 893]: Invalid Rule UUID in expression: ########-####-####-####-############
Line 893 is where I call the integration with the `Appian-API-Key` hardcoded as a header.
a!buttonWidget( label: "Submit", icon: "check-circle", saveInto: rule!Integration_apiPOSTToWebAPIEndpoint( payload: local!payload, onSuccess: { a!save(local!result, fv!result), a!save(local!competitionEntry, null) }, onError: { a!save(local!connectedSystem, fv!connectedSystem), a!save(local!result, fv!result), a!save(local!error, fv!error) } ), submit: true, style: "PRIMARY", loadingIndicator: true, validate: true )
I have tested the integration, web api and the the submit button - they all work as expected. When deployed as a portal on Appian CE, it fails with the error provided above. I have looked at the log files and cannot find any clues.
Any ideas or guidance would be appreciated.
Hi Philip, looks like now you're running into a bug with Portals that we noticed has been affecting all Community Edition sites made since Tuesday. The issue occurs when triggering some connected systems in a portal, and it shows as the error: "Invalid Rule UUID in expression." There's a fix in progress by our Engineering team and it should be resolved by the end of this week.
I apologize for the inconvenience!
Thank you Keanu. I thought I was going mad!? Looking forward to the fix!
Hi Keanu Delgado I'm getting slightly concerned as my Community Edition (with a lot I've built on it) has been showing this error since yesterday. Could it be the fix you mentioned?
Any Update on this?
I tried calling integration in portal but getting error like invalid uuid .
Property file is uploaded while publishing the portal.
Any luck with calling the integration from portal works?
We have fixed the issue. We're continuing to figure out whether it will roll out automatically to existing ACE sites or whether we need to take explicit action to fix affected sites.
I tried publishing new portal using the same interface but still I am getting the same error.
The System Has Encountered an Error - HTTP Code: 500`. refer to the screenshot which i have attached in the above discussion
Hey , as John mentioned, while we have identified and fixed the issue, it will take a little more time for the fix to be made available across existing Community Edition sites. We will update here when everything should be working again. Sorry for the inconvenience.
Okay, Thanks for the update Alex.