Page Comparison

• Magda: The development status, there is not much information on this because we are now mixing Lotus and Morning Glory builds.
• Magda: We have added radio buttons instead of checkboxes. There is a bug. the drop-down should default to  "select record identifier." it should not default to barcode. Uploading the barcode file does not work just yet.

• Magda: We get an error message when trying to upload barcodes.

• Magda: We are working on that. There is some progress on the backend, but this is not visible to the UI. So please continue to be patient.
• Magda: On the Scrum Board, you can see there is a lot of other issues. There is progress for items, mostly on the backend.  And front-end developers are working on addressing bugfest issues.
• Magda: And this is the work on the backend on issues of displaying records and saving them.

• Magda: The main part of the meeting today, I would like to return to our discussion from the last meeting about the behavior of the action menu, depending on the permissions that they use has. Their permissions will differ between the in-app and CSV approach. After that, I would like to walk again through user records in the in-app approach. I would like to get your feedback on priorities for the next steps. I would like to go back to our conversation regarding the apps with bug edit capabilities that we touched on. Erin mentioned that none of them are actually apps. We will need to either rename them or the options in the accordion. If time permits we will get to the pilot project UIT.
•  Magda: So let me start the presentation. I'll start with a quick review of what we discussed last time. So we talk about the permissions that were introduced in Lotus, which was separate for edit, view, and delete.

• Magda: And depending on the permissions you had, the behavior of the action menu, once you open the application and you have a CSV type of permission. You could see right away--start bug edit. Even before the preview was populated.

• Magda: Once the preview was populated, you could download the matched errors or start bulk edit. And if the error accordion was populated, you would have the additional options of download errors in CSV format.

• 
  

  Magda: Please feel free to interrupt me at any moment, if you have an additional question.

• Magda: And this is the last screen for a CSV approach. Once the edit has been completed we see the completed process and you can start another by uploading another CSV file. So this is how it works in Lotus.

NOTES ARE NOT COMPLETED YET. STILL WORKING ON THEM...

Revisit naming convention for Apps with bulk edit capabilities accordion

• Magda: Last week we also discussed that in the morning glory we will be introducing new permissions and we agreed that their names will need to be renamed in Lotus. The new ones in Lotus will be named
  • Bulk Edit: In-app- Edit 
  • Bulk Edit: In-app - View
  • Bulk Edit: In-app - Delete

• Magda: With in-app permission enabled – Navigating to the landing page the action menu is not available because there is nothing the user can do.

• Magda: Now we have uploaded the file. The preview is populated with errors. You see the following options:
  • Download matched records (CSV) - a copy of the preview of affected records
  • Download errors (CSV) - a copy of errors
  • Start bulk edit - will open a screen for in-app editing

• 
  

  Magda: Once the bulk edit is complete, what should be the actions displayed there? We discussed that it would have the option to save changed records in the CSV file and also saved errors.

• Erin: I have a question about this screen Magda. The green box success toast. Is that going to behave like a success toast, where it appears on the screen and then it goes away? Or is that going to stay on the screen?

• Magda: It will stay on the screen because I think you would like to have a longer notification, not something that will pass. And if you don't pay attention, you will not notice it. Do you have problems with this?

• Erin: No, that's, that's fine with me. I mean, others can chime in. It just wasn't clear to me from the screenshot.
• Magda: Yes this is the exact behavior we have right now. It does persist. And actually, there is a bug because it persists even into the next bulk edit.

• Erin: But let's say I do an update and for some reason, 340 work, and 10 of them fail. Is it still a green box?

• Magda: (summary of the discussion with Erin about this screen) Yes, but it will be a green box minus those that were not updated. So in this example, you submitted 250 entries. 248 records were matched, 1 was not updated because there was some error. And one was not matched. So you have here notification that one record was not updated of the 248 that has a match.

• Erin: So the error that appears on the screen is found before I push the ...

• Magda: Yes, but it's a matter of updating the mock-up. This actually should read instead invalid date for the status or something like that.

• Erin: Yeah. You would get a better error message?
• Magda: Exactly. And it will specify what went wrong and indicate the record identifier. And it will have the option to save those errors so you can go back to the records directly and see what went wrong? Okay. And the other questions?

• Magda: So this was the easy part of the presentation. Now the hardest part starts. Now we will talk about the case where the user has both CSV and in-app permissions, so they can do both.

• Magda: So the user has CSV and in-app approach. They are on the landing page. They have an action menu and they have start bulk edit (CSV). Does it make sense?

• Erin: Yeah.

• Magda: Okay. Now we are moving to a more complicated thing. We are in the inventory items and in inventory, we can only use the in-app approach edit. But they use it also have the permission to start bulk edit with the CSV approach, which is not fully applicable for items at this point. It's applicable only for users. So the question I have is, should this start bunk edit CSV approach display only when they are on the user tab, or should be displayed also on the inventory items tab when the user cannot do anything here with that?

Image Added

• Erin: So I think in an ideal world, you would go to that landing page and you have an option in the action menu, but you would document or train people to say that the first thing you're going to do is you're going to select the app that you're going to work with.
• Erin: If I'm going to edit user records and I click that user users radio button, then I should see the action menus options that are applicable to users. If I choose inventory, I should see the option menu options that are applicable to inventory. And then my other thought is that those actions should be sorted based on whether it's CSV or in-app and not sort them alphabetically. So you would have a clump of CSV actions, and in-app actions. That may be even play And maybe even playing around with labeling of the options , because that'll make it even more clear that this is for in-app stuff and this is for CSV stuff.

• Erin: I think the chatter in the chat is mostly in agreement with hiding the stuff that you don't need in places that where you can hide it. And then clumping the actions by a CSV or in-app.

• Magda: Great, thank you.

• Magda: So another question is, let's assume then that we are in inventory items and I have both CSV and in-app permissions, but I will see start bulk edit. Right? And then when I click the link and I switched to users, I will see a start bulk edit CSV option. Is this what you are proposing are agreeing or not?
• Erin: That makes sense to me (chat agreed).
• Magda: Now we are in users and we have both permissions.

Image Added

• The summary of this section is best stated by Erin below after some back and forth with Magda.

• Erin: That's a good question for the group. If you have just edited 500 item records and now you need to do another edit with a thousand item records, a separate recordset, how do you want to start that process over again? You could go over to the record identifier and click upload your file. One of the questions I would have Magda is can I get to any of these files after I've started a new load?

• Magda: All of them are stored in S3.  They should be in export managers. But I have not tested for how long they stay there.

• Erin: That's okay. I think we just need to get some clarity on it.

• Magda: But is that something that you would like to have?

• Erin: What happens if I accidentally closed the tab or I have to walk away and I come back in 30 minutes and suddenly I can't get back here. How do I get to my files? I think that's the question.

• Magda: They are stored. The matter is how do we make them accessible to you after a while. But when you are saying you want to access the files, you actually have those files on your local machine.

• Erin: I might not have the error messages. And some staff might change machines over the course of time to go show somebody something. It would be nice to be able to get to the file through a tool, an export manager is certainly available as an option. We don't have to go totally down that road because I know we were talking about resetting. Thomas said in chat that he would favor having some sort of reset or start new, start new, or something like that.