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
I guess I'm behind the curve here - how do you get Portals on Community Edition? I don't see any sign of it on my instance.
Hi Mike,
Should be there by clicking on the top right waffle icon. There's nothing I had to set up... after starting up my instance it was just there.
You might have to drop the existing instance and get a new one.
Unknown said:You might have to drop the existing instance and get a new one.
I have a bunch of utility rules I'd written in other systems which I manually (grumble) recreated in my CE instance, so I'm avoiding doing this at *all* costs.
FWIW this is the totality of the options in mine (i haven't added any additional Sites, nor removed any). I'm guessing Stefan might be right, in that mine was created too long ago to get it deployed automatically.
I can confirm that the age of the ACE site only matters in being older than ~Apr 15 or not. Because of how Portals are provisioned, only sites created after that date had Portals set up.
John Rogers said:only sites created after that date had Portals set up
Is this something that can be fixed from the Appian side? I don't want to lose what I already have set up on my current iteration, since there's no way to take a backup export.
There's no general fix for all ACE sites, given the fact that Portals is currently a feature that requires an app to publish Portals, and apps are only provisioned into an ACE site at startup.
We are working diligently to move the Portals publishing experience fully into the Designer environment. Among a host of other benefits, it also means that when we release that, existing ACE sites will be able to get Portals the way they get other new platform features.
@Stefan Helzle, I have tried this approach of dropping the existing instance and getting a new one and the error still exists in new one.
Stefan's comment was suggesting a method for getting an ACE site that has the Portals capability enabled. It wasn't a suggestion on how to avoid the error this thread is about.