How to prevent an object from being used where it shouldn't

Forum|Forum|2 years ago
April 30, 2024
7 replies
0 views

Hi all,

We need a rule expression to be used only in one process model.

How can we prevent that rule expression from being used in another process model or interface? The only way I can think of is to manually check the dependencies of that rule. Could this review of dependencies be automated in some way?

Thanks in advance.

stefanhelzle0001

Brainy

I do not see a way to prevent that. This feels like an awkward design decision. I am curious. Why is that?

Instead of writing an expression, you could put that code into a script task. This is not exactly a best practice, but might be an option for your specific case.

J

josejavierc0001Author

Known Participant

It is due to a security requirement. We have to store access tokens to client services in Appian database and we have to prevent a query to this table from being used from the Appian front-end. For this, we intend for this query to be done only from a specific process.

stefanhelzle0001

Brainy

Without knowing the details, but for me, this feels more like obscurity than security.

So this is not about the expression, but about restricting access to certain items in a database, correct?

I suggest to contact Appian for ideas about how to do this. If you do that, maybe you could share some details here.

harshk1671

Hi josejavierc0001,

Can you explain the rational behind this design decision?

davidj137213

Brainy

Why do you want to implement this behaviour? Could you explain a little bit about it?

Sign up

Login with SSO

Login to the community

Login with SSO