Expiry logic in WeGuide

Modified on Fri, 21 Jan 2022 at 07:06 PM

  • To avoid the cluttering of a Participants To-Do list, you can set a specific engagement to expire after some time. It allows a user only to see the engagements and questionnaires that are most important and relevant. 


TABLE OF CONTENTS


How to set expiry while building your Program?

  • You can set the expiry while adding an engagement to the respective Program.
  • Users need to select appropriate GAP TYPE based on their preferences from Days, Hours, Minutes.
  • Here is an example:

  • You enter the expiry in the form of Days/Hours/ Minutes. The first box "When should it expire?" is a number  input, and "Gap Type" denotes the type of time metric used. EG "2" "Days", will expire the engagement 2 days after it first appears in a user's Actions page. 
  • End-Users can also view the expiry for their programs.
  • Here is an example:


An example 

  • For instance, the program expiry is set to 6 days in the image below. 
  • It depicts that the questionnaire shall be available in the respondents' dashboard for 6 days only.
  • After 6 days, respondents will no longer have access to the respective questionnaire, and it will be cleared from their queue. 



Limitations

  • You can only set the expiry time from the date/time of a scheduled engagement in WeGuide (e.g. +6 days from the scheduled date). 
  • You cannot set an engagement to expire at a specific date/time (e.g. Monday 11th 10:30 AM).


Don't forget to update this before saving the program as it is non-editable at a later stage.


Was the article missing some information or unclear? Please click on the thumbs down below and let us know how we can improve. Your feedback is always appreciated.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article