Delete record on this realation based on state of the record

adrianf0

Is it possible to grant Delete record on this realation permission in the particular form based on the fields of the record?
E.g. we would like to grant requestors the possibility to remove absence requests, as long those are in the new state in the lsw_absence application.
Probably one could implement a custom backend function performing delete once a dedicated button in the form is pressed. However, maybe there is a more standard approach.

gabriel

Right now, the only things that can influence whether the delete action is available on a form, is the setting on the form relation and a relation policy. Within the application, the author can define a relation policy that allows the absence requestor to delete a particular record as long as its in a particular state (like 'new') - that would be the standard solution.

For this the delete setting must be enabled on the affected form relation - the policy would then restrict records to be deleted that do not follow it.

We do not get many requests for updates of the absence application - we think most orgas primarily use the TimeTracker and less the Absence app.

adrianf0

Thank you for the hint. It sounds like a clean solution. The only problem I see, is that policies are defined at the level of the application the relation belongs to. As I follow the recommended way of extending the existing application by creating a new one and adding extra features, the base application remains read-only. I think I cannot apply policy on the relation defined in the base application from the level of the derived application, right?
In other words, can I apply a relation policy to lsw_absence.absence from the level of my derived/extending application?

gabriel

adrianf0
Yes you are right. This is has to be done by the author. And it cannot really work any other way, as these kinds of changes will affect how the original application will behave.

But if your organisation needs a feature like this, you can contact us and we can check how much effort this would be to implement.

If you want complete freedom, you can create your own absence app and copy/paste the code we use to calculate absence times and so on. Then you can implement any feature or restriction that you need.