It is currently possible to update the layout of CTAs based on CTA type, and it's also possible to update the layout for tasks to display custom fields, however it is not possible to specify different layouts depending on the CTA Type the task is applied to. It would be a great improvement to be able to define a task layout based on CTA Type.
Use case: I have a customer who would like to have a Success Criteria field on Objective tasks only, so that they can document success criteria at both the Objective and Task level. This is not possible without adding a Success Criteria field to ALL tasks. Our work around is to add the Success Criteria in a dedicated section of the Task layout (titled: For Success Plan Tasks Only), however this is not an optimal solution; it is confusing for new employee adoption, and may become an issue if they add GS licenses for other groups.
Change task layout based on CTA type
None
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I have a similar use case where we would like to create a layout specific to Success Plans. In addition, we would like the ability to configure the sections in the layout to be “shareable with persons” (or not) for a Task that is Linked to an objective.
Thank you for explaining the use case. We will follow this threads for more upvotes so as to evaluate it for upcoming roadmaps
Our team has run across two similar use cases in the last week where multiple Task layouts would be beneficial/provide a better end-user experience.
The single task layout is currently leaving us unable to hide fields related to Risk CTAs on other CTA types, including Success Plan Objectives and new CTA types being brought in during a migration.
Resurfacing this idea for consideration.