This publication describes the latest NewStar for Windows (NSFW) version 8.26 changes. It includes a description of known problems and limitations, fixed problems, and enhancements.
Note: The NSFW v8.26 client must be run with NSFW v8.26 server. Additionally, when installing NSFW 8.26 client on Windows NT, you must be logged on as a user that has write access to the HKEY_LOCAL_MACHINE section of the registry. The install program writes information to this section of the registry, and if it fails to write to the registry, NSFW 8.26 will not install correctly.
This publication does not include all changes since NSFW v8.05 was released. Refer to the NSFW v8.10 Release Notes for additional information.
Known Problems and Limitations NSFW
If the Create Form of an assignment lineup has "Commercials" selected, then the first story filed for a particular date will not display when you open the assignment lineup to that date.
Be sure to uncheck/de-select "Commercials" in all of the Create Forms for your assignment lineups.
Print Management (FormPrint Management) does not work in the Lineup subapplication.
Workaround: Use Print Management from any other NewStar subapplication (the Editor, Directory Viewer, and so on).
If you use a slug with two words or more, with more than one space between the words, you will receive a Story Cannot be Loaded (0) message in the Preview pane.
This problem may occur:
- If more than one space exists between words in a script slug.
- If more than one space exists between words in the SLUG column of the rundown.
Fixed Problems NSFW
If a user did not define a Story ID field type in the Create Form subapplication, NSFW would crash when an attempt was made to load the lineup. (The Story ID field type is used for the column or field that displays the slug or title of stories.) This problem has been fixed.
New Functionality: If a user tries to save a Create Form without a Story ID field type, they will be prompted with:
Warning! No Story ID exists in this form. A Story ID must exist for NewStar Lineup to work correctly.
This is only a warning and will not prevent the user from saving the Create Form without a Story ID field type. If a Create Form is saved without the Story ID field type, the first time that it is opened, the user will be prompted with another message:
This lineup is missing a Story ID field. NewStar lineup forms must have a Story ID.
The lineup then closes down. The System Manager must access the Create Form and add a Story ID field before the lineup can be used again.
In the NSFW ADMIN subapplication, if a user was in the Studio Definitions tab and accidentally clicked Delete, a dialog box appeared that prompted you with “Are you sure...” and an OK button appeared, but Cancel was not an available option. If you clicked OK the Studio Definition would be deleted. If you closed the window (click on the x), you also deleted the Studio Definition. (The Studio Definition would also be deleted if you pressed ESC).
This has been fixed by making Cancel an available option.
A problem existed when a user opened an AUX (Auxiliary) page, minimized it, and then did a right-click-Close while the AUX page was located on the Windows taskbar. The AUX page would never reopen. As a workaround, it was necessary to delete the user’s Preferences in order for the AUX page to work again. This problem has been fixed.
New Functionality: NewStar retains information on the AUX page size if it was minimized when closed and also retains window “sizing” instructions. A user can now right-click and Close a minimized AUX page, then reopen it and it will appear in the minimized format. (A user can also right-click on the AUX page and select Restore, which opens the page in its pre-minimized size and position.)
In the NSFW Create Form subapplication, if you selected Line Numbers as a field type (Line Numbers is typically associated with Field 1 in a Create Form), Lineup would crash when you tried to open an AUX page or print selected scripts. This problem has been fixed.
New Functionality: If a user tries to save a Create Form with a Line Numbers field type, they will be prompted with:
Line Numbers field type can no longer be used. It is only here for upgrading purposes. Please use Story Numbers.
This is only a warning and will not prevent the user from saving the Create Form with a Line Numbers field type. If a Create Form is saved with this field type, the first time that it is opened, the user will be prompted with another message:
The Form for this Lineup contains the column type LINE NUMBERS. This column type is no longer supported. Use the Create Form to either change the type of the column or to remove the column from the Form. The lineup then closes down. The System Manager must access the Create Form and change the Line Numbers field type to a Story Numbers field type before the lineup can be used again.
When a user performed a copyflow, NSFW would not prompt for an “overwrite” until at least a “b” version of the script existed. This problem occurred with or without Script Registration turned on. This problem has been fixed. The baseman.exe file has been updated as part of the fix, and the NewStar client has been modified.
New Functionality: User number 1 writes a story called FIRE and saves the story. User number 2 also writes a story called FIRE and attempts to save it to the same script file. The second user will be prompted with:
Versions different, cannot overwrite.
The user must register the script before proceeding with the save. (Previously, the second user could have saved the story without being notified of the overwrite to the other script.)
User access to IXA was not working correctly.
Example: A user with an access level of “None” could still send files to the IXA, search the IXA, and kill items in the IXA. This problem has been fixed.
In addition, the wording of IXA access in the ADMIN Users tab has changed slightly:
Read/Write – user can send files to the IXA and search it (same functionality as “Write” was formerly)
Read/Write/Kill – user can send to, search, and kill IXA stories (same functionality as “Full” was formerly)
Turning off a user’s Popup Send access in the NSFW Chat subapplication did not prevent the user from sending Popup Send messages. This problem has been fixed.
A problem existed in which slugs were not being saved when creating and saving personal files and when sending mail. This has been fixed.
New Functionality ADMIN
Editorial Restriction is a new feature for NSFW v8.20. It allows a site to define the level at which a script becomes restricted. This feature is defined to work within the existing NewStar definition of Editorial Levels 1, 2, and 3 (Writer, Editor, and Manager).
Editorial Restriction is a global setting in the ADMIN SYSDEF tab. It can be set to 1, 2, or 3, with 1 as the default. A setting of 1 matches the way your system was configured prior to creating this new feature.
If the Editorial Restriction level is set to 2, then once a script has reached Editorial Level 2, only level 2s and higher may make changes to the script. Level 1 users will not be allowed to register or save an unregistered version of a script at any time.
If the Editorial Restriction level is set to 3, then once a script has reached level 3, only level 3 editors may make changes. Level 1 and 2 users are not allowed to register or save an unregistered version of the script at any time. When a user encounters a restriction, this message appears:
This script has been restricted to level ‘n’ editors only!
Users will not be allowed to proceed any further, other than to save the script with a different slug, or in a different file (current mechanisms). Additionally, if users have script override ability, they cannot override a registered script if the level of the user with the script registered is the same or higher than the Editorial Restriction level. If the Editorial Restriction is 2 or 3, the Save dialog will be enhanced to show a check box with the label:
If a user selects this check box then the action of “saving” the script will change the script status to 11, and also change the traffic light in the lineup to a red light.
Example: If the script status is 33a and the user chooses to “reverse copyflow” the script, it will change to 11b.
When users select the ADMIN Users Generic Access tab, the method of changing user access for IXA and Create Form has been updated to “radio” buttons for the options: None, Read, Read/Write, and Read/Write/Kill. Note:The above functionality was not implemented for ADMINGroup Modify, however, the options do work correctly. (FYI: Write=Read/Write and Full=Read/Write/Kill)