Portals on Community Edition - Can't save form input from Portal to DSE

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

Peter Lewis Can you do something about this? This is running in circles.

I do not know of a way to somehow get that template without export.

Sorry for the confusion in getting this set up! We are looking to make both the product and the documentation better in this area.

For now, there are 2 ways you can get get the integration to web API connection working on a Community Edition site:

1. Instead of using a connected system, reference the API key as a header directly in the integration object (Header Name -> Appian-API-Key)
2. Follow these steps to get the Connected System's UUID and put it in a properties file:
   
   1. Create your Connected System
   2. Create a constant object of type connected system that points to your new connected system.
   3. Create an expression rule, and inside the rule run test the following expression:
      getcontentobjectdetailsbyid(cons!<your connected system constant name>)
      

   4. Take the UUID, and add it to a text file like is listed below along with your API key. This .properties file can be uploaded with your portal to enable integrations to connect back to your site. (Make sure you have enabled editing file extensions, and save it as a .properties file.

      ## Connected System: <your connected system name>
connectedSystem.<your connected system UUID>.baseUrl=<your site URL>
connectedSystem.<your connected system UUID>.apiKeyValue=<your API key>

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 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.

Update: For existing Community Edition sites, the Engineering team is scheduling automatic restarts to pick up the fix. This process may take some time to get through all the existing instances.

If you would like to pick up the fix immediately, follow the steps provided in the Community Edition User Guide to shutdown and then restart your Community Edition site. This sequence will take about 50 minutes and will bring back the environment in the state you left it — your data and applications will not be deleted.