cancel
Showing results for 
Search instead for 
Did you mean: 
tSpratt
Level 4

Since upgrading to ROS add-in 2.6.0 our users have been seeing a "Save to Chorus" dialog box - requesting a file name - every time they create a new ROS document and then save it for the first time. While I can see the utility of this option in implementations of Chorus that allow multiple ROS documents per case, in our implementation each case can only have one ROS document and every ROS document is a summary sheet, so the filename is irrelevant and the users are asking why they now have to click through an unnecessary dialog box every time they create a summary sheet.

Is there any way to add a configuration option at the config console level to suppress this dialog box and go back to having the default "DocumentN.docx" filename for ROS documents?

NB: Apologies for selecting the "Chorus: Communications" label for this idea - there is no "Chorus: Revisable Objects", "Chorus: ROS" or "Chorus: Documents" label so I picked what appeared to be closest match. If there's a better match available, please feel free to change the label.

Thanks.

5 Comments
Status changed to: Reviewed
Karen_Hunter
Staff
Staff

This enhancement was added to support simple and complex naming of files on create and was part of improved save and rename requirements.  The current behavior should be using the default name from the file, and on create, you should be able to save the default name with only one click.

For those simpler use cases where the filename is not helpful on the tagline for the source or in the header of the document that is currently open, you are asking for a preference to suppress this dialog on create and use the default name.   Please confirm this is correct.

Please confirm whether or not you save the filename LOB field to the source at all (note that duplicate filenames are not a problem) and if your default filename is populating as expected from the template.  Thanks in advance for additional clarification.

 Karen_Hunter_0-1792764455315.png

 

tSpratt
Level 4

Hi @Karen_Hunter - that is correct; we would like the option to switch the dialog box off (suppress it) entirely, controllable by an option in the Chorus configuration console if possible.

Re your question "Please confirm whether or not you save the filename LOB field to the source at all (note that duplicate filenames are not a problem) and if your default filename is populating as expected from the template.  Thanks in advance for additional clarification" - I'm afraid I don't know where or how the document name is saved (we didn't write the process or the data storage routines, SS&C did all the development work), but I do know the file name is definitely stored as it is displayed on the list of file attachments (and a quick look at the data for one of the attachments shows the file name stored in a Data Dictionary field called "FLNM", if that helps).

Karen_Hunter
Staff
Staff

Thank you for your quick response. 

ROS uses an admin configuration to know which dataname to use when it saves the item and you see a source/attachment in your workspace.  You have confirmed that you do have this configured (it is optional but most implementations do it) in an option table and your data dictionary.

Our ability to allow you to "suppress" this dialog, could happen in several different ways - you have a global requirement that affects all of your users, but we need to allow the ability to configure different users within the organization to decide if they want to prompt for rename on create or not. 

I do not have a ROS release scheduled at this time - as the development team is working on other content related components, but I have added this into our backlog for the next release - it has not yet been estimated but it seems to be relatively small in scope - and you will see the status changed to planned.

Status changed to: Under Consideration
Karen_Hunter
Staff
Staff
 
tSpratt
Level 4

Hi @Karen_Hunter - thank you, that's extremely good to know. I'll pass on the news that the request is under consideration. Thanks again for picking this up so quickly - it's very much appreciated.