We have some course in another system and instead of creating manually the course in both apps, we would like to create them in our existing solution and automatically create them in Absorb.
Bumping this after 2+ years as this would be hugely helpful for our use case of having to manually sync course product data between multiple systems. Even the ability to clone an existing course via API rather than fully create a new one would be massively beneficial.
Our need for this feature is fairly lightweight. We have a number of documents that our team needs to review periodically and when they are updated and acknowledge that they have done so. A perfect feature would be a document acknowledgment module. We had intended to use Absorb for this purpose, however, because we cannot create and update the course automatically we are unable to do so. We have hundreds to thousands of these that are critical to our business, so solutions requiring manual entry and update won't scale sufficiently for our use. Unfortunately this is one of our primary needs for absorb and we have been unable to adopt absorb for our primary need.
Thank you for submitting and voting on this idea! We really appreciate your input and engagement. I'd love to learn more about your specific use cases for this idea to better understand how we can meet your needs. Feel free to share any additional details or insights!
Bumping this after 2+ years as this would be hugely helpful for our use case of having to manually sync course product data between multiple systems. Even the ability to clone an existing course via API rather than fully create a new one would be massively beneficial.
Our need for this feature is fairly lightweight. We have a number of documents that our team needs to review periodically and when they are updated and acknowledge that they have done so. A perfect feature would be a document acknowledgment module. We had intended to use Absorb for this purpose, however, because we cannot create and update the course automatically we are unable to do so. We have hundreds to thousands of these that are critical to our business, so solutions requiring manual entry and update won't scale sufficiently for our use. Unfortunately this is one of our primary needs for absorb and we have been unable to adopt absorb for our primary need.
Thank you for submitting and voting on this idea! We really appreciate your input and engagement. I'd love to learn more about your specific use cases for this idea to better understand how we can meet your needs. Feel free to share any additional details or insights!