You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/developerportal/_index.md
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -14,27 +14,29 @@ cascade:
14
14
15
15
## Introduction
16
16
17
-
[Apps](https://sprintr.home.mendix.com) is one of the key components of the Mendix Portal. In **Apps**, you can create, deploy, and manage apps as well as collaborate with each other. After you open **Apps**, you will get a summary of your current apps, your company apps, and your pending invites.
17
+
[Apps](https://sprintr.home.mendix.com) is one of the key components of the Mendix Portal. In **Apps**, you can create, deploy, and manage apps, as well as collaborate with others. **Apps** provides a summary of your current apps, your company apps, and your pending invites.
***App name** – Every app must have a name that abides by these requirements:
32
32
33
-
The app name cannot be longer than 200 characters (but preferably, no more than 40 characters). The app name can contain letters, numbers, underscores (`_`), dashes (`-`), or white spaces (). The app name must not start with a white space.
33
+
* It cannot be longer than 200 characters, but Mendix recommends no more than 40 characters.
34
+
* It can contain letters, numbers, underscores (`_`), dashes (`-`), or white spaces ().
35
+
* It must not start with a white space.
34
36
35
37
***App description (Optional)** – Give your app a short description. This is optional.
36
38
37
-
***App icon** – Mendix has generated an icon for your app. You can change the color of the icon if you like. You can upload a custom icon in the [App Settings](/developerportal/collaborate/general-settings/#general) page after you created the app.
39
+
***App icon** – Mendix has generated an icon for your app. You can change the color of the icon if you like. You can upload a custom icon in the [App Settings](/developerportal/collaborate/general-settings/#general) page once you have created the app.
38
40
39
41
3. Click **Next** in the lower-right corner to go to step 2.
40
42
@@ -52,9 +54,7 @@ To create a new app and start collaborating, you can perform the following proce
52
54
53
55
The **My Apps** tab displays all the apps for which you are a [Team](/developerportal/general/team/) member.
54
56
55
-
If you pin an app, it stays on top.
56
-
57
-
You can filter the overview to display only the apps that are marked for deletion. Read more about how we mark apps for deletion [here](/developerportal/deploy/mendix-cloud-deploy/#projects-deletion).
57
+
You can filter the overview to display only the apps that are marked for deletion. Read more about how we mark apps for deletion in the [Deletion of Unused Projects](/developerportal/deploy/mendix-cloud-deploy/#projects-deletion) section of *Mendix Cloud*.
58
58
59
59
Use the drop-down menu on the right side of the page to sort the apps by **Pinned**, **Recent Activity** or in alphabetical order of **App Name**.
60
60
@@ -89,7 +89,7 @@ The features in the navigation pane can also be accessed via APIs, enabling thir
89
89
90
90
### Pending Invitations {#pending-invitations}
91
91
92
-
If you are invited to collaborate on an app, the invitation will appear at the top of the **My Apps** page. You can accept or decline the invitation.
92
+
If you are invited to collaborate on an app, your invitation is displayed at the top of the **My Apps** page. You can accept or decline the invitation.
93
93
94
94
{{% alert color="info" %}}
95
95
You get an invitation only when someone invites you to an app from a different company. If someone invites you to an app from your company, you will be added automatically.
Copy file name to clipboardExpand all lines: content/en/docs/developerportal/app-insights/feedback.md
+39-25Lines changed: 39 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ aliases:
12
12
13
13
If your app uses the [Mendix Feedback](/appstore/modules/mendix-feedback/) module, users can report feedback to your team using the feedback widget in your app, and all their feedback goes to the **Feedback** page. **Feedback** enables your team to view all the feedback. It also allows team members with the right permissions to organize feedback and add feedback manually.
14
14
15
-
You can access the **Feedback** page by selecting your app in [Apps](https://sprintr.home.mendix.com/) and then clicking **Feedback** in the navigation pane.
15
+
You can access the **Feedback** page by selecting your app in [Apps](https://sprintr.home.mendix.com/), then clicking **Feedback** in the navigation pane.
16
16
17
17
The **Feedback** page contains two tabs: [Inbox](#inbox) and [Archive](#archive).
18
18
@@ -26,23 +26,32 @@ On top of getting a notification in the Mendix Portal, Scrum Masters of your tea
26
26
27
27
#### What Happens to the User
28
28
29
-
After a user reports feedback in the app using the feedback widget, they get an email with a link to their submitted feedback. When the user opens the link, a page opens and shows their feedback details. See the table below:
29
+
After a user reports feedback in the app using the feedback widget, they get an email with a link to their submitted feedback. When the user opens the link, a page opens and shows their feedback details.
30
30
31
-
| What a User Can See on the Page | What a User Cannot See on the Page |
| Name of the feedback they submitted | Metadata |
34
-
| Description of the feedback they wrote | Summary of the feedback that your team wrote |
35
-
| Screenshot (if they uploaded a screenshot for the feedback) | To which team member the feedback is assigned |
36
-
| Current status of the feedback | Tags that are assigned to the feedback |
37
-
| Submission date | Other feedback items that are associated with this feedback |
38
-
| Last activity on the feedback | Attachments that you team uploaded for this feedback |
39
-
|| Team comments on this feedback |
31
+
##### What a User Can See on the Page
32
+
33
+
* Name of the feedback they submitted
34
+
* Description of the feedback they wrote
35
+
* Screenshot (if they uploaded a screenshot for the feedback)
36
+
* Current status of the feedback
37
+
* Submission date
38
+
* Last activity on the feedback
39
+
40
+
##### What a User Can See on the Page
41
+
42
+
* Metadata
43
+
* Summary of the feedback that your team wrote
44
+
* To which team member the feedback is assigned
45
+
* Tags that are assigned to the feedback
46
+
* Other feedback items that are associated with this feedback
47
+
* Attachments that you team uploaded for this feedback
48
+
* Team comments on this feedback
40
49
41
50
This page also has a message feature for the user to communicate with your team directly. Users can upload images in the messages. When the user posts a message, the assigned team member receives an email. When there is a reply from your team, the user gets an email notification.
42
51
43
-
{{% alert color="warning" %}}Do not share the link to feedback details with someone unless it is necessary. Anyone who has this link can access the feedback details, including the title and the description of the feedback as well as the screenshot if there is one.{{% /alert %}}
52
+
{{% alert color="warning" %}}Do not share the link to feedback details with someone unless it is necessary. Anyone who has this link can access the feedback details, including the title and the description of the feedback, as well as the screenshot if there is one.{{% /alert %}}
44
53
45
-
If the user does not want to receive notifications anymore, they can clear the checkbox for the notification on the page, as shown in the image below:
54
+
If the user does not want to receive notifications anymore, they can clear the checkbox for the notification on the page.
@@ -73,11 +82,16 @@ Clicking the filter bar opens the **Filter by** side panel. In this side panel,
73
82
74
83
### Organizing Feedback in Inbox
75
84
76
-
If your [role](/developerportal/general/app-roles/) has the permission that **Can edit ‘Stories, Documents and Feedback'**, you can also organize feedback items.
85
+
If your [role](/developerportal/general/app-roles/) has the **Can edit ‘Stories, Documents and Feedback'** permission, you can also organize feedback items.
77
86
78
87
You can add new feedback manually yourself.
79
88
80
-
To manually add feedback, click **Create new feedback** (if there is not any feedback yet on the **Inbox** tab) or click **Add feedback** (if there is already feedback on the **Inbox** tab), and then fill in the **Subject**, **Description**, and **Submitter Email** fields, and optionally **Upload Screenshots** in the **New Feedback** dialog box.
89
+
To manually add feedback:
90
+
91
+
* Click **Create new feedback** if there is not any feedback yet in the **Inbox** tab.
92
+
* Click **Add feedback** if there is already feedback in the **Inbox** tab.
93
+
94
+
Then, fill in the **Subject**, **Description**, and **Submitter Email** fields, and optionally **Upload Screenshots** in the **New Feedback** dialog box.
81
95
82
96
If you select feedback, you can see the following items:
83
97
@@ -125,18 +139,18 @@ On the [Inbox](#inbox) and [Archive](#archive) tabs, you can open feedback by cl
125
139
126
140
### Feedback Tab {#feedback}
127
141
128
-
{{% alert color="info" %}}If your [role](/developerportal/general/app-roles/) has the permission that **Can edit ‘Stories, Documents and Feedback'**, you can edit the feedback details on the **Feedback** tab.{{% /alert %}}
142
+
{{% alert color="info" %}}If your [role](/developerportal/general/app-roles/) has the **Can edit ‘Stories, Documents and Feedback'** permission, you can edit the feedback details on the **Feedback** tab.{{% /alert %}}
* {{% icon name="view-off" %}} – Clicking the button to start receiving [notifications](#notifications) for this feedback. You also automatically start receiving notifications for this feedback whenever you respond to the reporter of the feedback or leave a comment for your team in the **Communications** section within the feedback.
134
-
* {{% icon name="view" %}} – Clicking the button to stop receiving notifications for this feedback.
135
-
***Copy Link** ({{% icon name="hyperlink" %}}) – Clicking this button copies the URL to the feedback. You can send the URL to other people.
136
-
***More Options** ({{% icon name="three-dots-menu-horizontal" %}}) – Clicking the button opens a menu with the following items:
137
-
***Move** – Clicking this button moves the feedback to any other app of which you are a member. Whenever you move feedback, you also move all linked feedback. If you only want to move one feedback item, you need to unlink the feedback from the group first.
* {{% icon name="view-off" %}} – Click this button to start receiving [notifications](#notifications) for this feedback. You also automatically start receiving notifications for this feedback whenever you respond to the reporter of the feedback or leave a comment for your team in the **Communications** section within the feedback.
148
+
* {{% icon name="view" %}} – Click this button to stop receiving notifications for this feedback.
149
+
***Copy Link** ({{% icon name="hyperlink" %}}) – Click this button to copy the URL to the feedback. You can send the URL to other people.
150
+
***More Options** ({{% icon name="three-dots-menu-horizontal" %}}) – Click this button to open a menu with the following items:
151
+
***Move** – Click this button to move the feedback to any other app of which you are a member. Whenever you move feedback, you also move all linked feedback. If you only want to move one feedback item, you need to unlink the feedback from the group first.
138
152
***Create Story** – If your app is connected to [Epics](/developerportal/project-management/epics/) or [Jira](/developerportal/project-management/jira-connector/), clicking this button converts the feedback to a story on the designated board in Epics or Jira. Once the story is created, clicking this button brings you to the story on the board right away.
139
-
***Delete** – Clicking this button removes the feedback permanently from **Feedback**. The result is irreversible.
153
+
***Delete** – Click this button to removee the feedback permanently from **Feedback**. The result is irreversible.
140
154
141
155
***Last activity** – This shows when the last edit to the feedback was made.
142
156
@@ -159,7 +173,7 @@ The **Feedback** tab shows the following items:
159
173
***Metadata** – This shows a list of metadata of the feedback.
160
174
161
175
***Active Userrole** – This is the user role the reporter has in your app
162
-
***Active form**– This is the page from which the reporter sent the feedback
176
+
***Active form**– This is the page from which the reporter sent the feedback
163
177
***Screen Size** – This is the dimensions of the reporter’s screen in pixels
164
178
***Browser** – This is the version of the browser the reporter was using
165
179
***Application location** – This is the URL of the page from which the reporter sent the feedback
@@ -229,4 +243,4 @@ You can receive a notification when new feedback lands in **Inbox** or when a re
229
243
230
244
### Receiving Notifications for an Individual Feedback Item {#notifications-individual-feedback}
231
245
232
-
You can also just receive notifications for an individual feedback item. Set this up by clicking the {{% icon name="view-off" %}} icon on the upper-right corner of the [Feedback](#feedback) tab after you open the feedback. You also automatically start receiving notifications for an individual feedback item once you [respond to the reporter](#contact-reporter) of the feedback or leave a comment for your team in the **Communications** section within the feedback.
246
+
You can also just receive notifications for an individual feedback item. Set this up by clicking the {{% icon name="view-off" %}} icon in the upper-right corner of the [Feedback](#feedback) tab after you open the feedback. You also automatically start receiving notifications for an individual feedback item once you [respond to the reporter](#contact-reporter) of the feedback or leave a comment for your team in the **Communications** section within the feedback.
0 commit comments