588647_en-US

liliconcom

Re: Provide Encryption / Password Protection capabilities for Workflow Builder and Application Builder

Great idea!

Provide Encryption / Password Protection capabilities for Workflow Builder and Application Builder

What inspired this Wish List Request? 

This discussion in the SE Discussion board: Locking a workflow for validated process (GMP) 

On checking, it also appears that Application Builder / Dashboard Builder don't provide locking/encryption capabilities either. 

All three are basically JSL under the hood, so it follows they should all have this capability. 

 

Please describe the new or improved feature or solution you would like to see. 

Provide the same run and edit encryption capabilities found for JSL files for workflows, application builder and dashboard builder files. 

 

What would the value be to you and/or other users if this new feature is provided? 

This would support customer usage of custom workflows and reporting in controlled environments (i.e., "validated environments" or other regulated manufacturing environments).

 

Is this an external customer request? 

The original request (see link above) was for a customer.  The extension of the request to Application Builder is a logical extension of the concept to other JSL-like objects in the JMP environment that are easy for a user to edit or modify.

Is there a competitive software package that has this feature or solution that we should be aware of? 

n/a

Will this impact a renewal, expansion, or adoption at a customer, and does this put an account at risk if we do not address this? 

Any action we can do to support easy adoption of JMP tools in controlled environments will aid in expansion of our user base in those environments. For HLS-type situations, one of the biggest hurdles for adoptions of new JMP releases and technologies is the "validation" step.  This will help with that process. 

 

Automation and ScriptingScriptingUser InterfaceRe: Provide Encryption / Password Protection capabilities for Workflow Builder and Application Builder - Status changed to: Acknowledged

Hi @MikeD_Anderson, thank you for your suggestion! We have captured your request and will take it under consideration.

Re: Provide Encryption / Password Protection capabilities for Workflow Builder and Application Builder - Status changed to: Not Planned For Now

@MikeD_Anderson  we reviewed this an have decided that does not fit into our product strategy.  The challenges associated with this type of feature would be the need to include having tools that provide encryption technology that would put us at risk of not being able to ship JMP software worldwide due to US export controls.  

Users working in a pharma GMP/GLP/GCP environment would need to use their own existing system tools and processes to protect JMP files as they see fit.  

For questions on validation, the standard response should be to direct the user or prospect to www.jmp.com/qualitystatement, where well documented and vetted approach to answering those questions is provided.   

Re: Provide Encryption / Password Protection capabilities for Workflow Builder and Application Builder

Thanks for the update, @SamGardner.  

 

Could you help me understand how this request is different than this: 

 

 

or this:

 

 

They've both been in the product for many years, so I'm having trouble understanding how having similar functionality in WFB (or even the limited editing that Earnest was working on) would be a new problem with export control, etc. 

 

Thanks!

 

M

Re: Provide Encryption / Password Protection capabilities for Workflow Builder and Application Builder

To encrypt JSL scripts, JMP uses SAS’s proprietary 32-bit zscode /zdecode (a now insecure) encryption algorithm.  This encryption is more of a "scrambler" than a true encryption.  

To provide file protection through modern encryption that a customer would expect, we would have to use stronger encryption.  That level of encryption is considered a restricted technology that, because we a US company, could prevent us from being able to sell JMP worldwide. 

In general, we avoid including any feature in JMP products that could be considered restricted technology.