M
matman
Guest
I'm currently making a little demo exercise and ran into a validation problem. Because you need to understand my situation for this, I'll explain my scenario: After a user has checked all the checkboxes of status #1, the user can switch to status #2. There are two ways to switch to status #2. The first one is by editing the record, and then selecting status #2 from the 'Status' dropdown field, created by the Workflow process. The second way is to press the Workflow action 'Switch to status #2'. Because the user must first check a 'Do you want to proceed?' checkbox, the first method to switch to status #2 has been disabled as the user can only check this checkbox on the status page. I disabled this first method using the 'Status' field validation. Okay so we have to use the second method, via the workflow action. Here comes the problem: Because I only want to show the 'Switch to status #2' action after the user checked all checkboxes, I can no longer use the action's execution condition as a validation for the confirmation checkbox. Since I cannot, I must find another way to verify the check before executing the action. So there are a couple ways I imagined. The first way was by using the Status field validation, because the status changes when executing the action. After some testing I discovered that the status field validation is completely ignored when executing a status changing action. The second way I imagined was by using a validation trigger, because the documentation stated that validation triggers are executed even before the 'Before Update' triggers. Apparently, the ' Before Before Update ' triggers are executed after the action has finished execution. Which makes them impossible to use as well. There are basically two ways I know of now to work around this issue: Put a validation script on the status change page to verify the user has checked the confirmation checkbox. However, since it's client side it's unreliable and can be hacked easily. Put the confirmation checkbox on the edit page (making the status change page useless in my case). And I also have three suggestions: Execute validation triggers during or before the execution of the action. Implement status field validation inside the action, because in my case the field will be updated during the action. Create another condition for Workflow actions: Instead of one for both execution and display, make one for display and an optional one for execution (and if execution condition empty, treat display condition as one for both display and execution). Does anyone know a way to work around my problem, but by keeping this scenario the same?
Continue reading...
Continue reading...