Understanding Fluid Discussion Service

Fluid Discussion Service is a simple and easy to use discussion tool that enables you to link Context Specific Discussions to PeopleSoft pages.

Discussion Service enables you to:

Initiate discussion from a page with the context of current transaction
Send/Receive messages and attachments
Easily identify when and who posted what to discussion
Search within discussions
Edit Subject, Add/Remove participants
Close/Reopen Discussions

To access discussion components, users need to be assigned with the below roles:

EOFD_USER: Discussions User, this role is required for accessing Discussions that the user is a participant of.
EOFD_ADMIN: Discussion Service Administrator, user with this role will have access to configure new Discussion Types and Discussion Groups.
EOFD_SUPER_ADMIN: Discussion Service Super Administrator, user with this role will have full access to all the Discussions in the system.

Note: In a cluster environment it is important that you assign the EOFD_USER role to the users in all the nodes.

The fluid discussion service implementation options are listed in the below table.

Sl. No:	Implementation Option	Description	Steps	Result
1	Assign Default Discussion Service at component level	The simplest way to implement Fluid Discussions is to assign the Default Discussion Service as a Related Content Tile or a Related Action	Assign the Default Discussion Service: EOFD_DEFAULT_DSCN to the component using Related Content framework. For details, see Assigning Default Discussion as a Related Content Tile.	Users with access to component can: Add a new topic, add participants and start discussion. View all discussions that they have been added to as participants. The discussion list will only show discussions created for the current component
2	Assign Default Discussion Service with context	Discussions can be made context specific by adding the context parameters to the service	Clone Default Service: EOFD_DEFAULT_DSCN and add context fields to the Service. Assign the cloned Service to the component as a Related Action or Related Content tile and map the page fields to the context fields so that values are passed at run time. For details, see Assigning Default Discussion as a Related Action with Context.	Users with access to component can: Add a new topic, add participants and start discussion. View all discussions that they have been added to as participants. The discussion list will only show discussions created for the current context. (example: current Class, Current Employee, etc.).
3	Implement Discussion Service with additional rules to auto-add dynamic participants and assign privileges.		Create Discussion Type and Discussion User Groups. Clone Default Service: EOFD_DEFAULT_DSCN and add context fields and discussion type field. Assign the cloned Service to the relevant Components and map the page fields to the context fields so that values are sent at run time. Specify the new Discussion type value for the Discussion type parameter. For details, see Implementing Discussion Service with a New Discussion Type.	Dynamic users are automatically added to relevant discussions with appropriate access based on the Discussion Type and Discussion User Group configurations.

Sl. No:

Implementation Option

Description

Steps

Result

Assign Default Discussion Service at component level

The simplest way to implement Fluid Discussions is to assign the Default Discussion Service as a Related Content Tile or a Related Action

Assign the Default Discussion Service: EOFD_DEFAULT_DSCN to the component using Related Content framework.

For details, see Assigning Default Discussion as a Related Content Tile.

Users with access to component can:

Add a new topic, add participants and start discussion.

View all discussions that they have been added to as participants.

The discussion list will only show discussions created for the current component

Assign Default Discussion Service with context

Discussions can be made context specific by adding the context parameters to the service

Clone Default Service: EOFD_DEFAULT_DSCN and add context fields to the Service.

Assign the cloned Service to the component as a Related Action or Related Content tile and map the page fields to the context fields so that values are passed at run time.

For details, see Assigning Default Discussion as a Related Action with Context.

Users with access to component can:

Add a new topic, add participants and start discussion.

View all discussions that they have been added to as participants.

The discussion list will only show discussions created for the current context. (example: current Class, Current Employee, etc.).

Implement Discussion Service with additional rules to auto-add dynamic participants and assign privileges.

Create Discussion Type and Discussion User Groups.

Clone Default Service: EOFD_DEFAULT_DSCN and add context fields and discussion type field.

Assign the cloned Service to the relevant Components and map the page fields to the context fields so that values are sent at run time. Specify the new Discussion type value for the Discussion type parameter.

For details, see Implementing Discussion Service with a New Discussion Type.

Dynamic users are automatically added to relevant discussions with appropriate access based on the Discussion Type and Discussion User Group configurations.

Understanding Fluid Discussion Service

Security Access

Fluid Discussion Service Implementation Options