Best Of

I want to propose an alternative solution that avoids the need to implement a custom OScript module, which you then have to deploy and maintain on all servers.

If you have the Module Suite, creating workflow dashboards is quite simple. You can have your "My Assignments" section (or "My Workflows," if you prefer) divided by type of flow, or even a generic dashboard if you want.

Additionally, you can add analytics and charts that help with monitoring.

You have building blocks that support the creation of these dashboards in WYSIWYG mode, allowing you to customize them as you prefer with the information you need.

In your specific case, you can customize the "My Assignments" grid with the information/columns you require using the GRID widget (which is part of the Module Suite), adding actions you find useful for individual or bulk assignments.

Moreover, the component already offers out-of-the-box features such as filtering results, grouping them, sorting columns, and exporting to Excel or PDF.

As I mentioned, you do this once on one server, and that's it—you don't have to deploy it on all other servers.

I will show you other examples just to help you understand the kind of results you can achieve:

Do you have the Module Suite?

With it, I've implemented a custom action that shows a sidebar with the email preview and the list of attachments. It's simple, quick to do, and moreover, you can reuse it for any project by attaching the action to the email subtype.

This way, you can have the preview in the smart UI without having to download it (which the Smart view forces you to do if you click on the email object).

Additionally, you have all the information in the same view without having to load new pages.

See here:

Hello Hugh,

From what I understood, you have an existing Smart UI extension (let's call it hugh 😉) and want to add a new command in there, but it's not working. The command never shows.

I'm not sure what's wrong, but for a command to actually show somewhere, you have to do a few steps:

• Create your command code (copy from SDK or make your own)
  • This means ****.command.js, which extends CommandModel
  • Plus a ****.nodestable.toolitems.js file, (which you pass to the nodestable widget using hugh.extensions.json later)

//open.classic.nodestable.toolitems.js
define(function () {
  'use strict';


  return {
    // "otherToolbar" here stands for one of the nodetables toolbars. 
    // There's also an "inlineActionbar", which shows when you mouse over a row
    otherToolbar: [ 
      {
        signature: 'OpenClassicCustom', // Must be same as the command signature
        name: 'Open Classic Page'
      }
    ]
  };


});

• Add the two .js files mentioned above into your src/bundles/hugh-all.js

// Placeholder for the build target file; the name must be the same,
// include public modules from this component


define([
  'hugh/commands/open.classic/open.classic.command',
  'hugh/commands/open.classic/open.classic.nodestable.toolitems'
], {});


require([
  'require',
  'css'
], function (require, css) {


  // Load the bundle-specific stylesheet
  css.styleLoad(require, 'hugh/bundles/hugh-all');
});

• Add the files into your src/hugh-extensions.json

{
  "csui/models/server.module/server.module.collection": {
    "modules": {
      "hugh": {
        "version": "1.0"
      }
    }
  },
  "csui/utils/commands": {
    "extensions": {
      "hugh": [
        "mps/commands/open.classic/open.classic.command"
      ]
    }
  },
  "csui/widgets/nodestable/toolbaritems": {
    "extensions": {
      "hugh": [
        "mps/commands/open.classic/open.classic.nodestable.toolitems"
      ]
    }
  }
}

• run grunt and copy the out-release contents into your OTCS/support/hugh folder on the CS location
• The command should now be showing inside the nodetable's top header (after you select an object using the checkbox in the leftmost column)

Can you check you got all these steps?

Other useful information:

• The open.classic.command has no enabled method, because it "inherits" it from CommandModel
• 'open.classic.command' extends 'csui/utils/commands/open.classic.page' which extends 'csui/models/command' which has the default enabled implementation hidden inside.
• It's actually possible to test and develop commands using the local server in the extension, but it takes some test/index.html setup

I've ran out of time, but I hope you have good luck with solving your problem.

I remember how happy I was when I finally managed to get the open.classic.command working for the first time 😅