nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SetDescription() not working as expected.

Pawan

I am setting the job description in my cgi task using the

$job->SetDescription($jobDesc);

Now the problem is if I give "test description" it is set as \"test description\". Everytime i use " in my description it gets converted to \".

Does anyone encountered this problem?

TS6.7.2 SP2
Sol 9

Find more posts tagged with

Comments

Adam Stoller

I am setting the job description in my cgi task using the
$job->SetDescription($jobDesc);
Now the problem is if I give "test description" it is set as \"test description\". Everytime i use " in my description it gets converted to \".

Does anyone encountered this problem?

TS6.7.2 SP2
Sol 9

Are you saying that it is displayed with \" - or that it appears in the job specification (XML) as \"?

The latter would make sense as otherwise it would break things.

Pawan

Are you saying that it is displayed with \" - or that it appears in the job specification (XML) as \"?

The latter would make sense as otherwise it would break things.

The job description appears with \" in the workflow tab as well as in the job specification file.

jbonifaci

The job description appears with \" in the workflow tab as well as in the job specification file.

Then there is probably something wrong with your code that is populating $jobDesc. Can you please post the remainder of your code?

~Jeff

Pawan

Then there is probably something wrong with your code that is populating $jobDesc...
~Jeff

May be.
Let me try a few more tricks, and I will post the result.

000-PortalList.rptdesign

excel file.bmp

Pawan

Okay, here is what I tried.

my $jobDesc = $cgi->{form}{"jobdesc"};
  print LOG "Before: $jobDesc \n";
  #above line prints "test description"
  $job->SetDescription($jobDesc);
  print LOG "Description:". $job->GetDescription() ."\n";
  #above line prints \"test description\"

When I give "test description" it sets the job description as \"test description\" in the workflow tab wheras & amp;quot;test description& amp;quot; in the job spec.

I am getting the value of a text field after user enters and submits the form and setting it as the job description. So far I found this problem only with " and not with ', @, $, &, etc.

Please note the space in the & and amp; is just in this post, not actually in the job spec file.

jbonifaci

Hmm, I can't reproduce this. I'm on 6.7.2 SP2, but windows and not unix.

There is still an unknown variable in your above code example, we don't know what the value of $jobDesc truly is.

Replace this line:

my $jobDesc = $cgi->{form}{"jobdesc"};

With this line:

my $jobDesc = qq|"test description"|;

Let me know if that produces the same result. If not, there is something funky with the value you are retrieving from the post data.

~Jeff

Pawan

Hmm, I can't reproduce this. I'm on 6.7.2 SP2, but windows and not unix.

There is still an unknown variable in your above code example, we don't know what the value of $jobDesc truly is.

Replace this line:
my $jobDesc = $cgi->{form}{"jobdesc"};
With this line:
my $jobDesc = qq|"test description"|;
....

Thanks for your effort in trying this out.

my $jobDesc = qq|"test description"|;

The result is the same using qq.
Can anyone please try this on your unix box and confirm the behaviour?

Adam Stoller

Okay, here is what I tried.

my $jobDesc = $cgi->{form}{"jobdesc"};
  print LOG "Before: $jobDesc \n";
  #above line prints "test description"
...

Please clarify - does the log show:[indent]Before: test description[/indent]or[indent]Before: "test description"[/indent]If the latter, the problem is that you have double-quotes embedded within your string (which is, I believe, what jbonifaci was indicating) - so instead of doing:
[indent]

my $jobDesc = qq|"test description"|;

[/indent]Just do one of the following:[indent]

my $jobDesc = qq|test description|;
my $jobDesc = "test description";

[/indent]and see if the problem goes away.

Or am I misunderstanding things and you want to put double-quotes in your description and have the show up un-escaped? If that's the case you could try something like:

use HTML::Entities;
my $jobDesc = encode_entities(qq("test description"));
...

This should be the same as:[indent]

my $jobDesc = qq|"test description"|;

[/indent]

Pawan

my $jobDesc = $cgi->{form}{"jobdesc"};
  print LOG "Before: $jobDesc \n";
  #above line prints "test description"
...
Please clarify - does the log show:[indent]Before: test description[/indent]or[indent]Before: "test description"

The above log prints
Before: "test description".

...Or am I misunderstanding things and you want to put double-quotes in your description and have the show up un-escaped? If that's the case you could try something like:
use HTML::Entities;
[/indent]my $jobDesc = encode_entities(qq("test description"));
...
This should be the same as:[indent]
my $jobDesc = qq|"test description"|;
[/indent]

I want to give double quotes in the job description. I tried this and its giving me & quot;test description& quot; in my job description in workflow tab and & amp;quot;test description& amp;quot; in my job spec.

Adam Stoller

The above log prints
Before: "test description".I want to give double quotes in the job description. I tried this and its giving me & quot;test description& quot; in my job description in workflow tab and & amp;quot;test description& amp;quot; in my job spec.

Hmm - okay - then try this:

# you could do this in one line, using two for clarity
my $jobDesc = $cgi->{form}{"jobdesc"};
$jobDesc =~ s|"|''|gsm;
...

That substitution is for a single double-quote to be replaced with two single-quotes. You could use a single single-quote too, depends on what you're willing to live with as a result.

Either that, or find some way to embed

<![CDATA[your-string]]>

in there.

Note: I have not tested either of these approaches in a workflow context - I'll leave that to you...

enlarge_chart.rptdesign

before.png

after.png

brizrobbo

Did anyone ever work out why this happens? We are exhibiting the same behaviour in one of our workflows (yes, we are running on a UNIX machine also :-) ).