As an objects admin, I want to be able to allow my users to upload files to a specific folder in Doc and Media

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Objects
• Labels:
  • bravo_q2
  • fc_22_04
  • fc_22_05
  • good-to-go
  • low-code-milestone
  • now-dxp-latam
  • qa_test_mapped
  • team-bravo
• Epic Link: Objects Fields

Context:

Differently from when the files are scoped by each entry, where only the users who have access to the entry itself have access to those files, there are use cases where the user needs to upload files into an application, but that those files become available for be managed by the portal admins, not only by accessing the context of that entry specifically. Allowing managers to evaluate the files together instead of individually.

Out of Scope:

• Map Form fields (upload field) when objects is the storage type to this new field;

Design Deliverables

Mockup Link

Acceptance Criteria

1 - Given a power user,
when adding an attachment field in my objects structure,
then I must be able define the attachment to only request uploads from Users

2 - Given a power user,
when adding an attachment that only request uploads from users,
then I must be able to define if those files will be visible in Documents and Media

3 - Given a user from the previous AC,
when defing that the files are visible in D&M,
then the default name of the folder should be the name of the object in the "root" folder

4 - Given a user from the previous AC,
when defing that the files are visible in D&M,
then I must be able to write the path defining in which folder they will be saved dinamically

• If the folder does not exist, the system should create the folder automatically
• The folder will be always created in the context of the scope of the object, virtual instance (company) or site (in each site)

5 - Given a user adding files in object entry,
when the attachment is only requesting uploads from Users,
then I must only be able to upload files directly from their computers

• Same experience for the end user as the one scoped by entry

6 - Given a user adding files in object entry,
when the field has format and sizing configurations defined,
then the files I add/select must respect those configurations

7 - Given an user,
when seeing an object view with uploads,
then I must only be able to read the file name and extension

• DefaultRenderer (string)

8 - Given an user,
when editing or viewing an entry,
then I must only be able to download the existing file and also change the file

Definition of Done (DoD):

• All Acceptance Criteria were passed;
• Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
• Validated by QA and Product Manager;
• No critical bug related to Story scope (FP5);
• Make sure that all system documentation were updated (if necessary)

Ticket Updates

• The "Show Files in Documents and Media" setting will not be available for editing after the object is published;
• The "Storage Folder" setting will be always available for editing;
• If, to the user, it's assigned the "Object Definitions: Update" permission, automatically, they will be assigned to the "Add Folder" permission in order to have access to create folders for the Attachment field in Document Library; cc luiz.jardim, daniel.angotti;
• If an Attachment field is created, the system will create the defined folder automatically. Only (site) administrators will have privilege to see/update this folder;
• Users that have permission to add object entry will need to also have permission to add document to the specific folder the Attachment field is uploading files to, but this permission will not be granted automatically to such users; cc luiz.jardim, daniel.angotti;
• Users that have permission to add object entry will be able to add/upload documents without needing the specific Documents & Media permissions (via UI); cc luiz.jardim, daniel.angotti;
• For security reasons, guest users (if granted permission to add object entry) will be limited to a number of 100 entries by default they can submit to an object (this can be edited in System Settings > Other > Object); cc luiz.jardim, daniel.angotti
• For security reasons, guest users (if granted permission to add object entry) will be limited to upload files of a smaller file size of 25MB by default (this can be edited in System Settings > Other > Object); cc luiz.jardim, daniel.angotti;
• Files that are uploaded without submitting entry will be included in a temporary folder (and assigned a temporary name), which is sanitized (out of the box and provided by DXP's frameworks) by DXP frequently and defined by portal properties (sanitization is not part of this story's scope). Only files submitted are persisted to their defined folders; cc luiz.jardim, daniel.angotti;
• The actual validation folder name structure is (defined by the Portal properties dl.name.blacklist, dl.char.blacklist and dl.char.last.blacklist):
  • The folder name cannot be blank or a reserved word such as nul, con, prn, aux, nul, com1, com2, com3, com4, com5, com6, com7, com8, com9, lpt1, lpt2, lpt3, lpt4, lpt5, lpt6, lpt7, lpt8, lpt9.
  • The folder name cannot end with the following characters: .
  • The folder name cannot contain the following invalid characters: \ // : * ? " < > | ../ /..