Question

Creating tables dynamically in Appian, firing SQL Queries and Maintaining sessions

Forum|Forum|3 years ago
October 9, 2022
9 replies
0 views

Hi Team,

I am having some queries as mentioned below:

1. Can we create tables in Appian db dynamically ?

2. Can we fire SQL queries to Appian db ?

3. How to maintain the session of a user in a portal? I want to delete some table rows if user session is logged of.

Please help in this regard.

Thanks in Advance,

stefanhelzle0001

Brainy

1) Yes

2) Yes

3) No

I would not do any of it, but I am interested in your use case. Would you mind telling us what you intent to do?

J

javedsahabj9665Author

Thanks Stefan,

My use case is like follows for the first point:-

1. A user comes up in the portal, I want to store some data of that person in the Appian db's dynamically created table specific to that use data only (the data will be populated from third party api). Now, remember, my third point, I want to flush out that table if user logs off or session is closed.

So now could u pls tell me how I can do this ?

stefanhelzle0001

Brainy

Your use case is not supported in that direct way. Can you add a few more details?

Is this about Appian Portals? I mean, with an anonymous user? What ist the use case?

richardm900458

Third is just simply currently not working.

Appian provides us, as designers, a certains set of functioanalities or settings we can influence. Checking if a user is ideling on a portal website is just not one of them (i would even ask, was the deeper sense is)
Portal has no "log in" -" log off" in the sense you perhaps want to use/need it. Appian is executing functionality the moment a user interacts with a link, button or inserting/selecting values. So even if there would be a functionality there, its not 100% that a db table row can be deleted that easy as there is no interaction to trigger the execute of the deletion action.

J

javedsahabj9665Author

Thanks Richard

richardm900458

if i read your use case,this feels like "overthinking"
-> why not just storing the data in a DB, the moment something is really submitted?
Edit: and why do you want to have a DB table per user? whats the benefit to just adding a row to an existing table?

Sign up

Login with SSO

Login to the community

Login with SSO