Trent Sherrell

Samir Swapnil Pandhare Molly Ronovsky Nandkumar Prabhakar Karlekar

Hi all,

Please check the attached user flow

cc Trent Sherrell

Molly Ronovsky Trent Sherrell : Kindly check the attached screens for Completed Forms Library.

cc: Samir Swapnil Pandhare Nandkumar Prabhakar Karlekar

Aruna Raheja
Hi Aruna,

Couple of things:

• Is there a standard delete confirmation message? I feel like there should be? I think it's awkward the way the title says Are you sure? and then the next part starts with the rest of the sentence? Does it make sense to repeat 'Are you sure' again? As well, it should read: By doing so, there will no longer be a record of this document in the system'. vs there will noT.
• After talking to the HR team, it does appear we would want to be able to to archive the document. For example an updated offer letter - you would want to keep a history of the old ones for record, but only the current/new is active. Can we add option for archive? If archived, it would still live with the candidate file, but we would know it's an archived/old file. can we mock that up?
• For the forms library, I think we need to rename partially complete column to 'Status'. As well we need a column of WHO the document was sent to - right now we only say who sent it, not who received.
• We need to mock-up what it would look like if multiple documents were sent to a user. We would want to see them grouped together - so if i received 4 documents - i would want to see that i received 4. As well, i would want to know that status by document (sub status), as well as the overall status of that 'package'.
• I'm wondering if it also makes sense to have filters on the top of the screen so you can filter by certain items: ie whomever sent, a candidate, status (so you can see what is pending easily), but you can enter certain criteria to then filter on vs. doing it one by one sorting of a column.
• On the success screen, it should read: The document(s) have been sent successfully!
  cc: Trent Sherrell

Aruna Raheja: I think the comments made by Molly Ronovsky makes sense.

Molly Ronovsky On a related note, can you tell us the actions that users should be taking by importance? For instance, I would not think that deleting documents would be the most important action. Aruna Raheja: once we have that ordered list, you should place the most important action's icon first (to the left) and then follow to the right from most important to least. Thanks!

Molly Ronovsky :

Please find my comments below-

• Is there a standard delete confirmation message? I feel like there should be? I think it's awkward the way the title says Are you sure? and then the next part starts with the rest of the sentence? Does it make sense to repeat 'Are you sure' again? As well, it should read: By doing so, there will no longer be a record of this document in the system'. vs there will noT.

I don’t have any standard delete confirmation message. I have taken the same from Jira ticket. I have changed it as per the requirement give in above point.

Trent Sherrell : Let me know if there is any standard message.

• After talking to the HR team, it does appear we would want to be able to to archive the document. For example an updated offer letter - you would want to keep a history of the old ones for record, but only the current/new is active. Can we add option for archive? If archived, it would still live with the candidate file, but we would know it's an archived/old file. can we mock that up?

I have added the archive option with archive screen. Kindly confirm do we have option to delete archive file or not and what will be the fields that need to be shown in the table like status etc.

Also confirm, Tabs name will be Active templates or Active Documents for this case

• For the forms library, I think we need to rename partially complete column to 'Status'. As well we need a column of WHO the document was sent to - right now we only say who sent it, not who received.

I have added the column for WHO by the name receiver. Kindly check

• We need to mock-up what it would look like if multiple documents were sent to a user. We would want to see them grouped together - so if i received 4 documents - i would want to see that i received 4. As well, i would want to know that status by document (sub status), as well as the overall status of that 'package'. 

I have done this, can you please review this

• I'm wondering if it also makes sense to have filters on the top of the screen so you can filter by certain items: ie whomever sent, a candidate, status (so you can see what is pending easily), but you can enter certain criteria to then filter on vs. doing it one by one sorting of a column.

I don’t think so it’s needed as we are giving sorting and search both

Trent Sherrell : Your suggestions please

• On the success screen, it should read: The document(s) have been sent successfully!

Done. Kindly check

Molly Ronovsky Let me know if still need changes in this.

Is there a standard delete confirmation message? I feel like there should be? I think it's awkward the way the title says Are you sure? and then the next part starts with the rest of the sentence? Does it make sense to repeat 'Are you sure' again? As well, it should read: By doing so, there will no longer be a record of this document in the system'. vs there will noT.
I don’t have any standard delete confirmation message. I have taken the same from Jira ticket. I have changed it as per the requirement give in above point.
Aruna, i had put this in a different ticket, can you confirm you have those comments / verbiage for the message?

After talking to the HR team, it does appear we would want to be able to to archive the document. For example an updated offer letter - you would want to keep a history of the old ones for record, but only the current/new is active. Can we add option for archive? If archived, it would still live with the candidate file, but we would know it's an archived/old file. can we mock that up?
I have added the archive option with archive screen. Kindly confirm do we have option to delete archive file or not and what will be the fields that need to be shown in the table like status etc.
Yes we can delete

Also confirm, Tabs name will be Active templates or Active Documents for this case
Documents for the sent completed library, but we need to make sure the breadcrumbs and header are consistent too

For the forms library, I think we need to rename partially complete column to 'Status'. As well we need a column of WHO the document was sent to - right now we only say who sent it, not who received.
I have added the column for WHO by the name receiver. Kindly check
Looks good

We need to mock-up what it would look like if multiple documents were sent to a user. We would want to see them grouped together - so if i received 4 documents - i would want to see that i received 4. As well, i would want to know that status by document (sub status), as well as the overall status of that 'package'.
I have done this, can you please review this
Aruna Raheja what happens if you sort by a different column? For example if you sort by creation date - then what? how does it look because you wouldn't have all the forms for a particular receiver together

On the success screen, it should read: The document(s) have been sent successfully!
Done. Kindly check
Looks good

Molly Ronovsky : All the points has been done. Kindly check.

Also if i sort by a column, the grouping will disappear. Kindly check screenshot "Completed_Form_list_sort.png"

Hi Molly Ronovsky

Below are some points where your feedback is needed:

• Archive functionality will set the Is Archive Flag to 1. Once done this record will not be displayed on the UI. It will be in database against that candidate ID
• Can we discuss “Sub Status, Signed and Final Status” columns in “Completed/Sent Forms Library”
• What’s the purpose of “Open Column” in “Completed/Sent Forms Library”
• As sorting is there on grid, do we still need grouping on “Receiver and Final Status”
• Can we add delete action in archive tables?
• Do we need multiple delete or Archive feature?

Regards,

Samir

Hi Samir,
Maybe we need to have a call, but I tried to answer your questions below the best I could...

• Archive functionality will set the Is Archive Flag to 1. Once done this record will not be displayed on the UI. It will be in database against that candidate ID Why would it not be displayed? Does that mean end user can no longer access?
• Can we discuss “Sub Status, Signed and Final Status” columns in “Completed/Sent Forms Library” Sure, looks like Aruna Raheja added a substatus so that you can see status on specific docs if more than one sent. What are your questions?
• What’s the purpose of “Open Column” in “Completed/Sent Forms Library” I am not sure – Aruna Raheja, looks like you added this?
• As sorting is there on grid, do we still need grouping on “Receiver and Final Status” How else do you ensure you can see that a package / multiple files were sent out together?
• Can we add delete action in archive tables? Yes
• Do we need multiple delete or Archive feature? Can you elarborate?

Aruna Rahejacan you please make the delete message left justified, not center? that is the standard way for ux

Molly Ronovsky : I have make the delete message left justified.

Also i have removed "Open Column" from "Completed/Sent Forms Library"

Kindly check

CC : Samir
Hi Molly Ronovsky ,

Please let me know when can we have this call to clarify Completed forms library?

Thanks,
Swapnil P.

CC : Samir
Hi Molly Ronovsky ,

As per our call, below is the MOM of call :

1. Archival functionality will be mutually exclusive on Forms library and Completed forms library. Forms library archive - It will just archive the document template . It won't have any impact on Completed forms library.
Completed forms archive - It will archive just candidate record that was assigned the document template.This would be needed when some offer letter needs to be updated.

2. Rename created date in mockup to "Send date". This is date when the document was initially sent.

3. We will keep one status as of now (Removing the grouped one). Also, we will add sorting on Receiver column to identify all documents sent to that user.

4. On resend form, email notification to candidate with link to DMS portal will be sent. Also, DB record of that will be maintened.

5. On delete ,records will be soft deleted.

Nandkumar Prabhakar Karlekar, Please check above comments and reply back if you find any discrepancy with database part..

Thanks,
Swapnil P.

Aruna Raheja see above comment - need to rename the created date to Sent Date. Also should we rename the column 'Form Name' to 'Document Name'? Same with the Sent/Completed Forms? Should it be document? Just want to make sure we are being consistent.

Trent Sherrellthoughts?

Molly Ronovsky Swapnil Pandhare

Changes has been done. Kindly check

Aruna Raheja I dont see the column updated for sender/creator? also, can we remove the images that are not relevant? i see a couple different ones. As well, wondering about the module name - did Trent Sherrell give any feedback if we should call document vs. form? I feel like we are not being consistent.

Molly Ronovsky : Have updated the columns already, can you please where it is not updated. There are reference documents that i didn't deleted.

Also i didn't received any feedback on Module name from Trent, so please confirm as heading is saying "Form" and table is saying "Document"

Aruna Raheja On all of the libraries, we have creator / sender as the column header, which doesn't make sense. When we are looking at the sent library, we should just see the title 'Sender' so we know who sent the form. Because the creator and sender might not be the same person.

We can leave the titles for now if he didnt' give feedback.

Molly Ronovsky : Kindly check now. If it is fine then i will close this ticket as well.

Please see the attached document for page fileds and DB field mapping.

Document name : Document libarary and DB fields mappingsDMS-5.docx

Aruna Rahejalooks good

Molly Ronovsky : As discussed yesterday night, i have added email ID in completed forms table. Kindly have a look.

Also i closing CBUX ticket of this.

Aruna Raheja, Can you please confirm me with the design patterns we are following for Modals and Grids?

I am comparing screens- Completed_Form_archive_delete.png and Completed_Form_resend.png. Few differences I found as below:

1. Left orange border is there for delete popup and not used for completed popup
2. Modal footer border not used on delete popup

Can you please share your thoughts. So I can proceed with integration.

Smita Pawar : Please find my answers below -

1. Left orange border is there for delete popup and not used for completed popup - This is as per Molly requirement that i need to change for delete only
2. Modal footer border not used on delete popup -  This is as per Molly requirement that i need to change for delete only
3. Grid - candidate forms from sertifi.png was uploaded by Molly for reference. So you need to consider Completed_Form_Archive.png

Aruna Raheja I would not call the column 'Owner' . In Sertifi, Owner is the person who SENT the email - their email address, and first signed is the person who RECEIVED it - so the candidate. I believe Swapnil Pandhare wants to include the receiver in the grid, so we probably should move it next to the receiver and call it receiver email.

In terms of the delete modal, Smita PawarAruna Raheja I gave Aruna an example of what other UX teams use for that action, as the first time i saw the pop-up it did not look like anything i had seen before / was not appealing to the eye. I do not care what it looks like, was just showing you how it is done with them. Shouldn't they all be the same? I am looking to the UX team to let me know that answer. Trent Sherrell Trent, shouldn't this type of stuff be similar across the board?

Aruna Raheja: Please reach out to Kristen Ruel and see if we have a standard pattern that can be used for the delete modal. Kristen doesn't have access to this instance of Jira or I would just tag her here. Thank you!

Molly Ronovsky : Have change all the delete popup's as per CB guidelines.

Also have changed the "Owner" to "Receiver Email" and updated the designs. Kindly check 

Aruna Raheja I do not see that change from owner to receiver email - wouldn't it also make sense to put it next to the receiver's name?

I'm ok with the delete pop-up if UX is - looks funny to me being centered, but if those are the guidelines that is fine.

Molly Ronovsky Have forgot to updated mocks here. Have done the same now.

Aruna Raheja

1. For Delete message we are referring updated screen.

2. Completed_Form_resend.png is having icon with success message. So for success we are going to shown message with icon? Please confirm.

3. I can see few screens uploaded twice and I did not find the differences, if those are similar then can we remove if repeated.

4. Older screens, can we remove from here. So we can avoid confusion.

5. Completed_Form_Archive.png: We have first column text in blue color and other columns in standard color.(Gray shade) As per my understanding clickable text would be blue and if not then will show it with standard color. Please confirm.

Smita Pawar : PFB my comments

1. For Delete message we are referring updated screen. Yes

2. Completed_Form_resend.png is having icon with success message. So for success we are going to shown message with icon? Please confirm. Yes

3. I can see few screens uploaded twice and I did not find the differences, if those are similar then can we remove if repeated. I have removed the old files, you can consider the files that was uploaded today

4. Older screens, can we remove from here. So we can avoid confusion. Done

5. Completed_Form_Archive.png: We have first column text in blue color and other columns in standard color.(Gray shade) As per my understanding clickable text would be blue and if not then will show it with standard color. Please confirm. First column is clickable that's why it is in blue color. You have to use the blue one