I am trying to build a portal to request Appian user account creation. From the interface I invoke an integration which in turn calls the webapi to trigger the process model to actually create Appian User. Individually each piece works fine from designer view. From the published portal however I am facing issue with the connected system. I created a service account and have mapped the API-Key in the CS.
Further I tried skipping the CS and instead use Basic Auth with a system admin credentials but that throws an error that parameters aren't being passed.
Any help on what am I missing here?
Discussion posts and replies are publicly visible
It seems like your CS is not deployed to the portal page. This is why you only see the UUID, but not the correct name.
Hi . Did you ensure to set up your import customization file?
Got it working. I had missed the CS import. Thank you for pointing that out.
Hey, If you don't mind, could you please let me know from where you got the customization file?
This is described in the documentation and currently has some issues on the Community Edition.
Check this: community.appian.com/.../portals-on-community-edition---can-t-save-form-input-from-portal-to-dse
What if we can use the first approach which alax suggested?
What do you mean?
Storing credentials in plain text is always a bad idea. Do you use a Community Edition? If yes, give it a try.
Yes, I am using CE. do we have to update the portal for this? I removed the CS and used the API key directly into Integration Header
Stefan, I have 1 more query. That is regarding the Record relationship, not for Portal.We have 2 tables and for those, the primary keys are auto-generated values. But here, for a record in the first table, we have a record in the second table as well and we have processID in both the tables as common. Now i am trying to create a relationship between these 2 records but I am not getting the option to get the data based on process id. Any idea what shall i do in this case?
Record relationships can only be defined on unique fields.
I would not use the processID as a common or unique value, as this will be reused.
Why not just store the primary ID of the first table into the second?
© 2023 Appian. All rights reserved.