@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.
Posts made by SadiqA2304
-
RE: New field request: Contact.FirstOrNickname
-
New field request: {Contact.USPTORegNumComma}
{Contact.USPTORegNumComma}
- Returns Contact's registration number with a comma where appropriate
Example 1:
{Contact.USPTORegNum} = 11222
{Contact.USPTORegNumComma} = 11,222Example 2:
{Contact.USPTORegNum} = 100000
{Contact.USPTORegNumComma} = 100,000 -
New field request: Contact.FirstOrNickname
I'd like to request a new field for the Contact object:
Contact.FirstOrNickname
- Returns Nickname if Nickname field has one character or more
- Returns First Name if Nickname field is empty
Example 1:
Contact First Name: Jonathan
Contact Last Name: Smith
Contact Nickname: [blank]
Contact.FirstOrNickname = JonathanExample 2:
Contact First Name: Jonathan
Contact Last Name: Smith
Contact Nickname: Johnny
Contact.FirstOrNickname = JohnnyWithout something like this, I'm not sure what the utility of the "Nickname" field is.
-
RE: New field: {Matter. InventorFirstNames}
@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.
-
New field: {Matter. InventorFirstNames}
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.