ScreenMeet Reporting without Cases

How to use ScreenMeet reporting capabilities when not using Cases

If you are using ScreenMeet with a different object other than a case, you can still take advantage of the reporting capabilities with additional setup.

The setup consists of 3 parts:

• Creating a junction Object

• Updating your parent Object

• Linking your parent object and the ScreenMeet Sessions

Creating the junction Object

Create a new object and call it join_[parent]_with_SM_session remember to change '[parent]' for the object name you are using as the parent of the SM session

Remember this object name as we will refer to it as the junction object in the future.

Add fields to the junction Object

On the junction object create 2 new fields with the following configurations:

• Field 1:

  • Type: Master-Detail Relationship

  • Related To: Your Parent Object (For example Account)

• Field 2:

  • Type: Master-Detail Relationship

  • Related To: ScreenMeet Live Session

Update your Parent object

In your parent object add a new field of type checkbox, with the following configuration:

• Label: Has SM sessions

• Name: Has_SM_sessions

• Default Value: Unchecked (false)

As for field level security Select any profile that needs to have access to the reports and give them read access.

Create the Flow to link your parent object and ScreenMeet Sessions

Now we require the object we just created to be filled with information. To do so we will be using a Flow

Create a new flow with a type of Record-Triggered Flow called.

As per the configuration use the following values

• Object: ScreenMeet Live Session

• Trigger the Flow When: A record is created

• Set entry conditions:

  • Condition Requirements: All Conditions Are met (AND)

  • Field: screenmeet__parentObjectType__c, Operator: equals, Value: your parent object name as a singular in lower case (ex: account)

• Optimize the Flow for: Actions and Related Records

Note: if you have multiple possible parent objects you could skip the Set entry conditions and use a decision block right after to differentiate the objects you are planning to support and repeat the following steps for each type of object you are planning to use as a parent.

Get the parent Object

Add a get records and call it Get Parent [object] select the object you are using as a parent.

For the filter select the field Id, Operator Equals and value {!$Record.screenmeet__parentObjectId__c}

For how many records to store select only the first record

For how to store Record Data Automatically Store all fields

Create the join record

Add a create record element with the following configuration:

• How Many Records to Create: one

• Hot to set the Record Fields: Use separate resources, and literal values

• Object: Select the object you created previously

• Set Field Values:

  • Field: Select the field name that corresponds to the parent object, Value: {!Get_parent_case.Id}

  • Field: ScreenMeet_Live_Session__c, Value: {!$Record.Id}

Update the parent object to change the Has SM session Field

How to Find Records to Update and Set Their Values: Specify conditions to identify records, and set fields individually Object: select your parent object your parent object

Filter Case Records

• Field: Id, Operator: Equals, Value: {!Get_parent_case.Id}

Set Field Values for the Case Records:

• Field: Has_SM_sessions__c, Value: True

With this is done click on save and name the flow with the following name: link_[parent]_with_SM_session

Now you should be able to replicate the reports we provide for cases for other parent object/s. Also please note that some fields will not be available since you will not be using cases which our reports are based on.