Best Of

@Steve Hulker If you want to implement robust attribute validation natively within Smart View without re-architecting your step layouts or relying on legacy classic JavaScript, Answer Modules' Module Suite is the ideal solution. Using its Scripting Engine and Smart View extensions, you can easily intercept step processing (such as the Start or Submit action) to execute custom validation logic—perfect for verifying that your initial date precedes all subsequent date fields before allowing the workflow to advance. This cleanly halts invalid submissions and displays clear, user-friendly validation alerts directly in the Smart View UI, completely bypassing the need for WebReport UI overlays, custom form templates, or complex post-step workaround triggers.

A lot of us have put code for EventScripts in this KB, some as starter work, more or less like Hello World. However, as OT has matured, many companies now deploy OT CS in the cloud, either as Kubernetes or in systems where the customer has no access to the internals. So you will face pushback after you develop code to run/install it on the servers.WR and AM address all of these more effectively, so they can pass under the radar. I would suggest you meet with the AM folks; they are known not to disappoint a prospective customer.The work that you want to do is basically less than 10 mins of validation work with the AM product or less.

You would need to create the OScript in a custom module as orphans of the appropriate WF Event Script and then you can set that script to run when at the appropriate step. If you dont have OScript developers, and the CS IDE, available to you, then you would need either OT or another firm / developer to create the appropriate code for you.

For some background on the Event Scripts, there is a good article from @Reiner Merz - https://www.linkedin.com/pulse/content-server-workflow-customization-new-event-trigger-reiner-merz-ygewf/

@Steve Hulker

Shame you're putting a line through AnswerModules - it's probably your best bet here and for any future Smart View requirements you may have….

As you're finding, the options for extending things in the Classic View simply don't "port across" to Smart View.

I'll zero in on your statement

I would prefer to have the attribute validation process without a form template or follow on web report actions and just done in the workflow step currently processing.

I've deliberately called out the bolded. Based on that you may want to look at event scripts in Content Server. These can be associated with a step (e.g. user step) in a workflow and can be set to execute when the step "becomes ready", "before send on" or "step is done". They can also be associated with "workflow initiated", "workflow completed", "…stopped", "….resumed", "…deleted", "…archived".

You might want to look at those - or as was mentioned earlier, a webreport step to do the validation. Either way, you'll likely need to then route based on the validation outcome.

PS - Event Scripts require knowledge of OpenText's proprietary Oscript language and access to the SDK (potentially additional license, or working with a partner to have them deliver)

Without AnswerModules or custom Smart View development - doing the validation at the start step itself and/or remaining in Smart View may prove a hurdle.

I incorrectly used WR Snippet to mean that it is just a few lines of code, not an elaborate setup like logic and other things when you do write a WR. See an example attached here as a Word document because I dont trust the editor :)

"WR interactive in SmartView" can be accessed via the following link: https://knowledge.opentext.com/knowledge/llisapi.dll/properties/83371290

@GMUU if you want to customize your extended ECM I recommend you to use https://www.answermodules.com/smart-pages it's probably the best way to manage customizations in the long term and it also includes low-code tools to do it.