Suggest features, upvote favorites, and use the user story format: > As a [role], I want to [action], so that [benefit]. Help us build what you need - post your idea now!
As a user I would like to get a list of all flocs and work orders in a defined space (e.g. within isolation boundaries) so that I am able to easily identify all upcoming takes that have to be executed and group them together for execution.
Feedback from customer:Can “Sign in with project name” be removed? It’s confusing for the users of inField.Importance: Nice to have.Context: When logging on inField for offshore workers.User story: As an offshore user of inField I would like for the app to either:“Remember” my choice of signing in with Microsoft (see picture). Or, have “Sign in with project name” removed.So that the log in process becomes smoother and faster.Picture:Is there a need for “Sign in with project name here”?
It's hard to tell the date of each checklist in the checklist view. As a process expert, it would be nice to have older checklists especially have dates so that it's easier to find more recently opened ones.
On behalf of Celanese Maintain super users: I would like the ability to attach non-contextualized files/documents to my canvas in Maintain. Currently, Maintain only has the ability to attach documents that exist in CDF and have been contextualized to an asset. There are often cases where, in addition to your standard documentation (P&ID for example), supporting files/documents need to be assigned to a work order such as material quotations, images/videos, and PM paperwork (equipment inspection forms) that would not be available in CDF.@Marius Biermann
As a data owner, I would like to prevent read access to data in a specific dataset for everyone outside explicitly specified groups. This is so that users or principals with non-scoped/”All” access do not accidentally get access to more sensitive data.Example:Dataset MyDataset exists and contains some sequence data we would like to restrict access to.Group A has sequences:read (unscoped) capability.Group B has sequences:read (scoped to MyDataset).Today: both Group A and B can read the sequence data in MyDataset.Desired: only Group B can read the sequence data in MyDataset.
On behalf of Celanese Charts super users:I would like the ability to take a single time series and overlay data from different time intervals (batches) on a single chart similar to what is possible in Pi. This would be a needed feature in order to affectively monitor and analyze batch performance. As it stands, the only workaround identified is using a function to generate new time series for each batch, with timestamp offsets. (However, this approach is less efficient for a high number of batches, presenting a non-ideal workflow)This idea request is related to the Hub post below:Cognite Charts: Ability to overlay a single time series for batch analysis
On behalf of Celanese InField super users:I would like for InField 2.0 to display the time stamp and user name who completed the item similar to what was available in InField 1.0. Currently, InField 2.0 only displays the user initials and requires that the user hover over the initials to see the complete details. Additionally, in the overview page, the assignees column does not show the names and requires the user to open the “Assign” tool to see who has been previously assigned. This functionality would make it easier to review and approve checklists.
On behalf of Celanese super users:When building a canvas, I would like the ability to create sections/views that allow me to quickly navigate without need to zoom/scroll to find what I need. This would be similar functionality to what is possible in a Miro Board using reference links. Functionality like this would be helpful in using canvas to document RCAs as this would cover large amounts of data and documentation.
This is a request for Cognite to make all of their applications Proxy Aware, allowing enterprise organizations to specify a proxy that will be used for all traffic.
In Cognite Chart send out notifications for monitoring jobs. Today, the Subject is “An alert was created”. It would be better if the Monitoring job would be mentioned.
We have an aggregation resolver, but we are unable with this resolver to group the data using the "Foreign key" for another object type as the group key. I think it would be a cool resource to suggest improvements to the tool in the future @Lucas Leocardo Araujo
Hi, I’m trying to add more fields to Dataset’s property, and would like to display them on the UI. Beside the existing fields (Labels, Owners, external ID, etc...), is it possible to display custom fields on the UI ( similar to metadata’s consoleLabels, consoleOwners)
If a time series is empty but used in a calculation - it should treat it as zero, rather than not allowing the calculation to function at all. Please refer to Bug #10057 where this was originally filled out (complete with pictures), but the outcome was a recommendation to fill out as a product enhancement request since this was as designed.
Multiprocessing feature addition in FileShare Extractor so that it can support the Thread concept for File Extractor. This is required so that multiple files can be processed parallely
Hello data modeling team, we define a 'Film' type which links to a 'Director' type, and prepare some test data as below:when executing the "listFilm" query and set the filter with director name, the query works well and return the expected results.when executing the "aggregateFilm" query, the Director fields are not available on Query Explorer. when adding the filter manually, the query failed.
Hi,To provide better view of the current status of the Cognite Extractors, our customer has requested the following UI improvements:Add a Filter option on the screen beside the Search box; Filter columns must include the Pipeline Last run status, Provide a toggle to switch between text and icon corresponding to the Last Run field (based on the ExtractionPipelineRun object), Add a column for the Last run success/failure message (based on the ExtractionPipelineRun object).
On behalf of Celanese Charts super users:When adding a new node on the canvas of a calculation, Charts uses the origin of where you are on the canvas to bring in new nodes. It would be beneficial for Charts to instead center new nodes using the equation/function as the point of origin. This would make it easier to manage larger calculations and decrease the chances of losing track of newly added nodes that may have been added outside of your current area of view in the canvas. This is especially important as the calculation canvas has a limit on how much you are able to zoom in/out. Example of a node added outside of range of the calculation
We have a large set of data models that is going to be released into our production environment soon.Some of these models and spaces are related to already existing products and datasets in our data catalog, but there are also some examples of industrial models or solution models that will only get data from a or several existing solutions/datasets. Or that there is a model that will only host data in a space and not connected to a dataset at all.We need to have the possibility to show more information to the users on the possible data models (some models and spaces would not be available to everyone as default so then how do they find that information).Is it possible to detach the data catalogue from datasets only and that we can also make data catalogue items for data models and spaces or other features aswell?Also is it possible to add the feature to add a relation from the existing items in the data catalogue to the possible related solutions and spaces.
When a new user logs into InField 2.0 for the first time, their default location is set to the very first location for the organization in the dropdown. This should instead be set to the proper site location that the user’s access permissions have them in. For example, someone from the Shelby site should see “SH” or something instead of “AT”.
On behalf of Celanese InField super users: When releasing a checklist in InField 2.0, it is not immediately clear what date the checklist had been opened. In InField 1.0, the release date was made part of the checklist title and made it easier to distinguish between other similar checklists that had been released. Can this feature be brought back into 2.0? Or at least make the release date easier to distinguish? @Kristoffer Knudsen
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.