Cockpit: Custom CTA fields should be visible by default

+100 votes. 

Beneficial requirement when it comes to new custom CTA Types asks are placed by business. Existing standard layout do not show or allow admins to add mandatory field info for CSM’s to populate it for their planning needs. When manual CTAs are created required fields are missed to capture values and later it pulls additional efforts for admins/process owners to follow up.

I concur.

@darkknight agree with this use case. When we do the admin revamp, we will evaluate if we can give finer controls to the order in which fields are displayed. Thanks.

We have had times that custom fields on certain CTA types would be so beneficial, but we actually don’t even bother creating them because they’re so hidden and therefore not well-used. Would love to have the option to hide or not hide them behind this add more detail section. The ideal solution is just being able to decide which fields (and if I’m dreaming in what order) the user sees when creating a new CTA.

This would be a prerequisite to another feature request we would like (being able to require custom fields at CTA creation on specific types)

Would love to see this!

@mindym @jlicciardello Thanks for the feedback. As a part of admin revamp, we are thinking of giving the admin ability the decide the field order.

I don’t see why no - we have the option for linked objects within a CTA as well. You can always assign a default layout we can modify.

@sriram pasupathi any update on if this has been added to the roadmap?

@anirbandutta may you check to see if this is on the near term roadmap?  As custom fields become more relevant for CTAs, having more granular control over the Create CTA layout becomes more of a necessity.  Thx!

@mpatra could you pl share any updates?

@darkknight - We are considering this as a part of our Admin Revamp initiative that we will be working on this in the second half of this year. We will have tentative timelines for this soon.

@mpatra - any further updates on the timeline for this as part of your Admin Revamp initiative? Our users are regularly forgetting these fields which then requires us to do manual data clean-up, so the ability to adjust the positioning/layout would be hugely beneficial. thank you!

Hi @lizcopeland ,

This is under development now. I will keep this thread updated on the status of the project and release dates.

Thanks,

Monica

@mpatra any update on the ETA for this? cc @revathimenon 

Wow, it surprises me that this idea pre-dates the Cockpit Admin revamp. All that work to Horizonize Cockpit without actually improving the functionality or use...very disappointing to see 😔

As @mindym stated - custom fields in CTAs are unusable in current state. They must be above the fold of a CTA layout, and they must have the ability to set as “Mandatory upon creation.”

The fact that this has been an issue for this many years is mind-boggling 😬

This one to me is a no-brainer. It’d also be nice to be able to make certain fields required not just for CTA closure but creation as well.

@wscuphamabnormal you might find this of interest as well: 

• Fields on CTA Should Honor Search Criteria Discovery
• 11 Votes