Play Details

Play Details is where you can obtain more specifics around a play, such as the accounts, durations, number of instances and much more. While in the Play library, clicking on any Play will direct you to the Play Details page, as seen in the below screenshot;

Play Performance Tab

The Plays Performance tab provides high-level metrics at a glance around the Play.

The screen contains a standard “search bar” that allows you to search for an instance of the Play by any of the column values, along with the option of viewing 5, 10 or 50 Plays instances per page.

Play Details section

This section contains important metrics around the play.

1. Expected Duration – The number here is calculated by adding all the due dates for each individual task in a play and creating a single due date. 
2. Instances – The number here shows the number of times that a version of the Play has been run due to either an automated trigger or a manual re-run.  Currently, if a play has 100 plus instances, it automatically stops the play from running despite being triggered by an automation.
3. Average Duration – The number here would show the average duration (in hours) that it is taking for an instance to be complete.
4. On-time rate – This percentage number (out of 100) indicates how on-time the tasks within the Play have been completed.
5. Last-Launched – This shows the last date during which an instance of the Play was launched.
6. Overdue Rate – This percentage number (out of 100) indicates how the overdue rate is for any Tasks part of the Play.

When has this play been run

The columns in this section can be sorted upon clicking the columns themselves.

1. Account – This column shows the account for which the Play instance was run.
2. Play Instance – This gives a clickable link “view details” that shows details of the Play instance that was run when clicked, along with the version number of the Play (new versions are formed when changes are made).
3. Assigned to – This shows who the Play instance was assigned to at the launch of the Play.
4. Launch Date – This would be the launch date of the Play instance.
5. Due Date – This would be the due date of the Play instance (takes into account the expected duration of the Play).
6. Days remaining – This would be the number of days remaining for the Play instance to complete on time.
7. Status – This would show whether the Play instance is on-track, behind, (i’m unsure of the other statuses if any more)

Play Steps Tab

The “steps” give a view into the components of the play Play which include the triggers and tasks that are part of the play.  The banner card at the top is simply the general details carried over from the performance tab.  

Additional cards and descriptions:

1. Play Details: This card will include any filter information around who the play applies to, if it’s all accounts or a subset of accounts or even users.  It also reflects the Category from the Library that the play is associated with.  Lastly the “Assign to” shows who the play is assigned to. 
2. Trigger:  This card contains details about the “required” trigger that has been set upon and what will cause this play to fire.  Here, you should be able to read clearly as to what is going to cause the play to move to active.
3. Tasks: This card contains details of the “Task” that needs to be carried out by the person assigned that will be created when the play triggers. 

Based on the different use cases there can be many tasks associated with a play so you may see more than one.