Integrate TaskRay with other Salesforce objects
- Use case example: Maybe you want to relate your TaskRay tasks with cases, so you can track those thing together. Or maybe you have a custom object you'd like to relate to TaskRay. Take a look at this article.
- Things to consider: There is a limit of 40 lookup fields you can create on an object in Salesforce. While that is a lot, it is something to consider and something you don't want to over-engineer. You will also want to consider how the lookup is created. Do you need many TaskRay projects to one case, or many cases to one task. This will dictate where the lookup field is created.
Add Custom Fields to TaskRay Objects
- Use case example: A company that has unique fields specific to their use case can add them to TaskRay objects.
- Things to consider: Custom fields can be displayed in the standard Salesforce interface, as well as in the details modals in TaskRay. They can be reported on and will be available as options for adding columns with task information in Plan View, Spreadsheet View, and Template Portfolio view.
Prevent the Completion of a Task When its Predecessor is Incomplete
- Use case example: This is useful when there are tasks that cannot be worked on until it's predecessor task has been completed.
- Things to consider: Dependencies must be enabled in order for the validation rule to work. With the rule activated, users will not be able to finish a task before all dependent predecessor tasks are completed (moved to the Finished column).
Prevent Tasks from Being Finished Until All Checklist Items Are Completed
- Use case example: This is helpful when a task's checklist items are crucial to task completion. This can be used as an added measure to make sure that those steps have been completed.
- Things to consider: This increases the number of clicks it takes a user to complete a project
Add Custom Tabs to Project and Task Modals
- Use case example: The most common use case for this is using custom tabs to pull in related lists on Tasks and Projects. We have also seen customers configure custom screen flows or Visualforce pages that were then surfaced in custom tabs in TaskRay.
- Things to consider: You can only add up to 2 additional customs tabs per object. These tabs can only display Visualforce pages or screen flows.
Exclude Modal Tabs
- Use case example: You may want to streamline the views for your community users. Your community users do not need visibility to the Chatter tab on the Project modal, the Chatter and Files tab on the Task Group modal, and the Chatter, Checklist, and Time tabs on the Task modal.
- Things to consider: This a Premium Edition Feature. This can be customized globally, by user, and/or by profile.
Modify Status Lists and Colors
- Use case example: If the out-of-the-box status lists (Holding, Prioritized, Started, and Finished) don't fit your process' task progression, you can customize them to make more sense for your users. You can also change the colors associated with each status list and the order in which they progress.
- Things to consider: Reordering status lists will also reorganize the columns in Kanban View accordingly.
Record Types (New)
- Use case example: Record Types can be added to TaskRay Projects and Tasks to offer different page layouts and picklist values for different kinds of records or different kinds of users.
- Things to consider: Once Record Types are enabled, it is difficult to reverse the changes. Please take a moment to evaluate how you would like to use Record Types in TaskRay before configuring them for TaskRay objects.
Exclude TaskRay Views
- Use case example: This is useful if you want to tailor the experience of using TaskRay for your organization, or even just a specific set of users (like your customers that use it in a Salesforce Community, for example).
- Things to consider: Excluding views can be done at the global level, Profile, or User level.