How do you "UN" PROTECT the PROTECT Action?
I read through the guide and read the forums but I can't find anything on the removal of the PROTECT action. I'm sure that this is easy and I am just missing it.
Is it as simple as adding NOT PROTECT?
Thanks for your help!
Unsure about the PROTECT Action
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
I'm sorry if this comes out harsh but what is point of having a PROTECT action without having the ability to reverse it? Isn't it possible that a record could become protected and then a user changes their mind (I know...that never happens).
Maybe I am not understanding the use of the PROTECT action...my assumption is that once a record reaches a desired status that a PROTECT action could be used to protect the record from being changed by a user or All users. If a change would then need to be made it would have to be modified (forever I am assuming) by an administrator (unless PROTECT FROM ALL was used...then nobody could modify the record).
I want to understand but your documentation can be confusing and the searching on the forum is really difficult.
Maybe I am not understanding the use of the PROTECT action...my assumption is that once a record reaches a desired status that a PROTECT action could be used to protect the record from being changed by a user or All users. If a change would then need to be made it would have to be modified (forever I am assuming) by an administrator (unless PROTECT FROM ALL was used...then nobody could modify the record).
I want to understand but your documentation can be confusing and the searching on the forum is really difficult.
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
I think you are misunderstanding the concept of protection. The user does not protect or unprotect anything - the system does all the protection and unprotection behind the scenes depending on the run-time conditions. So it is your responsibility as a configurator to provide protection rules according to the requirements of your system.
You have to provide conditions under which protection will happen. Consequently the reverse of these conditions is when the protection won't happen and so records will be "unprotected". For example, you can define a rule that looks like this:
If Transaction.Status = 'Completed' Then
PROTECT Transaction.Balance FROM ALL
Whenever a status of the transaction becomes "completed", the balance attribute becomes read-only (protected). It is unprotected if the status is anything else.
You have to provide conditions under which protection will happen. Consequently the reverse of these conditions is when the protection won't happen and so records will be "unprotected". For example, you can define a rule that looks like this:
If Transaction.Status = 'Completed' Then
PROTECT Transaction.Balance FROM ALL
Whenever a status of the transaction becomes "completed", the balance attribute becomes read-only (protected). It is unprotected if the status is anything else.
Aware IM Support Team