At showcase you can see what I am using the form for.

I was wondering, is it possible to add a ticketnumber system, or something like it.

That people get a reference number when they recieve an email. (one that is generated automaticaly, maybe with possibility to customize it a little.... example: start value=\"100200\"

Also handy for \"servicedesk\"/\"helpdesk\" forms.

Hm i do not see your post in the forme showcase. About the ticket system. That is interesting. Could you give me some more details about what exactly would you need in order to make that work?

What I mean is, a numbering system.

Which will also be used in an email.

Someone fills in the form.
He/she will get an email with the info.
it has name, number and other info in it.
We get the same email and/or export to excel.

When someone comes to us, who booked online, can give his/her name and we need to search that name.
If someone says, I got reservation *1501*, then search&finding that reservation easier.

For a helpdesk it could be, Customer types in problem and get ticket/referance number back. the problem (or complaint) can be found back easier.

(my form: 1st Click here. then: in menu goto -> Join Ultimate Party)

i see. I will think of it and add it to the next version.

Did anything come of this?

I am trying to create a purchase order number request form for our office.

Our accounts department require all purchases to have a order number. I am wanting for the form to sequentially generate a number, store it with the form, but then be able to feed back this number in the \"Thank You\" message.

Does this make sense?

What the form will do is send the purchase order number, purchase details, and purchasee to an email address and stored in the database.

Alternatively, does each new press of the submit button generate a unique ID? Can this be feed back in the thank you message to be used as the purchase order number?

Regards

Dan

@dharbottle You want a component that would generate a unique ID. Please consider this

1) How is the ticket generated? Is it randomly (we are currently working on a random generator, that can generate numbers, \"words\" (random character strings with a given length) or a combination of both. )?
2) The value can be referenced (using the placeholder system) in you thank you message and in your e-mail.

Please tell me if the above is ok for you.<br><br>Post edited by: sebyp, at: 2008/02/24 09:31

@sebyp
I would use this feature, too.
I'm taking registrations for a summer camp where we don't take money online during registration, but the camper goes to a local post office and transfers the money to our organization after registration. We would like to use a number that is visible on the registration form (or at least on the thank you and follow up email) so we can request that the camper include that number on their money transfer form at the post office. This way we can match the deposit with the web registration. In our location, such a number would be better than other ways (such as a name even) to match the deposit with the registration.

I think that the \"ticket number\" field-type will work for us, but I'd prefer sequential numbers if possible. Roman alphabet symbols aren't used much here and numbers would be more suitable for that reason - less chance of a transcription error on the money transfer form.

I would prefer sequential rather than random to ensure that there is 0% chance of overlap now and into the future.

Now that I think about it. It is best to only generate the next sequential number upon submission of the form... not the loading of the form. The \"ticket-number\" field type looks like it does this and will work for us... except that my preference is for sequential digits. I'm repeating myself... apologies...

@SquiggyJahmal, a little bit of math. Let's assume that the length of the random generated code is L. If we want to generate a random ticket number using only letters form the English alphabet (there are 26 letters), the total number of combinations is 26 raised to the power of L.

A simple calculus shows that for a ticket number with 6 characters in length, the total number of combinations is roughly 308.915.776. From this, we can calculate the probability the 2 generations are the same. The probability is 1/308.915.776, resulting a 0.00000003% probability. So, it's not impossible, but very unlikely that two random generated numbers are the same.

If this example still doesn't convince you, plese let us know as soon as possible.

that does make sense...
I was thinking about 4 characters and only using numbers (to keep transcription errors as low as possible) and using the form for a few sessions of the camp perhaps... so the math isn't unreasonable in that case at all.

I just discovered RSform! today and already been made to look stoopid on the forum... maybe I should stop posting on forums during all night web development sessions... at least I'm making progress on my registration form.

I wasn't making a case for the feature based on probability of the same number popping up twice anyway... I just think it is a more elegant solution in my particular case. Maybe others would not prefer it. Maybe those that would will also post here so the developers will know.

The \"ticket-number\" field type will work fine for me.
Thanks.

@ SquiggyJahmal, please accept my sincere apologies if you felt offended by my comment. It wasn't my intention to offend you, but merely to try and establish if a modification to the component is needed.

Now that you better described the problem, it would make sense for an auto-number feature in the ticket field.

Again, sorry if the you felt the comment offended you in any way.

1) A random generator isn't what I would be looking for. Sequential numbering is easier to track in our particular case. Our administrator would get the ticket/order numbers and cross reference this with the invoices that come it. It would be great to be able to append letters to the start of the sequential numbering and give a starting number. eg \"LBC08-1001\"

2) I would love to be able to have the value referenced in the thank you message and email! Yes.

Regards

@sebyp
apology accepted. Thank you.
I'm sure my lack of sleep contributed to my lack of clarity about what I was trying to describe.
All is well.
Thanks.