Process Failure Rules

ci_loi

Does anyone know how to use these process error rules? I just want the program to keep that one object alive in all its unfinished glory along with the error log message

Here is the log..
2008-12-05 02:16:54,388 ASO_v4#admin -15 Executing action FIND EbayListingChecklist WHERE EbayListingChecklist=ThisEbayListingChecklist

2008-12-05 02:16:54,404 ASO_v4#admin -33 Found 1 objects

2008-12-05 02:16:54,404 ASO_v4#admin -16 Finished executing action FIND EbayListingChecklist WHERE EbayListingChecklist=ThisEbayListingChecklist

2008-12-05 02:16:54,404 ASO_v4#admin -15 Executing action FailedEbayListingChecklist.ErrorLog=ProcessError.Message

2008-12-05 02:16:54,404 ASO_v4#admin -34 Value of EbayListingChecklist could not be resolved

2008-12-05 02:16:54,404 ASO_v4#admin -34 Value of attribute Message of object ProcessError could not be resolved

2008-12-05 02:16:54,404 ASO_v4#admin -Unable to find business objects to modify attribute EbayListingChecklist.ErrorLog

2008-12-05 02:16:54,404 ASO_v4#admin -16 Finished executing action FailedEbayListingChecklist.ErrorLog=ProcessError.Message

2008-12-05 02:16:54,404 ASO_v4#admin -15 Executing action REPORT ERROR RE 000-0006: LIST PRICE TEXT NOT ENTERED

2008-12-05 02:16:54,404 ASO_v4#admin -16 Finished executing action REPORT ERROR RE 000-0006: LIST PRICE TEXT NOT ENTERED

Here is the rule:

If ThisInventoryItem.ListPriceText IS DEFINED AND ThisEbayListingChecklist.ItemName='Yes' Then
ThisEbayListingChecklist.OptionsToken = 'Yes'
Else
FailedEbayListingChecklist.ErrorLog = ProcessError.Message
REPORT ERROR RE 000-0006: LIST PRICE TEXT NOT ENTERED

I've tried putting the Failed Text below the error and nothing happend. I am wondering if possibly the Process Error Rules can only be run from the Business Object Rules are initiated? Can anybody shed some light for me? Thanks

aware_support

Have you checked the User Guide? It has a section on failure rules.

ci_loi

At the time of trying to get the process failure rules to work I was a little tired. But now that I have entered it in the right place (presumably under the processes failure rules section 😉 ) I keep getting an Internal Error message.

The rule is written as follows:

      FailedMyObject.ErrorLog=ProcessError.Message

MyObject was passed into the process. Does anyone know why I might be getting "Internal Error" messages?

tford

If MyObject is passed into the process, are you sure you need to use the prefix 'Failed' in FailedMyObject.ErrorLog ? That prefix is only needed if you are trying to distinguish the FailedMyObject from other MyObjects in context.

Is ProcessError also in context?

Tom

ci_loi

According to the UserGuide ProcessError is automatically defined when Failure rules are created. And the Failed context in front is supposed to keep that particular object alive when a report error is called. Here is a link to the bsv.

Does anyone have an example I can use?

http://www.geocities.com/loivan/TestFail.zip

tford

Please describe what you are trying to test/demonstrate in the test bsv.

ci_loi

basically you just create a my object with its default value.

go to the homepage and run the process "change" on it

change will change its number to -4 and call a process that checks if the objects number is less than zero. a report error should be called and the failure rules should kick in. the failure rules set the objects number to 99.

If everything worked correctly. The report error should execute and MyObject.Random should be set to 99.

tford

ci_loi,

Sorry I was out in left field about the prefix issue.

Make these changes in your TestFail bsv & it will work:

1- You do not need the process CheckRandom. Instead move the rule that is now in that process to be a rule of MyObject "when it is created or modified".

2- In process ChangeRandom, eliminate the call of CheckRandom.

Does this answer it for you?

Tom

tford

ci_loi,

Sorry, I think that answer was too simple. Give me a bit more to look at this.

Tom

tford

ci_loi,

Will you always be dealing with one instance of MyObject at a time as in your TestFail.bsv example, or will you be processing multiple instances of MyObject in a process similar to the example giving in the processing of bank transactions in the Process Failure Rules section of the User Guide?

Tom

ci_loi

I will only be processing on object (the object in context) so you are correct when you write that I do no need the prefix of "Failed" but when I remove that I still get the internal error.

tford

ci-loi,

This should do it:

1- Add MyObject rule: If MyObject.Random<0 Then
REPORT ERROR 'My Random Less Than Zero'

2- Eliminate process CheckRandom

3- In process CheckRandom
a- Action Rule: MyObject.Random=-4
b- Failure Rule: FailedMyObject.Random=99

When you run CheckRandom process 3a will fire causing REPORT ERROR from #1. Because you have Failure Rule defined in 3b, the combination of #3a and #1 will always make MyObject.Random=99.

To test, you could also remove the negative in #3a and make the rule: MyObject.Random=-4. In that scenario, the Failure rule will never fire.

Tom

ci_loi

Hmmm.. I see what you are saying. Is there a way to avoid adding rules to MyObject? I will have to do a few more tests to see if this will work with the main application that I am building.

tford

Why do you want to eliminate MyObject rule. It's what creates the REPORT ERROR (i.e. Failure) that the Failure Rules are reacting to.

Feel free to describe what you are trying to accomplish in your applicaiton.

Tom

ci_loi

Thanks Tom. I just want to avoid have to running rules when it object is modified. Specifically in instances where an Object is modified often in one process. Essentially I am trying to create my own error log/checklist. There are about 15 points to examine. If the check is successful then the error log is updated. This gives the users a better idea of what was successful and what was not. The more rules that are attached to MyObject to verify when updated the more resource heavy my error logger becomes. In my particular case, I should be able to do what you've said before and not have too much of a hit on the system. But in general, being UNable to avoid having to check this rule every time makes my program much more bloated.

Thanks for your help.

tford

If you are trying to log checklist exam points in your checklist process, I'm not sure why you need to even involve REPORT ERROR action and process failure rules. Couldn't you use a conditional CREATE action to a BO like ChecklistLog?

Tom

ci_loi

Another issue with having the REPORT ERROR exception thrown from the object is that the ROLLBACK doesn't occur for things modified before the error.

I am involving the report error because my checklist is for an automated process. I rely on having the ROLLBACK feature of the REPORT ERROR to eliminate changes that may have been made in the processes.

aware_support

REPORT ERROR MUST rollback all changes UNLESS there were actions that involved user interaction. Consider this:

1.
MObject.MyAttribute = MyValue
REPORT ERROR 'Error'

In this case change to the object attribute will be rolled back

2.
MObject.MyAttribute = MyValue
EDIT MyObject
MObject.MyAttribute2 = MyValue2
REPORT ERROR 'Error'

In this case MyAttribute will NOT be rolled back because there is an action involving the user interaction that follows (EDIT). However, MyAttribute2 WILL be rolled back because there is no action that involves user interaction.

In other words, any action that involves user interaction, such as EDIT, ENTER NEW, PICK FROM etc causes the current transaction to be committed, no matter if there is an error afterwards.

ci_loi

Ok. So is there a sample BSV where I can see an example of a failure rule that is attached to a process?

aware_support

We have discovered a bug in failure rules after Tom kindly presented a BSV that demonstrates the bug. The bug will be fixed in the next build (due out this week)