We are currently performing maintenance on Appian Community. As a result, discussions posts and replies are temporarily unavailable. We appreciate your patience.
I am using Appian Community Edition to explore portal concepts.
Getting Invalid RuleUUID error when trying to call Integration rule which invokes WEB API to start a process in Appian.
Properly validated all the security mappings to the objects used.
Please suggest if I am missing something
Discussion posts and replies are publicly visible
Seems like the called expression did not deploy to the portal. By any chance, could it be that you missed to provide the required credentials for the connected system? This requires an import customization file.
Hi Stefan,
Thanks for the response,
As stated by you, I have encountered the initial issue with the connected system which is fixed by including the Import Customization file with connected system credentials. It was working properly before couple of days.
When I tried accessing now, its throwing on the Integration rule as Invalid UUID.
Any suggestion to solve this is much appreciated.
Thanks Vamshi
Hi Vamshi,
On a side note, where did you get the required Import Customization file on the Community Edition?
This probably means that the integration was not deployed. Again, probably by a missing dependency.
Any update Vamshi on this issue?
Is it resolved ?
If yes, then may i know what is the resolution for this.
Same topic including a solution
community.appian.com/.../portals-on-community-edition---can-t-save-form-input-from-portal-to-dse
Last comment was from keanu Delgado, that team is working on the fix.
Just checking whether the fix is applied for the appian community edition env or not?
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.
We won't ne getting import customization file on community edition. I have created it manually to include Connected System details.
John Rogers, Issue seems to be still exists in the existing Community Edition. Please provide an update once the fix has been rolled out in Existing sites.
Will do! We're working furiously on it and I (or someone else on the Portals team) will provide an update once there's one to share.
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.