Use of FAILED prefix to capture form cancel

kklosson

My process calls a form for edit. If the user cancels, it apparently stops all rule processing. I've read the docs that I use a failure rule, but I've tried and I don't quite get it. My form call a people BO and just needs to update a couple a attributes. After I call the EDIT BO USING... statement, what do I use to capture form cancellation?

tford

If you had a process called EditPerson, click on the + beside the EditPerson process in the config tool and you will see 2 more options with + beside them:

+Actions
+Failure rules

Add rules in the "Failure rules" section that you want to fire if the user cancelled the EditPerson process.

Tom

kklosson

Thanks Tom,

I'm still missing something because after adding a failure rule it doesn't fire. I added a simple rule to DISPLAY MESSAGE, but when I cancel, no message.

From the User's Guide:

NOTE: Process failure rules are also executed if a process has been canceled by the user. For example, if a process calls ENTER NEW action the form of the object will be shown to the user. If the user clicks on the Cancel button on the form, the process will be canceled and the failure rules (if any) will be activated. In this case no special predefined object describing the failure is written into the context.

This seems like exactly my situation, but the failure rule does not execute as this would imply.

aware_support

Failure rules will not display a message on screen. To check if failure rules are running please look at the LogViewer

kklosson

Well, I also tried calling a process - That didn't seem to work either.

aware_support

Is there anything about failed rules in the LogViewer?

kklosson

Well, there are some entries there but I haven't learned to read this log very well yet. But this should be simple. What basic rule can I put in the Failed rule that will trigger when the users cancels an EDIT session? Once I get something to fire, I should be okay, but so far, I just can't capture that event.

aware_support

It's hard to say what rule you need to put in there. You need to check the LogViewer and learn how to work with it - it should say something along the lines of "processing failure rules..."

tford

If you are just trying to understand how it works, try this:

1) create new Plain Text attribute People.FailTest
2) add a failure rule: People.FailTest='Failed'
3) run your process & cancel to cause the failure rule to fire
4) inspect the instance of People now to see that People.FailTest was set to 'Failed'

Tom

kklosson

Yes, I can make that work. But as you said earlier, I can't use a DISPLAY MESSAGE statement and it appears I cannot call other processes. Where is the rulebook on this?

Here's what I'm doing... I'm creating a mechanism that forces a user to change their password when they log in. So I have a form that simply collects the new password (with verify). I can make everything work but if they cancel the form, I need to be able to redirect them. My preference is to just call the same process they're in and put them in a loop until they get it right or depart.

What are my options?

aware_support

Failure rules are described in the User Guide - they are there mostly to perform corrective actions. In your case what you really need is to disallow user to cancel the process. Is that right?

We'll try to put this option into the next build - it's an omission from the product.

kklosson

Yes, that's what is needed. I can envision either the option to hide or remove the Cancel button, which would make the form "modal" or any ability to capture the fact that the user canceled and redirect their perspective as needed.

Thanks.

Also, speaking as a newbie, perhaps some amplified documentation about what commands can and can't be used in Failure Rules would be helpful.

aware_support

The option to disallow cancelling a process has been implemented in build 1158