AppColl Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Groups
    1. Home
    2. SadiqA2304
    3. Posts
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 16
    • Posts 72
    • Best 26
    • Controversial 3
    • Groups 0

    Posts made by SadiqA2304

    • RE: Task-Specific Background Color

      @BrandonK6644 Whoops, loos like I had the same idea, but a few weeks later https://forum.appcoll.com/topic/343/set-task-background-color-based-on-taskstatus?_=1748361445416

      posted in Product Requests
      S
      SadiqA2304
    • Set task background color based on TaskStatus

      Currently we are able to set a task background color based on deadline type and due date:

      5a3db216-5579-4e80-94fa-564ae56fbd4e-image.png

      It would be be helpful to be able to set the task background color based on other attributes such as TaskType or TaskStatus.

      posted in Product Requests
      S
      SadiqA2304
    • RE: Set "Favorite" form letters/customize form letter list

      @support_appcoll Any movement on this?

      posted in Product Requests
      S
      SadiqA2304
    • RE: "Clear own locks" button

      @joe_appcoll Nice, thanks

      posted in Product Requests
      S
      SadiqA2304
    • RE: "Clear own locks" button

      Any movement on this suggestion? This would remove a recurring source of frustration if implemented.

      posted in Product Requests
      S
      SadiqA2304
    • RE: Client Specific Billing Item Generation

      @BrandonK6644 What is the difference in your suggestion vs. having client-specific transient tasks that themselves trigger billing items?

      posted in Product Requests
      S
      SadiqA2304
    • RE: Ability to specify whether USPTO e-Office Action tasks default to Transient Events

      @ChristianS9906 I agree. For example, just got this today:

      12cc729e-c783-476c-b386-ab34cff7673e-image.png

      "review e-office action" and "review uspto communication" for the same item. No need for this.

      posted in Product Requests
      S
      SadiqA2304
    • RE: Automatically generated forms should use the latest USPTO information

      @RichardS3059 Do you have form letters attached to automatically generated tasks that are triggered when an eOfficeAction is received?

      posted in Product Requests
      S
      SadiqA2304
    • RE: Automatically generated forms should use the latest USPTO information

      @gregg_appcoll All first actions/notices of allowances on my account have this issue.

      a3759ad4-85a5-4865-b78f-7cf2b2a75b7b-image.png

      posted in Product Requests
      S
      SadiqA2304
    • Automatically generated forms should use the latest USPTO information

      Automatically generated forms, which are triggered by USPTO eOffice Actions, may use out-of-date information in certain circumstances, such as first Office Actions.

      In the initial stages after an application's initial filing, the USPTO has placeholder information is in the USPTO system such as "Docket Central" as the examiner and "OPAP" as the art unit. This information gets updated by the USPTO prior to the first Office Action being sent out.

      As one (basic) example, I have an Office Action Response template that is generated when an Office Action is received. This template populates basic bibliographic information, such as title, inventor, examiner, art unit, etc. In the current implementation, Appcoll does not update the information in the Appcoll system before automatically generating documents; it uses whatever was in the system before. Appcoll updates its internal information after generating documents based on an eOfficeAction. On second and subsequent actions (with no examiner or AU change), this works fine. However, on first actions, it results in situations like Appcoll-generated form fields getting populated with the placeholder information such as "Docket Central" and "OPAP."

      posted in Product Requests
      S
      SadiqA2304
    • RE: Email Intake address simplification

      @GeorgeJ4336 For what it's worth, I have only ever used Appcoll email intake as a CC, and I would imagine this is the intended use

      posted in Product Requests
      S
      SadiqA2304
    • RE: Email Intake address simplification

      @scott_appcoll Is there any concern with ambiguity here? If I have a first matter with MATTER ID 1234 and I have a second matter with MATTER ID 4321 and ATTORNEYREF m1234, wouldn't they both get resolved by [AccountIntakeID]m1234@intake.appcoll.com?

      posted in Product Requests
      S
      SadiqA2304
    • RE: Email Intake address simplification

      @scott_appcoll Nice, I think this works. Can we get an option to choose the new format in appcoll-generated notification emails as well?

      7eff1477-fa22-4818-9fc4-1b7c5e723a2d-image.png

      posted in Product Requests
      S
      SadiqA2304
    • RE: Email Intake address simplification

      @scott_appcoll Thanks for adding this so quickly. As @GeorgeJ4336 said, can you provide an example of the new format? It may be helpful to provide (1) an email address following the old format and (2) an email address, for the same matter, following the new format

      posted in Product Requests
      S
      SadiqA2304
    • RE: Email Intake address simplification

      @BrandonK6644 I have made this request before as well. This is better than having Appcoll's internal matter codes (sequential matter number for your account) as a client-facing email address. The simplest way to implement it would probably be to add a mapping between what they already have, and the email address we desire. This could be done on a per-matter basis, and would need a code/differentiator between different accounts. Example implementation:

      Friendly intake email address prefix for BrandonK's account: BK
      Friendly intake email address prefix for SadiqA's account: SA
      *Each account administrator may specify their own prefix via admin dashboard, so long as it is unique from all other account prefixes.

      BrandonK's matter:
      Attorney Ref: FOO123
      Appcoll Matter ID: BrandonK001
      Appcoll default intake email address (current implementation): BrandonK001@intake.appcoll.com
      Friendly intake email address (default): BKFOO123@intake.appcoll.com
      Friendly intake email address (customizable via Matters module UI; prefix is not changeable): BKpatent123@intake.appcoll.com

      SadiqA's matter:
      Attorney Ref: FOO123
      Appcoll Matter ID: SadiqA001
      Appcoll default intake email address: SadiqA001@intake.appcoll.com
      Friendly intake email address (default): SAFOO123@intake.appcoll.com
      Friendly intake email address (example customized address): SAmatter456@intake.appcoll.com


      Emails to BKFOO123@intake.appcoll.com and BrandonK001@intake.appcoll.com are routed to BrandonK's "FOO123" matter

      Emails to SAFOO123@intake.appcoll.com and SadiqA001@intake.appcoll.com are routed to SadiqA's "FOO123" matter

      ^ The client doesn't need to see the arbitrary Appcoll matter ID in the email fields; firm/account code is used to route emails to the correct account and matter, even if attorney docket number itself is ambiguous

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field formatting code to add periods after single letters

      @gregg_appcoll Thanks, looks like it's working. For Examiner names, I'm doing

      {Matter.Examiner(ToTitleCase, AddPeriodToSingleCharacter)}

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field formatting code to add periods after single letters

      @gregg_appcoll Has this been added?

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field: {Matter. InventorFirstNames}

      @gregg_appcoll These fields do not work correctly with two inventors. They populate as:

      Inventor1, and Inventor2

      There shouldn't be a comma here.

      posted in Product Requests
      S
      SadiqA2304
    • Improve workflow for adding Continuations

      I've used "duplicate matter" and "multi-country duplicate" for adding a Continuation of a matter, and found that "multi-country duplicate" works a little better. Ideally, this would require fewer clicks than it already does in order to add a Continuation. One suggestion I had is, when "Utility: Continuation" (or similar) is selected, the same country as the parent should be auto-selected. Unless I'm missing something, "Continuation" of a parent application in the US for example would necessarily refer to a child application in the US.

      2c35517f-8ae3-4783-b351-62e06157d3ac-image.png

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field: {Matter. InventorFirstNames}

      @support_appcoll Great - just to confirm, you'll also implement the {Matter.InventorNicknamesOrFirstNames} field?

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field: {Matter. InventorFirstNames}

      @gregg_appcoll Any updates? It is pretty nuts to be honest that such a simple request has been ignored for so long.

      posted in Product Requests
      S
      SadiqA2304
    • RE: Add Form Generation and Attachment to E-mail Templates

      @JasonP2345 In the email template a33040c3-90c8-4b30-ad0a-aabc44b64152-image.png

      posted in Product Requests
      S
      SadiqA2304
    • RE: Add Form Generation and Attachment to E-mail Templates

      @JasonP2345 You can. Click "Attach any documents linked to task" in the email template editing UI

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field: {Matter. InventorFirstNames}

      @gregg_appcoll have these been implemented?

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field formatting code to add periods after single letters

      @gregg_appcoll Has this been added?

      posted in Product Requests
      S
      SadiqA2304
    • RE: New field formatting code to return last word of a field

      @gregg_appcoll Thanks, I think it's working. I'm doing Examiner {Matter.Examiner(ToTitleCase, LastWord)} to change "Examiner John A SMITH" to "Examiner Smith".

      posted in Product Requests
      S
      SadiqA2304
    • New field formatting code to return last word of a field

      Appcoll allows for some field formatting options, as shown here: https://support.appcoll.com/form-emails-and-letters/formatting-text-fields-in-form-letters-and-emails

      I'd like to suggest an additional formatting code, such as (LastWord), which returns the last word in a field.

      Example:
      Hello Examiner {Matter.Examiner}, = Hello Examiner John A Smith,
      Hello Examiner {Matter.Examiner(LastWord)}, = Hello Examiner Smith,

      This would solve one of the manual corrections we need to perform.

      posted in Product Requests
      S
      SadiqA2304
    • New field formatting code to add periods after single letters

      Appcoll allows for some field formatting options, as shown here: https://support.appcoll.com/form-emails-and-letters/formatting-text-fields-in-form-letters-and-emails

      I'd like to suggest an additional formatting code, such as (AddPeriodToInitials), which adds a period to any letter that appears alone.

      Example:
      {Matter.Examiner} = John A Smith
      {Matter.Examiner(AddPeriodToInitials)} = John A. Smith

      This would solve one of the manual corrections we need to perform.

      posted in Product Requests
      S
      SadiqA2304
    • RE: "Documents" tab in Matters module

      @mike_appcoll 😮

      This is basically what I'm asking for actually

      posted in Product Requests
      S
      SadiqA2304
    • 1
    • 2
    • 3
    • 1 / 3