Conclusions

Conclusions
Name:	Conclusions
Tech Name:	Conclusions
Class Name:	Conclusions
Type:	Standard
Template:	Security_groups, Assignable, Basic
Custom Module:	No
Auditable:	Yes
Importable:	No
Reportable:	Yes
Hide module on Main Page:	No

Business Description

Missing User input

Collapse

Custom Actions

Collapse

Processes

Related Processes

Collapse

Related Process Steps

Related Features

Collapse

Affected by

Collapse

Initiating

Collapse

Related Integrations

Structure

Collapse

Fields

Name	Type	Required	Validations	Visible	Editable
Assigned to	relate	No		Yes	Yes
Created by	relate	No		Yes	No
Date Created	datetime	No		Yes	No
Date Modified	datetime	No		Yes	No
Description	text	No		Yes	Yes
Meeting	relate	No		Yes	Yes
Modified by Name	relate	No		Yes	No
Name	name	Yes		Yes	Yes

Collapse

Relationships

Laft	Type	Right	Short Description	Relationship
Meetings	one-to-many	Conclusions	One Meeting record can have many related Conclusions records, but a specific Conclusions record can be related to only one Meeting record.	Relationship: Meetings - Conclusions
Users	one-to-many	Conclusions	Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.	Relationship: Users - Conclusions
Users	one-to-many	Conclusions	Specific Sugar user can create many account records, but specific account record can be created by only one user.	Relationship: Users - Conclusions
Users	one-to-many	Conclusions	Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.	Relationship: Users - Conclusions