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

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.

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!

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.

Thank you Keanu. I thought I was going mad!? Looking forward to the fix!

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.

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.