
Hello, is there a way to use a FreeText to a field like a text area where the user be free to type whatever he wants? Thanks

On 8/17/11 5:02 PM, Wagner wrote:
Hello,
is there a way to use a FreeText to a field like a text area where the user be free to type whatever he wants?
Hi, choose an unused TicketFreeText Field and configure it properly: Admin -> SysConfig -> Ticket -> Core::TicketFreeText then make it visible for the customer: Admin -> SysConfig -> Ticket -> Frontend::Customer::TicketViewNew hth, Roy -- Roy Kaldung e-mail: roy@kaldung.com

I don't want to make the user select a value, I want that he can write
whatever is needed, like a description field, is there a way to configure a
FreeText like this?
Thanks
2011/8/17 Roy Kaldung
On 8/17/11 5:02 PM, Wagner wrote:
Hello,
is there a way to use a FreeText to a field like a text area where the user be free to type whatever he wants?
Hi,
choose an unused TicketFreeText Field and configure it properly: Admin -> SysConfig -> Ticket -> Core::TicketFreeText
then make it visible for the customer: Admin -> SysConfig -> Ticket -> Frontend::Customer::TicketViewNew
hth, Roy
-- Roy Kaldung e-mail: roy@kaldung.com --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

On 8/17/11 8:20 PM, Wagner wrote:
I don't want to make the user select a value, I want that he can write whatever is needed, like a description field, is there a way to configure a FreeText like this?
Yes, there is. E.g. for FreeTextField1 set up TicketFreeKey1 with a proper keyname and leave TicketFreeText1 empty. Roy -- Roy Kaldung e-mail: roy@kaldung.com

Hi Roy,
On Wed, Aug 17, 2011 at 20:28, Roy Kaldung
E.g. for FreeTextField1 set up TicketFreeKey1 with a proper keyname and leave TicketFreeText1 empty.
That is possible, but the TicketFreeText field will be just one single line. You can't configure it to display a text area. Also, you can't store more than 150 characters in a ticketfreetext field. In the upcoming OTRS 3.1 version we'll have a new feature called 'Dynamic Fields' where you could add text-areas, timestamps, and date fields, in a more dynamic fashion than previously. I look very much forward to it... Development for this just recently started. -- Mike

Thanks, thats what I wanted,
150 chracters is enough
but how I do this in Config.pm?
Thanks
2011/8/17 Michiel Beijen
Hi Roy,
On Wed, Aug 17, 2011 at 20:28, Roy Kaldung
wrote: E.g. for FreeTextField1 set up TicketFreeKey1 with a proper keyname and leave TicketFreeText1 empty.
That is possible, but the TicketFreeText field will be just one single line. You can't configure it to display a text area. Also, you can't store more than 150 characters in a ticketfreetext field.
In the upcoming OTRS 3.1 version we'll have a new feature called 'Dynamic Fields' where you could add text-areas, timestamps, and date fields, in a more dynamic fashion than previously. I look very much forward to it... Development for this just recently started.
-- Mike --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Also I need another thing,
I'll have 3 fields, the first 2, the user will enter a number, the 3 field
will be the SUM of the first 2 fields.
How May I do that?
Thanks
2011/8/17 Wagner
Thanks, thats what I wanted,
150 chracters is enough
but how I do this in Config.pm?
Thanks
2011/8/17 Michiel Beijen
Hi Roy,
On Wed, Aug 17, 2011 at 20:28, Roy Kaldung
wrote: E.g. for FreeTextField1 set up TicketFreeKey1 with a proper keyname and leave TicketFreeText1 empty.
That is possible, but the TicketFreeText field will be just one single line. You can't configure it to display a text area. Also, you can't store more than 150 characters in a ticketfreetext field.
In the upcoming OTRS 3.1 version we'll have a new feature called 'Dynamic Fields' where you could add text-areas, timestamps, and date fields, in a more dynamic fashion than previously. I look very much forward to it... Development for this just recently started.
-- Mike --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

You'd need to have either a bit javascript involved or add some back
end logic (and best is probably to do both). You'd absolutely need to
add code, you can't 'configure' this.
Of course, my company would be able to help you out, if needed, ==>
enjoy@otrs.com
--
Mike.
On Wed, Aug 17, 2011 at 21:50, Wagner
Also I need another thing,
I'll have 3 fields, the first 2, the user will enter a number, the 3 field will be the SUM of the first 2 fields.
How May I do that?
Thanks
2011/8/17 Wagner
Thanks, thats what I wanted,
150 chracters is enough
but how I do this in Config.pm?
Thanks
2011/8/17 Michiel Beijen
Hi Roy,
On Wed, Aug 17, 2011 at 20:28, Roy Kaldung
wrote: E.g. for FreeTextField1 set up TicketFreeKey1 with a proper keyname and leave TicketFreeText1 empty.
That is possible, but the TicketFreeText field will be just one single line. You can't configure it to display a text area. Also, you can't store more than 150 characters in a ticketfreetext field.
In the upcoming OTRS 3.1 version we'll have a new feature called 'Dynamic Fields' where you could add text-areas, timestamps, and date fields, in a more dynamic fashion than previously. I look very much forward to it... Development for this just recently started.
-- Mike --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Thanks,
Could you tell me which file should be changed?
Thanks
2011/8/17 Michiel Beijen
You'd need to have either a bit javascript involved or add some back end logic (and best is probably to do both). You'd absolutely need to add code, you can't 'configure' this. Of course, my company would be able to help you out, if needed, ==> enjoy@otrs.com
-- Mike.
On Wed, Aug 17, 2011 at 21:50, Wagner
wrote: Also I need another thing,
I'll have 3 fields, the first 2, the user will enter a number, the 3 field will be the SUM of the first 2 fields.
How May I do that?
Thanks
2011/8/17 Wagner
Thanks, thats what I wanted,
150 chracters is enough
but how I do this in Config.pm?
Thanks
2011/8/17 Michiel Beijen
Hi Roy,
On Wed, Aug 17, 2011 at 20:28, Roy Kaldung
wrote: E.g. for FreeTextField1 set up TicketFreeKey1 with a proper keyname
and
leave TicketFreeText1 empty.
That is possible, but the TicketFreeText field will be just one single line. You can't configure it to display a text area. Also, you can't store more than 150 characters in a ticketfreetext field.
In the upcoming OTRS 3.1 version we'll have a new feature called 'Dynamic Fields' where you could add text-areas, timestamps, and date fields, in a more dynamic fashion than previously. I look very much forward to it... Development for this just recently started.
-- Mike --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Yes, if you want onli a text area, don't check and no fill any TicketFreeText
value. on
*
*
http://server/otrs/index.pl?Action=AdminSysConfig&Subaction=Edit&SysConfigSu...http://localhost/otrs/index.pl?Action=AdminSysConfig&Subaction=Edit&SysConfi...
Now your Freetext is a text area.
2011/8/17 Wagner
I don't want to make the user select a value, I want that he can write whatever is needed, like a description field, is there a way to configure a FreeText like this?
Thanks
2011/8/17 Roy Kaldung
On 8/17/11 5:02 PM, Wagner wrote:
Hello,
is there a way to use a FreeText to a field like a text area where the user be free to type whatever he wants?
Hi,
choose an unused TicketFreeText Field and configure it properly: Admin -> SysConfig -> Ticket -> Core::TicketFreeText
then make it visible for the customer: Admin -> SysConfig -> Ticket -> Frontend::Customer::TicketViewNew
hth, Roy
-- Roy Kaldung e-mail: roy@kaldung.com --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
participants (4)
-
Carlos Andrés Gallego Arboleda
-
Michiel Beijen
-
Roy Kaldung
-
Wagner