RosterApps Release Notes 25.14

RosterApps Enhancements

RAPD-8022 API for Dependability

A new API endpoint has been added to allow for the retrieval of dependability information. The data that can be retrieved will be identical to what is displayed currently on the Dependability tab (under Location Admin role). The location must be specified within the call. Optionally, a type can be specified via a query string that corresponds to one of the tables in the Dependability UI. If no query string is specified, data from all three tables will be returned.

The REST API call is as follows:

/api/locations/{locationID}/dependability/summary?type=Pending
/api/locations/{locationID}/dependability/summary?type=Active
/api/locations/{locationID}/dependability/summary?type=Unassigned
The API documentation has been updated to reflect this change -> https://services-qa.arcos-inc.com/swagger/ui/index

Resolved Bugs

RAPD-15794 (ZD 69997) Unscheduled Punches Error

This fixes an issue when employees were trying to add unscheduled punches to their timecard. It had been displaying an error and not saving the punches. This has now been resolved so employees can add unscheduled punches.

RAPD-13695 (ZD 58586) Issue with ReliefShiftBid being marked absent with covering shift - wrong OriginalAssigned

This fixes a bug on the Multi Skill Duty Roster Report when you have a Relief Shift Bid shift owner who is marked absent with a covering shift, the OriginalAssigned column is looking at the original owner of the Relief Shift bid object, not the Original owner of the Standard Shift Bid object (like is displayed if there is not a covering shift created.) Now the owner of the original standard shift will be displayed in this scenario.

Testing Notes

RAPD-13695 (ZD 58586)

Preconditions:

Create a relief bid package
Add a bid line using the mix of cover shift(s), placeholder shifts (standard bid line shift(s) open on shift management), ad-hoc shift(s) and shift created using shift management. The shifts should have have at least one skill
- Note: Cover shifts can be created while marking any type of shift absent/ PTO, for example, Original Assigned(Base shift), Overtime or Traded shift
Assign this relief bid line to an employee.

Results:

Multi-Skill Duty Roster report should ran successfully

For covering shift(s):

Employee Name should show under Original Assigned column and should be strikethrough
Transfer Reason column should be populated with the reason used while marking shift absent/PTO
Covered By column should be populated with employee name with 'RLF' tag who is assigned with the relief bid line containing cover shift

For placeholder shift(s):

'Open Bid Line [Standard_Bid_Line_Name]' should show under Original Assigned column and should be strikethrough
Transfer Reason column should be populated with the reason 'Open'
Covered By column should be populated with employee name with '(RLF)' tag who is assigned with the relief bid line containing placeholder shift(s)

For the shift(s) created using shift management and ad-hoc shift:

Employee Name should show under Original Assigned column with '(RLF)' tag who is assigned with the relief bid line containing shift(s) created using shift management and ad-hoc shift(s)
Transfer Reason column should be blank
Covered By column should be blank

Report should be same for all three roles

RAPD-8022

Authentication:
- The API must use BasicAuth for authentication, consistent with other REST endpoints.
Request:
- The request must be a GET operation.
- The locationID parameter must be provided in the URL path and must be a valid string.
- They query string parameter called “type” is optional
Response:
- The response must include the following fields with the specified data types:
  - Type: string (must be one of “Unassigned”, “Pending”, or “Active”)
  - EmployeeName: string
  - EmployeeNumber: string
  - WorkGroup: string
  - TotalPoints: numeric
  - ActionName: string
  - ActionDate: date (nullable for “Pending” types)
  - ActiveUntilDate: date (nullable for “Unassigned” and “Pending” types)
  - AssignedTo: string (nullable for “Unassigned” and “Active” types)
  - AssignedDate: date (nullable for “Unassigned” and “Active” types)
Validation:
- Ensure locationID is a valid string and is not empty.
- Validate that the Type field contains only the allowed values (“Unassigned”, “Pending”, or “Active”).
- Ensure that nullable fields are correctly set to null when applicable.
- Ensure that data values match the data from the dependability tab for the same location
- Ensure that the records match the data from the dependability tab for the same location (same count)
Error Handling:
- Return appropriate HTTP status codes for different scenarios:
  - 200 OK: Successful retrieval of dependability summary data.
  - 400 Bad Request: Invalid locationName parameter.
  - 401 Unauthorized: Authentication failure.

RAPD-15802

Ability to sort Time Off Requests by various options

- Steps:
  - Supervisor > Home. Confirm there are multiple requests for multiple users in different work groups in the Paid Time Off Requests section
  - Click to enable:
    - Show All
  - Click to disable:
    - Rank Seniority by Location
  - Validate each sort option contains the following available selections:
    - Sort by:
      - Date
      - Shift Start
      - Shift Skill
      - Seniority Rank
      - Request Date
      - Shift Work Group
      - Employee
    - Then by: (includes "None" to previous list of options)
      - None
      - Date
      - Shift start
      - Shift Skill
      - Request Date
      - Shift Work Group
      - Employee
    - Then by: [same options as "Then by" above]
      - None
      - Date
      - Shift start
      - Shift Skill
      - Request Date
      - Shift Work Group
      - Employee
There are many combinations available for each selection and combination of selections. Test various selections and combinations between sort options to validate results reflect in the proper sort order.
- - - Example:
      - Sort by:
        
        Date
      - Then by:
        
        Shift Work Group
      - Then by:
        
        Request Date
    - Click Sort.
Try a few different combinations to validate selected options sort properly as reflected in the table.

Ability to filter Time Off Requests by various options

- Steps:
  - Supervisor > Home. Confirm there are multiple requests for multiple users in the Paid Time Off Requests section
  - Click to enable: Show all
    - Sort by: Date
    - Then by: Request Date
    - Then by: None
    - List in sorted from earliest shift date reflected in the "Date" column, to the latest shift date.
  - The following data is needed for use in the filtering steps that follow.
    - Capture the earliest shift "Date" value
    - Capture the the latest shift "Date" value.
    - Capture the latest "Requested On" value.
  - Click to disable: Show all
  - Confirm the following filter options are available.
    - Filter on shift work group: [ability to select active All Workgroups in the location or a specific active work group in the location.
    - from: [ability to manually enter date in the text entry box or update using the date picker in the calendar.]
    - to: [ability to manually enter date in the text entry box or update using the date picker in the calendar.]
    - requested by: [ability to manually enter date in the text entry box or update using the date picker in the calendar.]
  - Filter on shift work group: All Workgroups
  - Update the following based on captured data from Step 4.
    - from: [earliest shift date]
    - to: [latest shift date]
    - requested by: [latest Request On value]
    - NOTE: The date ranges include past and future shift dates as reflected in the Show all sort options. If the request was made on the Current date, even if the request is future dated, it won't appear in the list until tomorrow or beyond, so future dates are included in the Requested On date Filter.
  - Click on the select field to set the selection to "All Workgroups". NOTE: This select allows one to select All Workgroups in the location or a specific active work groups in the location.
    - Change the select field to a specific work group currently reflected in the list of Time Off Requests. Validate the list is limited to the selected work group.
    - Reset the list to All Workgroups.
    - Try different ones to validate list is displaying accurately. NOTE: Be sure to select date ranges in the future to cover current date and other future dated requests that appeared in the Time Off Requests screen when one clicks Show All.
    - If the request was made on the current date, it won't appear until tomorrow or beyond that date, so future date the Requested On date.

Validate there is an additional filter “Type/Reason” with a dropdown of the Type/Reason values from data in Time Off Requests.

Supervisor > Home. Confirm there are multiple requests for multiple users in the Time Off Requests section.
Click to enable: Show all
Click to disable: Show all
Select an specific value in “Type/Reason” dropdown. Click on "Filter".
Select "All Types" option and click on Filter button.
Select different options in the following filters:
- Filter on shift work group
- Filter on Type/Reason
- From
- to
- requested by
- Click on Filter button.

Validate there is an additional filter “Type/Reason” with a dropdown of the Type/Reason values from data in Time Off Requests and once you use this filter, it should persist across sessions.

Supervisor > Home. Confirm there are multiple requests for multiple users in the Time Off Requests section.
Click to disable: Show all
Select a specific value in “Type/Reason” dropdown. Click on "Filter".
Change the role, for example to "Location Administrator" and navigate to any available tabs, for example "Bid Packages".
Change the role to Supervisor again and navigate to Home tab.
Click on "Logout" button.
Enter your credentials again and click on Login.
- Validate the filters applied in above steps are selected and the data in the table is correct.

arcos_rosterapps_25.14_upd.pdf
200 KB Download

Articles in this section

Comments

Articles in this section

Related articles