Validation Rules Dilemma

Support, Troubleshooting, & Help
1

We have a situation where a validation rule should be applied, but not necessarily prevent the user from proceeding. This may sound contradictary but let’s say that the range is between 10 and 15. The user finds that something is 16 and will report this as an unusual entry, but he/she needs to proceed with the batch. We don’t want the user to force to report false data just to proceed.

We are considering allowing the transition out of the step when there are data validations with either: 1) a comment provided, or 2) an indication in the completion/signature data that exceptions were present.

Does anyone have any other/better suggestions?

Thank you.
Gerry

1 Like
2

Hi Gerry, thanks for sharing your question about configuring the signature widget for cases where the performer and verifier switch roles in the same app.

This is a flexible use case that Tulip apps can support with a few design choices.

Here’s one approach that avoids requiring users to log out and in:

  1. Add two signature widgets on the same step.
  2. Assign each to a different user role variable (e.g., PerformerUser, VerifierUser).
  3. Before the step, set those variables using a prompt or logic from prior steps.
  4. If roles swap later, update the user variables and move to a fresh step.
  5. Each step can track and store a different pair of signers.

This way, you can manage dynamic role switching and still keep clean records.

More details on signature widgets are here:

Let me know if this setup works for your workflow or if you’d like help modeling it.

3

I haven’t worked extensively on validation rules in Tulip (long story, but still on LTS 8.2), but I have played around with it in a test environment.

I would try to make it conditional such that if the value is out of range AND explanation is not provided, the operator cannot proceed, but if the value is out of range AND explanation is provided, the operator can proceed. The explanation could be verbose or shorthand, “auto-commented” via button click or manually input, with or without e-signature, etc.

1 Like
4

James,
Thank you very much. That is precisely what we are doing at the moment.
Our customer is testing it. Once I receive feedback, I will post some details to this thread. Thanks for the reply!