What are the types of message blocks available in Field Service?

These types of message blocks are available.

Block	Description
installed_inventory	This block retrieves the list of inventory from the install pool.
deinstalled_inventory	This block retrieves the list of inventory from the deinstall pool.
customer_inventory	This block retrieves the list of inventory from the customer pool.
resource_inventory	This block retrieves the list of inventory from the resource pool.
exchanged_inventory	This block retrieves the list of exchanged inventory.
required_inventory	This block retrieves the list of required inventory.
visit	This block can include information related to work orders that belong to a visit into a single message. This block can only be used in scenarios attached to the visit-related launch conditions.
team-members	This block retrieves the list of team-members for a given teamholder and a given day. It can be used in messages that are related to a route. It also it works for the Manual (service request) launch condition.
regular_calendar/oncall_calendar	These two blocks are intended for switching between the regular and on-call calendar types. The regular calendar is selected by default and it is not required to use the block in this case.
activity_workskills	Only the following placeholders can be used in this block: Activity Workskill Activity Workskill ID Activity Workskill label Activity Workskill Required level Activity Workskill Preferable label See What activity message placeholders are available?
destination_resource	This block retrieves values of fields (resource_* placeholders) and custom properties for a destination resource in the following cases: "move activity" trigger "move inventory" trigger
forbidden_resources/required_resources/preferred_resources	These blocks retrieve forbidden/required or preferred resources.
linked_activities	This block retrieves activities linked to the current one. The block has the following syntax: <BLOCK type="linked_activities: label of activity link type">. This block cannot be used without the label of activity link type. All related activity links are also handled as ordered even if the corresponding activity link type has two identical labels.
multiday_activity	This block temporarily switches the context to the related segmentable activity. It can be used in scenarios related to both segmentable activities and their segments. If this block is invoked for a single-day activity, it will not process any records and the result will contain no data.
multiday_activity_segments	This block prints information about all existing segments of a segmentable activity regardless of their statuses (except deleted segments). It can be used in scenarios related to both segmentable activities and their segments. If this block is invoked for a single-day activity, it will not process any records and the result will contain no data.