Hi All,
Any experts in Front Desk's Word Processor available (either in the community or at SS)?
I am trying to create a series of standard letters - FDDs - in the Front Desk Word Processor based on copy/pastes of treatment provider plan templates from MAIC, Allianz etc.
I am having particular difficulty with creating and changing the no. of columns on a page.
1. When I create a column break, it's not working as I expected.
2. Then, when I use Ctrl-Z to undo it, this isn't working as expected either (it doesn't uncreate the column break, but instead mucks up the formatting and undoes something else).
Searching the Word Processor Help files for help with "column break" gives zero hits.
I confess that I am frustrated to encounter these difficulties in an integral part of the FD software.
Many thanks for help - all tips and/or hand-holding gratefully received!
Joyaa
Here's a screenshot of the top of the page I am trying to recreate from a pdf, just to give you a gist of the changes in columns breaks. Thanks.
Any experts in Front Desk's Word Processor available (either in the community or at SS)?
I am trying to create a series of standard letters - FDDs - in the Front Desk Word Processor based on copy/pastes of treatment provider plan templates from MAIC, Allianz etc.
I am having particular difficulty with creating and changing the no. of columns on a page.
1. When I create a column break, it's not working as I expected.
2. Then, when I use Ctrl-Z to undo it, this isn't working as expected either (it doesn't uncreate the column break, but instead mucks up the formatting and undoes something else).
Searching the Word Processor Help files for help with "column break" gives zero hits.
I confess that I am frustrated to encounter these difficulties in an integral part of the FD software.
Many thanks for help - all tips and/or hand-holding gratefully received!
Joyaa
Here's a screenshot of the top of the page I am trying to recreate from a pdf, just to give you a gist of the changes in columns breaks. Thanks.
Posted 2 years ago
Andrew, Community Manager
Many thanks to everyone for their input.
Julienne - I admit that I agree with your first comment. And thanks for the pdf -> MSWord conversion idea - a great idea under the circumstances.
Indra - re. tables - I need to explore tables in FD's word processor more deeply - thanks.
Sharon - yes, I can see that this would work. Time consuming as I have forms to create for Suncorp, EML and QComp, but feasible. (See my comment below too). Thanks.
Andrew - thanks. First though, please can you clarify how your suggestion reconciles with Smartsoft's advice about moving away from MS Word docs? (Please see image). Also, can you let me know how column breaks work? Specifically, when I put one in and tried to "undo" it via Ctrl-Z, it doesn't work as one would expect. Many thanks, J.
Many thanks everyone.
Julienne - I admit that I agree with your first comment. And thanks for the pdf -> MSWord conversion idea - a great idea under the circumstances.
Indra - re. tables - I need to explore tables in FD's word processor more deeply - thanks.
Sharon - yes, I can see that this would work. Time consuming as I have forms to create for Suncorp, EML and QComp, but feasible. (See my comment below too). Thanks.
Andrew - thanks. First though, please can you clarify how your suggestion reconciles with Smartsoft's advice about moving away from MS Word docs? (Please see image). Also, can you let me know how column breaks work? Specifically, when I put one in and tried to "undo" it via Ctrl-Z, it doesn't work as one would expect. Many thanks, J.
Many thanks everyone.
Andrew, Community Manager
Hi Joyaa
We do recommend using the Front Desk Word Processor where possible for simple documents; this includes letter writing, mail merges and clinical notes. It is an efficient file-format that is quick to process, takes minimal space on a database and includes a medical dictionary. For documents that require more advanced page layouts, we recommend Microsoft Word.
A Column Break specifies when text within a given column should finish and is used to control the distribution of text across multiple columns.
For example, I have some text distributed across three columns:
As per the image above, I want the middle column text to end just after 'END OF COLUMN 2', and the column three text to start.
Placing my cursor where I intend to start column three, I can insert a Column Break.
As below, this breaks the middle column and moves the following text to column three.
In regards to the use of Ctrl + Z, this is not currently applicable to column related actions. You are likely seeing unexpected results as it is applying the undo to the last applicable action, which may have been the entry or deletion of text. We are happy for this to be a known issue as we are not looking to build a full-featured word processor, which would take resources away from working on our core functionality.
We do recommend using the Front Desk Word Processor where possible for simple documents; this includes letter writing, mail merges and clinical notes. It is an efficient file-format that is quick to process, takes minimal space on a database and includes a medical dictionary. For documents that require more advanced page layouts, we recommend Microsoft Word.
A Column Break specifies when text within a given column should finish and is used to control the distribution of text across multiple columns.
For example, I have some text distributed across three columns:
As per the image above, I want the middle column text to end just after 'END OF COLUMN 2', and the column three text to start.
Placing my cursor where I intend to start column three, I can insert a Column Break.
As below, this breaks the middle column and moves the following text to column three.
In regards to the use of Ctrl + Z, this is not currently applicable to column related actions. You are likely seeing unexpected results as it is applying the undo to the last applicable action, which may have been the entry or deletion of text. We are happy for this to be a known issue as we are not looking to build a full-featured word processor, which would take resources away from working on our core functionality.
Thanks Andrew. Your explanation of when to use MS Word (and when not) makes a lot of sense and certainly clarifies what was less clear to me within the help text.
Thanks too for explaining columns. Registering the issue with trying to undo a column break would be a good idea - thank you.
Thanks too for explaining columns. Registering the issue with trying to undo a column break would be a good idea - thank you.
the issue with MS word is (or am i wrong) that you cant create letter tags then to pull the data from Frontdesk database with name, claim number, address and details. So filling in a NSW AHRR means manually flicking between screens and copying and pasting. Alot of our detailed and complex formatted reports where we are uploading photos into them etc we start it in FD then export the shell of the report into Word where it is then finished and then imported back in as a PDF. You then need to make sure the word version is also saved to then allow changes as a later time... A admin timewaster
Andrew, Community Manager
Hi Julienne
There are over 160 letter tags within Front Desk that can be used as part of the Microsoft Word integration. Further, when creating a standard letter in Front Desk, or when opening a Microsoft Word Attachment, the changes are automatically saved back into Front Desk. Word documents can also be converted to PDF automatically when emailing from the Attachments tab.
Note that letter tags do not work if placed inside a 'Text Box' due to a limitation in Microsoft Word.
For further information, please refer to page 311 of our User Guide.
There are over 160 letter tags within Front Desk that can be used as part of the Microsoft Word integration. Further, when creating a standard letter in Front Desk, or when opening a Microsoft Word Attachment, the changes are automatically saved back into Front Desk. Word documents can also be converted to PDF automatically when emailing from the Attachments tab.
Note that letter tags do not work if placed inside a 'Text Box' due to a limitation in Microsoft Word.
For further information, please refer to page 311 of our User Guide.
That's a great idea Sharon. Andrew - is it worth SS uploading a series of such forms into FD as part of the standard package? Would that be more efficient than users in the field attempting to do the same for themselves? You guys would do a great job and it would negate a lot of unnecessary duplication of effort. What do you think?
Andrew, Community Manager
Hi Joyaa
We don't believe it is the role of Smartsoft to collect and maintain standard forms, but rather provide the functionality to store and use these forms.
We have made some forms available in the past, but only on a casual basis. We are more than happy that users share forms that they have created via the Community, so long as there are no copyright infringements in doing so.
We don't believe it is the role of Smartsoft to collect and maintain standard forms, but rather provide the functionality to store and use these forms.
We have made some forms available in the past, but only on a casual basis. We are more than happy that users share forms that they have created via the Community, so long as there are no copyright infringements in doing so.
Thanks Andrew. Can we get the ball rolling by Smartsoft sharing the forms that they have previously made available in the past? I ask because not all FD users utilise this forum, and so it's more efficient if this is first directed to Smartsoft.
Thank you.
Thank you.
Andrew, Community Manager
Hi Joyaa
As per our previous post, we have decided it is outside of our scope to manage a database of standard forms. We don't have reference to previous forms and some of them may even be out of date.
At this time we are closing this post.
As per our previous post, we have decided it is outside of our scope to manage a database of standard forms. We don't have reference to previous forms and some of them may even be out of date.
At this time we are closing this post.
