Be able to have a single field that captures a date range - Currently we can only setup 2 different static date fields for a planned start date and planned end date of a particular task but would like to have a single field that allows a date range to be selected for how long a task may take. Example would be that we have to perform 5 days of Operator training at some point once the machine is delivered - our Sales and Sales Support team want to be able to see what that date range of that onsite training is going to be. In addition, we would like to setup alerts / email notifications to be automatically sent based on a date condition instead of someone having to manually trigger it. Example would be to send an email alert once a date is reached or when a date is nearing. Example is an email alert to go to our Training coordination team within say 4 weeks of the estimated delivery date so they can plan the work.
Daniel Matthews
| How often would this idea be used? | Daily |
| How much time would you save when the idea is implemented? | It would save hours of work |
| How many people at your company would benefit from this idea? | Most people (25 + ) |
|
What problem is your idea trying to solve?
Machine deliveries incorporate nearly a dozen different departments across our dealership and the ability for all areas to see and access COTI data or be notified to upcoming work is critical. It is not feasible to expect team members living in an application to monitor what they need to do. We need to proactively be able to alert different teams and give them the right type of data to execute a task/checklist. Ie book travel and training for a date range |
|
That's perfect David!
We're working on replacing the TO and FROM date fields with a single field that captures the range. Here's an example of the concept:
David it was the Product Consultants that requested us to put this idea in as we had already gone through this and raised a Support ticket to try and configure alerts in this way.
Its worth noting that setting up additional fields to trigger logic for an alert isn't an effective solution - we would end up with dozens of fields requiring manual maintenance.
This idea is to challenge Texada to revise how COTI alerts are triggered as setting up additional fields and manually having to change the date or status of fields to trigger alerts is not a viable solution.
Today, COTI can be configured to send a notification when a date in a specified field is the current date. An alternative solution would be for a separate field to capture "4 weeks prior to estimated delivery date" and trigger the notification based off of that field.
You could speak to your Product Consultant on how this might get set up for you and possible automations around that.