2 results found
We are currently reviewing this idea as this is an interesting concept and one we would like to explore further. If anyone would like to add their use case to this ticket it would be helpful to understand all scenarios.
An error occurred while saving the comment An error occurred while saving the commentJames Winterman commented
We are more than happy top contribute at Warwick. Just let us know when you want to discuss.
JamesJames Winterman shared this idea ·
59 votesbacklog · Keji Adedeji responded
We think this is a valuable idea and something we will wish to investigate in the future, however its not in our near term development focu so its on our longer term backlogJames Winterman supported this idea ·
An error occurred while saving the commentJames Winterman commented
This would make a huge difference if we could see who did what and when in a report. From a compliance perspective we need to know this information to prove lists are not being edited after the fact.
This is a basic functionality in any system so it seems odd that this has not been done before, or is not being treated as a priority.
Hi, R Bramley,
The API will help with Moodle and any other integrations, currently once something is archived it is invisible to anything you have integrated using the API. Without a very time consuming and manual process of adding individual URL's you lose last years lists. This way at roll over as long as your API call is setup correctly you will not have to do anything for historic lists to still be shown.