The Submit an Idea micro-app is a generic micro-app that allows employees to post ideas to authorities deemed appropriate by management.
The micro-app is configured to create cloud communication messages on a configured channel. In order to allow regular employees to submit ideas to the channel, it should be made public for reading and only the appropriate groups should be marked as able to subscribe to it.
The employee composing the message will receive a copy of the idea as a cloud comm card and will be able to see the interactions and comments/answers that occur for that idea.
Configuring the Submit An Idea micro-app
- First, assign the Limeade ONE Cloud Communication Submit an Idea micro-app to the role the users wishing to communicate will be assigned to
- Configure the channel that a user wishes employees to use for communication
- See section about configuring channels
- Configure the micro-app instance so it sends to the appropriate channel
- The title given to the application instance will be the title that is displayed when running the application
- See section about available configuration options
Available configuration options
Configuration options are set in the application instance configuration form.
|
Configuration option name |
Expected |
Description |
|
TargetChannelName |
String |
The name of the channel the micro app should use when sending out the question. |
|
TargetGroupIds |
Guids separated by comma if more than one. |
The id (Guid) of the group or groups you want the application to target when sending the question. These are not mandatory. |
|
SendPushNotification |
True or False |
Indicates if a push notification should be sent to the targets of the message when it is sent. |
|
SummaryTruncationLength |
Integer |
Indicates how many characters of the question should be used to create the summary card of the message. |
|
BannerImageUrl |
url |
Indicates a url to a custom banner image you want to use in the app instead of the default provided one. |
|
TitleFormat |
String |
Allows you to control the title that will be set as the title for the message. It allows you to have the following tokens that will be replaced when creating the message : |
|
PostActionLabel |
String |
The label showed for the action button that will be used to send the message. |
|
PostTextWatermark |
String |
The watermark text showed in the post message field. |
|
MarkAsImportant |
True or False |
When set to true the user messages will be set as important. |
|
SendCardToAuthor |
True or False |
When set to true the author of the message will also receive the card. |
|
ShowPictureUpload |
True or False |
When set to false the picture upload isn’t available in the micro-app. |
|
PictureUploadLabel |
String |
The label showed on the picture chooser |
|
SuccessLabel |
String |
The message showed when the submit was succesful |
|
SuccessLabelTitle |
String |
The title showed for the success message |
|
ErrorLabel |
String |
The message showed when the submit was not succesful |
|
ErrorLabelTitle |
String |
The title showed for the error message |
Localizable configuration elements
Some configuration elements are localizable. That means that a different text can be specified for, depending on the current language of the user. To localize the text of one of the options, just add .[language code] at the end of the parameter name. Always keep a version without localization, as this will serve as the default and add the same parameter with the extra language code for other languages.
Example: TextFormat = default, TextFormat.fr = French.
Configuring channels for employee communication
Channels are configured in the Portal / Cloud Comm / Channels form.
Define a channel where all employees can write to and only certain groups can actually subscribe to receive the communications from those employees.
Figure 1 - Configuring a public write / private read channel
In the above image, a public channel called Cloud Comm Ideas was configured. For that channel, only users in the Cloud Comm Managers group will be allowed to subscribe and therefore receive messages targeted to the Cloud Comm Ideas channel.
Note: channels are subscription-based, so if users do not subscribe they will not receive the messages. To force all users in the configured group to get the message, the channel can be made mandatory, in which case all users in the configured group will always receive all the messages.
When a user submits an emergency with the micro-app, a cloud communication message is sent to the channel. Users subscribed to that channel will get the message and will be able to interact with the author of the question by commenting and liking. The author will also have received that card so they will also be able to interact.
Finding messages sent by users
To find all messages that have been submitted by users go to the Portal/Cloud Comm/Messages form. The messages form offers filters that can find all messages sent on the channel configured to receive the messages.
Figure 2 - The messages form filtering on a channel
Comments
0 comments
Article is closed for comments.