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.

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.