Celedon Autonumber v1.1 New Features

Version 1.1 of the Celedon Autonumber is now available
This new version includes three very interesting new features:

  1. Now supports 0 digit numbers (allows fully custom calculated fields, without adding any number)
  2. Added ability to generate random strings
  3. Can now trigger number generation on either a Create OR Update event of a record

Zero Digit Numbers

This is actually a very simple new feature. It is now possible to specify 0 as the # of digits in the autonumber configuration. When you do this, the autonumber itself will not be included in the generated value that gets stored on each new record. BUT all other values in the prefix/sufix do get stored. What this basically means is that this autonumber solution is now also a custom calculated field solution. All the power of the parameter engine can now be used to generate values without being forced to include the number.

Generated Random Strings

The next new feature is the ability to optionally generate random strings as part of an autonumber. This is done by adding a new parameter to either the prefix or sufix:
The output of that parameter would look something like this: “KMCTV”
By default, the string will be 5 characters long and all uppercase. However you can customize the length of the string by adding a number like so:
{rand:7} – now the string will be 7 characters long.
Additionally you can specify if the characters should be all uppercase, all lowercase, or mixed case by specifying “upper”, “lower” or “mixed” as a second value:

Trigger on Update

This is now one of the most interesting features of this entire solution. Previously, the autonumbers were always generated at the time of creation of new records. But now, we can configure the auotnumber to generate the number not on Create but on Update instead. This allows us to control not just “if” and “what” number gets created, we can now also control “when” it gets created.
A common usage scenario for this feature would be a support team that accepts new cases via email. It’s common to receive many spam emails, or other non-case related emails. If we don’t want all those incoming emails to receive actual case #’s, then we can trigger the number to generate only once the case has been updated to a certain stage or marked as a valid case by an actual user.
Here is what a sample config might look like that is using an Update trigger:
You will notice two new attributes: “Trigger Event” and “Trigger Attribute”.
Trigger Event is an optionset, either Create or Update. Create is the default.
Trigger Attribute is only applicable when Update is selected. This is the attribute that is checked, in order to determine when the autonumber should be generated. The first time that attribute has a value set, so that it contains data, that is when the number will generate.

Download Links

Source Code
Latest Release

  • Hi – how can I get this to work with non-padded numbers. Eg. For an autonumber with a prefix ‘PRF-‘, for number ‘123’, I want to see ‘PRF-123’, and for ‘1234’, I need ‘PRF-1234’.

    • To have non-padded numbers, just set the # of digits to 1. The current behavior is that if the generated number is greater than the number of digits, it will overflow and use the full number anyway.

  • Hi Matt
    I have been using you original solution and I am attempting to update to the new version.
    When I do the import I get the missing dependency error on ‘dd_chartmapentity’. Am I missing something?

    • Looks like it picked up a piece of a different managed solution when I exported it.
      I’ve cleaned that out, just download the zip again and it should work for you now.

Comments are closed.

Let's talk

If you want to get a free consultation without any obligations, fill in the form below and we'll get in touch with you.