Events
Events | |
---|---|
Name: | Events |
Tech Name: | FP_events |
Class Name: | FP_events |
Type: | Standard |
Template: | Security_groups, Assignable, Basic |
Custom Module: | No |
Auditable: | Yes |
Importable: | No |
Reportable: | Yes |
Hide module on Main Page: | No |
Contents
Short Description
The Events module within MintHCM is a tool designed to facilitate event scheduling and management within an organization. It offers functionalities to create, track, and organize various events efficiently.
Overview
This module is integral for handling event-related activities. It offers a comprehensive set of features to create, manage, and oversee events within an organization. Beyond scheduling, it records vital event specifics like start and end dates, duration, budget allocations, and location details. Users can assign responsibility, associate venues, manage delegate selection, and even send event invitations using predefined templates
Fields
The Events module comprises several standard fields, each serving a specific purpose in capturing and organizing Event-related information. Here is a detailed explanation of each field:
Name | A distinctive title for the event, serving as a primary identifier across the system's interface. | |
Start Date | Scheduled date and time when the event begins. | |
End Date | Expected completion date of the event. This field fills up automatically if 'Start Date' and 'Duration' fields are filled prior to this field. After that it can still be modified and it'll alter 'Duration' field accordingly to it's value. | |
Duration | Time span allocated for the event. This field fills up automatically if 'Start' and 'End Date' fields are filled prior to this field. After that it can still be modified and it'll alter 'End Date' field accordingly to it's value. | |
Locations | Establishes a relationship with the Locations module, linking the event to a specific venue or space where it will occur. | |
Budget | Specifies the allocated budget or financial resources assigned to the event for cost management and control. | |
Email Invite Template | Relationship to email templates within the system, enabling the selection of specific templates for event invitations. | |
Accept and Decline Redirect URLs | URL to redirect invitees who accept or decline the event invitation. | |
Description | Allows users to provide additional context or details related to this particular event they are scheduling. It can include any information that seem relevant to this particular event. | |
Assigned to | Assigns responsibility to a specific user or team within the organization for overseeing the event. It ensures clear ownership and accountability for each event record. |
Note: Fields marked with an asterisk on the form are required. Saving the record without providing input to them beforehand won't be possible.
FAQ
- Are event records visible on the calendar module and dashlet?
- Yes, event records are visible and integrated into both the Calendar module and the Calendar dashlet. When events are created within the Events module, they automatically populate the system's calendar.
- Can I change event details directly from the calendar view?
- Yes, it is possibble to edit the time frames of the scheduled event by clicking and dragging it across the calendar grid.
- Can I customize email invites for events?
- Yes. Please refer to Email Templates module for more details.
Custom Actions
Processes
Related Processes
Process | Short Description |
---|---|
Calendar | It is a functionality that allows the user to manage and track time in terms of meetings, working times, calls, holidays. |
Time Management | The process of planning the time spent on various activities, which aims to increase the efficiency of the time used |
Related Process Steps
Related Features
Affected by
Initiating
Related Integrations
Structure
Fields
Name | Type | Required | Validations | Visible | Editable |
---|---|---|---|---|---|
Accept Redirect URL | url | No | Yes | Yes | |
Activity Status | enum | No | Yes | Yes | |
Assigned to | relate | No | Yes | Yes | |
Budget | currency | No | Yes | Yes | |
Created By | relate | No | Yes | No | |
Date Created | datetime | No | Yes | No | |
Date Modified | datetime | No | Yes | No | |
Decline Redirect URL | url | No | Yes | Yes | |
Description | text | No | Yes | Yes | |
Duration | enum | No | Yes | Yes | |
Email Invite Template | enum | No | Yes | Yes | |
End Date | datetimecombo | No | Yes | Yes | |
LBL_RESPONSE_LINK | varchar | No | Yes | Yes | |
LBL_RESPONSE_LINK_DECLINED | varchar | No | Yes | Yes | |
Locations | relate | No | Yes | Yes | |
Modified By Name | relate | No | Yes | No | |
Name | name | Yes | Yes | Yes | |
Start Date | datetimecombo | Yes | Yes | Yes | |
hours | int | Yes | Yes | Yes | |
minutes | int | No | Yes | Yes |
Relationships
Laft | Type | Right | Short Description | Relationship |
---|---|---|---|---|
Users | one-to-many | Events | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - FP_events |
Users | one-to-many | Events | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - FP_events |
Users | one-to-many | Events | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - FP_events |