Waiting for #OTEW: a sneak peek into ModuleSuite 2.0

Coding without coding

In less than ten days we will be boarding a plane heading to Las Vegas, NV, to attend OpenText Enterprise World 2015, which we are proud to sponsor once again. We will have a chance to meet some of the world's most knowleadgeable minds in the EIM field, and really wanted something new to show.

Today we are excited to share a preview of one the new tools we have been working on lately, that will be part of the new ModuleSuite 2.0.

To introduce you to the topic, I will take the lead from various requests I've come across recently on the AppWorks Developer community.

Here is one that caught my attention (link. The main focus is the following: "Is there a way to request category information when querying subnodes? Or do you have to make an additional calls for the category information."

The reason of my interest lays in the fact that the most efficient answer to this question (and to many other similar ones I've heard that concerned integrating with Content Server through REST APIs) is to create one's own request handler to address the specific need.

The problem with this solution is that putting it in practice is not practical at all, as it involves low-level OScript coding in Content Server, which requires some very specific skills.

In the past I have already discussed solutions to this sort of problems by the means of using Content Script. An objection to this could be: "Ok, it's neat, but we are still talking about writing scripts..". What I want to show you today is how easy this can become in the very next future.

I am proud to introduce you to the brand new Visual Editor for Content Script.

This new ground-breaking tool is exactly what it seems: a drag&drop, visual editor to manage Content Script objects.
But let me show you in practice how the above problem can be solved: without having to see any actual coding.

Hope you enjoy, and be prepared for the next updates!