Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Advanced warning
Robert_Davies_(unlondonadmin_-_(deleted))
Hi.Does opentext provide any advanced warning to developers about area's of functionality that are going to change in the product and might affect developers?For example: I am about to implement a module to allow developers to have "skeleton folders" that can be used as a basis for creating a new users personal workspace.The only way I can see of doing this at the moment is to overrider the $LLIAPI.AdminPkg.UserCreated handler, and modify the "create user" html form to allow choosing templates.Neither of these is an upgradable modification as far as I can see. Clearly with 8.1 and who knows what else hanging in the wings I am worried that I am going to have problems.How does OTC educate developers about things that will change in future releases?And in the context of my particular problem is there a way to do this modification in a more upgradable fashion?Best regards/matt.
Find more posts tagged with
Comments
Simone_Oettinger_(SOettinger_(Delete)_177592)
Hi Matt,You are probably not going to like my answer... The only customizations to Livelink currently supported are the ones described in the Livelink Module Development Guide. In this case, by "supported" I mean documented and guranteed not to change without notice. This may exclude some of the customizations you are trying to do. We are always looking for better ways to support common customizations, so keeping the dialog open with Open Text to let us know what you are doing is very important. The more customers have a need for a certain feature, the most likely it is that it will be added to the product.To find out about future releases, contact your technical sales guy, and/or the Livelink Product Managers (I am the Product Manager for the Livelink SDK).Best wishes,Simone
David_Forbes_(dforbes_-_(deleted))
Being part of a LL beta program might ease our angst, regarding the evolution of LL. It also might help identify our exposure for both custom modules and LAPI based apps.David
Robert_Davies_(unlondonadmin_-_(deleted))
I think David has an excellent regarding beta program.Given that almost everything you want to do in Livelink ends up being a customization (and given that so many customizations fall outside of the "supported upgrade" path) it would seem that some kind of developer early access/beta program would be essential.So how about it?Best regards/matt.
Simone_Oettinger_(SOettinger_(Delete)_177592)
Simone here agrees whole-heartedly. We want very much to have that in place, but we are still working on infrastructure. Hang in there...Simone
Sjaak_van_den_Akker_(originuser2_-_(deleted))
Besides the Beta-versions it would also be very wise to publish as soon as possible a list with all possible new funtionalities and changes which are being worked on for future releases. These lists could be updated during the whole implementation phase of any new release and has of course only an informational purpose.In order to structure the "whish" list of several organizations and to see how many people agree having a certain functionality it would also be nice to have a list with suggested funtionalities / features / bugs where anybody can add new ones or "sign in" for existing ones. This would give a better overview of what's happening in the world of LL users and developers. Maybe a new object type within the Knowledge base?Regards,Richard.
Robert_Davies_(unlondonadmin_-_(deleted))
Sun have quite a nice model where their database is online and users/developers can vote for the bugs/features they believe to be most important.I don't know exactly how this feeds into Sun's developer priorities but I guess this feedback must be useful to them in their future planning, and in spotting/fixing problems.Our biggest problem with OTC in this regard is that they are completely opaque to us. We have no idea what their priorities are, what they are developing, why they take the routes they take, and so on.We believe (general) announcements of future work/directions (with more detail under NDA), early access programs, bug parades etc.. are all things OTC *could* do to improve the lot of the Livelink developer community.What they actually do. Well we'll just have to wait and see...Best regards/matt.
