@ChristianS2558 You could also simply add "under development" in the task title until it's ready for live use?
Posts made by SadiqA2304
-
RE: "Under Development" flag for task typesposted in Product Requests
-
RE: Test PDF documents upon upload to Prior Art module for acceptability by USPTOposted in Product Requests
@GeorgeJ4336 You can already test documents by uploading them in Patent Center. Whenever I have questionable PDFs, I just create a new dummy application in Patent Center and upload them and see if there are errors. IMO this should be very far down on the list for Appcoll to implement, if ever, in view of the numerous suggestions that have been made in this forum that have yet to be implemented.
-
RE: [Meta] Have any of the product requests made it into Appcoll?posted in Product Requests
@mike_appcoll Any idea of when the next feature set/QoL rollout will be?
-
[Meta] Have any of the product requests made it into Appcoll?posted in Product Requests
The oldest post in this forum is nearly 5 months old. There have been suggestions ranging from simple to complex, but it does not appear that a single suggestion has yet been implemented - not even the "escape to cancel" suggestion. What is the point of this forum if none of the requests are actually implemented?
-
RE: Template Emails with Attachmentsposted in Product Requests
Further to this, I'd like form letters to be able to be automatically added to a task when the task is generated.
-
Please fix column formattingposted in Product Requests
Columns in the UI are formatted such that there is a maximum quantity of characters in a column and, regardless of window size or column width, no additional characters are displayed. The following shows the same columns, with different window sizes:

^ Here, no ellipses are shown even though the column is cut off by the window.
^ Here, the column width happens to line up correctly with the ellipses, and it looks as it should.
^ Here, the window size is larger and the column is therefore wider. However, the ellipses don't change, and column now simply has blank whitespace where there could be letters.
^ There is no good reason for this to happen - dynamic columns are a problem that has been completely solved for many years in web page design. -
"Clear own locks" buttonposted in Product Requests
When hitting Back or closing a browser window, Appcoll will keep a page locked for editing. Currently there is an option for an administrator to go into a user's contact page and "clear all locks and filters." I'd like to request an easier and quicker solution: a "clear own locks" button that any user can press in the event that they accidentally navigate away from a page. This would also decouple "locks" and "filters," since this issue doesn't actually have anything to do with filters, and clearing filters is undesirable in these situations.
-
RE: Escape key to cancelposted in Product Requests
@jonah-soundhound-com bump, +1 for this request please
-
RE: New field request: {Contact.USPTORegNumComma}posted in Product Requests
@RichardS3059 I like the idea - but I'm not optimistic that Appcoll will add new syntax when it would be easier for them to add a new field. On the user side of things, learning syntax is a similar amount of effort as looking up/remembering field names is similar effort, if not more effort imo.
-
RE: New Field Request: InventorEmailsposted in Product Requests
+1 for this request (see also a similar topic https://forum.appcoll.com/topic/78/new-field-matter-inventorfirstnames/3?_=1663253526501 )
-
RE: .docx Form Letter templatesposted in Product Requests
@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.
-
RE: New field request: {Contact.USPTORegNumComma}posted in Product Requests
@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.
-
Please remove the ability to edit matter reference numbers in the Tasks moduleposted in Product Requests
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.
-
RE: New field request: Contact.FirstOrNicknameposted in Product Requests
@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.
-
New field request: {Contact.USPTORegNumComma}posted in Product Requests
{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.FirstOrNicknameposted in Product Requests
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}posted in Product Requests
@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}posted in Product Requests
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.