Preventing Empty / Abandoned records using IWP

[xochi]

I have the following script to create a new record using iwp:

Go to layout "Data Entry X"

New Record / Request

Set Field (Request Type) = (a calculation based on which layout they are on)

The layout has a "submit" button which does:

Commit Records/Requests

Go to layout "Main Menu"

This all works fine.

However, when reviewing my data, I notice that I'm getting a fair number of what appear to be empty / abandoned records.

Of note, they all have a Modification Date exactly 15 minutes after the Creation Date. I have my WPE set to timeout at 15 minutes.

So I'm guessing that someone runs script #1, but then walks away from their computer, and the page times out and leaves me with a 99% blank record.

Is there any way to prevent this from happening?

[Vaughan]

In the "old" days of CDML, the record could be created and data entered in one step. Can't this be done now?

[xochi]

FM 7/8 has XML to replace CDML, which I'm sure can be made to do what I wish, but I'd like to get it working in IWP for the time being, since it's so much easier to design in...

[Reed]

in IWP, you can use global fields for data entry and then use a script to create records with the contents of the globals, so it all happens within one script.

One consideration with this approach in IWP is record-locking with multiple users. I use a dedicated table with the globals, but the global table has multiple records. A looping startup script puts the user on the first unlocked record, so there won't be conflicts.

[Vaughan]

Global fields are not suseptible to record locking, and least not in the regular client. Is this different in IWP?

[Reed]

I have run into this problem, specifically in IWP... that's why the workaround.

If one user is in "edit" mode in a record in IWP, then no other users can use that record. (Even if the layout, or even the whole table contains only globals) I don't know if this is fixed in IWP in v8, but I haven't had a chance to play with it in v8 much yet. (Still waiting for FMSA v8)

[xochi]

The "bogus" records are pretty easy to identify (they have data in one field only, and everything else is empty). I suppose I could have the "Submit" script go through and prune these empty records. Then I end up with holes in the serial number sequence, though.

I suppose I could even write the script so that it pruned the empty records and re-set the serial number, though I'm always a little afraid of doing this in a multi-user scenario.

[Reed]

Who cares if there are holes in the serial numbers? All that matters is that they are unique...

[xochi]

This is for a HelpDesk system, so if the serial numbers are non-contiguous, I find that holes tend to confuse the help desk staff. "What happened to request #77! Why is there no #77?" etc.

[Rushhour]

Hi..

I am having the same problem.. After the user finish their form in iwp, they click the

'confirmation' button that will bring them to 'submit' layout prompting them to submit their record. So when they choose 'submit', it will open the related record and commit. If they choose 'no' it will bring them back to their record for editing.

My problem now.. when user click 'confirm', the moment it bring them to the 'submit' layout, it already saves that record and at the same time generate a new record.

when i choose 'no' it brings me to that new generated record and not the one i done. Total there are 2 forms now and 1 of it is blank.

Help..... My boss is stressing me to finish my first form and go live on iwp. im a industry attachment student, im still new to fm. Help will be very appreciated.

Thanks a lot..

Kelvin