Improvements:
1. Departments and roles order from the output file now identical to order on breakdown table of the scope
2. Now the user is unable to create Scope of Work Deliverable without a specified budget.
3. User is able to configure a breakdown table structure in the output editor. First of all, the user should add a breakdown table into the output file. Click on the block in output editor and type '#{' and select 'Breakdown Table'. Table will be inserted into the output block immediately.
After table was inserted user may configure which data should be displayed. Double click on the table and configuration menu will be displayed.
Select data which you want to see and save output template.
4. Custom date ranges were implemented for the duration of:
- Single Scope
- Scope of Work
- Single scope inside Scope of Work
- Deliverables
If user want change type of duration of a scope or deliverable he should open duration drop-down.

In duration drop-down user will have few options for specifying duration of a scope or deliverable.

He can specify specific time span or duration of scope or deliverable in days.

Bug fixes:
- Fixed an issue with output editor when the Second Party Table widget was moved or deleted and reinserted, all content beneath it was broken (SE-2024)
- Fixed an issue when the client was unable to retrieve published Scope of Work after login (SE-1999)
- Fixed an issue when two same components in different sizes were not merged automatically after size was changed to the same value for both components (SE-1866)
- Fixed an issue when the user was unable to generate the output template (SE-1942)
- Fixed an issue when library component discipline which was created automatically after ratecard version was changed has no used roles from ratecard (SE-1971)
- Fixed an issue when the user was unable to use fixed cost library deliverable for a single scope (SE-1993)
- Fixed an issue when tables in output word document were formatted incorrectly (SE-2025)
- Fixed an issue when brand ratecard was not applied to SOW after SOW creation (SE-1963)
Comments
0 comments
Please sign in to leave a comment.