Workaround was to add read access to Activity entity. This access was empty prior to deployments and working the night before.
Discovered during Scotia deployment.

Should see screenings as well as attestation and bookings.

The Generate timeslots flow uses the legacy dataverse connector. On deployment with one member, the flow would execute 2x (in parallel) whenever new timeslots where generated.
When looking at the flow, the environment value for the trigger was set to default.cds. Once changed the (Current) the flow would only trigger once.
Suggest we move to the new connector.

Which solution component is affected by this issue?

App

What happened?

One of our Rapid Screening app users (who also happens to be the person running the Facilities Safety Management configuration for our screening program) recently logged into the booking app via the Power Apps app on her Android phone to complete a home screening. She has screened several times prior to this incident without issue.

On this particular occasion, instead of the app taking her directly to the Home screen, she was instead pushed to the Profile screen as if she'd never used the app before. And the profile screen displayed the name and email address of a different user who had only logged into the app once to confirm it was working and set up their profile, but had not yet logged any screening results.

Of note - the "Welcome, ! header at the top of the booking app did list the user's correct name. It was just the profile details that listed a different user's name and email address (see screenshot).

She then closed the app, logged out of the Power Apps app, and logged back in and the app this time loaded the Home screen normally and she was able to open the Profile screen to confirm that her personal information, consent status, and default facility were all listed as expected.

Because she is the primary Facility Safety Management app user, she decided to check in that app to see if she could determine why she saw another user's profile information. She found that the other user now had two entries in the Employee Active Contacts list - one with the user's complete profile information created on Jan 18th, and a new one created on the day she encountered this issue with no profile information logged.

She deactivated the newer profile but flagged this as a concern for my team, who is responsible for supporting the Power Platform and this solution for our company.

This is the only instance we've noted of this behavior and have not been able to replicate it. The user whose profile information was displayed has never used this person's personal Android device and the user who encountered this data does not have access to the other user's credentials, so there could be no caching of a previous user's session or credentials happening here.

We used an integration partner that helped us set this solution up initially. We checked in with them to see if they have ever encountered this issue in past implementations and they had not. This issue occurred several weeks after their engagement with our company had ended so they are not available to provide support and recommended we connect with Microsoft, who in turn directed us to log this issue here.

This is what they had to say about how that aspect of the app works:

• The header that displays the text “Welcome! <>” is using the Canvas App command User(), which returns information about the user authenticated in the current session
• The profile page where the full name/email address are displayed, is displaying information retrieved from the Contacts (Employees) table in Dataverse.
• A variable that gets initialized when the App is loaded is set using the Office365 connector (Office365Users.myProfile().Id), which essentially uses the authentication token to check the graph API and retrieve the Active Directory ObjectID
• The ObjectId is then compared against the contact record (UserId) and it filters out the employee information.

Based on this information, we're unable to determine how the app confused the logged in user with an entirely different user's profile. We've looked through the available documentation to see if there's a way to view session logs but have been unsuccessful.

Steps to reproduce

Unable to reproduce. This has only occurred once that we know of, but because it involved revealing another user of the app, there are now concerns that the app has the potential to provide a user with information as to who else is in the screening program or even worse, provide a user with the past screening results of other users.

Expected behavior

When a user that has already used the booking app once logs into the app in the future, the app should always be able to accurately pull the user's profile from Dataverse and set up the app using their data. It should never under any circumstances display an entirely different user's profile or screening data.

Which version of the components are you using

ConsortiumMemberGlobal 2.0.0.125

Additional environment details

No response

Need to disable the Next button once clicked.
Need the same behaviour as the employee app.

Currently only includes name and createdon.
Should include date, start time, end time, area, etc.
Should also be sorted by date and start time

Discovered during v4 Scotia deployment

Randomly happening at Scotia

Release $(Release.DefinitionName) in environment $(Release.EnvironmentName) failed.

Which solution component is affected by this issue?

Portal

What happened?

For Rogers, when the employee attestation record is created, the attestationdatetimelocal field is stored in UTC. This is preventing the email confirmation flow from triggering.

Steps to reproduce

1. log in to portal
2. create onsite appointment
3. check facility management Employee Attestation record - AttestationDateTimeLocal is in UTC

Expected behavior

Value should in in local

Which version of the components are you using

latest

Additional environment details

No response

noticed in MDA

Renaming the file to show the result in the filename. Will save an extra click for users.
E.g. filename should be PositiveScreeningResult.pdf vs ScreeningResult.pdf

Need to remove the Outlook 365 connector from Employee and HSO app.
Need to create a flow to execute when an appt is made (user clicks I agree on attestation).
Need to create a flow for re-attestation email.

O# has provided sample flows, including an appt reminder.

All fields that have default text should show in English (default) and French. This includes Phone number, Personal email, Age Range and Workplace Location.

The default value of EmployeeApp is used.

Noticed on V2 but can be replicated on newer versions.

Attestaion and Booking records are created when the user clicks I Agree on the attestation screen. The button isn't immediately disabled, allowing the user to click multiple times.

Suggest we create a variable to control the state of the button.

Dataverse shows start arrival time from employee app in local.
Dataverse shows start arrival time from portal app in UTC. Portal shows start arrival time in local.

The email notification flow is failing for self-screening as there is no Employee Booking record.

Need to reset the variable to display the label when user clicks I disagree on retest.
Need to reset the variable after all appointments are cancelled.

In the HSO app the summary page has document icon in the header. this icon should have it hover properties set to be consistent with other object properties. Icon should also not be clickable.

One of the members needs a "delay" in the notification email flow. The delay value should be configurable via solution settings or facilities.

Was part of the MDA, Suncor and Scotia initial release.

Camera sometimes defaults to front instead of back. The app currently does not provide the ability to switch from front to back if both are present.

BMO had noted during testing that the Opt-in logic has issues as users can opt-out and still book as well as checking and un checking the optin "isn't smooth".

Local resolution applied:

1. Added I disagree button to the consent popup (was hidden)
2. Created new variable that is set to false when I disagree or the X is checked on the consent popup
3. Variable is set to true when I agree is checked
4. Optin checkbox is set to the value of the variable

1. A user books a screen and sits on the landing page in the employee app.
2. The hso screens them in and makes them positive
3. The employee can still book an appt because landing page hasnt refreshed and subsequently hidden the book a covid screen gallery item

(Confirmed with BMO. Fixed locally - needed to copy the code that is in scrnLanding.OnSelect to glryHomeOptions.Onselect and navigate back to scrnLnading if lastscreen = positive

A handful of members cannot use the Outlook365 connector in the Employee app for booking appointments or re-attestation emails. Replacement flows were needed to send the emails instead.

Could we investigate the use the of previously sent flows for appts, re-attestations and appt reminders for inclusion into the base template

Discovered during V4 prod deployment