A great place to post your ideas and vote on others so that you can let us know what is important to you.
Please take the time to register, and then share your detailed use case and how the proposed enhancements could provide value to your organisation.
We endeavour to provide an initial response to all ideas in a timely manner.
Our Experience Designers are always excited to talk to our customers about your experiences with the system. If you are keen to chat to them, you can easily book a short session with a member of the team right here.
I am proposing a column in the candidate grid for "date submitted" specifically for CTA form submissions. This will help us document form flow throughout the week (or month).
I know we now have the ability to filter by date, which is helpful, but when I'm sharing a group of registrants by exporting a weekly report for hiring managers, for example, it is difficult to guarantee I'm not accidentally exporting duplicates or leaving out some candidates.
I document the filters used each time, but pulling reports this way is more tedious. Having a "date submitted" column would provide another layer of data to ensure duplicate information is not being shared. It does need to be specific to a CTA so maybe this is a form field that could be added? I wouldn't want multiple dates for multiple CTAs within the field. Thanks for your consideration!
|
What is the business process you are trying to achieve?
Make reporting out on form fills easier |
Thanks for submitting this suggestion Kendall.
The use case you have described makes sense, and I understand the value that this could provide in terms of efficiency for your process.
There are some technical challenges in terms of potentially adding this column as a single candidate could have multiple CTA form submissions, and as a result, multiple submission dates. It is problematic to represent those multiple dates within a single row within the candidate grid without introducing duplicate / multiple rows per candidate.
As a result of the above, we don't have any immediate plans to add this column, but I do note the use case for future consideration.
--
Steve Oxley
Product Manager