MS Tasks (by Planner and To Do)
With each submission the user can select one or more of the following Projects:
Graphic Design
Photography
Social Media
SOURCE News Story
Video
Website
Other
A separate task will be created on the Communications Project Requests plan/board for each project type selected with the submission.
Assignments are made based on the table under the MS Teams section of the page. *When a person is assigned a task, they will receive an email from Microsoft Planner. They should keep an eye out for these emails! They will also receive an email notification when a task is past due.
Access tasks for submitted project
Sign in to MS Teams
Click Teams on left
Click “CHHS Team: Unit Communications Reps”
Click “Project Requests” channel on left
Click “Communications Project Requests” tab at top
You will see 7 buckets on the board that match the different project types
Tasks are created under the project type buckets
Move task from Communications Project Requests board to working project board
Hover your mouse over a task
Click the ellipse in the upper right
Select “Move Task”
4. Select Plan Name from the dropdown (there is a working project board/plan for each area)
5. Select Bucket Name from the dropdown (most project boards are using academic unit names for the buckets)
6. Make any adjustments to the task like assigning additional users within the communications team and most importantly set a DUE DATE so that assignees receive alerts when tasks are due or past due.
MS Teams
When a project request is submitted, a message is posted to the Project Requests channel in Teams and the project lead(s) will be @mentioned in the post.
Currently this is how the notices and assignments are set up:
Academic Unit | Graphic Design | Photography | Social Media | SOURCE News Story | Video | Website | Other |
CM | Avery & Dottie | Avery & Dottie | Avery & Dottie | Gretchen, Tracy & Dottie | Avery & Dottie | Jen & Dottie | Gretchen, Tracy & Dottie |
DM | Avery & Sara | Avery & Sara | Avery & Sara | Gretchen, Tracy & Sara | Avery & Sara | Jen & Sara | Gretchen, Tracy & Sara |
FSHN | Avery & Zara | Avery & Zara | Avery & Zara | Gretchen, Tracy & Zara | Avery & Zara | Jen & Zara | Gretchen, Tracy & Zara |
HDFS | Avery & Lauren | Avery & Lauren | Avery & Lauren | Gretchen, Tracy & Lauren | Avery & Lauren | Jen & Lauren | Gretchen, Tracy & Lauren |
HES | Avery & Sarah | Avery & Sarah | Avery & Sarah | Gretchen, Tracy & Sarah | Avery & Sarah | Jen & Sarah | Gretchen, Tracy & Sarah |
OT | Avery & Bobby | Avery & Bobby | Avery & Bobby | Gretchen, Tracy & Bobby | Avery & Bobby | Jen & Bobby | Gretchen, Tracy & Bobby |
RDC | Avery & Gretchen | Avery & Gretchen | Avery & Gretchen | Gretchen & Tracy | Avery & Gretchen | Jen & Gretchen | Gretchen & Tracy |
SOE | Avery & Ben | Avery & Ben | Avery & Ben | Gretchen, Tracy & Ben | Avery & Ben | Jen & Ben | Gretchen, Tracy & Ben |
SSW | Avery & Ben | Avery & Ben | Avery & Ben | Gretchen, Tracy & Ben | Avery & Ben | Jen & Ben | Gretchen, Tracy & Ben |
Power Automate
When a project request form is submitted there are three automated workflows that run:
Post New Project Request to Planner and Teams for CM – DM – HES – HDFS – RDC
Post New Project Request to Planner and Teams for OT – FSHN
Post New Project Request to Planner and Teams for SOE – SSW
*We had to create three separate flows because there is a limit to the number of actions (500) that ban a only 500 actions can be performed in a single flow
Access workflow
Sign in to Office 365 with the chhs_communications@colostate.edu account. Password is stored in KeePass.
Click the app launcher in the upper left
Select PowerAutomate from the list of apps
Click My flows from the sidebar menu
Hover over the flows to view the name
Edit workflow
Hover over the workflow
Click the pencil icon to edit the flow
View workflow run history
Double click on the workflow to see the details and run history
After a flow runs you can see the details of the flow to help troubleshoot if the flow failed
Double click on the run to open the details
The Error Details are listed on the right hand side
You can then drill down to the section where the flow failed and you can see the inputs/outputs that caused the error