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!
What you should know submitting product ideas to our product team
Share your product ideas with the community and our product team
I was fixing a task in InField 2.0 by deleting the synthetic tag assigned. But then I wanted to see what the original tag chosen was. Unfortunately when I clicked “Cancel” at the bottom of the editing window of that task, and then I re-entered the task - the task had auto-saved and I couldn’t go back to what it had originally been. The auto-save is great - but what if I want to see prior edits for a given task?
One of our users from HESS reached out to Support with the below request. Currently the user can create an entity matching pipeline, but there's not way to schedule it to run and have to trigger it manually.This used to be possible, but seems to have been removed.Please bring this feature back as it's a core capability and differentiator that Cognite offers that they need to utilize to effectively contextualize their data.
Is there a way to delete the files from CDF if it has been deleted in the source using FileShare Extractor? # (Optional) Behavior when deleting files. # "soft" means that a metadata field will be added to the file if it is deleted in the source. # "hard" means that the file will be deleted from CDF. #delete-behavior: # mode: soft # key: "deleted" # OR #delete-behavior: # mode: hardThis concern was raised on behalf of neha.a.saini@accenture.com at CNTXT.
Hi! Our organization has strong desire for OpenID/OAuth2 authentication against the DB extractor. We are currently using SQL authentication, which is outdated.
Request: Enhance our SAP extractor by incorporating compatibility with SAP transaction codes. This integration is crucial for seamless communication between systems, allowing to execute specific SAP transactions directly through the extractor interface. . This feature will streamline processes, providing efficiency and convenience for obtaining data from SAP system.
Idea to develop an API-based extractor designed to facilitate seamless integration between external system APIs and Cognite. This extractor serves as a crucial link between diverse APIs and the Cognite platform, ensuring efficient data transfer and integration capabilities.Current approach is we go to the source system and custom configure the API’s of source system and Cognite API’s to integrated data. API Compatibility: - The extractor must support a wide range of APIs to accommodate various data sources and types, including RESTful, GraphQL, and other standard API protocols. - It should be adaptable to changes in API versions and structures, allowing for easy updates and maintenance.Extractor should have capability to send data to Cognite Raw/FDM/any specific target area within Cognite. Data Extraction and Transformation - The extractor should enable configurable data extraction parameters such as date ranges, filters, and pagination options to retrieve relevant information from source APIs. - Capability to call a transformation /function and pass inputs Scalability and Performance: - The solution must be scalable to handle large datasets and high-frequency data updates, ensuring optimal performance even under heavy loads.Support for Queuing mechanisms where the data can be queued and processed to CDF in the order - Support for asynchronous processing and parallel execution to enhance speed and efficiency in extracting and transferring data. Security and Authentication: - Robust authentication mechanisms, including API key management, OAuth support, and secure token handling, to ensure data security during extraction and transmission. - Compliance with industry-standard security protocols, such as TLS/SSL, to safeguard data integrity and confidentiality. Configurability and Customization: - Intuitive configuration options for users to set up and customize extraction parameters based on specific API and Cognite requirements. Monitoring and Reporting: - Integration with monitoring tools to track extraction performance, detect anomalies, and generate reports on data transfer activities. - Real-time alerts for system administrators to address issues promptly and ensure continuous data flow. By addressing these requirements, the API-based extractor will serve as a robust and versatile solution, facilitating smooth integration between APIs and the Cognite platform while meeting the diverse needs of users and maintaining high standards of security and performance."
In InField 1.0 process experts have the ability to open checklists from templates. In InField 2.0, process experts cannot even access the templates. The process experts should be able to access the templates in case their templates do not have time intervals and are on an "as needed" basis for opening checklists. Learning facilitators or team captains will need to open on-demand checklists on their desktop as a workaround.
On behalf of Celanese InField super users:Currently, InField only supports an itemized list view when creating templates. However, for Maintenance applications, I would like to see some flexibility in template formatting to allow support for tables (multiple columns and rows) similar to original Excel forms today. Given that maintenance checklists cover multiple inspection criteria per equipment, a list is not the ideal interface as the users would be required to scroll through a long list of items.
On behalf of Celanese InField super users:When building templates in InField 2.0, it has been discovered that there is currently a limit of 500 tasks that can be added to a template. Can this be increased? There are a few checklists in the unit where this limit is easily reached. The only workaround today is to separate the checklists into parts, which is not ideal.
On behalf of Celanese InField super users: I would like to see improved functionality for adding line items to an existing group or merging groups. Currently, I am unable to drag and drop a new item into an existing group. Instead I am required to select the item I want to add and an item within an existing group and merge the groups as a “new” group. However, when this is done, the new group is moved to the bottom of the checklist. It would be a smoother user experience to be able to add an item to a group directly and without the position of the group being moved.@Kristoffer Knudsen
As Daily Execution Leader, when something is marked Not OK and in red, I would like my process experts (those doing shiftly rounds) to be required to enter in a comment to make sure the issue is communicated and visible to all. Make it so that it cannot be skipped without putting a comment.Feedback from the Daily Execution Leader @ VAM (Vinyl Acetate) Unit at Clear Lake going through onboarding now
We would like to have the ability to put or move the message to show at the beggining of the taske (currently it moves it below) to give instructions to conduct the activity or input an answer.
After inputting data in a section with a lot of line items, you must scroll back to the top to collapse the section.If there were a collapse button at the top and bottom of the sections, this would save time in the scrolling back through longer sections. This could be used in other checklists and or procedures as well. I created an example below with just a copy of the header at the bottom of the section.
On behalf of Celanese Clear Lake DEL (Daily Execution Lead) for Laboratory Unit. As a DEL, I want a function that automatically sends me checklist report or notification through email when they are completed. The benefit of this enhancement will save me time from consistently checking when a checklist is completed.
Submitted on behalf of Celanese Learning Facilitators (Kenny, Kyle, Rudy, and Hud): As a Learning Facilitator or process expert, I want to be able to trend line items from my InField checklist rather than have to rely on tags so that I can see what the past values for that specific checklist item have been. InField will only visualize tags with a hyperlink, but some checklist items don’t contain tags. There is no way to see the history on it without having to go back to completed/archived electronic checklists. The Learning Facilitator said, “At that point, I'd rather just go back to using paper than having to check each individual archived checklist.”
On behalf of Celanese Clear Lake InField super users:As a user, when creating a template in InField, I would like the ability to choose from a standardized list of units (UOM). This will help standardize template creation across the site and avoid confusion due to discrepancies related to variation and syntax errors. An example of this can be seen below:PSI > psi > psig or GPM > gpm > gal/min
On behalf of Celanese InField super users:As a user, when marking a section of line items as “N/A”, I would like the completion status to show that the section was marked as “N/A” and highlighted as yellow. Instead, InField currently shows the status as “Done” and highlights the section in green. This gives the impression that the tasks were completed, which is not the case.
English is currently set as the default language for all users. If the user changes the language in his account, this setting is not saved. The user has to change it every time he logs in into Infield. This request has a high priority from the the adoption perspective.
In Data Explorer, when selecting events resource types, you can filter on Event Types and Subtypes on the left filter panel. currently, when you click the Event Type and Subtype drop-down, it allows you to type the name of the event type or subtype that you want to filter by and shows the ones that start with the searched word. e.g. If I start typing “PM” I will see “PM Compliance” Event Type shown. However, if I start typing “Compliance” It does not return “PM Compliance” event type. The idea is to be able to “Search” by any word on the event types and subtypes and not only starting with. This is particularly useful when the CDF solution contains many event types, which the user cannot remember what it was called exactly.This concept can be extended to Metadata filter for all resource types also.
Hello, I have a time series that accumulate values during the day and at 9pm it resets to zero. I am interested in creating a calculation to storage only the value every day at 9 pm in a new time series. I thought about Scheduling a Calculation on charts and schedule it to every day at 9 pm and run it to backfill, but it seems that there is no option. Also when I schedule a calculation and select to run every 1 day, it does not give the option to select time. Is it possible to schedule it to a specific time?Also is there a better way to do it?
As a user I want to have an improved search to include components of the string and not only the start of a string.
Please extend the maximum length of Activity ID from 30 to 41 characters. Length of internal generated ID for direct planning is 41 characters, all other Activity IDs are shorter than that.
As an end user I would like to get the possibility to see the different (major) versions of a Template from the past to today and not only the latest version. This is quite important to see how the template has changed overtime. The reason behind is that not only users can see what is changed also that auditors can see it.
I believe it would be really beneficial to create some ways for the users / teams of a Cognite Project to create new versions for the given Streamlit application, or at least give the ability to copy the whole Streamlit app with a new name in the same Cognite Project. In case of sprints and tasks in Scrum or Agile the feature development is done in separate segments, so the stable code should be available for the users while the development could be continued in an unpublished copy of code. An import / export functionality for Streamlit Apps could also solve the problem and it would make the migration between dev and prod environments much easier.
We are a Cognite customer who provides our own customers with access to CDF APIs.These customers develop their own software to consume our data, and use the Cognite SDKs to do so.Currently we generate client credentials for each customer and rely on them to keep these safe. An optimal solution for this would involve: Not to have to administer on our side which users from the customer have access. This is the customer's responsibility, and we want to avoid both the admin, and potential IdP charges from adding many additional users to our IdP. Not to have to supply customers with client credentials that they must then keep safe. This makes us overly reliant on the security practices of the customer org and individual developers. First class support in the Cognite SDK (i.e. not having to treat it as a special case and build a custom token provider).
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
