[#13126] - Scheduled job parameters not loaded when editing

Category:
Bug report
Priority:
Urgent
Status:
New
Project: Severity:
Critical
Resolution:
Open
Component: Reproducibility:
Always
Assigned to:
5

When editing a schedule job input control values are not filled with the job parameter.
Every input control shows the default value.
I tested it with the latest Firefox and Chrome.
A practical example, I have a report that's scheduled many times, every job has different parameter values.
If I edit one job the parameters are displayed with the default values for every job despite the job report is correctly configured.

Developer tools confirm this.

The response to the call that loads the job
GET http://<server>/jasperserver/rest_v2/jobs/5250?_=1601617687643
returns a json with the correct parameters
{
"id": 5250,
"version": 7,
"username": "jasperadmin",
"label": "<label>",
"creationDate": "2018-11-14T11:28:20.612+01:00",
"trigger": {
"calendarTrigger": {
"id": 5247,
"version": 0,
"timezone": "Europe/Rome",
"startType": 1,
"misfireInstruction": 0,
"minutes": "4",
"hours": "7,13",
"daysType": "ALL",
"monthDays": "",
"months": {
"month": [
"1",
"10",
"11",
"12",
"2",
"3",
"4",
"5",
"6",
"7",
"8",
"9"
]
}
}
},
"baseOutputFilename": "<outfile>",
"outputLocale": "it_IT",
"outputTimeZone": "Europe/Rome",
"source": {
"reportUnitURI": "<report-uri>",
"parameters": {
"parameterValues": {
"Magazzino": [
"2"
],
"DescReparto": [
"PRESSOPIEGA"
],
"Media": [
"2400"
],
"Reparto": [
"GA06"
],
"TipoValore": [
"T"
],
"Riferimento": [
"C"
],
"GG_RIF": [
"5"
]
}
}
},
"outputFormats": {
"outputFormat": [
"PDF"
]
},
"repositoryDestination": {
"folderURI": "/Report/Produzione",
"id": 5248,
"overwriteFiles": false,
"sequentialFilenames": false,
"version": 7,
"saveToRepository": false,
"usingDefaultReportOutputFolderURI": false,
"outputFTPInfo": {
"userName": "anonymous",
"type": "ftp",
"port": 21,
"implicit": true,
"pbsz": 0,
"propertiesMap": {}
}
},
"mailNotification": {
"bccAddresses": {
"address": []
},
"ccAddresses": {
"address": []
},
"toAddresses": {
"address": [
""
]
},
"version": 7,
"id": 5249,
"includingStackTraceWhenJobFails": false,
"messageText": "",
"resultSendType": "SEND_ATTACHMENT",
"skipEmptyReports": false,
"skipNotificationWhenJobFails": false,
"subject": "<subject>"
}
}

The call to set the input controls fails
GET http://<server>/jasperserver/rest_v2/reports/<report-path>/inputControls/selectedValues
{
"selectedValue": [
{
"id": "DescReparto",
"options": [
{
"label": "~NULL~",
"value": "~NULL~"
}
]
},
{
"id": "Riferimento",
"options": [
{
"label": "~NULL~",
"value": "~NULL~"
}
]
},
{
"id": "GG_RIF",
"options": [
{
"label": "",
"value": ""
}
]
},
{
"id": "Media",
"options": [
{
"label": "",
"value": ""
}
]
},
{
"id": "TipoValore",
"options": [
{
"label": "---",
"value": "~NOTHING~"
}
]
},
{
"id": "Reparto",
"options": [
{
"label": "~NULL~",
"value": "~NULL~"
}
]
},
{
"id": "Magazzino",
"options": [
{
"label": "~NULL~",
"value": "~NULL~"
}
]
}
]
}

Because of this, the job parameter values must setted every time although they are lost on save.

v7.8.0
Schedules
m.longo's picture
63
Joined: Oct 24 2012 - 4:42am
Last seen: 6 days 4 hours ago

12 Comments:

#1

We have migrated a bunch of reports to a new server, but are now unable to save a parameter value when creating a scheduled job. So you create the schedule, select a value (i.e. client) from a parameter single select query, list of values, or single value input. Add output options & notifications (at which point the the parameter still exists). Save the schedule, go back in to have a value of NULL ? No problem running the reports manually with the parameters, and the same reports worked correctly on the previous server. Have compared settings & permissions with previous server, and can see no differences.

#2

A similar problem is reproduced when you enter a parameter value in the schedule and then save it. Please fix this bug as soon as possible.

#3

Any solution for this issue? We are facing the same problem after migrated our reports to a new server.

#4

We have the same issue with version 7.8
I tried it upgrading to same database and a fresh install with import same result.
Also a fresh install with creating a new report

#5

Experiencing the same issue, just upgraded our Jasper server and now scheduled jobs will not save parameters for new or pre-existing jobs. This is something that needs resolved right away.

#6

Same problem
after update

#7
  • Priority:Urgent» None

I had the same problem, I solve it by applying the latest 7.8.0 hotfix.

#8
  • Priority:None» Urgent
  • Severity:Block» Critical

Where can I find the hotfix?
try this page but direct link doesn't work
https://support.tibco.com/s/article/TIBCO-JasperReports-Server-v7-8-0-cu...

#9

Where can I find the hotfix?
try this page but direct link doesn't work
https://support.tibco.com/s/article/TIBCO-JasperReports-Server-v7-8-0-cu...

#10

Another hot fix release today.
The direct link for this one does not work.
It gives error in Chrome and Mozilla.
The version that is in the community download area is not the latest release of the product. That is 7.9 I do not know if that
version has the same issue.
It would be nice if the community version was on the same release version. It might lead to a faster resolution.

A new Release Announcement has been published.

Title: TIBCO JasperReports Server v7.8.0 cumulative hot fix 20210406_1035 is now available

Product: TIBCO JasperReports Server

Link: https://support.tibco.com/s/article/TIBCO-JasperReports-Server-v7-8-0-cu...

#11

Is there any option to resolve this critical issue available to users of Community Edition?.. Apart from downgrading back to 7.5.0

#12

Same issue with version 7.8. New Install/New report/New schedule. Edit schedule - parameters are back to default.

Feedback