...
If you have content that you think might be useful for other users and you want to be an active part in the process, you can send it to us through our content proposal tool for evaluation.
Content proposal tool explained
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
| Rw ui steps macro | ||||
|---|---|---|---|---|
To access the content proposal tool to submit you content for evaluation and publishing you can click the Content proposal button at the top right (the button with a share icon).  
In the Content proposal window, select the type of content you would like us to publish.  
Then, introduce all the settings of the item so that we can effectively recreate it. Try to be as descriptive as possible and provide all the details you can for an effective recreation. In some content types such as Activeboards or lookups you can provide an existing item to offer a more concise insight. See the different settings for the different content types in the section below.
Check the terms and conditions box (required) and click Submit proposal when you finish. After you submit your proposal, it will be evaluated by the Exchange team. While being evaluated, it will be in pending status and you will be notified whether it is approved or rejected.  |
...
 |
Settings for each content type
Activeboards
| 1 | Proposed name: specify the name for the Activeboard. |  |
| 2 | Content description: specify the details of the Activeboard, such as the purpose, the widgets it’s composed of, or the intended data composition. | |
| 3 | Source requirements: specify the data tables required to extract the data from. | |
| 4 | Open data: choose a method to replicate the Activeboard.
| |
| 5 | Sample screenshots: provide screenshots of the Activeboard as support materials to help us understand the intended content and layout. | |
Applications
| 1 | Proposed name: specify the name for the application. |  |
| 2 | Content description: specify the details of the application, such as the purpose, the different components and areas, or how it works. | |
| 3 | Link: provide the URL of the Github project so that we can analyze the structure and coding of the application. You can use our Application Developer Kit to maximize compatibility and efficiency when creating new applications. | |
| 4 | Source requirements: specify the data tables required to extract the data from. | |
| 5 | Sample screenshots: provide screenshots of the application as support materials to help us understand the intended content and layout. | |
Alerts
| 1 | Proposed name: specify the name for the alert. |  |
| 2 | Content description: specify the details of the alert, such as the anomaly to find, the trigger method, or the specific settings according to the trigger method chosen. | |
| 3 | Query area: specify the query that defines the alert condition. |
Lookups
| 1 | Proposed name: specify the name for the lookup. |  |
| 2 | Content description: specify the details of the lookup, such as the context of use, fields contained, or the key field used to correlate values. | |
| 3 | Open data: choose a method to replicate the lookup.
| |
Synthetic data
| 1 | Proposed name: specify the name for the synthetic data. |  |
| 2 | Content description: specify the details of the synthetic data, such as the context of use, fields contained, or the specific items it’s designed for (e.g. Windows Activity Activeboard). | |
| 3 | Source requirements: specify the data tables that will contain the synthetic data. | |
| 4 | Synthetic data: specify the values and data patterns to simulate. | |