In this article, we run through some basic steps that could be done to shake out some basic errors in the Smart UI generator.
Today we want to expand on that work to also automate some builds of the widget. In the end, we will then have a system in place that will allow us to:
In this, we will be making changes to the repo and the pipeline which is going to trigger the existing pipeline. In some instances…
Recently a new version of the Smart UI SDK (21.2) however there breaking issues:
Now both articles detail some workarounds what I wanted to run through was how some basic steps could be taken to ensure that software doesn't get shipped to your customers in the first place.
In this article, we will not be deep-diving too much into the world of continuous integration / continuous delivery. But hopefully, give you enough information to perform the bare minimum that would have picked up some of the errors experienced in this release.
I have to admit, I have been avoiding this for a while. Every time I get myself psyched to look at building a Smart UI module I get frustrated by the gaps in the documentation, the workflow that seems at times to be janky. Compared to other similar addon mechanisms (like Microsoft SPfx ) this has some similarities, but the lack of a total end-to-end getting started tutorials means it can be a steep climb for newcomers.
So let's create a Smart UI module and then and deploy this to a server.
You are going to need some things for…
This is part of my series looking at why You may not need WebReports
You having your spiffing new Content Server and you now want to create a simple workflow where a user submits a document where it can be reviewed.
As the process relies upon the reviewer being able to view a document you want to ensure that a user attaches a document.
The many ways to solve a riddle so simple…
There are good ways and bad ways to approach this — but in my mind, there are three ways:
Opentext Content Server (OTCS) is a document/record management application — it comes with a bunch of practical functionality that makes getting off the ground with basic compliance pretty simple. It does the basic stuff right (opening documents, version management, auditing, and compliance). But once you get beyond the basic use cases where configuration does si where you need to do some customisation— which is why you are here today. In this series I am looking at one of those methods of customisation that has grown in popularity in the OTCS sphere — WebReports.
In the past, changes to the UI…
For a while, I have been playing in SharePoint land. While there, I have been making good use of Power Automate and Azure Logic Apps.
Primarily I have been using Azure Logic Apps as a means of integration and orchestration using it to overcome limitations of a customer-specific workflow engine as well as a means of integration with on-premise applications.
Whilst the environment does come with a bunch of pre-canned SharePoint actions and triggers there are times where you need to go beyond standard steps and make use of the SharePoint REST API.
One of those use cases is definitely…
Six months ago I put together a three-part (one, two, three) series on the difference between the Smart UI and the Classic UI. Well with the release of Content Server 16.2.8 over the weekend it was time to dust off the project and run some tests.
With the quarterly patches, there have been some changes to the layout of both the Classic UI and the Smart UI.
Classic UI selectors
await page.click('div#browseCoreDiv > table.browseTable > tbody > tr[data-tnode="Performance Test"] > td.browseItemName > a')
Smart UI selectors
await page.click('div.csui-table-cell-name-div > a[title="Performance Test"]');
I have been a convert to Typescript — it was introduced to me via Angular and now I am introducing it to my workflow in the Node.js world.
Recently I have been building a Node.JS project and deploying this through to an Azure Web App — Why Azure Web App, well I have an MSDN and I have some credit so I thought why not.
In this post, I am going to build a basic express application using TypeScript, we will build out a couple of controllers (with some basic auth), and then we will use Microsofts DevOps tools to…
This is the third in my series covering Content Server browse performance.
In Part 1 I examine the setup and tooling I will be using
In Part 2 I run through some of the elements of the tooling that I used to capture performance timings.
So where we are — tests created, code running and successfully executed so let's have a look. For the sake of speed, I will be looking at the end to end test results. That is, the total time taken to perform the following tests:
/nodes/2000in Smart UI)