Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
@Makoto Tono Our current estimate is end of Q2.
@Makoto Tono This is on our radar and we are currently working on getting attached images into the templates/checklist in a future version of InField. The feature is currently on the design stage – thank you for the input. We can follow up after New Years :)
It’s on our radar, we have some design ideas for it and it’s something we want to tackle (hopefully) early next year.
Hello! Nicklas from InField here. Thank you for chiming in! We are very aware about this issue – and we’re discussing how to best go about solving it with a future release. In the meantime, there a template section guide screenshot in the toolbar when editing template which might offer some help.I’ll update this thread once we have the fix in place!
Great feedback – I have some ideas for improvements and I can follow up with Hud on this.
We appreciate the input. It’s been brought to the team and we will discuss how to solve this need. Can’t promise a timeline but since it’s one part of a larger theme we’re working on in the team, hopefully we can tackle this sooner rather than later.
Definitely great feedback. Will bring this to the team as part of our ongoing work on improving the checklists.
@Anita Hæhre @Kylie R Surprise! This functionality actually in InField right now! 😊
@Kylie R Added it to the task in our backlog and we’ll evaluate 👍🏻
@ibrahim.alsyed Makes total sense! We’ve been discussing that functionality for some time, and I’ll push for it to get higher priority. Will keep you updated.
Hello again, Ibrahim. I’ve been digging into this functionality a bit this week, and if I’m understanding your feedback correctly, we are working on being able to show the all my time series data associated to a tag. Perhaps @Cathrine Horn Stenstadvold can shed some more light on this.
@Kylie R We have been in discussion with other end users about similar functionality before, so it is definitely on our radar 😊
@ibrahim.alsyed Today in InField, if you search for a tag, and navigate to the associated Trends page, you’ll see a section on the left-hand side with the name “Other time series on this tag” – is the functionality you’re requesting something separate from this? 😊
Hi @ibrahim.alsyed. Thanks again for the great feedback! I’ve created a ticket in our internal backlog and will evaluate with the InField if this is something we can handled in the near future. If so, I might reach out to you with some following questions for clarification. Thanks again, Nicklas
Hi @ibrahim.alsyed. Designer from InField here 😊 Can you elaborate a little bit on your request? Perhaps share a screenshot of the context you’re referring to? I’m curious about what would be most helpful in your use case.Nicklas
Hi @Kylie R! Thanks again for great feedback 😊 I’ll create a task in our backlog and evaluate with the team if this is something we can get into InField. If so, I might reach out to further understand the request. Nicklas
Release should be around April 6, is that correct? Or will this end up in the release following on 4/20? Pending a bit more internal testing today, the update will be sent to our QA testers later this week and hopefully the change will be part of a release on Wednesday next week 😌
Hello again, @Kylie R!After discussing your post with the InField team and other stakeholders, we landed on changing the default behavior of the measurement readings input field to what you’re suggesting in your post.Pending final testing, with the next release of InField, which you will be getting automatically, the value of the input of the measurement reading determines the task status. If the value is within range, the task is automatically set to “OK”. If the value is outside of range, the task is automatically set to “Not OK”. If no range is set in the template, the task is set to “OK” when any value is inputted. You can always “manually overwrite” this, of course, simply by tapping the radio button and selecting a different status.Hopefully that takes care of the second part of the request as well, since you won’t have to manually select “OK” or “Not OK” on tasks with a measurement reading anymore – I can ping you again once the change is out, and you can let me know if this sol
This is very valuable insights – thank you so much for sharing!I pretty much concur with Jonas above. To give a little context regarding the setting of the task state to ok/not ok depending on the input: This is something we’ve discussed throughout the design and implementation of the measurement reading feature. The challenge – based on our existing users’ needs – has been that for some tasks it would be detrimental to rely solely on the value of the input to determine whether a task status is “ok” or not. Therefore, we decided to include that one additional manual check to make sure that the status is set as intended by the user. However, seeing this implementation if not ideal in your case, I think we might be able to escalate this within the team to find a solution.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.