PAZO updated to V8.5

Home
>
Blog
>
Categories
Pazo News

PAZO updated to V8.5

Wherever you are on your journey, we are always here to help you write your story the way you want it. Which story are we talking about? It’s your own; whether you are a manager, supervisor or a staff member, you have a story to tell about your work. It’s stories like yours that helps PAZO add useful features from time to time. So, what’s new this time?

Read the full feature list to find out…

Gallery now shows attachments, images, and videos. It also allows users to give review comments and score

  • In the gallery, users can view attachments, images or videos that are submitted via checklists.
  • Flagged fields will be highlighted with red borders and flag icons.
  • Users with viewer or site admin permissions can view the gallery.
  • Users can filter the image gallery by site groups, sites, checklists, file types and flagged items.
  • With this release, the gallery is now more collaborative and helps users act faster. When the ‘Allow reviewer to score’ setting is enabled on the Checklist page, users can give review comments and review scores on the Web app Gallery. 
    • Users need to open the image they want to review and then give review comments in a textbox and score from 1 to 10.
    • All the review comments and scores can be viewed on the same page by clicking ‘Previous review comments’ so that anyone can see them.

Revamped UI for Issues Mobile app screens

  • Fresh UI for a more natural user experience.
  • Added filters for ease of use on mobile.

Specific Time Schedules with expiry option

  • We have added something new to our specific time schedules. Previously, if specific time schedules were left unfilled, they went ‘missed’ at the end of the day. The problem with that is not all schedules are meant to be completed in one single day. That’s where this new update can make things more flexible; users can now manually set the expiry duration. Such checklists need to be filled before the due expiry or else they cannot be submitted.
  • This is how users can set expiry duration for specific time schedule:
    • In the manage schedules page, select checklist, and then choose ‘specific time schedule’ from the dropdown.
    • Add the new schedule:
      • Choose Site from the dropdown.
      • Under schedule plan a user can select multiple date slots and for time, they can either select anytime or select a specific time.
      • To add specific expiry, users must tick ‘expire the slots on’ checkbox and then manually set the expiry in duration (no. of days, hours, and minutes)
      • All the slots will have a common expiry duration.
  • For example: If 2 slots are added for the 21 Feb 10:00 AM and 22 Feb 11:00 AM and expiry duration is given as 5 hours then
  • Schedule for 21 Feb 10:00 AM will be available for submission till 21 Feb 3:00 PM (5 hours expiry duration).
  • Similarly, schedule for 22 Feb 11:00 AM will be available for submission till 22 Feb 4:00 PM (5 hours expiry duration).
  • Note: All the slots within the same schedule can be given one expiry duration. Separate expiry duration for separate slots of the same schedule cannot be given.
    • If the ‘expire the slots on’ checkbox is not selected, then the specific time schedule will be scheduled as a daily checklist without an expiry.
    • When the ‘expire the slots on’ checkbox is checked: the escalation timings for specific time schedules with the expiry time is equally divided by 3.
  • For example: if the time is given for expiry: ‘<no. of days, hours and minutes>’ is 21 hours then 1st escalation will be after 7hours, second escalation will be after 14 hours and third escalation will be received after 21hours.
  • When they do get missed, you can view missed schedule info in the schedule page on the same date when it was scheduled.

Mandatory comments for completing or closing an issue

  • Earlier, while changing an issue status, leaving comments were optional. But to make things more transparent, issues now can be marked as completed or closed only after the users comment.

You can track your previously assigned issues even after it is reassigned to a different department

  • Earlier, users could only view/modify issues that were assigned to their departments. But issues don’t always get resolved without additional help and may even be reassigned. If this happened from user to user within the same department, there was no problem. But when an issue got reassigned from one department to another, previous users no longer had track of it. With this update, that is no more a problem; every user ever assigned to an issue can keep track, even when their departments differ.
  • Users from different departments cannot change the status, due date or reassign issues but they can comment using the issues chat.

New Checklist View on Tabular Dashboard

  • Checklist View displays the list of site-wise and department-wise information.
  • List of Checklists will be shown and along with that following details will be shown for each checklist:
  • Checklist Name– The Name of the selected checklist given on Add/Edit Checklist page.
  • Sites assigned- The total number of Sites for which the selected checklist is assigned (includes sites which have ad hoc checklists).
  • Scheduled- Thetotalnumberofschedules that are assigned to the selected checklist(except ad hoc).
  • Submitted- The total number of submitted schedules (except ad hoc).
  • Missed- The total number of missed schedules (except ad hoc).
  • Ad hoc- Total number of ad hoc submissions for the checklist.
  • Flags- If there are flags raised on the submitted checklist reports for that particular day, then the total number of the flags will be shown.
  • Reviews pending- Forchecklists which have ‘Review every submission of this Checklist’ setting as enabled, count will be shown if they are not reviewed even once. This count reduces accordingly after the checklists are marked reviewed at least once.
  • Created On- Displays the checklist created date.
  • Each checklist can be clicked to expand the Site wise details such as:
    • Sites Assigned | Departments | Schedule Type | Scheduled | Submitted | Missed | Ad hoc Flags Raised | Schedule Start Date.
  • Each number is clickable, and users can drill down to the last level to check the final report details.
  • The information can be filtered as per the needs: users can filter by Site groups, Daily Schedules, Weekly Schedules, or Monthly Schedules.
  • Users can also download the checklist wise report by selecting excel download option and choosing ‘checklist wise’ report.

Various levels of Issue Turnaround time (TAT) will be shown in reports

In Issues, the different levels of TAT will be shown:

TAT to accept

  • Time taken for an issue to be accepted for the first time since it is raised.
  • Even if reassigned to multiple users, the time taken will be calculated up to the moment an issue is first accepted.

TAT to complete

  • Time taken to switch from ‘Issue Raised’ to ‘Issue Completed’ status.If an issue is raised to a department- it can be accepted by a person within that department.
  • The time it took for a user to accept the Raised Issue.
  • When an issue is directly raised to a user, there are 2 options from which they can choose: Accept | Reject.Time for an issue raised (Open Status) to be accepted for the first time.
  • If the issue is rejected, it is assigned back to the user who raised it and the time taken will not be calculated.

TAT to close

  • Time taken to switch from ‘Issue Completed’ to ‘Issue Closed’ status.
  • The time it took to switch from ‘Issue Completed’ to ‘Issue Closed’ status (even if there are multiple status changes in between such as deferred, duplicate; the whole time will be calculated when the issue is marked as closed for the first time after it is completed).

Default due date for Issues setting-> on Add Checklist->flag->Auto Raise issue

 

  • On the Add Checklist page whenever Single select, Multi-select, drop-down and Image fields are chosen, there is an option to flag. After a flag is selected->select ‘raise issue on flag’ setting.
  • When the setting ‘raise issue on flag’ is selected- the auto- issue is raised whenever a flagged answer is selected. The due date for these issues is 1 day by default.
  • Now, users can set a custom due date for these auto-raised issues on flags.
  • The due date can be set for each question separately.
  • By default, 1 day is selected for the raise issue option in flag.

‘Accept Issue’ and ‘Reject Issue’ from Web App

  • REJECT ISSUE option along with ACCEPT ISSUE option for all the issues assigned to a user.
  • ACCEPT ISSUE option for all the issues assigned to a department
    • When a user Accepts Issue- the next steps remain the same i.e., users must enter the issue chat and can then change the status.
    • When a user Rejects Issue- it will be reassigned back to the initiator (user who raised the issue) to verify and close it, in the same way that issues are marked. completed. The issue will be automatically re-assigned to the person who raised it so that he/she can verify it and then close or reassign it.

Auto raised issues will attach the images(camera) from attachments

  • Issues that are auto raised from checklists, camera images uploaded in attachments will be shown within that issue.
  • Maximum 3 images will be attached to the issue details.

Users can now set the same date as “to” and “from”

  • The web app now allows users to set the same to and from dates wherever the option to select date range is available.

General department no longer a necessity for Viewers and Site admins

  • While adding viewers or site admins, it is no longer necessary to add them to the General Department; users must be present in at least 1 department can be assigned to their respective departments.

That’s everything we included with this new update. For any queries, and feedback contact customer support at support@gopazo.com.