In the course, while creating the record type on the community edition under IT Request - we are instructed to add a field in the data model for "caseContact" and keep its type as "User". Further, in the tutorial, Appian automatically creates a relationship between the record type and users, but this is not shown in my Community Edition. Could anyone guide me and point out any errors? Will this create any future problems for the application or any of the generated actions?Attaching the screenshots.
Discussion posts and replies are publicly visible
That chaining sign is coming for relationship only. It means you got the relationship
I think that the second screenshot is the one from the doc... the first one doesn't have the sign...
Review previous steps in the doc .... probably you missed something...
Yeah, the second one is from the tutorial.
I have followed each step. I referred to the YouTube video as well as the PDF and followed what they've done. They just added a field and set the type to User, that's all.
Nothing extra. Appian created the relationship on its own. In the same way it did for the choice list fields. But for me, the user part didn't get linked.
Oh sorry , I have followed the line what he has written above the snippet.
adityat7800 At first you should know why we are using relationship. Let's say, we have two table in our database, one is for customer details and another one is for customer address. So now, I have a name "Aditya", that name and other details I want to store. So with the help of primary key the name "Aditya" will get the ID(primary key) 1. But my address table is different. I cannot store address of Aditya in the customer details table. But if I want to map that two table I can create a column named "customerId" in address table and can create a relationship with the "ID" (primary key) of my main table (customer table). Now whenever I want to submit the details the details will go for customer details table and address will come to address table with the help of primary key of the main table(customer table).
So, that is the purpose of relationship, I think if you have any scenario like that you can use relationship. Or else no need to configure the relationship.
Hope you can understand.
**And just an information, we can create relationship by mapping in database also.
I understood the purpose of relationships. But that's also why I have this doubt. This particular record type is linked to a form which delegates tasks to the case contact users - shouldn't there be a relationship for such a process model? That's why I wanted to clarify the error.
I hope I'm conveying what I want to know.
adityat7800 said:shouldn't there be a relationship for such a process model?
Can you please clarify?