[rt-users] Commandline interface

[Andy Harrison]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Tue, 17 Feb 2004 13:34:52 -0600, Patrick Hurley wrote
Subject: "RE: [rt-users] Commandline interface"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

> I'm personally in the middle of attempting to modify SelfService so it
>  would actually use custom fields -- we definitely need specific
>  information from users, and I don't think making everyone privileged is
>  a decent solution.  I find it interesting that the perl code for ticket
>  creation in SelfService is rather different than the code used for
>  ticket creation in the privileged interface (under /share/html/Ticket).
> 
>  Of course, being new to perl doesn't make it any easier.

I found it easier just to take the Ticket/Create.html doc and make a
custom version of it.

Then I made custom versions of /Ticket/Elements/EditCustomFields and
/Ticket/Elements/EditCustomField and pointed my newly created document
(Systems-Create.html) to the new EditCustomFields doc, which needed to
be changed to point to my new EditCustomField doc.

EditCustomFields isn't very different from stock at all, mainly it's
additions to point to a new mason doc that I created so that you can
click on a link and pop up a little window that displays a table with
values and descriptions for the clicked custom field.

I modified EditCustomField more heavily.  It has dynamic rowsize for
custom fields of type 'FreeformMultiple' with a max of 30.  And also a
few cheesy lines that choose different SELECTED items for custom
fields of type 'Select', like:

$Default = "CSS" if $CustomField->Name eq "Group";

% if ($TicketObj) {
  <% $Values->HasEntry($value->Name) && ($selected = 1) && 'SELECTED' %>
% } elsif ($Default) {
  <% ($Default eq $value->Name) && ($selected = 1) && 'SELECTED' %>
% }


-- 
Andy Harrison
(full headers for details)