Notification Manager

Developed a Power Apps Canvas application that streamlines the notification process for users requesting case documentation from field staff. The application automatically applies business rules to generate notification drafts while allowing users to review, modify, or send them as generated. Notifications escalate based on prior correspondence and request age, ensuring timely follow-up. The app also maintains a complete notification history by leveraging the Microsoft Graph API to retrieve Outlook messages, eliminating the need for manual Outlook searches and significantly improving performance.

Default View of the Notification Manager App - Shows all requests with notifications due today.

Pending View - Shows all requests

Filtered View - Shows only the selected Request Type

Edit View - Edit form to manipulate the record.

Notification Draft View - Automatically updates the Request Type based on the corresponding selected gallery item. Allows the user to manipulate the Notification Type, Request Subtype, and Documents Requested fields to dynamically update the Body of the notification.

Filled Draft State - The Body of the email updates dynamically depending on dropdown selections. The To: and Cc: fields also update based on business rules. Users can modify any of the email draft information. This automates the business rule, but gives end users the flexibility to stray from the rule if the situation needs it.

Post Send State - After the notificaiton is sent, the app updates the status field to ‘Sent’, and dynamically calculates the second notification due date (highlighted in yellow) which is five business days from the first notificaiton sent date displayed in the tooltip of the status pill.

History View - After a notification is sent, users can click the history button on the record to view any prior notifications sent, the time it was sent, the message included, and all recipients.

Microsoft Graph API

I accoplished the history requirement of this project by leveraging the Microsoft Graph API functionality of the Office365Outlook.GetEmailsV3 connector.

ClearCollect(
    colFilteredEmails,
    Office365Outlook.GetEmailsV3(
        {
            folderPath: "Inbox",
            searchQuery: "subject:[Documentation Reminder] AND (subject:[1st] OR subject:[2nd]) AND subject:[" & 'Notification Gallery'.Selected.'<redacted> Number' & "]",
            subjectFilter: Blank(),
            from: Blank(),
            to: Blank(),
            cc: Blank(),
            toOrCc: Blank(),
            importance: "Normal",
            fetchOnlyUnread: false,
            fetchOnlyWithAttachment: false,
            includeAttachments: false,
            top: 3,
            skip: 0
        }
    ).value
);
UpdateContext(
    {
        varEmailHtml: Concat(
            colFilteredEmails,
            "<h3>" & ThisRecord.subject & "</h3>" & "<p><strong>From:</strong> " & ThisRecord.from & "<br>" & "<strong>To:</strong> " & ThisRecord.toRecipients & "<br>" & "<strong>Cc:</strong> " & ThisRecord.ccRecipients & "<br>" & "<strong>Received:</strong> " & Text(
                ThisRecord.receivedDateTime,
                "yyyy-mm-dd hh:mm"
            ) & "</p>" & "<div>" & ThisRecord.body & "</div>" & "<hr style='border: 0; border-top: 2px solid #0078d4; margin: 30px 0;' />"
        )
    }
);

This formula executes a Microsoft Graph API call searching the subject line for any matching results for the Advanced Query Search (AQS) on the ‘searchQuery’ line. Results are stored in a local variable called varEmailHtml that is used in the History screen for display.

Email Input Validation

I also had to ensure users did not send emails outside of their department by mistake as it would constitute a breach of confidentiality. To accomplish this, I leveraged the Office365Users.UserProfileV2 connector.

//If(IsBlank(Dropdown2_2.Selected) Or IsBlank(Dropdown2_1.Selected), DisplayMode.Disabled, DisplayMode.Edit)
If(
    IsBlank(TextInput7.Text),
    DisplayMode.Disabled,
    If(
        And(
            // 2. Validate Primary Email & Department
            IsMatch(
                TextInput7.Text,
                "^[a-zA-Z0-9._%+-]+@<domain>\.org$",
                MatchOptions.IgnoreCase
            ),
            IfError(
                IsMatch(
                    Office365Users.UserProfileV2(TextInput7.Text).department,
                    "<redacted>|<redacted>|<redacted>",
                    MatchOptions.IgnoreCase
                ),
                false
            ),
            // 3. Validate Cc Email & Department (ONLY if it is not blank)
            Or(
                IsBlank(TextInput7_4.Text),
                And(
                    IsMatch(
                        TextInput7_4.Text,
                        "^[a-zA-Z0-9._%+-]+@<domain>\.org$",
                        MatchOptions.IgnoreCase
                    ),
                    IfError(
                        IsMatch(
                            Office365Users.UserProfileV2(TextInput7_4.Text).department,
                            "<redacted>|<redacted>|<redacted>",
                            MatchOptions.IgnoreCase
                        ),
                        false
                    )
                )
            ),
            Or(
                IsBlank(TextInput7_3.Text),
                And(
                    IsMatch(
                        TextInput7_3.Text,
                        "^[a-zA-Z0-9._%+-]+@<domain>\.org$",
                        MatchOptions.IgnoreCase
                    ),
                    IfError(
                        IsMatch(
                            Office365Users.UserProfileV2(TextInput7_3.Text).department,
                            "<redacted>|<redacted>|<redacted>",
                            MatchOptions.IgnoreCase
                        ),
                        false
                    )
                )
            ),
            Or(
                IsBlank(TextInput7_5.Text),
                And(
                    IsMatch(
                        TextInput7_5.Text,
                        "^[a-zA-Z0-9._%+-]+@<domain>\.org$",
                        MatchOptions.IgnoreCase
                    ),
                    IfError(
                        IsMatch(
                            Office365Users.UserProfileV2(TextInput7_5.Text).department,
                            "<redacted>|<redacted>|<redacted>",
                            MatchOptions.IgnoreCase
                        ),
                        false
                    )
                )
            ),
            Or(
                IsBlank(TextInput7_6.Text),
                And(
                    IsMatch(
                        TextInput7_6.Text,
                        "^[a-zA-Z0-9._%+-]+@<domain>\.org$",
                        MatchOptions.IgnoreCase
                    ),
                    IfError(
                        IsMatch(
                            Office365Users.UserProfileV2(TextInput7_6.Text).department,
                            "<redacted>|<redacted>|<redacted>",
                            MatchOptions.IgnoreCase
                        ),
                        false
                    )
                )
            ),
            Or(
                IsBlank(TextInput7_7.Text),
                And(
                    IsMatch(
                        TextInput7_7.Text,
                        "^[a-zA-Z0-9._%+-]+@domain>\.org$",
                        MatchOptions.IgnoreCase
                    ),
                    IfError(
                        IsMatch(
                            Office365Users.UserProfileV2(TextInput7_7.Text).department,
                            "<redacted>|<redacted>|<redacted>",
                            MatchOptions.IgnoreCase
                        ),
                        false
                    )
                )
            )
        ),
        DisplayMode.Edit,
        DisplayMode.Disabled
    )
)

This formula is placed in the DisplayMode property of the Send button on the notification screen. Unless the email meets the Regex expression requirements and the user’s profile matches certain search criteria specific to the appropriate department, the button will be disabled preventing accidental emails to outside departments and typos that would cause failures. It’s important to ensure the controls are triggered either on delay or focus out to prevent constant API calls.