Custom (weblingo) Pages in Smart UI

In the classic UI we make use of weblingo files to display html output. Can these weblingo pages be shown in the smart UI , for example inside a custom widget?

In the Smart UI SDK 16.0.3 there is a page example, which contains a file "hello.page.weblingo".

However when modifying this weblingo file, e.g. <body>TEST WEBLINGO OUTPUT</body> these changes are not reflected when opening samples/pages/hello/test/index.html

Is this because this is a mocked example?

Can you provide an example which connects to OTCS and retrieves object data (DataID, Name) and uses the weblingo to render this data?

Find more posts tagged with

Comments

Martin_Elsaesser

Regarding the SDK sample: The samples/pages/hello/test/index.html sample from the SDK in no way depends on that weblingo file, so there is no reason to expect any changes there would affect the output of the sample. The weblingo file should just be removed from the directory of the sample to aboid confusion.

Ian_Whitfield

I suppose the question is what do you want to show in the Smart UI and why. You could, for instance, create a custom widget and include an iFrame URL to a classic UI page if you wanted to embed a classic weblingo view.

If you have Content Intelligence/WebReports the HTML WebReport widget will allow you to do this without building the custom widget. You can just put the iFrame in the WebReport.

However, in general, the two UIs are designed to be separate and best practice is to use the development conventions of the Smart UI SDK to build a new view.

Regards
Ian

Alexander Kühn

Quoted Ian Whitfield on 02/01/2017 04:43 PM:

We usually use Weblingo in classic UI when the output should look completly different to what OTCS looks like, e.g. a custom Page designed according to the customer's corporate design or specific needs to show certain information (Metadata) on a certain position when the page is being printed. I will look into the idea with the iFrame URL in a widget, since in that case the effort to implement the same page (as in the classic UI) for the Smart UI seems to be low.

If you have Content Intelligence/WebReports the HTML WebReport widget will allow you to do this without building the custom widget. You can just put the iFrame in the WebReport.

The HTML WebReport is very useful, but not all our customers have a WebReports license. Which is the case for our current requirement.

However, in general, the two UIs are designed to be separate and best practice is to use the development conventions of the Smart UI SDK to build a new view.

I agree with the idea to stick to one UI. But when you open a LiveReport it opens in the classic UI. Will it be implemented in the future releases to show LiveReports in the SmartUI? Our customers prefer not to switch beetween the different UIs.

Regards
Ian

Ian_Whitfield

One other thing that is available as an option is to call a classic URL from your custom widget and override that page using ActiveView. ActiveView is included for free in CS16 and has a number of templates to get you started in customising common areas of the classic UI e.g. changing the appearance and surfacing custom data. Again, this is not ideal but can help bridge the gap while waiting for more native Smart UI functionality to be implemented.

There is still a lot of work to be done to implement all node types in the Smart UI. There are no plans to implement LiveReports in the Smart UI in the short term. At the moment the only way to get LiveReport data into the SmartUI is to using WebReports.

Regards
Ian

Ferdinand Prantl

On the contrary, the file "samples/pages/hello/hello.page.weblingo" does belong to the sample. It is the release versio of the HTML page to deploy on the server. The file "samples/pages/hello/test/index.html" is a page to develop the custom page content.

This example demonstrates, how to create a custom CS page using CS UI Widgets (building blocks of Smart UI). It does not demonstrate, how to create a widget or how to put a custom content on the Smart UI main page (/app).

Ferdinand Prantl

Could you write more about the scenario, which you are implementing, please?

If you look for something similar, like replacing an entire Classic UI page shown for a particular node type using a Custom View or a custom request handler, you could compare it to a custom perspective in Smart UI, which would show a full-page widget. So, you would use a widget in your case.

Showing a WebLingo output inside Smart UI is unusual, because Smart UI components are usually rendred by JavaScript (views) using data received by CS REST API (models). Separation of data and presentation layers is one of architecture cornerstones of Smart UI. For example, if you want to support LiveReports, you could write a widget showing a list of nodes, which depends on the REST API returning the LiveReport result. You would probably make it working similarly to the Favorites widget. I admit, that the LiveReport widget should be a part of CS OOTB, but I do not know, when or if it would be delivered by OpenText.

If you do not want to write UI + REST API the Smart UI way and you already have a CS request handler, which returns HTML content suitable for being placed into an iframe, you could create a simple iframe-widge for such purpose. The administrator would place it on landing page or other perspectives and set up the URL parameters. For example:

src/widgets/classic.content/classic.content.view.js:

  define(['csui/lib/marionette', 'csui/utils/url',    'csui/utils/contexts/factories/connector'  ], function (Marionette, Url, ConnectorFactory) {    var ClassicContentView = Marionette.ItemView.extend({      tagName: 'iframe',      attributes: function () {        var data = this.options.data || {},            connector = this.options.context.getObject(ConnectorFactory),            cgiUrl = new Url(node.connector.connection.url).getCgiScript(),            classicUrl = Url.appendQuery(cgiUrl, data.urlQuery);        return {          src: classicUrl        };      },      template: false    });    return ClassicContentView;  });

src/widgets/classic.content/classic.content.manifest.json:

  {    "$schema": "http://opentext.com/cs/json-schema/draft-04/schema#",    "title": "Classic UI Content",    "description": "Shows a content of a CS request handler serving HTML markup (Classic UI).",    "kind": "tile",    "schema": {      "type": "object",      "properties": {        "urlQuery": {          "title": "URL Query",          "description": "URL query part of the CS request handler URL",          "type": "string"        }      },      "required": ["urlQuery"]    }  }

Karthik_Raj_Govindarajan

How to call classic view from the smart UI widget

eLink User

Have a look at "samples/commands/open.classic" in the SDK, please.

Karthik_Raj_Govindarajan

Thanks for your reply.

can you please give the url for sdk?

Ferdinand Prantl

CS Smart UI SDK can be found at https://knowledge.opentext.com/go/65414087.

Karthik_Raj_Govindarajan

How to use that sdk to call classic view from smart UI widget

Alexander Kühn

Thanks Ferdinand for the classic.content widget example.

However this does not show up in the perspective manager.

I registered the .view and .json in the <module>-all.js:

    'dtcsuiext/widgets/hello/hello.view',
   'json!dtcsuiext/widgets/hello/hello.manifest.json',
   'dtcsuiext/widgets/classic.content/classic.content.view',
   'json!dtcsuiext/widgets/classic.content/classic.content.manifest.json',

as well as the widget container in the <module>-extensions.json:

"csui/models/widget/widget.collection": {
    "widgets": {
      "dtcsuiext": [
       "dtcsuiext/widgets/hello",
       "dtcsuiext/widgets/classic.content"

Then I compile the project, copy the release to my otcs /OTHOME/<modulename>/support as well as /OTHOME/support/<modulename> and restart OTCS.

However only the "hello" widget appears in the Perspective Manager.

As a workaround I replaced the hello widget files (.js and json) with the "classic.content" source code.

Is there more documentation about how to register custom widgets .view and JSON? Are the *.model.factory.js and *.model.js always required for widgets to load?

Karthik_Raj_Govindarajan

In our scenario we are having customized smart UI page .If we press any tile from the samrt UI page it should be direct to the classic view page not smart UI.How to achieve this?