Community Discussions

Hello Team,Although i have checked the documentation. I would be interested to understand if there is any discussion to generate charts programattically. this would help us Automate ESP surveillance for wells in one go.the idea is that once a well comes online it would automatically generate a ESP chart. 

Add functionality to visualize mathematical formulas rather than the raw LaTeX formatting which Atlas AI currently outputs. If you take a look at the screenshot I think it’s clear that is not a very friendly format to show to our end users Example of preferred output format: Example prompt for replication:Hvordan regner jeg ut volum til 100% fylte endekapsler til en horisontal sylindrisk separator. må anta en endebunnfaktor k, hva betyr denne?Example of how the formulas should be visualized (the visualization of LaTeX, not the raw format)Markus PettersenAker BP - Data Platform Architect

This feature request is to add the ability for Charts to send notification alerts via mobile texts. Often times, manufacturing leadership would like to be alerted off-hours for major operational issues. Text messages have proven to be an excellent means of alerting key resources outside of normal working hours.

When creating calculations in CHARTS it would be VERY useful to have logic functions (AND, OR, NOT, XOR) which allow multiple (>6 for AND and OR) boolean inputs (TRUE/FALSE) and a single output.This would be really useful for tracking events which may be dependent on multiple conditions being active (or not active). 

Manual rotation of credentials is often time-consuming and leads to outages when done incorrectly. To make it simpler to automate, could Cognite add API endpoints dedicated to updating credentials?This is especially relevant for Cognite functions, which currently require sometimes lengthy redeployments to update secrets. When I ask GitHub Copilot about which API endpoints Cognite Toolkit invokes to update secrets and credentials used by a Cognite function, implementing this myself on top of the existing API seems very brittle.I think automating the rotation of credentials will be much simpler if it can be decoupled from other deployment processes.

We observed that search behavior differs between Asset Centric and Data Model.Asset Centric search provides more flexible matching and returns results based on relevance, allowing users to find assets using partial text. The Asset Centric View would performs a Fuzzy Search and returns results that are best match to the search text.However, in Data Model View we are required to input the exact text with correct spacing/hyphenation, prefixes etc. to get the results and does not perform fuzzy search.Users transitioning from Classic to Data Model have found difficult to work with the new search mechanism as they do not always key in the correct names or search queries. While we understand the Search mechanism from Classic cannot be implemented on Data Model we wanted to add a topic to see if we can have the Data Model search to more forgiving and user-friendly through partial matching, typo tolerance, relevance-based ranking or similar mechanisms.

Preference to use the term "time series" instead of "trend". 

Add SORA attribute from BMS. 

Add location codes as static information in the F.LOC view to inhance user experience.

Ability to create conditional tasks in InField. An example is shown below: If a user answers "Yes" to any of the items in the checklist below, new checklists (Category 1, 2, 3) should be generated.Norwegian: Ønsket er å kunne opprette conditional oppgaver i InField. Et eksempel er vist under. Hvis man svarer "Ja" på noen av punktene i sjekklisten under ønsker man å opprette nye sjekklister (Kategori 1, 2, 3) 

As an administrator of CDF in Aker BP I have a need to see all apps we have deployed, not necessarily accessing the apps, but knowing they exists. As a minimum this information should be available through the API. This is the information I’ve found in the Cognite Docs, I can do it per app from the app repo. But that requires that I already know it exists and that’s the heart of the issue, I don’t know all the apps that exists. If someone has deployed and published an app without activating it, then I have no way of knowing about it. Hiding non-activated apps from most users is a useful feature, but hiding it from the admins is a security breach. I am aware that tooling for managing this will come, but that does not remove the need for the information to be available through the API. There is still a need to export the information to data/app catalogues for the sake of governance. Markus PettersenAker BP - Data Platform Architect