Record not being written to DB and no error being displayed

BobK

I have a BO TimeObject with the following attributes:
Name: EndTime, type: Timestamp, calculated: yes
Name: EndTimeText, Type: Plain Text, Max. length: 5, input mask: /^[012]\d:[012345]\d/
Name: StartTime, type: Timestamp, calculated: yes
Name: StartTimeText, Type: Plain Text, Max. length: 5, input mask: /^[012]\d:[012345]\d/
Name: WorkDate, Type Date

With the following rules:
1) TimeObject.StartTime=AS_TIMESTAMP(AS_STRING(TimeObject.WorkDate)+' '+TimeObject.StartTimeText,'yyyy-MM-dd HH:mm')
2) TimeObject.EndTime=AS_TIMESTAMP(AS_STRING(TimeObject.WorkDate)+' '+TimeObject.EndTimeText,'yyyy-MM-dd HH:mm')
3) TimeObject.EndTimeText=AS_STRING(AS_NUMBER(CHARS_FROM_LEFT(TimeObject.StartTimeText,2))+1)+CHARS_FROM_RIGHT(TimeObject.StartTimeText,3)

Rule 3 is suppose to set the EndTimeText to 1 hour after the StartTimeText

All rules are set to use in dynamic re-calculation on forms.

Only WorkDate and StartTimeText are on the form.

When I try to create an object, I enter the WorkDate (05/01/2009) and StartTimeText (12:34) and hit the create button.
I get the progress bar that the information is being submitted and then a new blank form with no errors.
When I search for the object I just created, I can not find it. It does not appear to get written to the database.

After much investigation, the problem appears to be with rule 3 above.
The AS_NUMBER() function returns a float number instead of an integer, as I expected, and EndTimeText is being set to 13.0:34 which is an invalid format.

I believe that I should have gotten some kind of error. Either an invalid format for EndTimeText or a failure trying to write to the database.

If I add EndTimeText to the form, I do get an invalid format error, but I do not want it on the form.

I was able to get this to work by changing rule 3 to:
If TimeObject.StartTime IS DEFINED Then
TimeObject.EndTimeText=SUBSTRING(AS_STRING(TIME_ADD(TimeObject.StartTime,1)),11,16)

As a side point, shouldn't AS_NUMBER return an integer if there is no period in the string?

aware_support

If you want to add 1 hour you can just add 1 to a timestamp, so rule 3 can be:
TimeObject.EndTimeText=TimeObject.StartTime + 1

You need to look at the LogViewer (and possibly at the output of the Aware IM Server) if something goes wrong with your rules. LogViewer should have detailed explanation of how rules are executed

BobK

Support,

Your suggested rule of 'TimeObject.EndTimeText=TimeObject.StartTime + 1' does not meet my requirements. It sets EndTimeText to the Date and Time (dd/mm/yyyy hh:mm) and I only want the time (hh:mm).

That does not matter anyway because the second version of my rule 3 gives me what I want.

The real reason for my post was that nothing was being written to the database and I did not receive any error message telling me that something was wrong. IMHO, a failure to write to the database is such a MAJOR problem I should have receive some kind of visual error message when I hit the 'Create' button. I only looked at the database to make sure that the EndTimeText was being set to 1 hour after the StartTimeText. What did I find when I looked? That the expected record did not even exist. The log did show the EndTimeText being set to '13.0:34', which is wrong, but it appeared as normal processing, not as an error.

aware_support

We have never seen the situation when a record was not created without something being wrong with the rules. What is in the LogViewer? Is there any exception in the output of the Aware IM Server and Tomcat?

BobK

Yes, there was a problem with the original version of my rule 3. I just don't think that I should have had to look in the logs or the database to find out that there was this major of a problem.

The following is from the test.log when the original version of rule 3 is executed:
Executing action TimeObject.EndTimeText=AS_STRING(AS_NUMBER(CHARS_FROM_LEFT(TimeObject.StartTimeText,2))+1)+CHARS_FROM_RIGHT(TimeObject.StartTimeText,3) from rules of object TimeObject
EndTimeText=11.0:00

The following is from the Aware IM Server Output when I use the original version of rule 3:

com.bas.basserver.persistence.PersistenceException: Error persisting business object TimeObject A truncation error was encountered trying to shrink VARCHAR '11.0:00' to length 5.

at com.bas.basserver.persistence.EntityDBPersister.updateEntity(Unknown Source)

at com.bas.basserver.persistence.PersistenceManager.a(Unknown Source)

at com.bas.basserver.persistence.PersistenceManager.a(Unknown Source)

at com.bas.basserver.persistence.PersistenceManager.commit(Unknown Source)

at com.bas.basserver.bsmanager.e.a(Unknown Source)

at com.bas.basserver.bsmanager.f.a(Unknown Source)

at com.bas.basserver.bsmanager.f.a(Unknown Source)

at com.bas.basserver.iopipes.ComponentSink.processMessage(Unknown Source)

at org.openadaptor.adaptor.STPipelineController.processMessage(Unknown Source)

at com.bas.openadaptor.NonTransactionalController.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimplePipe.processMessage(Unknown Source)

at org.openadaptor.adaptor.STPipelineController.processMessage(Unknown Source)

at com.bas.openadaptor.NonTransactionalController.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimpleSource.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimpleSource.sourceProcess(Unknown Source)

at org.openadaptor.adaptor.AbstractSimpleSource.sourceProcess(Unknown Source)

at com.bas.openadaptor.a$a.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

com.bas.basserver.persistence.PersistenceException

at com.bas.basserver.persistence.PersistenceManager.commit(Unknown Source)

at com.bas.basserver.bsmanager.e.a(Unknown Source)

at com.bas.basserver.bsmanager.f.a(Unknown Source)

at com.bas.basserver.bsmanager.f.a(Unknown Source)

at com.bas.basserver.iopipes.ComponentSink.processMessage(Unknown Source)

at org.openadaptor.adaptor.STPipelineController.processMessage(Unknown Source)

at com.bas.openadaptor.NonTransactionalController.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimplePipe.processMessage(Unknown Source)

at org.openadaptor.adaptor.STPipelineController.processMessage(Unknown Source)

at com.bas.openadaptor.NonTransactionalController.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimpleSource.processMessage(Unknown Source)

at org.openadaptor.adaptor.AbstractSimpleSource.sourceProcess(Unknown Source)

at org.openadaptor.adaptor.AbstractSimpleSource.sourceProcess(Unknown Source)

at com.bas.openadaptor.a$a.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Exception com.bas.basserver.persistence.PersistenceException trying to commit transaction null

aware_support

You need to allocate bigger length to the EndTimeText attribute of the TimeObject. The current length is too small - see the truncation error in the exception.

BobK

Support,

You are not getting the reason for this post. So, I will try one more time.

Yes, there was a problem with my original rule, but I fixed that before I made this post.

The reason for this post is the following:
When I was testing my application with the original rule, but before I realized it was wrong, I peformed the following actions with the corresponding results:
Created a new TimeObject with the default form.
Hit the 'Create' button.
A progress bar was displayed stating that the data was being submitted.
A blank default TimeObject form was displayed.
The status bar read 'Record created. Create another record'

BUT THE RECORD WAS NOT CREATED

I only realized that there was a problem when I looked in the database to verify the recored had the correct values and there WAS NO record.

I would hate to have to tell my users 'whenever you create an order, be sure to check the log to make sure the order was actually created'.

Granted, this particular problem should have been, and was, caught in testing. But this makes me wonder what other problems that might occur in production that would go unnoticed because the user received no error message.

aware_support

OK, we understand the reason for your post now. As you have noticed the problem is really a development problem and has nothing to do with end users. Even with development most problems are reported to the developer straight away. There are occasional situations when a developer has to look at the logs and output of the servers to understand the problem (as was your case).

Rest assured that end users should be fine. We NEVER had complaints that records haven't been created without the appropriate message.

Thanks for bringing this to our attention.

BobK

Thank You.

Rest assured that end users should be fine. We NEVER had complaints that records haven't been created without the appropriate message.

Glad to hear it.

Hope I did not come off too obnoxious.

Thanks again.