Search the Community
Showing results for tags 'date ranging'.
Found 2 results
We currently use the date range selection on a business process in order to limit what dates can be selected by the customer in the progressive capture. The date range is between 5 business days into the future to 180 days in the future. Customers should not be able to select any date prior to 5 business days and certainly not before the current day. We have however received a call where a customer was able to type the date in the field in the format dd-mm-yyyy, which then allows them to override the date selection and input any date they want. This effectively renders the date range selection tool useless and could cause issues with calls logged. I tried this myself and was able to repeat the result inputting any date I wanted if I used hyphens between the date numbers. It should be noted that it did not work when forward or back slashes were used in the same manner. Is there any way this can be deactivated so a customer cannot free type a date into the field using hyphens? I have attached a screen shot of the prog cap below to show how it is currently set up.
I am in the process of setting up a number of measures which do no have a Date Ranging criteria as I am attempt to capture the current 'state' of requests in an analyst's queue, i.e. number of open requests, new requests, on-hold etc. At the moment in order to start these running you have to set them to re-sample, but as there is no date ranging condition you will get x number of samples of the same value. When there is no date ranging criteria, can the system detect this and just sample the one current value? Cheers Martyn