{"id":655,"date":"2014-06-20T11:01:18","date_gmt":"2014-06-20T05:31:18","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=655"},"modified":"2014-06-20T11:01:18","modified_gmt":"2014-06-20T05:31:18","slug":"adding-timer-control-to-lead-entity-in-dynamics-crm-2013-spring-release","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2014\/06\/adding-timer-control-to-lead-entity-in-dynamics-crm-2013-spring-release\/","title":{"rendered":"Adding Timer Control to Lead Entity in Dynamics CRM 2013 Spring release"},"content":{"rendered":"

Introduction<\/span>:<\/strong><\/p>\n

A new concept of timer control has been introduced in CRM 2013 SP1 which can be used against date fields on customizable OOB entities or custom entities. This timer control has been designed to help users notice the nearing SLA or resolution times.<\/p>\n

For example, if your organization has certain process to be followed which needs to be\u00a0completed in specific time and be noticed by agents as well then timer control is a powerful tool which would help you keep tab on the process. We have illustrated this through a lead process and an example below:<\/p>\n

Working<\/span>:<\/strong><\/p>\n

This timer control gets date\/time field value as its time limit and from that time begins the timer countdown.\u00a0 You can place multiple timer control on a single form which you can assign to different date & time fields.<\/p>\n

How to use Timer control<\/span>:<\/strong><\/p>\n

Before using Timer control you must consider following points:<\/p>\n

1)\u00a0\u00a0\u00a0\u00a0\u00a0 First you need to plan on what are the fields you will be going to use.<\/p>\n

2)\u00a0\u00a0\u00a0\u00a0\u00a0 Then decide where to place the control on the form.<\/p>\n

3)\u00a0\u00a0\u00a0\u00a0\u00a0 When you add the control on the form, you will be required to select the associated date\/time field as well as configure the desired conditions.<\/p>\n

Note<\/span>:<\/em><\/strong><\/p>\n

1)\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0Timer control is currently available in CRM web application and CRM Outlook Client but is not available on CRM for tablets.<\/em><\/p>\n

2)\u00a0\u00a0\u00a0\u00a0\u00a0 The timer control refreshes on the<\/em>\u00a0OnChange<\/em>\u00a0form event, and also when the form is loaded.<\/em><\/p>\n

The following example describes how to use timer control on lead entity:<\/p>\n

Here, we need to set process and timer control on lead entity to monitor when the lead is first created in CRM, the first Email response should be sent to lead within specific minutes of time interval. If response is not sent, we should update the \u201cResponse status\u201d field and send email to owner to notify no response has been sent as yet to that lead.<\/p>\n

We have created fields called Response status, First response sent and First response by on lead entity. Response status is OptionSet with different options, First Response sent is a Boolean field and First response by is a date time field. We will associate First response by field with Timer control.<\/p>\n

Customize Timer Control<\/span>:<\/strong><\/p>\n

1)\u00a0\u00a0\u00a0\u00a0\u00a0 Customize lead entity –> drag timer control on lead entity as shown below:<\/p>\n

\"img1\"<\/a><\/p>\n

2)\u00a0\u00a0\u00a0\u00a0\u00a0 Then you need to set Timer Control properties as shown below:<\/p>\n

\"img2\"<\/a><\/p>\n

Here you need to\u00a0set the name and label of the timer control, a unique name should be specified.<\/p>\n

Then you need to\u00a0provide the data source for this timer.<\/p>\n

i. Specify Failure time field (Date time field), in our case it will be First Response by field (the Timer Control will start working once the first response by date time is set).<\/p>\n

    \n
  1. Then set the Success condition: Our success condition is when Response status is \u201cProcess Followed\u201d (if Response status is \u201cProcess Followed\u201d the timer will show status as \u201cSucceeded\u201d with green color).<\/li>\n<\/ol>\n
      \n
    1. Set warning condition: Our warning condition is when Response status is \u201cSend Response\u201d. (It means that if Response status is \u201cSend Response\u201d, timer control will show time in orange color), this color specifies that the time is about to expire.<\/li>\n<\/ol>\n
        \n
      1. Set Cancel condition: Our cancel condition is set Response status as Process not followed.<\/li>\n<\/ol>\n

        Once all the properties are set click on OK\u00a0and save the customization and publish them.<\/p>\n

        Working of timer control with example<\/span>:<\/strong><\/p>\n

        Here we have criteria, when a lead is first created in CRM, the phone response or email response should be sent to that lead within 10 minute time interval.<\/p>\n

        As explained above, we will be setting timer for response by time field. Here, we have created workflow to calculate First response by time, so our timer will be\u00a0set for that field. Also this workflow will wait for specific time and check for lead first response sent status and on that basis it will update Response status and email will be sent to owner of that lead. If no response is sent to the lead then that lead will get disqualified with Response status as \u201cProcess not followed\u201d and timer will be set as \u201cCancelled\u201d.<\/p>\n

        Workflow to Update Response status and send mail:<\/strong> This workflow will get executed on lead creation.<\/p>\n

        \"img3\"<\/a><\/p>\n

        Also we have another workflow to set First response sent on the lead as \u201cYes\u201d and Response status as \u201cProcess followed\u201d.<\/p>\n

        \"img4\"<\/a><\/p>\n

        Working of timer on lead<\/span>:<\/strong><\/p>\n

        1)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 As seen below, when First Response By date field\u00a0is not set, the timer is set with default status as \u201cNot Set\u201d.<\/p>\n

        \"img5\"<\/a><\/p>\n

        2)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 When first lead is created, its First Response by time is calculated with the time interval remaining to close the lead as shown below. Note that the First response sent is set to \u201cNo\u201d.<\/p>\n

        \"img6\"<\/a><\/p>\n

        3)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Once time elapses, workflow gets executed after timeout and it will set Response status as \u201cSend Response\u201d which is a\u00a0warning condition that\u00a0we have specified while setting timer control properties through customization. As you can see below, Response status is set as \u201cSend Response\u201d and timer\u00a0displays timing with orange color as warning.<\/p>\n

        \"img7\"<\/a><\/p>\n

        4)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If first response is not yet sent to lead and timer is about to reach the specific time its color get changed to red to highlight that no response has been sent to lead. As seen in below screenshot, it shows the timing in red color:<\/p>\n

        \"img8\"<\/a><\/p>\n

        5) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Once the time expires and First Response sent is No, the email is sent to the owner of the lead as shown below:<\/p>\n

        \"img9\"<\/a><\/p>\n

        6)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If First Response is sent and Response status is set to Compliance, the timer success condition gets fulfilled and timer status will be set as \u201cSucceeded\u201d as shown below:<\/p>\n

        \"img10\"<\/a><\/p>\n

        7) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0If you set status as the lead, Timer status will be set as \u201cCanceled\u201d as shown below:<\/p>\n

        \"img11\"<\/a><\/p>\n

        Hope this helps.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Introduction: A new concept of timer control has been introduced in CRM 2013 SP1 which can be used against date fields on customizable OOB entities or custom entities. This timer control has been designed to help users notice the nearing SLA or resolution times. For example, if your organization has certain process to be followed\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[11,21,22,24],"tags":[392,987,1106,1673,1715],"class_list":["post-655","post","type-post","status-publish","format-standard","hentry","category-controls","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-crm-2013","tag-lead-response","tag-microsoft-dynamics-crm","tag-status","tag-timer-control"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/655","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=655"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/655\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=655"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=655"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=655"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}