Support Forum
Hi
1. How you determine which activity is critical?
2. Have we have to pass any extra fields from backend. like totalSlack.
3. In Demo data set i can see you don't pass any extra fields.
4. But in
Columns columns : [
{ type : 'name' },
{ type : 'earlystartdate' },
{ type : 'earlyenddate' },
{ type : 'latestartdate' },
{ type : 'lateenddate' },
{ type : 'totalslack' }
You use this why . Is total slack auto calculated.
1. How you determine which activity is critical?
2. Have we have to pass any extra fields from backend. like totalSlack.
3. In Demo data set i can see you don't pass any extra fields.
4. But in
Columns columns : [
{ type : 'name' },
{ type : 'earlystartdate' },
{ type : 'earlyenddate' },
{ type : 'latestartdate' },
{ type : 'lateenddate' },
{ type : 'totalslack' }
You use this why . Is total slack auto calculated.
Both totalSlack and critical fields are automatically calculated.
A task is considered to be critical if its delaying causes the project delay. The field value is calculated based on totalSlack field value.1. How you determine which activity is critical?
No, you shouldn't pass any extra fields from backend. totalSlack is calculated too. Total slack is amount of working time the task can be delayed without causing a delay to the project end.2. Have we have to pass any extra fields from backend. like totalSlack.
Yes, that's correct. In examples/_datasets/criticalpaths.json we don't have any extra fields related to slack3. In Demo data set i can see you don't pass any extra fields.
The lines you provided from examples/criticalpaths/app.js are correct. Yes, total slack is autocalculated.4. But in
Columns columns : [
{ type : 'name' },
{ type : 'earlystartdate' },
{ type : 'earlyenddate' },
{ type : 'latestartdate' },
{ type : 'lateenddate' },
{ type : 'totalslack' }
You use this why . Is total slack auto calculated.
Pavlo Miklashevych
Sr. Frontend Developer