Scenario pricing (Guided selling) additions:
- Improve the UX for making the selection of deliverables mandatory: admin can clearly see when they are making deliverables mandatory (“pinning”) or optional (“unpinning”) in the configuration form
- Quantity modifiers now impact the total hours of the hours-based components
- Scope dynamic fields (custom fields) are now available and can be referenced inside scenarios
New feature: Exchange rates
We are excited to release a new feature: convert a scope into a different currency.
- The conversion rates are set up and managed by the admins with the track record of changes
- Users can view a scope that was created in one currency converted to another currency if the conversion rate is set up
- Users can add fixed-fee components in different currencies to scope and convert them to the scope’s base currency on the fly
New feature: Deliverable custom fields (deliverable tags)
We listened to the feedback of our clients and added a new feature to help them manage the deliverables once they are trafficked to the third-party systems.
- Up to two deliverable tags can be added to the deliverables
- The tags can be added in the library to all or some of the deliverables
- When the deliverables are added to scope, the tags can be edited if needed
- The tags can be of the TEXT or single-select DROPDOWN format
- The tags are included in the scope payload for trafficking
Scope dynamic fields
This is our existing feature used primarily for adding extra fields to scope to map them to mandatory fields in the third-party systems to which we traffic scope data.
- We added the ability to view and edit these fields after the scope has been created
Integrations
- We updated our Open API swagger documentation
Scope by Role
While it was possible to build scope by role from scratch and to save and re-use the Tasks, the users were not able to build a catalogue of Tasks prior to scoping.
- We build a Task building page where users can create or edit the Tasks by changing the roles and hours.
Bugs and improvements
- Component was moving with the mouse in cases where the fixed price was edited for components with quantity more than 1
- Date format in scenario pricing date-based calculations was throwing errors when the user’s format was not dd/mm/yyyy
- Scenario pricing – large deliverable names were not fitting into the fields and were mis-formatted
- Enabled SAML 1.0 for SSO authentication
Comments
0 comments
Please sign in to leave a comment.