In the OOTB Change Request workflow, we have the number field set to Auto generate.
In the OIR for Change Request, we have the following lines for the number field.
<AttrValue id = "number"
ignore="false" force="false" final="false"
When we create new Change Requests, we get a random higher than-the-last number for the change request and what we are looking for is a controlled sequential numbering scheme.
Last week, I created 3 CRs, CR-00021, CR-00023 and CR-00041. This week, the next one created was CR-00061.
What do I need to change in the OIR to get the system to give me a steady sequential numbering scheme? If Windchill cannot do it automatically, we may have to fall back to a manually entered numbering scheme from an external database which we are trying to replace with Windchill Change Management. We do not want to maintain 2 systems for tracking changes.
Solved! Go to Solution.
I will try that on my test system.
I would guess that other numbers could also be changed to be sequential by doing the same nocache alteration.
How do I alter the initial starting number to 3000?
It is currently at 63 and when I tried to edit it in the Oracle Console, it said start number cannot exceed current number. Current number could not be editted in the console.
This is assuming Oracle database. The difference between the desired next number and the current next number is (3000-64 = 2936).
ALTER SEQUENCE WTCHANGEREQUESTID_seq INCREMENT BY 2936;
SELECT WTCHANGEREQUESTID_seq.nextval FROM dual;
ALTER SEQUENCE WTCHANGEREQUESTID_seq INCREMENT BY 1;
Again, test it. I might be off by 1 number?
I am quite perplexed as to why these sequences aren't set up OOTB as NOCACHE. I continuously hear of admins complaining about number sequences jumping by 20 (the default cache value) sometimes.
FYI...I have never created the sequence with the exec.wtpk.createSequence() command. Instead, I've always used the CREATE SEQUENCE ... command with correct parameters (including NOCACHE at the end of the statement). I don't know of the difference between the 2 methods.