The autosuggest is too slow, as shown in ry_autosuggest_each_requirement in the performance tests:

• We must rely on an internal table to generate IDs, or perhaps a cache,

• This table needs to be administered in the RY administration, so admins can lock requirement keys to certain prefixes.

Re-run the Data Center tests and check whether results become consistent.

Implementation

• Introduced the table AO_32F7CE_DBKeySuggestion,

• We’ll store the highest key of each prefix/suffix, and we’ll do it during an initial upgrade task.

• We’ll always rely on this table to suggest keys, so as not to browse the database every time, which is extremely costly with many requirements.

• For the moment, there is no UI to “fix” key suggestions which are wrongly recorded.

Risks

• We won’t suggest keys which are in gaps. For example, if REQ-058, REQ-060 and REQ-062 are defined, we’ll always suggest REQ-063.

• If the customer changes the settings between “Reassign deleted keys”, the next suggestion is already saved.