Content Server is a document manager made up of modules, whose out-of-the-box functionality is very extensive and allows for a large number of business scenarios. However, requirements or needs can always arise that are not covered by the standard and therefore there is the dilemma of whether the chosen platform was a good choice.
There are several ways to extend the basic functionality of Content Server that can be adapted to a wide variety of scenarios. The different approaches will depend on the complexity of the requirement and this will determine the type of extension to be carried out. This blog entry seeks to expose the different means that are available and that we apply to our clients at Brait.
External developments
LoThird-party developers use the Content Server Rest API and its various modules to provide functionality and perform processing. These developments can range from small applications operated remotely to document service frameworks that turn the Content Server into a horizontal document manager for the entire company.
Developments in WebReport
WebReport is a tag-based language, as each tag represents a set of Oscript instructions, Content Server’s native language, which allows you to execute the most popular instructions. In addition, it allows you to insert JavaScript code, in combination with CSS and HTML.
Several highly requested features implemented using WebReports are:
- Advanced forms to add documentation.
- Reports related to documentation or workspaces.
- Mass processes.
- Processes based on events (WR Trigger).
- Processes based on scheduled executions.
- REST integration to obtain information from external systems.
- Implementation of REST services to consume from external systems.
- Add scripts as workflow steps to extend functionality and automate steps.
At Brait, we are experts in development exploiting the WebReports module and providing functionalities avoiding resorting to non-standard development frameworks.
By using WebReports, OpenText ensures continuity and compatibility of scripts written in its language throughout future updates.
Developing tags for WebReport using Oscript
The versatility of using WebReports is very wide, but certain actions can always arise that are not provided by the standard WebReport tags, and are necessary for business. If the functionality is very limited, it is possible to make customized labels that implement this function. The impact of carrying out these developments and introducing them into the system is very low, so they are agile solutions to complement the developments.
At Brait we have developers who can generate these functionalities and allow, for example, exposing functions not initially available in WebReport and thus expanding the potential of this module.
Deveopment of Oscript modules
When the number of changes to be made is high, and their impact on use is greater than usual, WebReports may not be enough to achieve the goal. In these cases, the development of a custom module enhances both front-end and back-end development (interface and server). These modules provide solutions to demanding business needs, allowing the implementation of complex processes, exposing advanced services or introducing changes in the user interface that provide access to new features.
A module developed to measure allows covering needs such as the following:
- Generation of advanced Jobs.
- Extension of the standard Rest API.
- Creation of new objects.
- Advanced integrations with external systems.
- Introduce events and actions natively, more efficient than WebReports.
- Execution of advanced functionalities in a simplified way for the user.
At Brait, we work generating new modules or giving support to already developed modules. Soon our first module will be available in the OpenText market place, which allows you to anonymize sensitive document content.
Extending the functionality of SmartView using Oscript modules and the SmartUI SDK
One possibility of module development includes extension of the user interface. With each release, OpenText increases the functionality and efficiency of the new SmartView interface. However, users may require buttons, reports, or widgets to be generated to facilitate operational control and facilitate user actions.
The limit is in the knowledge
At Brait, we always look for the simplest approach to meet business needs, however, we weigh all available options to provide the most economical and optimal approach for each solution. We avoid proposing the most complex solutions from the beginning and adapt the developments to the needs. Our goal is always to find a balance between versatility and functionality.
If you consider that there are functionalities that you would need to have in the Content Server and you have doubts about its viability or approach, do not hesitate to contact us! Our colleagues are experts in the analysis of needs and knowledge of the standard, detecting efficiently and in advance the needs that require specific developments.
