Community
Participate
Working Groups
If one is creating a number of artifacts of the same type, and OSEE is configured to have quite a large number of artifact types, it can be painful to have to keep re-selecting the artifact type. If OSEE remembered the last artifact type selected, this problem would be removed.
I managed to just barely implement this improvement, but it was amazingly difficult due to the way that dialog was written. Since the quality of the code I came up with is so abysmal, I'd rather hold back until we can rewrite the dialog from scratch. Why are you creating large numbers of artifacts by hand? It's not necessarily the wrong way of doing what you need to do, but normally people import artifacts in bulk rather than create them natively.
An example is our "Signal/store" artifact type. When a user is defining the characteristics of a signal, it is easy to enter into OSEE directly. The user creates the textural requirements, either in Word and then using the xml import, or more typically by copying the template artifacts from the template branch and then populating them using OSEE's Word editing. They then create the outgoing signals by going to the correct folder and just adding the artifacts (which is where this dialog not remembering is a nuisance) and filling in the attributes using the OSEE GUI.
