Question about tag shapes for validation in Workflows

[Rebecca Jackson]

I was wondering if it is possible to set up a workflow with a "Validation" status that runs the SHACL constraints specified by teamwork:tagShape in the workflow definition?

From the docs:
If teamwork:tagShape statements are present for a workflow template, then the Commit button will force the user to first go through a dedicated page that checks whether the workflow conforms to the specified shapes.

We would instead like the user to be forced to go through this when they click a "Perform Validations" button, and not have to do it again when they go to commit changes to production.

Here is the workflow we are setting up (the custom entry script for "Frozen for review" is already set up and working):

[Holger Knublauch]

Hi Rebecca,

I am a bit unclear what user experience you would like to see here. You say that users should be forced to go through a validation step, but what would they do to trigger that? Would this be a specific set of shapes or shall the workflow simply not have any new constraint violations?

Holger

<Screen Shot 2024-01-12 at 9.01.27 AM.png>

--
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
To post to this group, send email to topbrai...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/3a88a3a1-abe7-4fab-9fb2-db96fe47b688n%40googlegroups.com.

[Holger Knublauch]

(It may also help if you want to share your workflow definitions file with me so that I can see what constraints you are using. Private email is fine.)

Holger