Duplicated HR case number are getting created after transferring the case. - Known Error

Duplicated HR case number are getting created after transferring the case. Description When we set the property "glide.itil.assign.number.on.insert" to true then padded number or next increment number for a record is only generated when it is inserted in DB. We were inserting dummy records in DB to get a padded number for swapping, and then deleting it. But due to scope issues sometimes the record is not deleted and thus two records can be seen with same number. Please see the swapNumber function of hr_TransferCase script include.

Steps to Reproduce

Set " glide.itil.assign.number.on.insert" to true.

Create a new HR case. Transfer the case with existing case number 2 new HR cases with same number will be created

Workaround To resolve this issue please make following modifications:

Create below function in global script include, getNextObjNumberPadded cannot be accessed in scoped app and thus this function should be created in a global Script include (like: HRSecurityUtils) so that we can access it in hr_TransferCase. getNextObjNumberPadded: function(tableName){

return new global.NumberManager(tableName).getNextObjNumberPadded();

}

Then in hr_TransferCase script include inside swapNumber function replace the code which creates a new record in db with the function we created in step 1 for getting next iteration number for the case. Just remove the if/else statement where we are checking for the property "glide.itil.assign.number.on.insert" and Update the newNumberForOldCase variable with the next number. newNumberForOldCase = new global.HRSecurityUtils().getNextObjNumberPadded(originalRecord.getRecordClassName());