Add a modifier for incremental number

Current number modifier checks unicity in the LDAP, and increments as many times as necessary, which may end up being quite slow if a lot of values are already taken.

An incremental number modifier would instead store the last used value in the LDAP configuration and increment from there.

added templates label

assigned to @bmortier

By bmortier on 2020-06-02T07:26:39 (imported from GitLab)

added telecom sud paris label

changed the description

By bmortier on 2020-08-17T13:14:24 (imported from GitLab)

assigned to @cchilliet and unassigned @bmortier

By bmortier on 2020-08-17T13:14:38 (imported from GitLab)

changed milestone to %FusionDirectory 1.4

By bmortier on 2020-08-17T13:14:42 (imported from GitLab)

added PJ1801-0146 label

changed due date to October 29, 2020

By bmortier on 2020-10-29T08:11:23 (imported from GitLab)

changed the description

By bmortier on 2020-10-29T13:44:05 (imported from GitLab)

created merge request !820 to address this issue

By Côme Chilliet on 2020-10-29T13:52:18 (imported from GitLab)

mentioned in merge request !820

By Côme Chilliet on 2020-10-29T13:52:20 (imported from GitLab)

mentioned in commit 34f4f8b9

By Côme Chilliet on 2020-10-29T15:55:37 (imported from GitLab)

I used e because n and i are already used, for number modifier and title case respectively.

e is both the first unused letter in the alphabet, and the first unused letter in incremental.

Any suggestion on which better letter to use is welcome.

The last attributed values are stored in the configuration object, which means the lock is the one of the configuration object. It also means using a template with such a modifier while someone is modifying the configuration object will fail.

When using the modifier, one has to provide an id for it as first parameter. This is because when the modifier is called it cannot easily get the template or field name, so this id is used to associate it to the value. This is actually a feature, as it enables using the same id for two templates or two fields if you want them sharing the same number pool. (Like if you have several user templates but want unique incremented employeeNumber you can put %e[userEmployeeNumber]|% in all of them.)

By Côme Chilliet on 2020-10-29T16:07:58 (imported from GitLab)

added 2h 30m of time spent at 2020-10-29

By Côme Chilliet on 2020-10-29T16:08:21 (imported from GitLab)

mentioned in commit d9374c27

By Côme Chilliet on 2020-11-02T13:49:43 (imported from GitLab)

added 30m of time spent at 2020-11-02

By Côme Chilliet on 2020-11-02T14:24:25 (imported from GitLab)

mentioned in commit 5f53704b

By Côme Chilliet on 2020-11-02T14:41:37 (imported from GitLab)

added technical discussion label

added 15m of time spent at 2020-12-17

By Côme Chilliet on 2020-12-17T08:28:34 (imported from GitLab)