[imthenachoman]

Thanks Alexander! We’re also looking at other ways to accomplish this. I’ll report back my findings if we have anything worth reporting.

[imthenachoman]

@Jon

Unfortunately no. Obfuscation is not, unfortunately, enough of a control to meet the requirement. :/

[imthenachoman]

Thank you!

And yes, I know there is no compromising information but we have a requirement that application users cannot see application configuration information. JavaScript applications are in this grey area.

I thought I’d check with you to get your perspective on this. I appreciate your help sir.

[imthenachoman]

If a workflow is set to use an impersonation step to run as another user than if a workflow is initiated via JavaScript, wouldn’t the workflow’s impersonation step still work?

The issue is that there is a requirement to hide the configuration/settings from the user. I know there is nothing dangerous/risky but that is the requirement we have.

I’m thinking that as long as we rely on a JavaScript solution like DFFS then there is nothing we can do. Might have to just get an exception…

[Author]

Posts