Global lists: Deliverable types [in-depth guide]
Guide contents: System setup | Deliverable custom fields | Approval process | Resources
This feature allows you to create a more customized deliverable review/workflow process that goes beyond the default internal & client steps.
NOTE: To access this setup, you must first enable 'deliverable types' from Transaction preferences > Deliverables > Use types with deliverables.
Menu > Admin/manager > System setup > Global lists > Deliverable types
Here you can add & edit deliverable types.
Type: Label the type of deliverable so your users can easily recognize what this type's workflow entails.
Color: You can color code each type for when viewing your deliverables in the Deliverables board.
Description: Only visible here. Used for administrative purposes to add more details regarding this type.
Custom fields: If left blank for all types, then the system will pull from the deliverable custom fields in system setup. If this is populated for any one deliverable type, then you must use custom fields on all types you want there to be custom fields on.
Approval process: This allows you to create a unique approval workflow process.
Active: Allows you to make a type inactive, so no one can use it going forward. But also allows you to make it active again.
Deliverable custom fields
As described above, there are two places for custom deliverables-related fields. It comes down to what your needs are that will determine how or if you need to set these up.
These can then factor into your custom reporting needs or how you set up the deliverables board.
All the same.
If you want all deliverables to have the same pool of custom fields, set these up in Menu > Admin/manager > System setup > Custom fields > Deliverable fields.
Unique to each type.
If you want custom fields to be unique to all types, then click on Edit within the row of the Deliverable type.
Any previously made deliverable custom fields or other fields made in other types will show here as available fields. From there, move them to the current layout to be available for this deliverable type only.
This is where this feature has the most benefit. Where each type can now have its own approval process defined, regardless of which project you create it for.
From the type's row, click on Edit to define its process.
Add steps, give them a step name, instructions and send options.
When adding people to the approvers & notify lists, you can define specific users or pull from key people.
Key people by default, allow you to choose from 'account manager' (on the project), 'primary contact' (on the Project), 'billing manager' (on the project) and 'project manager' (if enabled and also on the project).
In the example below, you can see additional defined key people (from Transaction preferences > Projects) that you can then assign to each project setup.
Additionally, you can pull users who are assigned a matching service in the team of the project. This works great if you assign a default service to each of your users.
NOTE: If no user meets the requirements on the project when you create the deliverable, then that specified approver or notify is not added to the round and acts as if it was not ever part of its process.
Transaction preferences [in-depth guide]