Cognite InField: YES/NO options for template status fields

Thanks for posting! We discussed this one in our Celanese meeting on Tuesday, and I believe we understand the need and we want to support this. 

As mentioned on Tuesday, we currently don’t have this on our roadmap for Q4, but we’ll do an assessment and see when this can be included. Thanks again! 

@Kristoffer Knudsen Is there any update on this?

@Benjamin A Onweni there is an update and feedback session scheduled Tuesday next week. Let’s let the Utilities unit interact with the product team for any followup questions/feedback on this product idea.  thanks!

Hi @Benjamin A Onweni!

As Crystal mentions, happy to interact on this topic on Tuesday. Although we want to incorporate this use case and totally understand the need, we are not planning to do it this year. 

Br,

Kristoffer  

As we scale Infield, there are lot of requirements to digitize checklists as we go paperless on rounds/checklists but requiring YES/NO or other text options. I would start with YES/NO first. Is there a way to include this in an upcoming sprint at the soonest?

Hi @ibrahim.alsyed ! 

YES/NO, as well as other types of “custom states” that you might have in the current “paper-based” round/checklists, is something that we will have functionality for. We do not want to implement this on a case-by-case basis (e.g. only doing YES/NO), but rather have a robust and flexible way of doing any “custom state” you need.

When do you think we have such flexibility? Q1?

End of Q1 is the current plan 

Hi @crgomez13 ! Just to update on this feature request. This functionality will be available to you out-of-the-box with InField v2 once you are migrated over. When building Template items/task you can utilise a component called “custom labels”, where you essentially have the possible to define any type of custom buttons you might need (e.g. yes, no). 

Br, 

Kristoffer