PROD-I-329 Have Required Fields in the AL

Hi All,

Invesco would like us to consider having required fields when content is uploaded to the AL. As a content manager, I completely get this business case.

1) No content will be in the Default collection
2) Content MUST be assigned to the correct Custom Field or Collection on import

I know workflow can assist with the correct collection, but having feature parity between Projects and AL uploads would be lovely!

Created date : 2021-09-22

Votes : 0

Find more posts tagged with

Future consideration

Status: Future consideration

Comments

Bharath S

@sathish s Is this still relevant in V2?

sathish s

@Bharath S Actually it is not related to UX. The customer is expecting the collections and custom fields to be made mandatory so that when the content is created or imported, those fields has to be mandatorily provided by the user. Making these fields mandatory will create difficulty for the users to invest more time in cautiously creating each and every field by filling the respective values. As of now making it mandatory for custom field is configurable in org settings and with respect to collections, if user does not map any collection it will be mapped to default collection. FYI @VISWA S