tracker issue : CF-4198269

select a category, or use search below
(searches all categories and all time range)
Title:

Chained task configuration bug

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Lahebullah Sharief Shaik Mohatad / Lahebullah Sharief Shaik Mohatad ()

Created: 01/17/2017

Components: Administrator

Versions: 2016

Failure Type: Non Functioning

Found In Build/Fixed In Build: current /

Priority/Frequency: Normal / All users will encounter

Locale/System: ALL / Windows 7 64-bit

Vote Count: 0

Problem Description:
When we try to configure chained tasks thru Administrator it is not saving as a chained task with in neo-cron.xml. instead it is defaulted to Frequency > Repeat and it is setting itself day and time it is running for the first time after parent is executed and there on it is running independently.

ref : https://bugbase.adobe.com/index.cfm?event=selectBug&CFGRIDKEY=4196251

Steps to Reproduce:
Create a parent task, set frequency to daily and URL: <path of job> on-complete give reference to <task name : Group name>
Create another task set frequency to Chained Task and give URL <path of Job> provide a task name and group name, should match to on-complete values within parent task.

Actual Result:
1.after saving the job. Under list of jobs please look at Duration and interval,. Duration will be date time and interval is Daily on both jobs.
2. If you check neo-cron.xml, Chained node is marked as FALSE
<var name="chained"><string>false</string></var>

Expected Result:
Under duration only parent job should have date and time and interval, Child job should display as "Chained Task" under Duration and interval should be Blank.
If you check neo-cron.xml, Chained node should be "True"
<var name="chained"><string>true</string></var>

Any Workarounds:
If you configure jobs using <Cfschedule> tag, Then tasks are configured correctly. and neo-cron.xml values are also looking good.

Attachments:

Comments:

Hi, We have migrated the previous bug. Link to the bug on Tracker: https://tracker.adobe.com/#/view/cf-4196251. We had missed the bug during migration but it is available now. Hence closing this bug. Thanks, Suchika.
Comment by Suchika S.
1325 | January 23, 2017 08:06:42 AM GMT