Very gerneral and basic question

Hi All,

I read all the documentation (short of what is in the zip files) about Smart UI. I did not find out how you can develop the Smart UI and then deploy it elsewhere. If you have a test environment, is it just a question of copying the files to the production evironment or are any of the "parts" inside of content server and can be exported/imported with Transport or XML Import/Export? Is that supported? Sorry for the admittedly super basic question!

Tammy

Find more posts tagged with

Comments

Ian_Whitfield

Hi Tammy,

The output of the SDK build process comprises the html/javascript/css application bundles which are usually added to the support directory and an oscript module which registers the bundle with the oscript CSUI Extensions registry. If you have a custom oscript module already then you just need to orphan CSUI::CsuiRoot::Extension and you shouldn't need the build oscript component as far as I'm aware.

The support files and the ospace can be migrated between instances in the usual way. You can check at /app/config to make sure your bundles are registered with the Smart UI.

Usually the only situation where there is additional CS content is if you have created a custom widget that is registered with the Perspective Manager and you have created custom perspectives for a system which include your widget. If this is the case then you should just be able to use Transport to move the Perspectives and any associated content you have for your widget. Transport support for this was added in the 2016-12 update.

Regards
Ian

Tammy_Jakubowski

Thanks Ian. That is EXACTLY what I needed to know.

Again, sorry for asking such a painful newbie question.

;-)

Cheers,

Tammy Jakubowski

Tammy_Jakubowski

Thanks Ian. That is EXACTLY what I needed to know.

Again, sorry for asking such a painful newbie question.

;-)

Cheers,

Tammy Jakubowski

HFCDev

For the case where you're trying to add Smart UI to an existing module (i.e. one that already has your REST extensions), what needs to go into CSUI::Extension (you actually wrote CSUI::CSUIroot::Extension, but that's the one I found)? There's the obvious fEnabled feature but it has module prefix code as well. I imagine that needs to be overridden. Anything else I'm missing?

-Hugh

Ferdinand Prantl

The easiest way, how to see a working sample is:

Inspecting the OScript sources in the Greetings sample project.
Generating a new project using the csui-extension generator and inspecting the generated OScript sources.

This is the minimum object registering a CS UI extension:

package YOUROSPACEpublic object YourExtension inherits CSUI::Extension    override Boolean fEnabled = TRUE    override String  fModulePrefix = 'yourprefix'end

If you do not want to deploy the extension files directly to your "/support/module" directory, you can put them to a subdirectory there, for example to "/support/module/app" by adding the following feature:

    override String  fExtensionPathPrefix = 'app/'

You can read the comments in the CSUI::Extension object, if they were not stripped; I am not sure, what CS 16 does about them.