{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":14553,"path":"field-service-management/create-agent-calendar-event-config.md","title":"Create an event configuration","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create an event configuration\n\nCreate event configurations to define and manage event types for the team calendar.\n\n## Before you begin\n\nThe schedule entry uses the Schedule Span \\[cmn\\_schedule\\_span\\] table to store different types of events.\n\nThe following types of schedule entries for event type configurations are available by default:\n\n-   Event — Appointment\n-   Event — Excluded\n-   Event — Meeting\n-   Event — Phone\n-   Event — Time Off\n-   Event — Other\n\nThese configurations are inactive by default. You can activate a configuration by navigating to **Agent Schedule** &gt; **Event Configuration**, selecting an event type configuration, and setting the **Active** field to **true** for one or more event configuration types you would like to activate. Each configuration displays as a separate event type on the team calendar.\n\nRole required: agent\\_schedule\\_admin\n\n## Procedure\n\n1.  Navigate to **Agent Schedule** &gt; **Event Configuration** and perform one of the following actions.\n\n<table id=\"choicetable_v4z_cfp_gfb\"><thead><tr><th align=\"left\" id=\"d155102e123\">\n\nOption\n\n</th><th align=\"left\" id=\"d155102e126\">\n\nDescription\n\n</th></tr></thead><tbody><tr><td id=\"d155102e132\">\n\n**Create a configuration from an existing event configuration**\n\n</td><td>\n\n1.  Select the desired configuration.\n2.  Right-click the form header and click **Insert and Stay**.\n\nA copy of the selected event type configuration is created.\n\n</td></tr><tr><td id=\"d155102e155\">\n\n**Create a new event configuration**\n\n</td><td>\n\nClick **New**.\n\n</td></tr></tbody>\n</table>2.  Fill in the fields on the Event Configuration form, as necessary.\n\n<table id=\"table_czw_ftc_nr\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nA descriptive name for this configuration.\n\n</td></tr><tr><td>\n\nConfig Label\n\n</td><td>\n\nName displayed for this event in the agent calendar.\n\n</td></tr><tr><td>\n\nColor theme\n\n</td><td>\n\nColor used to display this type of schedule on the agent calendar.\n\n</td></tr><tr><td class=\"sub-head\" colspan=\"2\" align=\"center\">\n\nSetup\n\n</td></tr><tr><td>\n\nSetup\n\n</td><td>\n\nSetup method for this configuration.-   **Simple:** use condition builder to set up this configuration.\n-   **Scripted:** use advanced scripts to set up this configuration.\n\n\n</td></tr><tr><td>\n\nTable\n\n</td><td>\n\nThe table where the tasks for this type of configuration are stored.\n\n</td></tr><tr><td>\n\nFilter\n\n</td><td>\n\nUse condition builder to create the desired conditions for the selected task type. For example, the event configuration for Case Tasks includes a filter on the task **State** field to display only those tasks that are open.\n\n</td></tr><tr><td>\n\nUser Field\n\n</td><td>\n\nA field from the **Table** that provides the user assigned to the task. For example, the event configuration for Case Tasks uses the **Assigned To** field from the Task table \\[sn\\_customerservice\\_task\\]. When a case task is assigned, it appears on the agent calendar for the user selected in this field.\n\n</td></tr><tr><td>\n\nEvent type\n\n</td><td>\n\nType of schedule entry.\n\n</td></tr><tr><td>\n\nDisplay Field\n\n</td><td>\n\nA field from the **Table** that provides the information to be displayed for this event type on the agent calendar.For example, the event configuration for Case Tasks uses the **Subject** field from the Task table \\[sn\\_customerservice\\_task\\]. When a case task is assigned, the subject of the task appears on the agent calendar.\n\n</td></tr><tr><td>\n\nStart Date Field\n\n</td><td>\n\nA field from **Table** that provides the start date for the task. For example, the event configuration for Case Tasks uses the **Expected start** field from the Task table \\[sn\\_customerservice\\_task\\]. When a case task is assigned, it appears on the agent calendar starting on the date and time specified in this field. The **Expected start** field must contain a value for the event to appear in Workforce. If the field is empty, the event will not be displayed.\n\n</td></tr><tr><td>\n\nEnd Date Field\n\n</td><td>\n\nA field from the **Table** that provides the end date for the task. For example, the event configuration for Case Tasks uses the **Due date** field from the Task table \\[sn\\_customerservice\\_task\\]. When a case task is assigned, it appears on the agent calendar ending on the date and time specified in this field. The **Due date** field must contain a value for the event to appear in Workforce. If the field is empty, the event will not be displayed.\n\n**Note:** Because the agent schedule administrator can select any fields from the **Task Table** for the **Start Date Field** and the **End Date Field**, it is possible that the end date may be earlier than the start date. In this event, the task is displayed on the agent calendar between the two points in time.\n\n</td></tr><tr><td>\n\nScript\n\n</td><td>\n\nUse advanced scripts to create the event configuration.**Note:** This field is available when the **Scripted** value is selected from the **Setup** field.\n\n</td></tr></tbody>\n</table>3.  Perform one of the following actions:\n\n    -   If you created the configuration from an existing configuration, click **Update**.\n    -   If you created a new configuration, click **Submit**.\n\n"}}