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; } } }

Locking a workflow for validated process (GMP)

Florian_Vogt

Hi all,

I have a customer who fell in love with workflow builder. What they need in order to apply it to regulated, validated processes would be a way to lock steps or the entire workflow, to assure that the method of analysis cannot be manipulated.

Does somebody have an idea how to accomplish this? Did I miss an option to achieve this, maybe?

Thanks for your thoughts and input!

Best regards from Heidelberg,

Florian

Accepted answers

ian_jmp

Maybe there's a better way, but they could always get the script from Workflow Builder and encrypt it to require a 'Decrypt' and/or 'Run' password (or both). If lots of folks are using it, you would probably want to put this in an add-in with a menu option.

All comments

ian_jmp

Florian_Vogt

Thank @ian_jmp . That's definitely an option or maybe the way to go. It would actually be nice to have that built into workflow builder

ErnestPasour

There is nothing of the kind built into workflow builder. Can you elaborate on what the user request is?

Does the user have Workflows that fully perform a process? I.e. they require no user intervention.

The user can perform actions after the workflow has completed. Is that a problem?

Or are these just "scripts", not actual analysis?

MikeD_Anderson

@ErnestPasour - Hey, just going to chime in on this because I expect a lot of our Pharma/ biotech's to bring similar requests.

The issue is kind of like with software development. There's a point where you guys lock down the codebase for a version, do a final set of quality checks, and then release it in a state it can't be changed by the end user. They basically want to be able to do something similar.

They want to be able to verify that a workflow is running as expected on a standard data set (like what we do with our NIST verification tool) and then lock the workflow down so that it can't be changed. The data going in and the results coming out of the workflow will be different from the test case when it's used in the wild. The point is that they've verified that the workflow is producing expected results under controlled test conditions and that it can't be modified after that verification process. Any prompting, dialogs, etc. would be part of that verified workflow.

I don't know if @Florian_Vogt put it in the Internal Wish List, but this would be a good addition to WFB's capabilities as an LRT option and I'd expect to hear more requests for it from our customer base as 17 gains traction for work in validated environments.

Best,

MikeD_Anderson

As a follow on question to this - does anybody know if there's a way to lock a JMP App (.jmpapp or .jmpappsource file)? I can't seem to find anything around that either.