Skip to main content

Product Ideas Pipeline

Filter by Idea Status

Filter by Topic

1298 Ideas

Shun Takase
MVP ⭐️⭐️⭐️⭐️⭐️
Shun TakaseMVP ⭐️⭐️⭐️⭐️⭐️

【InField】It would be helpful if automatic switching of certain status filters could be restricted.Gathering Interest

If you perform the following actions in InField while status filters (“Ready,” “In Progress,” and “Done”) are set, I believe the status filters will automatically switch.① If you change the “Done” checklist to “In Progress,” only the “In Progress” filter will remain② If you change the “In Progress” checklist to “Done,” only the “Ready” filter will remain③ When you start reviewing a checklist marked as “Ready,” only the “In Progress” filter remainsRegarding point ③, I believe this is by design since it’s a natural flow considering the user’s workflow; however, we’ve received feedback from our users that points ① and ② are somewhat cumbersome to use.① ⇒ In our company, when an approver reviews the checklists Doned by an inspector, they sometimes review them all at once using the following workflow; however, this creates extra effort when instructing a re-inspection.Workflow OverviewConduct inspection (Inspector)⇒ Once the inspection is Done, change the checklist status to “Doned” (Inspector)Repeat this for each checklist.⇒ Review all Doned checklists at once (Approver)⇒ Change the status of checklists requiring re-inspection back to “In Progress” and instruct a re-inspection*Note: When changing the status from “Doned” back to “In Progress,” the filter defaults to “In Progress,” so we must apply the “Doned” filter again to review the next Doned checklist.② ⇒ In our company, inspectors often check multiple checklists simultaneously during a single round. However, when one checklist is Doned and the “Ready” filter is applied, we have to switch the status back to “In Progress” to view the checklists being processed in parallel.If this is an intentional design, it is fine as is; however, if there is no specific reason for this behavior, we would appreciate it if you could implement a specification that retains the filter settings for the scenarios described in ① and ②.I apologize for making such a detailed request, but I would appreciate it if you could consider this.

Markus Pettersen
MVP ⭐️⭐️⭐️⭐️⭐️
Markus PettersenMVP ⭐️⭐️⭐️⭐️⭐️

Uploading files to Canvas: the list shows data sets I can read, not data sets I can write toImplemented

This is the cause of a lot of frustration from our users at the moment. When trying to manually upload a file to Canvas you need to select a data set. However, the list you get is not the data sets that you can actually upload a file to, but simply a list of all datasets you have read access to. This makes it really difficult to identify the data set that you can actually use as there is no indication before you click upload and get an error popping up.In general end users of CDF at us will not have access to upload files manually to most of our data sets in production due to governance. Which is why we’ve set up a dedicated data set for this purpose. So we think a better solution would be if this list showed all the data sets that the user could actually upload to (all data sets the user has write access to) rather than all the data sets that will produce an error.Or at the very least have some kind of an indicator of the access level. Trial and error on the user side here is just a nuisance. We don’t see the point in showing all the data sets that will fail without indicating that they will fail.The intended audience for Canvas are not the developers that know all aspects of our implementation of CDF, but the domain experts that know the data. We want their experience to be as seamless as possible and right now it is not, and to avoid the system even allowing for these kinds of mistakes. Markus PettersenAker BP - Technical Domain Architect for CDF