M
matman
Guest
Because of an earlier topic in which I was talking about some issues I had with a delayed trigger, I was fooling around a bit with delayed triggers. I set my Query API permission to the following settings: Then I went back to add some Employee objects to my Employer object (1 - N) using Quick Create. Then, I immediately removed the Employee object using the X-icon. Which results in an orphan Employee object. Since I don't like orphan records, I added a delayed trigger with the following code: rbv_api.log("debug", "{!name#text}'s master: {!R108244227#id}"); if ({!R108244227#id} 0) { rbv_api.deleteRecord("medewerker", {!id}); rbv_api.log("debug", "{!name#text} has been deleted!"); } The trigger is set to "Run trigger on 'After Create' with a 1 minute delay". Knowing that the trigger is delayed and the Query API doesn't have the permissions to delete the Employee record, the record should stay alive. So after creating an Employee, the trigger gets added to the queue. It was supposed to run on 9:41 AM, but when I checked back on 9:42 it was still there. Only a little later it disappeared from the queue, leaving the following in the log: When I check back at my Employee objects view, I cannot find that record anymore. Now.. I don't know if you guys consider this a bug. It's most likely caused by cached permissions or something like that.
Continue reading...
Continue reading...