DEX Event Experience Platform

User Documentation

Version 2.0 | January 2026
Deloitte Deutschland GmbH

Created by: Eike Brenneisen, Andreas Enk, Nils Felten

1. Management Summary
2. Application Description
- 2.1 Purpose and Benefits
- 2.2 Technical Architecture
- 2.3 Architecture Flowchart
- 2.4 Power App Screens
- 2.5 Event Creation - Architecture in Detail
3. Power Automate Flows - Overview
4. Flow Detail Documentation (with clustered Actions)
- 4.1-4.4 Event Management
- 4.5-4.9 Registration
- 4.10-4.12 Check-In
- 4.13-4.17 Email & Calendar
- 4.18-4.23 Utility & Administration
5. Appendix

1. Management Summary

The DEX Event Experience Platform is a fully Microsoft Power Platform-based event management solution for internal Deloitte events. The platform digitizes and automates the entire event lifecycle.

Initial Situation

Before DEX: Manual event management with email registrations, Excel lists, manual calendar maintenance, and paper check-in lists.

The Solution

DEX automates these processes through Power Apps (Frontend), Power Automate (23 Flows), SharePoint Online (Data) and Office 365 (Email/Calendar).

Achieved Results

15+ Events	successfully executed
80% time saved	in event administration
23 Flows	implemented and productive
100% Compliance	BR and SecO approved

Core Functions

Event Creation: Automatic SharePoint subsite with participant list
Self-Service Registration: Registration with automatic confirmation email and calendar entry
Waiting List Management: Automatic advancement when cancellations occur
QR Code Check-In: Individual QR codes for quick check-in
Email Communication: Centralized via shared mailbox (no_reply.events@deloitte.de)

2. Application Description

2.1 Purpose and Benefits

DEX replaces manual event processes with automated workflows for organizers, participants, and check-in teams.

Benefits for Organizers

Quick event creation with automatic infrastructure
Real-time overview of registrations and waiting list
Integrated email communication

Benefits for Participants

Self-service registration without email
Automatic Outlook calendar entry
Personal QR code for check-in

2.2 Technical Architecture

Component	Technology	Purpose
Frontend	Power Apps	User Interface
Backend	Power Automate (23 Flows)	Business Logic
Data	SharePoint Online	Events, Participant Lists
Communication	Office 365 Outlook	E-Mail, Calendar

SharePoint Structure

Element	Path
Base Site	https://deudeloitte.sharepoint.com/sites/DOL-c-DE-B2Run/
Events List	/Lists/Events
Event Subsites	/sites/DOL-c-DE-B2Run/[EventName]/
Participant List	/[EventName]/Lists/Participant List

Environments

The project has three separate environments for the entire development lifecycle:

Environment	Purpose	Description
Development (DEV)	Development	Active development of new features and bug fixes. Unstable environment for developer testing.
Quality Assurance (QA)	Test & Acceptance	Quality assurance and User Acceptance Testing (UAT). Stable test environment.
Production (PROD)	Production	Live system for end users. Only tested and released versions.

Service Accounts & Connection References

All connection references in Power Automate and Power Apps are provided through Service Accounts:

Aspect	Description
Authentication	Dedicated service accounts for all connector connections
SharePoint	Service account with Site Collection Admin rights
Outlook/Exchange	Service account with access to shared mailbox
Office 365 Users	Service account with Directory Read permission
Benefits	Independent of personal accounts, central management, audit trail

2.3 Architecture Flowchart

The following diagram shows the data flow between users, Power App, Power Automate Flows, and data stores (SharePoint & Office 365).

SharePoint List Structure in Detail

Data Flow: Registration Process

2.4 Power App Screens

The DEX Power App includes 27 screens for different user groups and use cases.

Screen Navigation

Screen-Descriptionen

Screen	Purpose	Key Features
LandingScreen	Welcome page	Start button, info text, email link to developers
StartScreen	Main Menu	Navigation to Registration, My Events; Settings icon (Admin only)
RegisterScreen	Event selection	Gallery with events, filtered by location and audience
RegisterB2EventScreen	B2Run Registration	Form with running distance, team, additional fields
RegisterOtherEventScreen	Standard Registration	Form for JP Morgan Run and other events
MyEventsScreen	My Events	Registered events + waiting list; deregistration option
CheckInScreen	QR Code Check-In	BarcodeReader, Office365 profile picture, Check-In button
SettingsScreen	Admin area	Create event, edit, send emails
AllEventsScreen	Event-Overview	DataTable with all events (Admin)

App Data Sources

Connector	Data Source	Usage
SharePoint Online	Events	Main list of all events
	Registrations	Queue for new registrations (trigger)
	Deregistrations	Queue for deregistrations (trigger)
	Event visitors	Participant list (dynamic per event)
	Check-In	Queue for check-in actions
	Admins	List of admin users
Office 365 Users	User Profile	Name, department, location, profile picture
Power Automate	GetParticipantEvents	Loads "My Events" for user
	CheckRegistrationStatus	Checks registration status
	GetWaitinglistPosition	Waiting list position
	CheckInFromQRCode	Performs check-in
	SendMailParticipantlist	Send mass email
	ExtractParticipantMails	Extract email addresses

User Groups & Permissions

Role	Recognition	Accessible Screens
Participant	Every authenticated user	LandingScreen, StartScreen, RegisterScreen, MyEventsScreen
Admin	Email in Admins list	+ SettingsScreen, CheckInScreen, AllEventsScreen, EventCreation, SendMail

Admin check in code:

If(IsBlank(LookUp(Admins,'Admin Account'.Email = User().Email)), false, true)

2.5 Event Creation - Architecture in Detail

Event creation is a central process in the DEX platform. This section documents the Power App architecture for event creation to support potential modernization.

Event Typee Selection (EventCreationSelectionScreen)

The entry point for event creation is the EventCreationSelectionScreen, which offers three event types:

Form Architecture (Form Control)

Each event creation form uses a Power Apps Form Control with the following structure:

Property	Value	Description
Control	`Form@2.4.4`	Standard Power Apps Form
Layout	`Vertical`	Vertical arrangement of fields
DataSource	`=Events`	Direct binding to SharePoint Events list
DefaultMode	`=FormMode.New`	Always in creation mode
OnVisible	`=ResetForm(Form1)`	Reset form when opening

Field Configuration by Event Typee

Common Fields (all event types):

Field	Control	DataField	Required
Title	TextInput (Multiline)	`Title`	Yes
Standort	TextInput	`Standort`	No
Standort Filter	ComboBox	`Standort_x0020_Filter`	No
Organizer	ComboBox (MultiSelect)	`Organzier`	Yes
Event time	DatePicker + DropDown (HH:MM)	`Event_x0020_time`	Yes
Event end time	DatePicker + DropDown (HH:MM)	`Event_x0020_end_x0020_time`	Yes
Last Register Date Time	DatePicker + DropDown	`Last_x0020_Register_x0020_Date_x`	Yes
Last Deregister Time	DatePicker + DropDown	`Last_x0020_Register_x0020_Event_`	Yes

B2Run-specific fields:

Field	Control	Description
Max Fun-runner	Number Input	Maximum number of fun runners
Max Durchstarter	Number Input	Maximum number of serious runners
Startblock	ComboBox (Multi)	Available start blocks ["17:00", "18:30"]
T-Shirtgrößen	ComboBox (Multi)	Available T-shirt sizes
T Shirt Größe visible	Toggle	Show T-shirt selection?

Other Event-specific fields:

Field	Control	Description
Audience Mail	TextInput (Dialog)	Email addresses for access restriction
Frage Freitextfeld 1/2	TextInput	Custom question fields
Dropdownfeld 1/2	Dialog with Collection	Custom dropdown options
Location Hotel	TextInput	Hotel information (if relevant)
Allergien visible	Toggle	Show allergies field during registration?

DataCard Structure

Each field is implemented as a TypedDataCard with the following structure:

TypeedDataCard@1.0.7
├── DataCardKey (Text)        - Field label
├── DataCardValue (Input)     - Input field (TextInput/ComboBox/DatePicker)
├── ErrorMessage (Text)       - Validation error
├── StarVisible (Text)        - Required indicator "*"
└── InfoButtonCanvas          - Help tooltip (optional)

Submit Logic

When saving an event:

Form.Submit() - Creates new entry in Events list
SharePoint Trigger - "Item Created" triggers NewEventAdded_SiteProvis Flow
Flow processing:
- Creates SharePoint subsite
- Calls ApplyTemplateB2Run or ApplyTemplateOtherEvent (based on content type)
- Sets permissions
- Creates Outlook calendar entry

Modernization Recommendations

For future modernization of event creation:

Area	Current	Recommendation
Form	3 separate screens	Single dynamic form with conditional display
Validation	DataCard-based	Central validation logic with Custom Connector
Event types	Hardcoded in screens	Configuration list for dynamic event types
Field configuration	Defined per screen	Metadata-driven form based on content type
Custom Fields	Freitextfeld1-7	JSON schema for flexible field configuration

3. Power Automate Flows - Overview

The DEX platform includes 23 Power Automate Flows in five categories:

3.1 Event Management (4 Flows)

Flow	Trigger	Description
NewEventAdded_SiteProvis	SharePoint Item Created	Main flow: Creates subsite, template, Outlook event
ApplyTemplateB2Run	Child Flow	B2Run participant list with special fields
ApplyTemplateOtherEvent	Child Flow	Standard participant list
EventPermission	Manual Button	Set permissions for target audience

3.2 Registration (5 Flows)

Flow	Trigger	Description
RegisterParticipant	SharePoint Item Created	Registration: capacity check, registration/waiting list
DeregisterParticipant	SharePoint Item Created	Deregistration with automatic advancement
CheckRegistrationStatusParticipant	Power App	Checks status: registered/waitlist/not_registered
GetWaitinglistPosition	Power App	Determines position on waiting list
GetParticipantEvents	Power App	Lists "My Events"

3.3 Check-In (3 Flows)

Flow	Trigger	Description
Check-In	SharePoint Item Created	Manual check-in
CheckInFromQRCode	Power App	Check-in via QR code scan
EventQRCodeGenerator	Manual Button	Generates QR codes, sends via email

3.4 Email & Calendar (5 Flows)

Flow	Trigger	Description
SendMailSharedMailbox	Child Flow	Central email function
SendMailParticipantList	Power App	Mass email to participants
RegisterOutlookEventParticipant	Child Flow	Adds participant to Outlook appointment
CreateOutlookEventSharedMailbox	Child Flow	Creates Outlook appointment
HelperFlowMailToRegistered	Manual Button	Helper flow for special emails

3.5 Utility & Administration (6 Flows)

Flow	Trigger	Description
Flow-Dokumentation-Export	Manual Button	Exports flow definitions
SharePoint_Batch_Update_V2	Manual Button	Batch updates via REST API
SetPermissionForSubWeb	Manual Button	Set subsite permissions
UpdateAllEventsWithNewFields	Manual Button	Migration: Add new fields
CorrectOutlookID	Manual Button	Corrects Outlook event IDs
SP List Numbering Correction	Manual Button	Corrects No. field

4. Flow Detail Documentation

Each flow is documented with clustered actions. The actions are divided into logical groups, each with a description of what the cluster does.

4.1 NewEventAdded_SiteProvis

Flow-ID	9722b1ef-8f72-83a4-55f8-e69cb548ea04	Status	Stopped (manuelle Aktivierung)
Trigger	SharePoint - When an item is created (Intervall: 1 Minute)

Description

The central flow for event creation. Is automatically triggered when a new event is created in the Events list. Creates the complete infrastructure: SharePoint subsite, participant list, Outlook appointment and notifies the organizer.

Supported Event Types

B2Run Event: Uses ApplyTemplateB2Run with special fields
JP Morgan Run / Other: Uses ApplyTemplateOtherEvent

1. Initialization & Status Update

Sets event status to "Under Construction" to indicate creation is in progress
Initializes all required variables (Titel, URL, Content Typee)
Prepares data for further processing

Action	Type	Description
Update_item-_Set_Status_to_Under_Construction	SharePoint PatchItem	Status → "Under Construction"
Initialize_variable-_varSiteTitle	InitializeVariable	Event-Titel speichern
Initialize_variable-_varSiteURL	InitializeVariable	URL-Variable initialisieren
Initialize_variable-_varContentTypeeName	InitializeVariable	Event-Type speichern

2. URL-Bereinigung

SharePoint URLs cannot contain certain characters (spaces, #, %, etc.)
Event title is iteratively cleaned of invalid characters
Result is a URL-safe site name

Action	Type	Description
Compose-_Create_FilterCharArray	Compose	Array with invalid characters
Apply_to_each (Filter)	Foreach	Removes each invalid character

3. Create SharePoint Subsite

HTTP POST to SharePoint REST API creates new subsite
Template STS#3 (Team Site without M365 Group) is used
ServerRelativeUrl is extracted from API response

Action	Type	Description
Send_an_HTTP_request-_Create_New_Sub_Site	SharePoint HttpRequest	POST to /_api/web/webinfos/add
Parse_JSON-_Parse_Response	ParseJson	Extracts ServerRelativeUrl
Compose-_FinalURL	Compose	Combines to final URL

4. Call Template Flow

Switch branches based on Content Type (Event Type)
B2Run Events → ApplyTemplateB2Run (Special fields for running distance, team)
Other Events → ApplyTemplateOtherEvent (Standard fields)

Action	Type	Description
Switch	Switch	Branches by event type
Run_a_Child_Flow (Template)	Workflow	Calls template flow

5. Create Outlook Calendar Entry

Start/end time is converted to ISO format
CreateOutlookEventSharedMailbox creates appointment in shared mailbox
Outlook event ID is stored for later participant invitations

Action	Type	Description
Compose_2, Compose_3	Compose	Formats date to ISO
Run_a_Child_Flow_1 (Outlook)	Workflow	Creates Outlook appointment
Update_item_-_Events	SharePoint PatchItem	Stores Outlook ID

6. Notify Organizer & Set Permissions

Logos are loaded and prepared as data URI for email
Each organizer receives confirmation email with link to participant list
If audience is defined, EventPermission is called

Action	Type	Description
Get_file_content-_Logo	SharePoint GetFileContent	Loads event logo
For_each (Organizer)	Foreach	Iterates over organizers
Send_an_email_from_shared_mailbox	Office 365	Sends confirmation email
Run_a_Child_Flow_3 (Permission)	Workflow	Sets permissions

4.2 ApplyTemplateB2Run

Flow-ID	a95f473c-36d2-d9b3-e8fe-16896b20c492	Status	Started
Trigger	Manual Button (Child Flow) with URL parameter

Description

Called by NewEventAdded for B2Run-Events. Creates the participant list with all B2Run-specific fields.

1. Receive Parameters

Receives subsite URL from calling flow
URL defines where the Participant List will be created

Action	Type	Description
Initialize_variable-_varURL	InitializeVariable	Stores subsite URL

2. Create Participant List & Fields

POST to /_api/web/lists creates the "Participant List"
Standard fields: Participantname, Email, Status (Choice), Nr, CheckIn
B2Run fields: Freitextfeld1-7 for race distance, team etc.

Action	Type	Description
Send_HTTP_request-_Create_Participant List	SharePoint HttpRequest	Creates list
Send_HTTP_request-_Create_Fields	SharePoint HttpRequest	Creates all fields
Respond_to_a_Power_App_or_flow	Response	Confirms success

4.3 ApplyTemplateOtherEvent

Flow-ID	cfcce4df-e10c-eb93-b80e-b65c12c4de4c	Status	Started
Trigger	Manual Button (Child Flow)

Description

Creates standard participant list for JP Morgan Run and other events. Structure identical to ApplyTemplateB2Run, but allows separate customizations.

4.4 EventPermission

Flow-ID	8c702f7e-b925-6769-ba71-102a65c4d0be	Status	Started
Trigger	Manual Button with Parameters (ItemId, Audience)

Description

Manages permissions for events with restricted target audience. Removes default sharing and sets specific permissions for the defined audience.

Permission Management

Removes all existing shares for the event
Grants the audience group read access
Grants the organizer full access

Action	Type	Description
Stop_sharing_an_item	SharePoint UnshareItem	Removes shares
Grant_access (Audience)	SharePoint GrantAccess	Read access for audience
Grant_access (Organizer)	SharePoint GrantAccess	Full access for organizer

4.5 RegisterParticipant

Flow-ID	12db96ef-b7e7-6cf8-c1c4-24d7f9fb96c5	Status	Started
Trigger	SharePoint - When an item is created (Interval: 5 minutes)

Description

The core of the registration process. Processes new participant registrations, checks capacity and decides between registration or waitlist.

1. Initialization & Data Query

Initializes variables for item ID, user list ID, status
Loads event details from SharePoint (capacity, current participant count)
Counts already registered participants

Action	Type	Description
Initialize_variables	InitializeVariable	Working variables
Get_item (Event)	SharePoint GetItem	Loads event details
Get_items (Registrations)	SharePoint GetItems	Counts registrations

2. Capacity Check & Decision

Compares current participant count with maximum capacity
Space available → Status "Registered", email + calendar entry
Event full → Status "Waitlist", info about position

Action	Type	Description
Condition (Capacity)	If	Checks: Registered < Capacity?
Update_item (Registered)	SharePoint PatchItem	Status → "Registered"
Update_item (Waitlist)	SharePoint PatchItem	Status → "Waitlist"

3. Email & Calendar Integration

On registration: Participant is added to Outlook event
Confirmation email via shared mailbox
On waitlist: Info email with position

Action	Type	Description
Run_a_Child_Flow (Outlook)	Workflow	RegisterOutlookEventParticipant
Run_a_Child_Flow (Mail)	Workflow	SendMailSharedMailbox

4.6 DeregisterParticipant

Flow-ID	b2a06173-2d29-950e-7470-24cbd2a4c247	Status	Started
Trigger	SharePoint - When an item is created (Interval: 5 minutes)

Description

Processes deregistrations and triggers automatic waitlist advancement. The first waitlist participant is automatically registered.

1. Load Data & Validate Deregistration

Loads participant data and event logos
Checks if deregistration is valid
Sets status to "Cancelled" or deletes entry

Action	Type	Description
Get_item_-_Event_Visitors	SharePoint GetItem	Loads participant data
Condition (Valid)	If	Checks validity
Update_item (Cancel)	SharePoint PatchItem	Status → "Cancelled"

2. Waitlist Advancement (FIFO)

Waitlist is queried sorted by creation date
First entry (oldest) is selected for advancement
Status → "Registered", email + calendar entry for advanced participant

Action	Type	Description
Apply_to_each (Waitlist)	Foreach	Finds first waitlist participant
Run_a_Child_Flow (Promote)	Workflow	Status, mail, calendar for advanced participant

4.7 CheckRegistrationStatusParticipant

Description

Checks the registration status of a user for an event. Returns: registered, waitlist or not_registered.

Status Check

Searches participant list for user email
Reads status value from found entry
Returns status to Power App

4.8 GetWaitinglistPosition

Description

Determines the current waiting list position of a participant (FIFO principle).

Position Calculation

Loads all waitlist entries sorted by Created
Counts position up to the searched email
Position 1 = next to be advanced

4.9 GetParticipantEvents

Description

Lists all events for the "My Events" view in the Power App.

Event Query

Checks all active events for user participation
Returns list with event details and status

4.10 Check-In

Description

Manual Check-In on event day. Fallback when QR code doesn't work.

Perform Check-In

Identifies participant from check-in queue
Sets CheckIn field to true
Stores check-in timestamp

4.11 CheckInFromQRCode

Description

Check-In via QR code scan. The check-in team scans the QR code, the flow identifies and checks in the participant.

1. Process QR Code

Receives QR code content from Power App
Parses JSON to extract participantId and eventId
Validates QR data format

2. Validation & Check-In

Checks if participant is registered and not yet checked in
Sets CheckIn=true, stores timestamp
Returns success/error with participant name

4.12 EventQRCodeGenerator

Description

Generates individual QR codes for all registered participants and sends them via email.

1. Load Participants

Loads event details and all participants with status "Registered"
Prepares email assets

2. Generate & Send QR Codes

For each participant: create JSON payload with ID and email
Generate QR code via API, encode as Base64
Send email with embedded QR code

4.13 SendMailSharedMailbox

Description

Central email function. Sends emails via the shared mailbox no_reply.events@deloitte.de.

Email Dispatch

Receives parameters: recipient, subject, HTML body
Sends via Office 365 Outlook Connector
Called by other flows as child flow

4.14 SendMailParticipantList

Description

Mass email to all participants or only waitlist of an event.

Batch Dispatch

Filter options: all, registered, waitlist
Iterates over participants, sends individual emails
Returns number of sent emails

4.15 RegisterOutlookEventParticipant

Description

Adds participant to existing Outlook calendar entry via Graph API.

Attendee Add

Retrieves existing event via Graph API
Adds email to attendee list
PATCH request updates event

4.16 CreateOutlookEventSharedMailbox

Description

Creates new Outlook appointment in shared mailbox calendar. Base appointment for participant invitations.

Create Event

Receives event details (title, start, end, location)
Creates calendar entry via Outlook Connector
Returns event ID for later reference

4.17 HelperFlowMailToRegistered

Description

Helper flow for special email scenarios to registered participants.

4.18 Flow-Dokumentation-Export

Description

Exports the definitions of all flows to a text file for documentation purposes.

Export Process

Lists all flows in the environment
Reads JSON definition of each flow
Writes all definitions to SharePoint file

4.19 SharePoint_Batch_Update_V2

Description

Batch updates on SharePoint lists via REST Batch API for better performance.

Batch Processing

Bundles multiple updates into one request
POST to /_api/$batch endpoint
Up to 1000 operations per batch

4.20 SetPermissionForSubWeb

Description

Sets permissions on SharePoint subsites. Breaks inheritance and assigns specific permissions.

Set Permissions

Breaks permission inheritance of subsite
Assigns users/groups specific permissions

4.21 UpdateAllEventsWithNewFields

Description

Migration flow: Adds new fields (Freitextfeld3-7) to all existing participant lists.

Migration

Iterates over all event subsites
Creates missing fields via SharePoint REST API
Error handling when field already exists

4.22 CorrectOutlookID

Description

Corrects faulty Outlook event IDs in the Events list by matching with Graph API.

ID Correction

Identifies events with faulty/missing Outlook ID
Searches for matching appointment in shared mailbox calendar
Updates OutlookEventID in SharePoint

4.23 SP List Numbering Correction

Description

Corrects the numbering (Nr. field) in participant lists after manual changes.

Correct Numbering

Loads participants sorted by creation date
Sets No. field to sequential number (1, 2, 3...)
Ensures continuous numbering without gaps

5. Appendix

5.1 Glossary

Term	Explanation
Child Flow	A flow that is called by another flow
Shared Mailbox	Shared mailbox (no_reply.events@deloitte.de)
Subsite	Subsite within a SharePoint Site Collection
FIFO	First In, First Out - queue principle
Graph API	Microsoft Graph REST API for Office 365 services

5.2 Technical References

Resource	URL / Value
SharePoint Base Site	https://deudeloitte.sharepoint.com/sites/DOL-c-DE-B2Run/
Shared Mailbox	no_reply.events@deloitte.de
Power Apps Environment	Default Environment

5.3 Contact

For questions about the platform or technical issues:

Eike Brenneisen - Product Owner, Development, Event Coordination & Onboarding
Nils Felten - Product Owner, Development, Event Coordination & Onboarding
Andreas Enk - Product Owner, Development

DEX Event Experience Platform - User Documentation v2.0
Generated: January 2026

DEX Event Experience Platform

Table of Contents

1. Management Summary

Initial Situation

The Solution

Achieved Results

Core Functions

2. Application Description

2.1 Purpose and Benefits

Benefits for Organizers

Benefits for Participants

2.2 Technical Architecture

SharePoint Structure

Environments

Service Accounts & Connection References

2.3 Architecture Flowchart

SharePoint List Structure in Detail

Data Flow: Registration Process

2.4 Power App Screens

Screen Navigation

Screen-Descriptionen

App Data Sources

User Groups & Permissions

2.5 Event Creation - Architecture in Detail

Event Typee Selection (EventCreationSelectionScreen)

Form Architecture (Form Control)

Field Configuration by Event Typee

DataCard Structure

Submit Logic

Modernization Recommendations

3. Power Automate Flows - Overview

3.1 Event Management (4 Flows)

3.2 Registration (5 Flows)

3.3 Check-In (3 Flows)

3.4 Email & Calendar (5 Flows)

3.5 Utility & Administration (6 Flows)

4. Flow Detail Documentation

4.1 NewEventAdded_SiteProvis

Description

Supported Event Types

4.2 ApplyTemplateB2Run

Description

4.3 ApplyTemplateOtherEvent

Description

4.4 EventPermission

Description

4.5 RegisterParticipant

Description

4.6 DeregisterParticipant

Description

4.7 CheckRegistrationStatusParticipant

Description

4.8 GetWaitinglistPosition

Description

4.9 GetParticipantEvents

Description

4.10 Check-In

Description

4.11 CheckInFromQRCode

Description

4.12 EventQRCodeGenerator

Description

4.13 SendMailSharedMailbox

Description

4.14 SendMailParticipantList

Description

4.15 RegisterOutlookEventParticipant

Description

4.16 CreateOutlookEventSharedMailbox

Description

4.17 HelperFlowMailToRegistered

Description

4.18 Flow-Dokumentation-Export

Description

4.19 SharePoint_Batch_Update_V2

Description

4.20 SetPermissionForSubWeb

Description

4.21 UpdateAllEventsWithNewFields

Description