Posts made by SadiqA2304

Appcoll's form generation has been making great strides. It would be helpful to be able to quickly see all documents for a given matter. I'd like to recommend a tab in the Matters page:

(I know my masterful photoshop skills make it hard to see my edits, but I tried to highlight the suggested change in red)

When clicking the "Documents" tab, it would show all documents that have been generated for the matter, which would be similar or identical to navigating to the folder for that matter in the Files module (Top -> Client -> Matter folder).

When adding a document to a task, we are required to click a folder to which that document is added. I'd like to request that the top level folder be set as the default folder, so that we don't have to make this extra click. Users like me have no preference as to which folder the document is placed in - we just want the document to be created so we can use it.

Current result after selecting a document and NOT selecting a folder (e.g., the top level folder):

Desired result after selecting a document and NOT selecting a folder (top level folder pre-populated, eliminating clicks for users who want the document in the top level folder or who have no preference which folder the document is placed in):

@support_appcoll I may have missed it, but have these been implemented?

@support_appcoll Any update on this?

Bump for my request to add a {Matter.InventorNicknamesOrFirstNames}. We are so close, let's please bring this home and get this feature implemented.

@support_appcoll Thank you. Hopefully the nickname option can be incorporated as well, otherwise we're kind of back where we started in situations where inventors go by a nickname.

@mike_appcoll nice

@support_appcoll This helps for now. Hopefully in the near future it gets augmented into a full Contact object.

@ChristianS2558 Would using different browsers or browser profiles accomplish this?

@gregg_appcoll Any update on this one? It's been requested a few times by a few members. One additional request, allow for nicknames as well (similar to the newly added Contact.NicknameOrFirstName field). So the request is the following two fields, both which return a formatted list with commas for 3 or more inventors and an "and" preceding the last inventor:

{Matter.InventorFirstNames}
{Matter.InventorNicknamesOrFirstNames}

@support_appcoll Looks like it works, thank you.

@support_appcoll Yes you are correct about nickname being preferred. Thanks for doing this.

Bump for this request. Although this thread got derailed with an irrelevant discussion about augmenting AppColl's syntax, I believe that a "FirstOrNickname" field would save a lot of time and improve the user experience, as many inventors prefer to be called differently than their formal names.

This will help greatly with form letters such as interview agendas, in which we address the examiner by their name. For example, assume that we have an Examiner named Joe Smith. The Examiner's information is imported from PAIR as "Joe SMITH." If I write a form letter in which I address the examiner, I would write it as:

Hello Examiner {Matter.Examiner},

which would populate as:

Hello Examiner Joe SMITH,

I would then need to manually remove the Examiner's first name, and re-type or otherwise reformat the last name to get what I really want, which is:

Hello Examiner Smith,

Appcoll already has some level of intelligence when importing contacts, such as when importing an Excel file with plain names. Appcoll does create/identify contact records, and populates first/middle/last names accordingly. Appcoll should do this with Examiner names as well.

The ideal user experience would be:

Hello Examiner {Matter.Examiner.Last},

which would give the desired result.

This also provides the benefit of allowing us to maintain examiner contact information, such as emails and phone numbers, which makes our lives easier and reduces time spent finding this information from other sources.

@mike_appcoll New features are great, and it's good to see that after an extremely lengthy wait, some of the suggested features have made it into the system. But it's discouraging that no attention seems to be made to improving the usability or UI of the system, such as to reduce the number of clicks and speed up the actual use of the system. Stuff like escape to cancel, automatically attaching form letters to tasks or being able to email form letters, fixing the column whitespace issue, a "favorite" or "recent forms list, an "inventor first names" field (which has been suggested by multiple people), etc. These are low-hanging fruit that improve usability and can greatly reduce time spent for all users, and it's frustrating that the development emphasis seems to leave these types of concerns in the dust.

Zero updates in nearly a year. Not even the simplest QoL updates have been made. This is frankly nuts. I remember many years ago, Appcoll was very fast to make fixes and implement new features that steadily improved the system and, ultimately, saved us time. There have been dozens of good new ideas thrown out there and none have been implemented. What is going on?

@support_appcoll Pretty good solution!

@support_appcoll Yes, the search tab works, but it's a very bad user experience to type in the same form name each time. Better would be to have my commonly used forms sitting there at the top ready for me to click, instead of obscure forms that I will never use. I thought this was clear, I'm not sure what the response of "use the search box" was supposed to accomplish.

It would be nice if we could more quickly/readily access the form letters we most commonly use, while removing or de-emphasizing form letters we use less or not at all.

@ChristianS2558 You could also simply add "under development" in the task title until it's ready for live use?

@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.

I made this same suggestion in September: https://forum.appcoll.com/topic/128/new-field-request-contact-firstornickname/5?_=1675177027325

@mike_appcoll Any idea of when the next feature set/QoL rollout will be?

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?

Further to this, I'd like form letters to be able to be automatically added to a task when the task is generated.

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.

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.

bump, +1 for this request

@jonah-soundhound-com bump, +1 for this request please

@GeorgeJ4336 Thank you for sharing