API Enhancements
Hi Team,
I would like to see the following API enhancements.
Comment one:
The course instance POST/PUT API currently allows us to provide a free-text location, but it does not allow us to assign an existing aXcelerate venue or room to the course instance using a venueID and roomID.
Could the course instance API be enhanced to support assigning an existing venue and room when creating or updating an instance?
Comment two:
When running the resourceLibrary report through either:
- POST /report/run
- POST /report/saved/run
the request fails if resources.updatecomments is included as a view field.
For example, when the field contains the text Annual review, the report returns:
"Can't cast String [Annual review] to a value of type [datetime]"
It appears that resources.updatecomments is being treated as a date/time field, although its stored value is text. Could this field be corrected so that it is returned as a string?
Comment Three: (This one would be a good quality of life change)
We would also like greater control over session data when creating a course instance using POST course/instance/.
Currently, aXcelerate automatically generates sessions based on the instance date range:
- For courses shorter than seven days, sessions are created for each day.
- For courses longer than seven days, sessions are created for the start and finish dates.
Could the API be enhanced to let us supply the complete session/complex-date structure when creating a course instance? Ideally, each session could include:
- Session date
- Start and finish times
- Venue and room
- Assigned trainers and their session times
- Other supported complex-date fields
We would also like the ability to update and delete individual sessions/complex dates after an instance has been created. The existing complex-date endpoint supports retrieving and creating sessions but does not appear to provide complete update and deletion functionality.
This would reduce follow-up API calls and manual corrections while giving API-created instances the same session structure as instances configured through the aXcelerate interface.
Thanks,
Myrthe
-
Official comment
Hi Myrthe,
Thank you for sharing your feedback on the ideas forum.
Comment 2 is actually a bug, so I appreciate you bringing it to our attention. Because it only occurs via the API, it had previously gone unnoticed. I’ve submitted a fix (reference: AX-27204), which will go through our standard release cycle and is scheduled for production release on 11 November.
Regarding your other two comments, we’ve taken note of them. We are likely to make improvements to our Course and Session APIs in the near future.
Thanks,
RodComment actions
Please sign in to leave a comment.
Comments
1 comment