Okay, I do not think that we are on the same page here.
I guess I am just trying to understand why we can no longer modify the standard web forms, which seemed to work perfectly until recently.
We have the Issues Form that we at the company access from the Desk view.
Within this form, we have a few custom fields that we’ve added, that allows for us to collect specific information concerning the issue (ex. Brand, Model, Serial Number, PO Number, etc). Nothing out of the ordinary.
There is also the Issues Web Form that the customers access.
Both of these are connected to the Issues doctype.
Originally, before a more recent update, I could include any of the custom fields from the Standard Issues Form (Make, Model, Serial) on the Web Form for the end user to fill out. Unfortunately, a recent update has locked the Issues Web form, as well as removed all the fields that were once on there, and so now I cannot include the fields that we need the customers to fill out.
I understand that I can create a new web form tied to the Issues doctype, which I have done (in my case I called the form “Tickets” with the weblink …/tickets), and it does work.
However, the problem is that when the customer clicks on the issue, even if they are on the /tickets page, it takes them to the standard form from the issues page, and not the new one.
I’m the customer, and I want to review and add a PO number to a ticket that I had previously opened.
I go to www.companyurl.com/tickets where I see all the tickets I have opened listed.
I then click on ISS-00001.
It then redirects me to /issues?name=ISS-00001 instead of /tickets?name=ISS-00001
I cannot add my PO number, because I do not see the PO Number field listed on there.
Instead, all I see are Subject, Status, and Description.