Which of the conditions require the use of a numbered list
This seems to be a tricked question, I can not figured how this is not correct
[Image Removed by Moderator]
This is the reference from Planual:
[Image removed by Moderator]
Hey, you're almost done with Level 2. Congratulations. When we use a numbered list, there are usually these reasons:
- With regular lists we're limited to 60 characters. Numbered lists allow us to have any size because we can swap out the generated number with the display name.
- We need to have list items that have duplicate display names
- In the CLASSIC dashboard, we want the user to add their own list items. This is not the case with UX since you can use forms.
Try to phrase your certification questions so we can point you in the right direction. Please don't post the questions on the Community, as others will need to work these questions out themselves. Thanks!
You got this.1
Hi, what do you mean by "not the case with UX"? If the users import items, it is very likely that they have a duplicated names list?0
Great question. Forms were introduced almost a year ago so users can add list items directly from the UX page. In the past, the only way to create list items was to use an action that created a list item on a numbered list. This is no longer the case with UX but you still have to do it with Classic.
There are two terrific benefits of using forms. The first is that you can create a list item to any list, numbered or regular. The second is that at the same time you create the list item you can also add all the properties assuming you've set up a system module that only uses that list.