Enforce unique numbering - avoid duplicates on child tables of task

useful reading here:




for my solution I went for the recommended business rule solution, and defined the business rule to run on "task" table and inherited by child tables (incident etc)

still trying to get to the bottom of how exactly the issue of duplicate incident numbers being generated on the incident form arises, but in the meantime no more duplicate tickets in our instance!

examples of how the transaction logs might be checked for the issue:

/syslog_transaction_list.do?sysparm_query=sys_created_onBETWEENjavascript%3Ags.dateGenerate('2018-05-03'%2C'12%3A50%3A00')%40javascript%3Ags.dateGenerate('2018-05-03'%2C'12%3A50%3A59')%5EurlSTARTSWITH%2Fincident%5Esql_count%3E0%5Eresponse_time%3E25%5Esys_created_by%3DSmith

Comments

Popular posts from this blog

Running transform maps asynchronously

Post a command to the ECC queue for the mid server to initiate a powershell file copy

GlideRecord setValue