Due to various limitations (e.g., uAchieve with 280 positions, DARwin with 96 positions, standard keyboard limitation of 94 characters), running out of condition codes can present an encoding challenge. Below are a few useful workarounds when encountering such encoding hindrances.
Cut-and-Paste Non-Keyboard Symbols
Create new condition codes by cutting and pasting symbols from another source or by using extended ASCII codes entered by keying ALT+number on the keyboard number pad. This approach will take some trial and error on your part to identify which symbols will work because it depends on the codes supported by your institution's infrastructure. For this approach to work, the symbol entered must show up on the CONDTB-US line and in the Accept/Reject field as the specific characters–not as blanks or empty boxes.
Use Course Flags
Up to five course flags may be assigned to taken courses and sent in with student data from your student information system or assigned through transfer articulation. These flags can range from one-to-three characters in length (including letters, numbers, and symbols), allowing a great many combinations to work with.
Flags can be tested on Course lines using the CFlg field in conjunction with A- or R-lines.
In DARwin, course flags must be encoded with a blank Course field, per the screenshot above. A/R-lines will match any course with a matching course flag.
In uAchieve, a specific course identifier can be added.
Liberate unused reserved condition codes
If you are certain that your institution does not use certain functionality (e.g., C Strings or course splitting), then you can put spaces in the 4th, 10th, 11th, and 12th positions of CONDTB-RES and move those characters to a CONDTB-US field. The same may be done with other position characters (e.g., 13th, 14th, and 15th), but make sure to read the Help file documentation on the functions of those positions to ensure they are not being used in audit processing.