I have not blogged in a long time not since CollabSphere 2019. We have been relatively busy working on projects and on our newest versions of our Domino-based iPhora solutions. We started working on our iPhora platform over a decade ago with the focus of creating a platform that we would use to help companies automate their complex business processes.

Years ago I created few solutions for Domino using DSAPI: 1. remove last slash in URL served by Domino. 2. rewrite URL. 3. better control over 404/500 error pages.

LotusScript function to count how many embedded attachments are in a Rich Text Field. Function accepts two arguments, NotesDocument and RTI name as string. We came across a situation where we needed to be able to count how many attachments were in a rich text field in LotusScript. Scenario – We had a table with four tabbed rows. In each tab was a rich text field (which was hidden unless user clicked on tab). We needed a way of viewing how many attachments (if any) each rich text field was holding without clicking on each tab to see.

I recently had occasion to break ground on a new web project that uses a Notes runtime and has a web front end, and I figured it would be a perfect occasion to structure it in a way that is clean, portable, and, while it will run on Domino, doesn't have to use Tycho. I ended up coming up with a setup that I'm pretty happy with, and so I put up an example on GitHub for anyone else to use as a reference for similar cases.

Maybe I am thinking to complicated.. But I did not find an easier solution .. I had an interesting issue yesterday when adding multi timezone and date-time format to my backup solution, because I cannot store everything in Notes native TIMEDATES. There are some text logs involved, when storing information about a backup. To ensure I have an unified format, I decided to change the internal storage to UTC (in Notes terms: GMT).

When I started building the Flexible View Control, one of the driving forces was to significantly reduce the amount of back-end Domino views that would collect in my applications. I was just as guilty as anyone of creating a new view with the same selection formula and columns as an existing view.

A couple of weeks ago I explained that, even though the UI of DQL Explorer is a React app, the use of DQL is in agents. The two key agents, found within the NSF itself are runDQLExplain and runDQLQuery - the purpose of each should be apparent from the name. But the purpose of this blog post is to outline the interaction points between DQL Explorer and Domino.