nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smart View validation on attributes in a workflow start or user step.

Steve Hulker

I've been looking for a solution to attribute validation in a smart view workflow (Multiple date fields that require 1st date to be less than any other date field) when the workflow step is processed (Start button pressed).

I have this working with form template/ custom views with embedded JavaScript in classic views, but smart view do not seem to trigger the JavaScript.

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.

This KB article (KB0567773 - Content Server - Validating Workflow Attribute values when entered by a user) describes the preferred solution for additional logic within the attribute processing, but does not seems to be available.

We also have tried GCI Powertools using XSL templates with the embedded JavaScript in a webreport, but requires regenerating the entire workflow step, which is something we do not with to do.

Any ideas are appreciated.

Find more posts tagged with

xECM

WebReport

SmartView

Comments

appuq

Classic UI Dynamic JS was killed when OT adopted SmartUI.However, in a not-so-elegant solution, you can use embedded WR snippets; for e.g if the user forgot to add an attachment, when the user presses a button, the call will go to a WR, and the WR will say you forgot to add a file.

On the SmartUI, if you have the budget, install AnswerModules which will provide every which way you want the user experience not to suffer; if not, the SmartUI SDK is albeit, written to target advanced JS development.SmartUI SDK hasn't caught on in the OT field; very few people know how to modify it.AnswerModules is one where they inject their own JS framework for this.There are others GCI may be one I am not sure

Christie Dunn

Thank you for your comment appuq. Could you give an example of what you mean by embedding WebReport snippets? Where would the WR snippets be added?

appuq

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

appuq

Another easier way advocated by people in the field, like Mathew Barben, is to put a skin of SmartUI on classic UI so the managers/end users can be tricked into thinking they are on SmartUI. some examples

https://medium.com/driver-lane/you-might-not-need-webreports-so-when-should-you-use-webreports-8d07342215e2

We are all very old, experienced OTCS CS people, so if this is an option, I would do that as well

Steve Hulker

Thank you for the information. Could MetaData Validation Rules be applied and used as custom attributes with validation in a smart view workflow? Found this post that provided it as a possible option:

https://community.opentext.com/portfolio/content-manager/w/tips/47131/knowledge-document-metadata-validation-rule-that-can-connect-two-date-fields-without-relying-on-a-specific-value

appuq

OpenText started somewhere in 1995 or so at this time, it has bought almost all its competitors. What I showed with WR and others is its flagship product called Livelink, written in Oscript. The link you show is OT Content Manager, which is likely a different product.

FYI, Livelink is now called OT Content Server or an XECM flavor of anything :)

AFAIK, if you want to stay within the realm of SmartView and do WF very nicely, you have to buy Answer Modules

David Henshaw

@Steve - the link in your post is for Content Manager, different product to Content Management (aka Content Server/Suite/Extended ECM).

Question - are you working with a new workflow or pre-existing here..? And do you need to support both Classic and Smart View, or just Smart?

Steve Hulker

Thank you for the insight. We are using OpenText Content Server v23.4 and updating to Content Manager (xECM) v25.4. This is for current workflows that we are converting to Smart View. The guidance is pretty limited on what is available to use from the product documents and have found more info from these forums and Gen.AI prompts unfortunately. We do not have the budget for answer modules but have GCI Powertools and have tried XSL with embedded javascript along with form templates that worked in classic view but not so much with Smart View. Would love for multiple validation (2 or 3 dates with each greater than the others) to be available as an extension to the workflow attributes without extra coding or SDK module updates.

Greg Griffiths

The KB article KB0567773, is just a record that someone has requested that functionality, as it shows that the request is still open it has yet to be included in the Product.

Steve Hulker

Thank you. Was also going to submit an additional feature request but continuing to look for alternatives.

David Henshaw

@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.

Steve Hulker

Thank you for the guidance. We had a call with tech support on using the Event scripts on the "workflow initiated" event on the overall workflow, but they were unsure of where to put the OScript code. They seemed to fall back to we needed to use the workflow api to add scripts for the validation code and referred us to the forums or Professional Services for additional help.

Greg Griffiths

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/

David Henshaw

Steve - to be fair here, OT Support handle queries etc and triage of the "out-of-box" product. They're not specialists in extending/developing the platform - and in my experiences working with/in L1 support teams, people aren't around long enough to develop those skills.

Being referred here to OT PS is what I'd have expected - but you do have other options, partners like Fastman have strong development skills and products augmenting the core OT platform. Full disclosure, I'm with Fastman and look after that capability.

I'd also say here that I mentioned Event Scripts as a fallback given your comment re lack of budget for AnswerModules. Without having a discussion, my suspicion based on the information you've provided here is that AnswerModules will give your more mileage and a better user experience. Fastman are also an AnswerModules' partner.

Should you want to talk further, reach out via our website.

AbelJM

@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.