Ideas
| Ideas | |
|---|---|
| Name: | Ideas |
| Tech Name: | Ideas |
| Class Name: | Ideas |
| Type: | Standard |
| Template: | Security_groups, Assignable, Basic |
| Custom Module: | No |
| Auditable: | Yes |
| Importable: | No |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Short Description
The Ideas module is designed to facilitate the submission, evaluation and management of ideas related to the company and its processes.
Business Description
Overview
The Ideas module is used to collect and evaluate improvement proposals submitted by employees. Each idea has an author, a decision maker, a status and, optionally, an explanation of the decision. It streamlines the process of idea submission and decision-making, helping to enhance the company's processes and overall efficiency.
Ideas can be followed on the dashboard with the My Ideas dashlet.
Fields
| Name | The name or title of the idea. This field is required. | |
| Description of the Idea | A detailed description of the idea, including its purpose and potential impact. This field is required. | |
| Status | The stage of the idea in the evaluation process: New (default), In progress, Suspended, Accepted or Rejected. This field is required. | |
| Explanation of the Decision | The reasoning behind the decision made about the idea. | |
| Author of the Idea | The user who proposes the idea. This field is required. | |
| Current Decision Maker | The user responsible for evaluating the idea. This field is required. When you create an idea, the field is filled in with the supervisor of the author ("Reports to" in the user's profile), and it is updated when you change the author. You can change it at any time. |
Subpanels in Detailed View
Below the main idea record, users have access to the following subpanels:
| Notes | Notes related to the idea, which facilitate communication and collaboration on the idea's development. | |
| Organizational Unit | Organizational units that have access to the idea. |
Actions Available in the Module
The Ideas module offers the standard record actions: Edit Details, Duplicate, Delete and View Change Log. Changes of the name, description, status, explanation, author and decision maker are recorded in the change log.
Workflow for Decision Makers
The decision maker evaluates the idea by changing its Status and describing the decision in the Explanation of the Decision field:
- Accepted - the idea is accepted for further consideration or implementation.
- Rejected - the idea does not align with the company's objectives or is not feasible.
- In progress or Suspended - the evaluation or implementation is under way or put on hold.
To pass the idea to another person for evaluation, change the Current Decision Maker in the edit view.
When an idea is saved, the decision maker and the author receive a notification in the system. The decision maker is also given access to the idea automatically.
Custom Actions
Processes
Related Processes
| Process | Short Description |
|---|---|
| Employer Branding | Building the image of the company as an employer among its employees: surveys, ideas and kudos |
Related Process Steps
Related Features
Affected by
Initiating
Related Integrations
Structure
Fields
| Name | Type | Required | Validations | Visible | Editable |
|---|---|---|---|---|---|
| Author of the Idea | relate | Yes | Yes | Yes | |
| Created By | relate | No | Yes | No | |
| Current Decision Maker | relate | Yes | Yes | Yes | |
| Date Created | datetime | No | Yes | No | |
| Date Modified | datetime | No | Yes | No | |
| Description of the Idea | text | Yes | Yes | Yes | |
| Explanation of the Decision | text | No | Yes | Yes | |
| Modified By Name | relate | No | Yes | No | |
| Name | name | Yes | Yes | Yes | |
| Status | enum | Yes | Yes | Yes |
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Ideas | one-to-many | Notes | Flex relate used in Idea | Relationship: Ideas - Notes |
| Users | one-to-many | Ideas | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Ideas |
| Users | one-to-many | Ideas | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Ideas |
| Users | one-to-many | Ideas | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Ideas |
| Users | one-to-many | Ideas | One User record can have many related Idea records, but a specific Idea record can be related to only one User record. | Relationship: Users - Ideas |
