How Can we modify Survey expiration Date?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2015 02:05 AM
Hi
DO anyone have any idea about how the Survey expiration Date is set.
In our scenario, we are running the surveys via trigger condition and the period is schedule to 'No Limit' as suggested.
But when a survey instance is created the Expiration Date is also set to the created Date.
I never find a Business Rule which Calculates and sets the expiration date. We need to modify it to 30 Days. All I get is the new AssessmentUtils() called in a business rule but I did not find setting Expiration Date Logic. Do I need to create a new BR on insert of new record to accomplish this?
Please suggest any ideas.
Thanks
Deepak

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2015 02:43 AM
HI Deepak,
Survey expiration date: is based on schedule period
http://wiki.servicenow.com/index.php?title=Survey_Definitions#Schedule_Periods
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2015 03:34 AM
Hi Pradeep,
I had gone through his article. This explains how survey frequency can be managed via schedule periods.
But in our case the surveys are handled via trigger conditions.
For a temporary solution, I created a new BR on insertion of Assessment Instance Record and setting the expiration date to 30 days after creation date.
Regards
Deepak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2015 10:38 AM
Hi Deepak,
The expiration of each survey instance is determined by the Assessment Duration on the survey definition -- you may need to modify the form to make that field visible.
Howard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2017 06:40 AM
I believe the Assessment Duration controls the Due Date, not the Expiration Date. We are using trigger conditions with a No Limit schedule and 14 day duration. The default behavior is to set the Expiration Date equal to the Created date and the due date is 14 days in future. The problem we've experiences is that the monthly "Cancel Expired Assessments" script can cancel a survey too soon. For example, if the Cancel script runs on 06/15/2017, a survey issued on 06/14/2017 is canceled because its Expiration date was 06/14/2017.
We are considering altering the Cancel script instead. Perhaps we will use the survey's Due Date, canceling any survey that is passed its due date if the schedule period is No Limit. I hate to go outside the box unless its warranted. Are we missing something? Other suggestions?