If you think that something doesn't work in Aware IM post your message here
#30884 by Rennur
Fri Jan 16, 2015 3:28 am
Few Issues with timestamp:

1) The separate time dropdown must always be defined, even though 'value must be provided' is not checked.
My order from in 6.0 is not unsuable.

2) Rule to define this timestamp based on a another timestamp e.g timetampB=TimestamA, defines the time dropdown with both date and time information.

3) Even when READ PROTCEDed the borwser error message posp-up "Form Data Invalid"

4) When you have the time min and max value defined eg 6:00 AM - 6:00 PM it gives out error on the form.
The format is correct and the time value selected are withing min/max.

#30888 by aware_support
Fri Jan 16, 2015 4:47 am
Could you please send us a BSV for testing?

#30889 by eagles9999
Fri Jan 16, 2015 5:09 am
Wow Rennur.....

You should have been a Beta tester. ;-)
#31325 by Rennur
Thu Feb 12, 2015 1:04 am
2) Rule to define this timestamp based on a another timestamp e.g timetampB=TimestamA, defines the time dropdown with both date and time information.


Issue 1:
When you define the DATE part on Timestamp1 the RULE executes to define Timestamp2, it defines the date field correctly but the time field is defined with both date & time.

Issue 2:
The whole Timestamp is considered DEFINED when only the date part is selected (defined) with Time field remaining undefined; meaning the RULE (to define Timestamp 2) will execute as soon as the date is selected (defined).
What happens now:
As soon as the date part of Timestamp1 is defined the rule (TIME_ADD) is executed and assumes Timestamp1's time filed is 00:00 AM, and it defined Timestamp 2 as 02:00 AM. I want to for example, set the time as 07:00 AM and once I define that, the RULE will execute and define Timestamp2 as 09:00am.
Rule to fire only when both date & time fields are defined. That way when I define the time field the TIME_ADD rule will define the correct Timestamp2 time field and not 02:00 am.
When both date+time is defined then the FUNCTION TIME_ADD will work properly.
Example, a RULE to define a Timestamp2 two hours more than the first as in order requested between Timestamp1 and Timestamp2, the rule will change the second attribute to allow 2 hours between the 2 e.g Order between 7 AM and 9 AM, not 7AM and 2 AM.

Issue 3:
System always assigns 00:00 to the time field, even when not defined. I know this is intentional.
If you have set up a time range and 00:00 does not fall in this range, the system will still assign it as 00:00 and potentially cause problems.
#31557 by Rennur
Tue Feb 24, 2015 9:41 am
Hi Support,

- Regarding issue 3:
Has the time range option now been completely disabled? I've set up my time range but all times are displayed.

- Issues 1 & 2 makes the TIME_ADD function ineffective.

In a separate post on this issue, you stated that this is how timestamps work now, meaning they have been changed even though they worked just fine before.
#31908 by Rennur
Tue Mar 10, 2015 7:46 am
BUG remains

BSV Emailed.

Steps: Pres on 'Tabindex Issue' button in menu toolbar and enter both timestamp 1 & 2 values and save form.
Tiem range format error
(70.75 KiB) Downloaded 148 times
#51792 by Jaymer
Wed Oct 09, 2019 3:08 pm
Rennur wrote:SOLVED.
The correct way is 6:00 AM, without the 0 in front of the 6

Just want you to know this saved me.
Lots of times people make a post "nm - I figured it out" and they don't bother to post the solution (even though others have taken time to try and help them).
I don't think this answer is THAT obvious - already tried many ways and was getting the error, even in v 8.3

Some help text on this item in the Config Tool wouldn't be a bad thing.


Who is online

Users browsing this forum: Google [Bot] and 3 guests