@BrandonK6644 said in .docx Form Letter templates:
I'd also love to be able to automatically generate a template within a task when the task is generated. Is that possible?
+1 for this request - automatically adding documents to tasks would be a great time saver.
@RichardS3059 OK... so instead of having to remember a "new" field name, you have to remember to type in your proposed new syntax for the "old" field name? I don't see how your proposal makes things easier... in fact seems a bit more complicated. As far as "remembering" field names, I think that's a non-issue - the documentation is available and all fields are provided there. Personally I haven't memorized any field names despite using fields and forms heavily.
In-line editing is great, especially for adding comments. However, the ability to in-line edit a matter number does not seem make sense; is anyone out there frequently changing their matter reference numbers? The problem arises when I try to click the matter reference from the Tasks module in order to go to the Matter page. The in-line edit arrow occupies most of the space so I have to aim my click very carefully, which is annoying and non-user friendly. Currently the only option available is to disable in-line editing entirely, or deal with this.
^ Picture of what I'm referring to. In the Tasks module, it doesn't seem to make sense for the "Matter" field to be in-line edited; every firm I've worked at has had their own internal matter number for a matter set in stone once created.
@RichardS3059 I think it's a better solution to add fields and have Appcoll do the logic on the backend, rather than requesting Appcoll to create a new programming language for its end users. I don't think your solution of using the nickname instead of the first name solves anything at all, either - it is the exact same thing, as you're still just using one field and not two.
{Contact.USPTORegNumComma}
Example 1:
{Contact.USPTORegNum} = 11222
{Contact.USPTORegNumComma} = 11,222
Example 2:
{Contact.USPTORegNum} = 100000
{Contact.USPTORegNumComma} = 100,000
I'd like to request a new field for the Contact object:
Contact.FirstOrNickname
Example 1:
Contact First Name: Jonathan
Contact Last Name: Smith
Contact Nickname: [blank]
Contact.FirstOrNickname = Jonathan
Example 2:
Contact First Name: Jonathan
Contact Last Name: Smith
Contact Nickname: Johnny
Contact.FirstOrNickname = Johnny
Without something like this, I'm not sure what the utility of the "Nickname" field is.
@MarkW5689 IMO this solution has the same problem, which is the need for manual changes to what should be a pretty simple and easy field to be provided to us. For email addresses, your solution works great and I appreciate the info.
I'd like to request a new field in Appcoll, that returns a comma separated list of inventor first names.
Currently, the way we have to do it is like this:
Step 1 - template definition:
Hello {Matter.Inventor1.First}, {Matter.Inventor2.First}, {Matter.Inventor3.First}, {Matter.Inventor4.First}, {Matter.Inventor5.First},
Step 2 - form generation based on template (assume this matter has 3 inventors)
Hello John, Tim, Mike, , ,
Step 3 - manual editing
Hello John, Tim, and Mike,
[["and" inserted and extra commas removed]]
My proposal would eliminate step 3.
Proposed step 1 - template definition:
Hello {Matter.InventorFirstNames},
Proposed Step 2 - form generation based on template:
Hello John, Tim, and Mike,
[["and" inserted and extra fields removed by AppColl backend logic]]
A similar proposal is possible for other lists of variable length, such as inventor full names and email addresses. This would eliminate a lot of manual editing on our end and further reduce likelihood of errors.